Académique Documents
Professionnel Documents
Culture Documents
<Project Name>
<Student Name>
<Date>
Preface
This is a proposal for a Studio Project for partial fulfillment of the requirements of
the Master of Science degree in Computer Systems and Software Design at Jacksonville
This proposal provides the scope and context of the project to be undertaken. It
details the intended user group and the value that the system will have to them. It also
provides a schedule for the completion of the project, including a list of all the
The intended audience of this document is the graduate faculty of the department
so that they can determine whether the project should be approved as proposed, approved
< If a section is empty, for example, if there are no references, just enter “None” for its
body. If a section is not relevant, just enter “Not applicable” for its body. The document is
double spaced with pagination starting with the first page of section 1.0 as page 1. This
previous section is Roman numbered with the title page (not numbered) viewed as page i.
Each major section starts on a separate page.
Delete this bracketed instruction. Replace all other bracketed instructions with
appropriate text. Correct the footer to include your name. >
< This is the Purpose, Scope and Objectives of the project and the products to be
delivered and those excluded. It should contain a brief statement of the business or
system needs or hypothesis to be tested. Every project is designed to serve a need. In this
section you provide the background for the project. Overview who needs it and what is
the intended user group? What is the value of the product over the status quo? Where will
< The Literature Search Results may be included in section 1.1, if appropriate. No project
is developed in isolation. Either there are related projects available that can be used as
literature search is till yet to be done, summarize here what you have done and include a
statement “Further literature search will be conducted during the project. See schedule
for when a literature search document will be submitted to the committee.” >
< Sections 1.1 and 1.2 provide a high level view of the product or question to be
For a product, start with a clear concise description of the problem and include
specific objectives for a product that would solve the problem. You should discuss the
inputs of system — where does data originate, when and in what form? Discuss the
outputs of system — what information is needed, by whom and in what form. Provide an
projects to undertake than there are resources to undertake such projects. The Business
Case argues why this project should be the one the company should invest its resources to
should be done. Because something can be done is no reason that it should be done.
For a hypothesis to be tested, provide the background necessary for a person who
does not specialize in the application to understand what you are proposing. Discuss
work that has been done related to this. Indicate the type of experiment that you will be
conducting, what methods you will use to analyze the data, and the type of results that
Discuss what are you bringing to this project that will enable you to successfully
finish it? What previous courses are relevant? Do you know the language/platform? Do
you have domain knowledge (i.e., do you really understand the project or will you need
to have someone to answer questions about the context of the project)? In which case,
The most critical question facing the review committee is the level of the project.
Is it too simple for the time available? Experience has shown us that a more critical
aspect is whether the project can be successfully accomplished in the time available, that
is, the proposed project may be too large for the time period. Address this concern in this
proposal.
< List here any assumptions on which the project is based and imposed constraints such
1.4.Project Deliverables
Deliverables include
• <other documents>
• Exposition
Schedule
Item Date
Project Proposal <date>
Proposal Presentation <date range>
Software Project Management Plan <expected Studio I date>
<other studio I deliverables> Studio I
< Fill in the expected deliverables (see Studio Guide for suggestions). The actual dates
for the items marked “Studio I” will be provided in the SPMP. The actual dates for the
items marked “Studio II” will be provided in the Progress report. >
Budget
< Unless there are budget considerations beyond using your own or department
resources, enter “No budget required.” Otherwise include needed items. >
<Insert here any document referred to in the proposal. An example might be articles or
Web sites that you consulted during the literature search. >
<Insert here any technical word for which the meaning may not be known. Do not
assume that the readers have specialized knowledge in the application. Use a table format
< Insert here any people or entities such as the customer or technical staff that may need
to be involved. Specifically name these people. Each person must have been approached
prior to submission of the proposal and the exact relationship approved by him or her. >