System Proposal TemplateCSC 545 System Design When preparing a.docx

System Proposal Template
CSC 545 System Design
When preparing a systems proposal, systems analysts should
arrange the following items in order:
Ten Main Section of your System Proposal
1. Cover Letter
List of people who did the study and summarize the objectives
of the study are provided in your cover letter. Also, prearranged
time and place for oral presentation of the system proposal can
be included. Keep your cover letter concise (one page
maximum) and friendly.
2. Title Page of project
Include the name of the project, the names of the systems
analysis team members, and the date the proposal is submitted.
3. Table of Contents
If the proposal is very short (less than ten pages), you can omit
the table of contents since it is unnecessary on such a short
document. The purpose of your table of contents is to indicate
the contents of your proposal.
4. Executive Summary (including recommendations)
Usually, the executive summary is 250 to 375 words and can
answer the questions such as who, what, when, where, why and
how of the proposal. It should also include recommendation of
the system analysts since some people will only have time to
read the summary.
5. Outline of system study with appropriate documentation
Provides information about all the methods used in the study,
and who or what was studied.

6. Detailed results of systems study
The details what the system analyst has found out about the
system through all of the methods described are included in this
section. It also presents problems with the system
7. Systems alternatives (3 or 4 possible solutions)
The analyst will present two or three alternative solutions that
directly address the aforementioned problems. Each alternative
should be explored separately. Describe the costs and benefits
of each situation.
8. System’s analysts’ recommendations
After the systems analysis team has weighed the alternatives, it
will have a definite professional opinion about which solution is
most workable and best to solve the problem. It expresses the
recommended solution.
9. Summary
It is brief statement that mirrors the content of your executive
summary. It gives the objectives of the study and the
recommended solution. Also, it allows the analyst one more
chance to stress the project’s importance and feasibility along
with the value of the recommendations.
10. Appendices
It might include pertinent correspondence, a summary of phases
completed in the study, detailed graph for analyses purposes, or
even previously done systems studies.
Source: http://sampleproposal.net
Project Design Document Template
CSC 845
Project Title
[Give your project a short but meaningful title]

Problem Definition
[In one or two paragraphs, describe the problem that you are
trying to solve. For some projects in business this may be
something that needs to be fixed but for the class project, you
will be describing a brand new mobile application here. Mention
what you application is, why your application will help others
Issues
[What issues are you trying to solve. What are you trying to
accomplish? Mention why this product will be better than
existing ones.
Objectives
[State what the objective of your project is. A sample objective
is something like "upgrade the helpdesk telephone system by
December 31 to achieve average client wait times of no more
than two minutes". Objectives should be “SMART - Specific,
Measurable, Attainable/Achievable, Realistic, and Time-
bound”]
Requirements
[Here are some samples:
Business Requirements - “need to provide a 30 day turnaround
from application to approval.”
System Requirements - “24 by 7 system availability 6days per
week”
Reporting Requirements - “Report to produce a count of new
applications by state for each week by application type”
Data Requirements - “based on fields in the report, need
specific data elements from the following data sources “
Security Requirements - The need for securing the system to be

developed should be stated in section including levels of access
that can be granted e.g. “headquarters’ staff may have read only
access the following specific data measures”
Personnel Requirements - The following table should contain a
list of everyone who will play a role in the development of the
system.
Name
Organization
Role
CUW-MSIT
CUW-MSIT
CUW-MSIT
Constraints
[What limitations are there on this project – time, budget,
knowledge of team, etc. You may also want to mention the
boundaries of the project stating what will be included or what
will not be included]
1A Assignment
Answer the following based on your reading in Brooksheer
· Give an example of how efforts in the development of
software can pay dividends later in software maintenance.
· What is evolutionary prototyping?
· Explain how the lack of metrics for measuring certain
software properties affects the software engineering discipline.

2A Assignment
Answer the following based on your reading in Kendall:
· What are the five major project fundamentals?
· List the five criteria for systems project selection.
· What does COTS stand for?
· Define tangible costs and benefits. Give an example of each
one.
· When is break-even analysis useful?
· List the five steps in interview preparation.
· When are open-ended questions appropriate for use in
interviewing?
· When are closed questionsappropriate for use in interviewing?
· Define what is meant by diamond-shapped structure. When is
it useful to employ it in interviews?
3A Assignment
Answer the following questions based on your reading in
Kendall:
· List four reasonswhy the systems analyst would want to
sample data or select representative people to interview.
· What are the four steps to follow to design a good sample?
· List five steps to help the analyst observe the decision maker's
typical activities.
· Noting that the idea of STROBE originally came from the
world or film, what does the system analyst's role resemble?
· What four kinds of information is the analyst seeking through
prototyping?
· List the advantages and disadvantages of using prototyping
to replace the traditional SDLC.
· List four guidelines the analyst should observe in developing a
prototype.
· What are the four values that must be shared by the
development team and business customers when taking an agile
approach?

5A Assignment
· List six objectives the analyst pursues in designing system
output.
· Contrast external outputs with internal outputs produced by
the system. Remember to consider differences in external and
internal users.
· What output type is best if frequest updates are a necessity?
· What kind of output is desirable if many readers will be
reading, storing, and reviewing output over a period of years?
· What are five ways the analyst can avoid biasing output?
· List the four guidelines for good form design.
· What is a specialty form? What are some disadvantages of
using specialty forms?
· What are dynamic Web pages?
· What are three-dimensional Web pages?
· How does Ajax improve a Web page that changes based on
user actions?
6A Assignment
· Explain how fit among the HCI elements of the human, the
computer, and the tasks to be performed leads to performance
and well-being.
· What is meant by the word well-being when used in an HCI
approach?
· What are the five objectives for designing user interfaces?
· Define graphical user interfaces. What is the key difficulty
they present for programmers?
· What are the four primary objectives of data entry?
· Define the term simple sequence code.
· What are changable data?
· What are differentiation data?

7A Structured Walkthrough
Design a structured walkthrough as part of the quality assurance
measures for one of the following:
· a new online course
· a website designed to provide members of a church with
information
· a website designed to provide members of the larger
community with information about a church
· the class registration process at a university
· your scenarion application project from weeks 2-4
Discuss
· the format
· how a structured walkthrough would be initiated
· participants and their respective roles
· what form the output would have and how it would be utilized
Scenario Application Project
Overview:
This project is based on the seven steps of the SDLC from
Kendall and Kendall. You will need to pick one of the four
scenarios below. Note that not all of the seven steps will be
assigned in this class.
Project Goal:
Gain practical experience with the System Design process to
support the theoretical knowledge gained during the course.
Scenario 1:Congratulations on being brought in as a consultant
here at Amazing Apple Applications. Your job is to come up
with an idea for the next “killer” iPhone Application. Once you
have the idea for the application, you will need to do parts of
each of the seven SDLC design steps. Since the length of your

engagement with our company is only 8 weeks, you will not
need to do any actual coding or testing of the application.
https://developer.apple.com/library/ios/documentation/Miscella
neous/Conceptual/iPhoneOSTechOverview/Introduction/Introdu
ction.html#//apple_ref/doc/uid/TP40007898
Sample Applications: http://www.apple.com/itunes/charts/paid-
apps/http://www.apple.com/itunes/charts/free-apps/
here at Better Blackberry Bloatware. Your job is to come up
with an idea for the next “killer” Blackberry Application. Once
you have the idea for the application, you will need to do parts
of each of the seven SDLC design steps. Since the length of
your engagement with our company is only 8 weeks, you will
not need to do any actual coding or testing of the application.
http://na.blackberry.com/eng/developers/
Sample Applications:
http://na.blackberry.com/eng/builtforblackberry/
here at Wonderful Windows Mobile Widgets. Your job is to
come up with an idea for the next “killer” Windows Mobile
Application. Once you have the idea for the application, you
will need to do parts of each of the seven SDLC design steps.
Since the length of your engagement with our company is only 8
weeks, you will not need to do any actual coding or testing of
the application.
https://dev.windows.com/en-us/
Sample Applications: https://www.microsoft.com/en-
us/store/apps/windows-phone
Scenario 4:
Congratulations on being brought in as a consultant here at
Awesome Android Apps. Your job is to come up with an idea
for the next “killer” Android Application. Once you have the
idea for the application, you will need to do parts of each of the
seven SDLC design steps. Since the length of your engagement
with our company is only 8 weeks, you will not need to do any
actual coding or testing of the application.

http://developer.android.com/index.html
Sample Applications:
http://www.android.com/market/#app=com.joelapenna.foursquar
ed
Step 1 - Identifying Problems, Opportunities, and Objectives
(week 2)
· Activity:
· Interview someone with an iPhone, Blackberry, or Windows
Mobile device and find out if there is an application they would
like to see developed. If this is not possible, think of your own
idea for a good mobile application. Note that it does not matter
for this project if a similar application already exists. We are
going to ignore whether or not competing products exist.
· Summarizing the knowledge obtained.
· Estimate the scope of the project (number of people multiplied
by the number of estimated hours).
· Document the results (see attached Project Design template)
· Output:
· Feasibility report containing problem definition and objective
summaries from which management can make a decision on
whether to proceed with the proposed project
Step 2 - Determining Human Information Requirements (week
3)
· Activity:
· Interviewing
· Sampling and investing hard data
· Questionnaires
· Observe the decision maker’s behavior and environment
· Prototyping
· Learn the who, what, where, when, how, and why of the
current system
· Output:
· Analyst understands how users accomplish their work when
interacting with a computer; and begin to know how to make the

new system more useful and usable. The analyst should also
know the business functions and have complete information on
the people, goals, data and procedure involved
· For this course project, research what similar applications
already exist.
Step 3 - Analyzing System Needs (week 4)
· Activity:
· Create data flow diagrams
· Complete the data dictionary
· Analyze the structured decisions made
· Prepare and present the system proposal
· Output:
· Recommendation on what, if anything, should be done
Step 4 - Designing the Recommended System
· Activity:
· Design procedures for data entry
· Design the human-computer interface
· Design system controls
· Design files and/or database
· Design backup procedures
· Output
· Model of the actual system
Step 5 - Developing and Documenting Software
· Activity:
· System analyst works with programmers to develop any
original software
· Works with users to develop effective documentation
· Programmers design, code, and remove syntactical errors from
computer programs
· Document software with help files, procedure manuals, and
Web sites with Frequently Asked Questions
· Output:
· Computer programs
· System documentation
Step 6 - Testing and Maintaining the System
· Activity:

· Test the information system
· System maintenance
· Maintenance documentation
· Output:
· Problems, if any
· Updated programs
· Documentation
Step 7 - Implementing and Evaluating the System
· Activity:
· Train users
· Analyst plans smooth conversion from old system to new
system
· Review and evaluate system
· Output:
· Trained personnel
· Installed system
2B Project Step 1
Step 1 - Identifying Problems, Opportunities, and Objectives
Activity:
· Interview someone with an iPhone, Blackberry, Android, or
Windows Mobile device and find out if there is an application
they would like to see developed. If this is not possible, think of
your own idea for a good mobile application. Note that it does
not matter for this project if a similar application already exists.
We are going to ignore whether or not competing products exist.
· Summarize the knowledge obtained.

· Estimate the scope of the project (number of people multiplied
by the number of estimated hours).
· Document the results (see attached Project Design template)
Output: Feasibility report containing problem definition
and objective summaries from which management can make a
decision on whether to proceed with the proposed project.
Project_Design_Template.rtf
3B Project Step 2
Step 2 - Determining Human Information Requirements (week
3)
· Activity:
· Interviewing
· Sampling and investing hard data
· Questionnaires
· Observe the decision maker’s behavior and environment
· Prototyping
· Learn the who, what, where, when, how, and why of the
current system
· Output:
· Analyst understands how users accomplish their work when
interacting with a computer; and begin to know how to make the
new system more useful and usable. The analyst should also
know the business functions and have complete information on
the people, goals, data and procedure involved
· For this course project, research what similar applications
already exist.
· What features do they include that you didn't think of?
· What features do you offer that others don't?
· Will you change your design based on what you see in other
similar applications?
· Make a mock up drawing of what your application screen
might look like. This can be done on MS Paint, iPlotz, MS
Word, etc. Download iPlotz from
http://iplotz.com/whatisiPlotz.php.

4A Project Step 3
Step 3 - Analyzing System Needs (week 4)
· Activity:
· Create data flow diagrams
· Complete the data dictionary
· Analyze the structured decisions made
· Prepare and present the system proposal
· Output:
· Recommendation on what, if anything, should be done
System_Proposal_Template.doc
Text book Links:
Brooksheer:
https://eembdersler.files.wordpress.com/2010/09/computer_scie
nce_an_overview_11th1.pdf

System Proposal TemplateCSC 545 System Design When preparing a.docx

More Related Content

Similar to System Proposal TemplateCSC 545 System Design When preparing a.docx (20)

More from ssuserf9c51d (20)

Recently uploaded (20)

System Proposal TemplateCSC 545 System Design When preparing a.docx