Table of Contents
Purpose and Description
Scope and Limitations
II. Design and Methodology
Schedule and Timeline
Project Teams and Responsibilities
Systems Analysis and Design
Data Flow diagram
Interview Result and Observation
Documentation (Pictures during interview and project making)
A. Project Context
This will be the general overview of the project
Introduce your project by capturing the reader’s interest in the first paragraph. Discuss the problem background and why you decided to develop your project. What’s wrong with the traditional method?
B. Purpose and Description
Provide a short description of the project being specified and its purpose, including relevant benefits (or beneficiaries) What is your main purpose in doing the project?
Who is/are your target clients, end user/s or beneficiaries of the project?
Detailed statements or elaboration of the project goal and should be clearly stated and logically presented Present the sub-objectives in a logical sequence from factual to analytical along mutually exclusive dimensions (no overlaps) with the exclusion of the overview, expected conclusions, implications and recommendations of the project. Specific objectives should be SMART. Specific, Measurable, Achievable, Realistic and Time-bounded.
D. Scope and Limitations
Discuss here the boundaries of the study and those likely part of the study researcher/s do not intend to accomplish (or what the design of the study inherently will not allow) Describe any global limitations or constraints that have a significant impact on the design of the system/software (and describe the associated impact). Describe any items or issues that will limit the options available to the developers. These might include: corporate or regulatory policies; hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards Limitations that are not readily apparent at the start of the research project may develop or become apparent as the study progresses. In any case, limitations should not be considered alibis or excuses; they are simply factors or conditions that help the reader get a truer sense of what the study results mean and how widely they can be generalized. While all project have some inherent limitations, you should address only those that may have a significant effect on your particular study.
II. DESIGN AND METHODOLOGY
A. Development Model
This may include the following models: Conventional waterfall type, Incremental, Throw-away, prototyping, Evolutionary prototyping and any other model which is most appropriate to the kind of research project being undertaken.
B. Development Approach
This may include either Top down or Bottom-up approach of development.
C. Schedule and Timeline
It may contain Gantt Chart, Activity Chart, Critical Path Analysis and other scheduling techniques that will list the activities to be done in order to achieve the objective. Usually it includes the phases and its sub-phase of the systems development life cycle.
D. Project Teams and Responsibilities
It should contain the assignments of modules and activities to be done by each team member.
E. Systems Analysis and Design
System analysis focuses on system requirement description; defines the system functional requirements, and requirement specification of the proposed system. System design provides the technical specification and construction of the solution for the requirements identified during the system analysis phase of the research/project. This should include...
Please join StudyMode to read the full document