TABLE OF CONTENTS

Chapter 1. The Project

A. IntroductionB. ObjectivesC. Scope and BoundaryD. Feasibility StudiesE. Planning ActivitiesF. Composition of the TeamG. Responsibility Area/s of Each MemberH. Schedule of Activities

i. Work Breakdown Structureii. Gantt Chart / Milestonesiii. PERT Diagram

Chapter 2. The CompanyA. Background and HistoryB. Organizational ChartC. Contact Person/s, their position/designation and their contact numbers/addresses (mobile

no., tel, fax, email, etc)

Chapter 3. The Present SystemA. Detailed Description of the SystemB. Statement of the ProblemC. Objectives of the System

i. General Objective/sii. Specific Objective/s

D. Scope and Limitations of the System

Chapter 4. Analysis of the Current SystemA. Data Gathering Techniques Used (chap.5 for guide)

i. Sources of Informationii. Instruments Used in the Survey, Sample Questionnaires, Interview Questions,

Communication Letters, Documentation of the Observation, etc.B. Consolidated Tables, Findings, Analysis of Information Gathered, Summary of Information, etc.

(output of A)C. Business ActivitiesD. LOGICAL Data Flow Diagram (chap. 7)E. USE CASE – present graphical overview of the functionality provided by the current system. (Over-all

to Sub-System) (Chap. 2)

Chapter 5. The Proposed SystemA. Comparison of the Present and Proposed System in Terms of

i. Objectivesii. Advantages and Disadvantages iii. Technical, Operational, and Economic Justification

B. Development Cost (chap. 3)C. Technical Specifications

i. Proposed Data Flow Diagrams (chap. 7 )a. LOGICAL DFDb. PHYSICAL DFD

ii. Process Specifications (Apply at least 3 or more techniques that will specify specific process or task) (Chap. 9)

decision tables

structured English (favored technique of most systems analysts)

HIPO

Decision Tree

Nassi–Shneiderman diagram

iii. Data Dictionary (chap. 8)iv. Database Specifications (Chap.13)

1. Enhanced - Entity Relationship Diagram2. Normalization of Tables3. Database Structure

v. Input/Output Forms (Must Provide Sample data and transactions) (Chapter 11/12/15)vi. Screen Designs (Chapter 11/12)vii. Object-Oriented Systems Analysis and Design Using UML (chapter 10)

1. Structural diagrams - Used to describe the relation between classes

a. Class diagrams

b. Object diagrams

c. Component diagrams

d. Deployment diagrams

2. Behavior diagrams - Used to describe the interaction between people (actors) and a use case (how the actors use the system)

a. Use case diagrams

b. Sequence diagrams

c. Collaboration diagrams

d. Statechart diagrams

e. Activity diagrams

Chapter 6. Summary and ConclusionsA. Summary of Changes, and ImprovementsB. Constraints of the New System

Chapter 7. Activities in the Next Stage of DevelopmentA. Testing PlansB. Maintenance Plans (recommendations for upgrades and / or updates)C. Security Plans

Appendices

A. Start-up Procedurei. Minimum Hardware and Software Specificationsii. Installation Procedure

B. Initial Entry / Accessi. Levels of Usersii. File/s to Open iii. Default Password (for each level of user) / How to Change Password

C. List of Error MessagesF. Curriculum Vitae of Developers