SAD/SDD PROJECT DOCUMENTATION FORMAT

I. TITLE PAGE

INSTITUTE OF TECHNOLOGY
PUP STA. MESA MANILA
{in bold characters, font size 16}

<PROJECT TITLE>
{in bold characters, underlined, font size 14}

A Project Presented to
COMPUTER/MANAGEMENT Department

In Partial Fulfillment of the Requirements for

-----{state the specific subject/course}

by:

<lastname, firstname, m.i. of the proponent 1>

<Date of Submission>
1.0 ADVISER’S RECOMMENDATION SHEET

INSTITUTE OF TECHNOLOGY
STA. MESA, MANILA
{in bold characters, font size 16}

ADVISER’S RECOMMENDATION SHEET

{in bold characters, underlined, font size 14}

This Project Entitled

<Project Title>
{in bold characters, font size 14}

by:

<lastname, firstname, m.i. of the proponent 1>

And Submitted in Partial Fulfillment of the Requirements of

-----( state the specific subject/course ) has been
Examined and is Recommended for Acceptance and Approval

<Project Adviser’s Signature>

<Project Adviser’s Name>
<Adviser>

PANEL’S APPROVAL SHEET

INSTITUTE OF TECHNOLOGY
STA. MESA, MANILA
{in bold characters, font size 16}

PANEL’S APPROVAL SHEET

{in bold characters, underlined, font size 14}

This Project Entitled

<Project Title>
{in bold characters, font size 14}

by:

<lastname, firstname, m.i. of the proponent 1>

after having been presented is hereby approved

by the following members of the panel

<Panelist 1’s Signature> <Panelist 2’s Signature>

Panelist Panelist

<Lead Panelist’s Signature>

Lead Panelist
CHAIR’S ACCEPTANCE SHEET

INSTITUTE OF TECHNOLOGY
STA. MESA, MANILA
{in bold characters, font size 16}

CHAIR’S ACCEPTANCE SHEET

{in bold characters, underlined, font size 14}

This Project Entitled

<Project Title>
{in bold characters, font size 14}

After having been Recommended and Approved is hereby

Accepted by the COMPUTER/MANAGEMENT
Department of
Institute of Technology
Sta. Mesa, Manial

<Chair’s Signature>
<Chair’s Name>
Department Chair

2.0 TABLE OF CONTENTS

TABLE OF CONTENTS
{in bold characters, font size 14}

1.0 INTRODUCTION
1.1 Background of the Study 1-1
1–1
1.2 Statement of the Problem
1 – 2.

--------------------------------------

7.0 LIST OF APPENDICES

Appendix <Appendix number>

<appendix caption>
3.0 ACKNOWLEDGEMENT

This section contains expressions of appreciation for assistance and

guidance. This should be expressed SIMPLY and TACTFULLY and should fit
into a single page only. See the attached sample for your reference.

4.0 REVIEW OF RELATED STUDIES

4.1 General Literature Survey (resources according to your major or area of

study)
4.2 Personal Interviews, Survey, Questionnaires

Example:

A. General Literature Survey

A.1 Computer Assisted Instruction

Computer Assisted Instruction (CAI) refers to the use of

----------------------------

A.2 Intelligent Computer Aided Instruction

---------------------------------------------
 THESIS PROGRAM
MAIN DOCUMENTATION OUTLINE

Title Page
Adviser’s Recommendation Sheet
Chair’s Acceptance Sheet
Panel’s Approval Sheet
Table of Contents
List of Appendices
List of Tables
List of Figures
Acknowledgement

1.0 Introduction
1.1 Background of the Study
1.1.1 Symbol / Logo with description
1.1.2 Organizational Chart
1.1.3 History
1.1.4 Stake Holders
1.1.5 Location and Size
1.1.6 Mission
1.1.7 Vision
1.1.8 Objectives / Thrust / Services
1.2 Statement of the Problem
1.3 Cause and Effect Relationship
1.4 Alternative Solution
1.5 Objectives of the Study
1.5.1 General Objective
1.5.2 Specific Objectives
1.6 Significance of the Study
1.7 Scope and Limitation

2.0 Review of Related Studies

3.0 Methodology of the Study

4.0 Data Gathering Procedures and Output

5.0 Online System Flow

5.1 Decision Tree
5.2 System Flowchart
5.3 Context Diagram
5.4 Data Flow Diagram (LEVEL 1-3)
5.5 Use Case Diagram
5.6 Class Diagram

6.0 Documentation of the System Design

6.1 Description of the System
6.1.1 Definitions, Acronym and Abbreviations
6.1.2 Database Design
6.1.2.1 Database Schema
6.1.2.2 Data Dictionary
6.1.3 ERD Diagram (Entity Relationship)
6.1.4 Screen Design
6.1.4.1 Screen Inventory
6.1.4.2 Screen Transition Diagram
6.1.4.3 Screen Layout
 6.1.5 Reports Design
6.1.5.1 Reports Inventory
6.1.5.2 Reports Layout

6.2 Hardware Setup

6.3 Software and Application being used
6.4 Personnel

7.0 System Requirement Specification

7.1 Hardware Requirements
7.2 Software Requirements
7.3 Human Resource Requirements

8.0 Summary, Conclusion, and Recommendation

Appendices
Bibliography
Resource Person
Personal Vitae
THESIS PROGRAM
MAIN DOCUMENTATION GUIDELINES

1.0 All Thesis Documentation should adhere to the following standards:

a. Margins
Left Right Top Bottom
1.5” .75” 1.0” .75”

b. Font
Font Size Font Style
1. Text Bookman 12 Regular
Old Style *use Italics or single
underline in emphasizing
some text.
2. Heading or Bookman 14 Bold
Sub-headings Old Style

c. Alignment
- Justified

d. Spacing
- 1.5 Space

e. Footer

<Thesis Title> <Page # of #>

Line Black, 1 pt.

Text Bookman Old Style, size 11, Regular

f. Pages
- The page notation to be used is: <chapter/appendix letter – page
number>. Thus the first page for Chapter 2 is at 2-1, while the first page
of Appendix A is at A-1.
- There should be no page numbers for items before Chapter 1.

g. Sub-headings and text

All text and sub-headings should be in the following format as shown by an
example below:

2.0 REVIEW OF RELATED STUDIES

2.1 Computer – Assisted Instruction

Computer-Assisted Instruction (CAI) refers to the use of

computers to present drills, practice exercises, and tutorial
sequences to the student.

One extensive type of CAI system is the PLATO[RALS1993]. It

was developed by a group of engineers and educators in the
Computer-based Education Laboratory at the University of Illinois,
Urbane.
Stanford University operated CAI system to distribute instructional
computing to a number of centers throughout the United States.
 2.2 Intelligent Computer-Aided Instruction
Computer-Assisted Instruction (CAI) refers to the use of
computers to present drills, practice exercises, and tutorial
sequences to the student .

One extensive type of CAI system is the PLATO [RALS1993]. It

was developed by a group of engineers and educators in the
Computer-based Education Laboratory at the University of Illinois,
Urbane.

 Title Page
The first page of a thesis is the title page. The title page presents the title,
the full name of the writer, and the submission statement, which includes
the faculty or school, and the institution, the degree sought (granted), and
the month and year in which the degree is to be (or was) granted.

 Thesis Title
The title of the project should be concise as well as descriptive and
comprehensive. It is a distinctive name given to the project describing the
work scope in a specific context and indicates the content of the paper.

Generally, project titles begin with a noun or present participle form of an

action verb. IT is advisable to state the project titles in general forms in
order to bundle a number of problem areas. Humorous or catchy titles are
not appropriate and are discouraged.

 Adviser Recommendation Sheet

No final thesis documentation will be accepted if the thesis adviser does

not duly sign all copies.

The Adviser’s Recommendation Sheet provides space for the signature of

the adviser of the group indicating that he/she has examined and
recommended the thesis for acceptance and approval.

 Dean and Thesis Coordinator’s Acceptance Sheet

No final thesis documentation will be accepted if the dean and the thesis
coordinator do not duly sign all copies.

The college acceptance sheet provides space for the signature of the Dean
and Thesis Coordinator of the college indicating their acceptance of the
work.

 Panel’s Approval Sheet

No final thesis documentation will be accepted if all the defense panelists

do not duly sign all copies.

The approval sheet provides space for the signatures of the members of
the panel indicating their acceptance of the work.
  Table of Contents
Observe the following format.

TABLE OF CONTENTS
(In bold characters, font size 14)

1.0 Introduction 1-1

1.1 Background of the Study 1-1
1.2 Statement of the Problem 1-2
1.3 Statement of Objectives 1-2
1.3.1 General Objectives 1-3
1.3.2 Specific Objectives 1-3

List of Appendices.
Observe the following format.

APPENDICES
(in bold character, font size 14)

Appendix <appendix #> <Appendix Caption>

Appendix A Project Schedule and Work Assignment

Appendix B Certification
Appendix C Transcript of Interview
Appendix D Survey Forms/Questionnaire
Appendix E Sample Forms and Reports
Appendix F Screen Design
Appendix G User’s Manual
Appendix H Program Listing
Appendix I Others

Project Schedule and Work Assignment

Observe the following format.

Project Schedule

ACTIVITIES 6/1 6/2 7/3 7/1 7/1 … 12/ 12/ 1/8

9 6 0 7 18 25
Planning
<subtask1>
<subtask2>
System Analysis
 <subtask1>
<subtask2>
System Design
<subtask1>
<subtask2>
System
Development
<subtask1>
<subtask2>
System
Implementation
<subtask1>
<subtask2>
Others

Use a Gantt Chart, a scheduling chart, which marks off time periods in days,
weeks or months. This chart must illustrate the different activities performed,
when each begins, and when each terminates.

The left-hand column are listed the tasks or activities to be performed. The
right-hand portion of the chart has horizontal bars that show the duration of
each activity.

A Gantt chart is based upon time intervals and does not show the logical flow
of information throughout a system. It shows the total time involved from the
beginning of the project to its completion.

Work Assignment
- Identify the project involvement and participation of each group
members.

Certifications
Include the following certifications:
Certificate of Interview
Certificate to Use Company’s Data / Information
Certificate of Acceptance

Transcript of Interview*
- Contains documentation of all questions and answers obtained during the
data-gathering step.

Survey Forms/ Questionnaires*

Sample Forms and Reports*

List of Tables
Observe the following format:
LIST OF TABLES
(in bold characters, font size 14)

Table <chapter#>-<table#> <Table Caption>

Examples:
Table 1-2 Percentage Ration of Sophomore vs. Seniors
Table 3-4 Mortality Rate of THESIS2 vs. School Year

List of Figures
Observe the following format.

LIST OF FIGURES
(in bold characters, font size 14)

Figure <chapter#>-<figure#> <Figure Caption>

Examples:
Figure 2-2 System Development Life Cycle
Figure 4-1 Data Flow Diagram

Acknowledgement
The acknowledgement section contains expression of appreciation for assistance
and guidance. The given by the advisers and readers does not require written
acknowledgement, but the recognition of generosity with time and knowledge is a
courtesy that is widely appreciated. Acknowledgements should be expressed simply
and tactfully and should fit into a single page only.

Abstract
From 150 to 200 words using direct and complete sentences, the content should
be informative enough to serve as a substitute for reading the thesis itself. This should
contain a very brief rationale and statement of the problem or issue, a brief description
of the research method and design, major findings and their significance, and the
conclusion.

Do not put any citations or quotations. An abstract is usually limited to one page.
Do not start the Abstract with “This thesis paper project”

Resource Persons
For each resource person:
<Full name and Title> Dr. Juan Dela Cruz
<Profession> Faculty
<Department> Information Technology
<Name of Institution> Systems Technology Institute
<e-mail address/ tel. no> jdc@sti-edu.net
 840-5618/ 818–1621 loc. 301
Personal Vitae
For each proponent:

<Last Name>, <First Name>, <Middle Initial> Cruz, Maria Josefa F.

<Address 1> 269 San Marcelino St.,
<Address 2> Golden Gate Subd., Tambo
<Address 3> Pasay City 1300
<Tel. Nos> 833-8972/ 831-2213
<pager and cellular phone nos.> 1277-89221/ 0981-8711622
<e-mail address> maria@skyinet.net

The Text (or Body)

The text, or body, of a thesis begins with the first page of Chapter 1. All pages
are numbered, including chapter and section title pages. Start using Footers in this
part.

1.0 Introduction
Give a brief introduction about the study.
1.1 Background of the Study
1.1.1 Symbol / Logo with description
1.1.2 Organizational Chart
1.1.3 History
1.1.4 Stake Holders
1.1.5 Location and Size
1.1.6 Mission
1.1.7 Vision
1.1.8 Objectives / Thrust / Services

1.2 Statement of the Problem

 Current problems that are evident with the system or area under
study. These problems may not necessarily be the problem of the
study.
 The problem of the study. Answering the question identifies this:
What is being solved by this research or thesis project.

 The statement of the problem is a clear, definite, and logical

statement of the major problem(s) and the sub-problem(s) if any.

How to write the problem.

 State a general problem or issue of the current situation/ system.
 State the problem fully and precisely in enumerated form.
 State the problem in complete grammatical sentence,
punctuation is important. Provide justification to support the
statement.

1.3 Cause and Effect Relationship

1.4 Alternative Solution
1.5 Objectives of the Study
1.5.1 General Objective
This is a statement that what the research or thesis project
is trying to accomplish.

1.5.2 Specific Objectives

These are statements that try to achieve the general objective.
Specify the things that would be done to accomplish the
general objective.

Objectives are statements of WHAT the project is expected to

accomplish. Each objective should be stated to describe what is to be done.
Since objectives are associated with action, they usually start with action
verbs.

Starting project objectives:

The study aims to…
develop conduct assess
design implement enhance
produce train strengthen
acquire improve evaluate
A satisfactory objective should be Specific, Measurable,
Attainable/Achievable, Realistic, and Time-bounded. It should be stated
to include the following information:
a) an action verb;
b) the outcome to be accomplished;
c) the time-frame the outcome is to be accomplished; and
d) the criteria or conditions for measuring the accomplishment

Few objectives should be considered in a proposal and they should be

arranged in their order of importance. It is more likely that few objectives
can be successfully accomplished given the available resources.

Objective must always relate to the expected outcomes or project outputs.

Moreover, objectives determine the methodology – how each objective is to
be accomplished.

Objectives are normally classified as general and specific. A general

objective states what the research or thesis project is trying to accomplish.
Specific objectives are statements that try to achieve the general objective.

Example:
1. System Development – Inventory System

General Objective
The project aims to improve the current inventory system of XYZ
Company by reducing 80% of time needed between the project request
and goods delivery before the end of the fiscal year.
 Specific Objectives
Specifically, this study aims to:
 Improve the procedures for verifying invoices and shipments;
 Add an inventory control function to hold frequently used parts;
 Integrate the Goods Received System (GRS) and the Project
Ordering System (POS) to reduce the manual effort needed to
maintain information flows between these two computer systems.

Analysis of the objectives:

Criteria Justifications
Specific? YES! Because the objectives state particular, precise and
definite details about the project.

Measurable? YES! Because the objectives state weighable (80%)

indicator to measure the success of the project

Attainable? YES! Because the procedures, function and integration of

GRS and POS is feasible and within reach

Realistic? YES! Because the objective states practical and viable

methodology
Time- YES! Because the objective states the time when the
system will be accomplished.
Bounded?

1.6 Significance of the Study

 A discussion on who benefits from the output of the research or
thesis project.
 Discusses the contributions/benefits of the study to
1 Individuals
2 Corporations
3 Country
4 World or humanity in general

The resources allocated for the purpose research (human, financial

and material) should be justified in terms of expected
utility/significance of the results for the following concerns:
1. Nationhood and Development
 Will the research produce new technology?
 Does research address current social economic political
and cultural problems?
 Will innovation natural infra and human rescue
management results from the study?
2. Scientific and Artistic Domain
 Will the research contribute new information?
 Are data gaps to be filled?
 Is a new point of view to be applied to a previously studied
phenomenon?
3. University Trust
 Will contribute to expansion of knowledge?
 Will it develop strong scientific base for national mastery?
 Will it develop strategies to address present socio-
economic?
4. Specific Users/Beneficiaries
  Will it benefit specific users?
 How it benefits those users?

1.7 Scope and Limitation

 Discusses the boundaries of the system to be developed
 Enumerates items shall will not be covered by the study
 Gives a general view of the features/characteristics of the output
of the system.
 Assumptions made about certain things stated in this section
 These are statements of what can be taken for granted about
research project

2.0 Review of Related Studies

2.1 General Literature Survey – resource according to your major or area
of study
2.2 Abstract/ Compiled Abstracts – crude sources of material
2.3 Bibliographical References – Bibliographic or bibliographies
2.4 Personal Interviews – ask the following persons about the field of
studies, conclusions, recommendations for future works, present
and future trends of particular research, advice, etc.
2.5 Evaluation of Existing System Software
Literature or Background of the study will:
 Reveal Investigation Similar to the study how, other researchers
approach the problem
 Suggest method or technique of dealing with problems, suggest
approach and strategies
 Reveal significant research personalities
 See your study in historical/associative/perspective
 Provide new ideas and new approaches
 Assist you in evaluating your own research effort
 Provide information on what is current in terms or similar
technologies and solution to particular problem domain.

3.0 Methodology of the Study

Identifies the formal method that the proponents intend to follow in order
to accomplish what have been see in the objectives. The formal
methodologies are any of the software engineering systems analysis and
design methodologies.

1. Waterfall model or Software Development Life Cycle (SDLC) Model

 System Engineering and Analysis
 Software Requirements Analysis
 Design
 Coding
 Testing
 Maintenance
2. Prototyping
 Requirements Gathering and refinement
 Quick Design
 Building Prototype
 Customer Evaluation Prototype
 Refining Prototype
 Engineer Product
3. The Spiral Model
 Planning
 Risk Analysis
  Engineering
 Customer Evaluation
4. 4th Generation Techniques
 Requirements Gathering
 Design Strategy
 Implementation using 4GL
 Testing
5. Rapid Application Development
 Requirements Planning
 User Design
 Construction
 Cutover
6. Join Application Development

4.0 Data Gathering Procedures and Output

This section produces on gathering data such as interview,
survey/questioners, etc. It also includes tryouts and other validation
procedures, observation techniques, distribution and collection of
questioners and whichever approach(es) is/are to be employed is/are
described. All each procedure, an accompanying output should also be
described. If needed statistical treatment of data using statistical formulas
and procedures are described.

5.0 Online System Flow

5.1 Decision Tree
5.2 System Flowchart
5.3 Context Diagram
5.4 Data Flow Diagram (LEVEL 1-3)
5.5 Use Case Diagram
5.6 Class Diagram

6.0 Documentation of the System Design

6.1 Description of the System
6.1.1 Definitions, Acronym and Abbreviations
6.1.2 Database Design
6.1.2.1 Database Schema
6.1.2.2 Data Dictionary
6.1.3 ERD Diagram (Entity Relationship)
6.1.4 Screen Design
6.1.4.1 Screen Inventory
6.1.4.2 Screen Transition Diagram
6.1.4.3 Screen Layout
6.1.5 Reports Design
6.1.5.1 Reports Inventory
6.1.5.2 Reports Layout
6.2 Hardware Setup
6.3 Software and Application being used
6.4 Personnel
7.0 System Requirement Specification
7.1 Hardware Requirements
7.2 Software Requirements
7.3 Human Resource Requirements

The requirements definition describes everything about how the system interact with its
environment. Includes are the following kinds of items:

Physical Environment
 Where is the equipment to function?
 Is there one or several locations?
 Are there any environmental retractions such as temperature, humidity or magnetic
interference?
Interfaces
 Is the input coming from one or more other system?
 Is the output going to one or more other system?
 Is there a prescribed way in which the data is formulated?
 Is the prescribed medium that the data must use?
Users and Human Factors
 Who will use the system?
 Will there several types of user?
 What is the skill level of each type of user?
 What kind of training will be required for each type of user?
 How it easy will it be for user to understand and use the system?
 How difficult it will be for a user to use the system?
Functionality
 What will the systems do?
 When will the system do it?
 How and when can the system be changed or enhance?
 Are there constraints in execution speed response time or throughput?
Documentation
 How much the documentation is required?
 To what audience is documentation addressed?
Data
 For both input and output, what should the format of the data be?
 How often will it be received or sent?
 How accurate must it be?
 To what degree of precision must the calculation be made?
 How must data flows through the system?
 Must any data be retained for any period of time?
Resources
 What materials, personnel, or other resources are required to built, use and
maintained the system?
 What skills must the developers have?
 How much physical space will be taken up by the system?
 What are the requirements for power, heating or air-conditioning?
 Is there prescribed timetable for development?
 Is there a limit on the amount of money to be spent on development or on hardware
and software?
Security
 Most access to the system or information is controlled?
 Flows will one user’s data is isolated from others?
 How will user programs be isolated from other programs and from the OS?
  How often will the system be backed up?

8.0 Conclusion, Justification and Recommendation

Conclusion & Justification

This section should discuss what has been accomplished in the study
written in the objective to see clearly all the significant aspects. It may be
subdivided into those that are primarily esthetic, those that announce the
results on an investigation, and those that present discussion concerning
in the course of action. Also, if may be numbered with respects to problems
and sub-problems in the study.

Recommendation
This section should finish future undertakings base on the analysis and
conclusion of the stud. It may also recommend potential application of the
study, other solutions, enhancement and/or development related to the
study.