Systems Analysis Final Paper Template Document
1. Introduction
Brief description of your project to an audience of those approving your project.
2. Executive Summary
Summarize your project and include the triple constraints (Cost, time, resources) and anything that an executive that is short on time needs to know to understand your project.
3. Application Context
a) Project objectives and benefits:
What is the purpose and why would someone do this project. Objectives are specific measures to evaluate your success/failure against at the end of the project.
c) Exclusions- Document all project exclusions.
d) Constraints: Document constraints to the project. A constraint is any limitation or restraint that will affect the performance of the project or a process.
e) Assumptions: Document project assumptions. Assumptions are factors that are considered to be true, real, or certain without proof or demonstration.
f) Deliverables: Include a listing of all project deliverables. Identify project specific milestones beyond the standard project deliverables. This may be in the format of a milestone chart or Work Breakdown Structure (WBS) showing each major deliverable by phase and the date the deliverable is due to be completed.
4. Functional Requirements (use the drawing tools from the text)
a) This is a high-level representation of the business program or service. It shows who is interacting externally with the program or service and what information is being exchanged.
As Is Flow-The purpose of the As Is Flow is to depict the current process in place and describe the interaction among processes from start to finish.
c) To Be Flow- The purpose of To Be Flow is to depict the re-design process of the As Is Flow. It describes the interaction among processes from start to finish.
d) Gap Analysis- After the completion of the As Is and To Be flows, it is critical to go back and evaluate the flows to identify any gaps between the processes. Gaps between the As Is and To Be represent requirements.
5. Environmental Requirements

a) Database Design-Logical If designing a system do a logical design of your system and the relationships.
Data Definition Diagram (See text)
c) Data Dictionary (See text)
d) Security Requirements- The purpose of this section is to specify security requirements for the project if applicable.
e) Architecture- Specific architecture requirements for the project.
f) Infrastructure- Specific infrastructure requirements for the project.
6. Other Requirements
a) Estimate a cost for your project in detail. Also identify the ROI for your project to identify a payback period.
Training budget and how it will be accomplished.
c) Make or Buy Decision: Are you going to purchase software/service or do it in-house.
d) Resource requirements- identify the resources that you need to accomplish your project. Do you have them? Will you purchase them?
7. Time Schedule
a) Gantt chart to outline a schedule of your project with tasks, dates, predecessors and resources identified.
8. Potential Risks
a) Identify risks in your project and their severity and what you are going to do about them.
A Risk Matrix would help define these.
9. Future Changes
a) Identify changes that you are going to make in the future.
10. Glossary
11. References