Sie sind auf Seite 1von 5

<<TITLE OF THE PROJECT>>

In Partial Fulfillment of the Requirements in Systems Analysis and Design with Prototyping

Submitted by: <<Students Name>> <<Students Name>> <<Students Name>> <<Students Name>>

Submitted to: << Subject Teacher >>

2nd Semester, S. Y. 2011 2012

OUTLINE OF DOCUMENTATION Systems Analysis, Design and Prototyping I. INTRODUCTION A. Company Background B. Problem Definition 1. Statement of the Problem 2. System Objectives 3. System Scope and Limitation FEASIBILITY STUDY A. Overview of the Existing System B. User Overview C. Data Flow Diagram D. SWOT RECOMMENDED SOLUTION A. Overview of the Recommended System B. System Design 1. System Framework 2. User Overview 3. Data Flow Diagram 4. Minimum System Requirement

II.

III.

APPENDICES A. Distribution of Developmental Schedule Gantt Chart PERT B. Fact-Finding Techniques Interview Report Observation Report Gathered Documents Analysis of Survey Form (if any) C. Screen Shots D. Sample Reports E. Users Manual Product Overview Minimum System Requirement Installation Procedure How to Use Error Messages and Recovery Procedure F. Students Profile

OUTLINE OF DOCUMENTATION Systems Analysis, Design and Prototyping I. INTRODUCTION A. Company Background - History of the Company - Products / Service and Clients - Organizational Charts / Divisions and Departments B. Problem Definition 1. Statement of the Problem State this in question format - General Statement of the Problem (This states the main problem as identified in the feasibility study) - Specific Statement of the Problem (This states specific problems. Each question should be explained further in subsequent paragraph(s)) 2. System Objectives - General Objective (This is the main goal to be achieved by the system) - Specific Objectives (This includes specific goals of the system. Each objective should be explained further in subsequent paragraph(s)) 3. System Scope and Limitation - State the boundary of the system II. FEASIBILITY STUDY A. Overview of the Existing System This is a narrative description of what the existing system is all about. B. User Overview Identify all possible users and the roles each of them play pertaining to how they interact with the system. Example: User1 : Student User2 : Cashier User3 : Dean C. Data Flow Diagram Include Context, Diagram 0 and Child diagrams with explanation for each figure

D. SWOT (Strength, Weakness, Opportunities, and Threats)


After careful study of the existing system, this section should state the strength weaknesses, opportunities, and threats of the existing system and organization. For each characteristic, explanation should follow. III. RECOMMENDED SOLUTION

A. Overview of the Proposed System This is a narrative description of what the proposed system is all about. B. System Design 1. User Overview Identify all possible users and the roles each of them play with regards as they interact with the system. User1 : Student User2 : Cashier User3 : Dean 2. Data Flow Diagram Include Context, Diagram 0 and Child diagrams with explanation for each figure 3. Minimum System Requirement (This includes all hardware and software requirement needed to develop the proposed system) APPENDICES A. Distribution of Developmental Schedule Gantt Chart (from SADP1 to SADP2)

ACTIVITIES Activity 1 Activity 1 Activity 1 Activity 1

Nov 2011

Dec 2011

Jan 2012

February 2012

March 2012

PERT The activities in the Gantt chart should be converted into its equivalent PERT diagram B. Fact-Finding Techniques Interview Report All Interviews conducted should have the following as summary Date: Time: Venue: Interviewee: (Name and Position)

Interviewer: Summary: - (list of interview results) Observation Report Each observation conducted should be presented in the format given below; Date: Time: Entity to be Observed (Person, Location, Procedure, etc) Observer: Summary: - (list of observation results) Gathered Documents Copy of sample documents should be placed here. Analysis of Survey Form (if any) If survey / questionnaire was designed, copy of a blank survey form should be included here, as well as the summary and interpretation of the results.

C. Users Manual Product Overview Description of the Finished System is placed here. It includes the features and capabilities of the system. Minimum System Requirement Hardware and Software requirement necessary for the system to be installed in the company Installation Procedure Step by step instruction to install the system How to Use For each user, create at step by step procedure on how to use the system. Include screen shots as you specify the steps needed. Error Messages and Recovery Procedure For each module developed or as per user, identify all error message and recovery procedure. D. Students Profile - Resume of all member of the group. (With picture and signature)