1.

0 Introduction

1.1 Background of the Study

 This section gives background information on the study by discussing any or all of the
following in textual paragraph form:

 The general area in Computer Science or Information Technology where the study may be
classified. Examples are the following:

1) For Payroll, Accounts Receivable/Payable, Inventory, Reservation, Library, etc.

Systems, the general area which may be discussed is Information Systems.

2) For Expert Systems, CAIs, ICAIs, ITSs, etc., the general area is Artificial Intelligence.

3) For Editor Softwares, Utility Softwares, Compilers, etc., the general area is Software
Technology.

4) For Multimedia Systems, Geographical Information Systems, Hypertext, etc., these

are the actual general areas.

 The current state of technology on the general area leading to the current state of
technology in the specific area.

 The specific company/corporation/institution on which the study is being conducted. A

brief history, organization, some statistics (e.g. number of employees, locations/branches,
etc.) products and/or services, etc.

 A general and brief description of the system under study.

1.2 STATEMENT OF THE PROBLEM

 The problem of the study. This is identified by answering the question: 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.

1) State the problem of the study fully and precisely in enumerated form
2) State the problem in complete grammatical sentence, punctuation is important.
Provide justification to support the statement.
 Example:
Systems Development – Payroll System

General Problem
 How to design, develop and implement a computerized payroll system for XYZ
Company?

Specific Problems
Specifically, the study aims to answer the following problems:
 How to develop and integrate an automated time keeping system that will
monitor employees’ log-in/out?
 How to create a module that will automatically compute for the employees’
salary?
 How to design a security module that will decrease the risk of data loss?

1.3 OBJECTIVES OF THE STUDY

1.3.1 General Objective

- This is a statement that states what the research or thesis project is trying to
accomplish.

1.3.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.

 Stating 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:
 o an action verb;
o the outcome to be accomplished;
o the time-frame the outcome is to be accomplished; and
o 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.

 Objectives 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. 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:
System Development – Inventory System

General Objective

The main objective of this study is to develop a computerized inventory system for XYZ
Company which could help reduce at least 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:

1) Add an inventory control function to hold frequently used parts;
2) 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
bounded? accomplished

1.4 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:

o Individuals
o Corporations
o Country
o World or humanity in general

 Enumerates the problems that may be solved by the output of the study.

 The resources allocated for the proposed research (human, financial and material) should be
justified in terms of the expected utility/significance of the results for the following concerns:

o Nationhood and Development

o Will the research produce new technology?
o Does research address current social, economic, political and cultural problems?
o Will innovations in natural, infra and human rescue management result from the study?
o Scientific or Artistic Domain
o Will the research contribute new information?
o Are data gaps to be filled?
o Is a new point of view to be applied to a previously studied phenomenon?
o University Thrust
o Will it contribute to expansion of knowledge?
o Will it develop strong scientific base for national mastery?
o Will it develop strategies to address present socio-economic?
o Specific Users/Beneficiaries
o Will it benefit specific users?
o How will it benefit these users?

1.5 Scope and Limitation

 Discusses the boundaries of the system to be developed.

 Enumerates items that 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 Methodology of the Study

Identifies the formal method that the proponents intend to follow in order to accomplish what
have been set 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 of 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 (RAD)
 Requirements Planning
 User Design
 Construction
 Cutover
 6. Joint Application Development (JAD)

3.0 Review of Related Studies

A. General Literature Survey – resources according to your major or area of study

B. Abstracts/Compiled Abstracts – crude sources of materials
C. Bibliographical references – bibliographies of bibliographies
D. Directories and Periodical guides
E. Trade literature
 National Journals – research and development trend in the country
 Information Journals – research and development at international level
F. Go to Industry/Research Institutes/Government Agency/Private Corp. – interview/visit site
and inquire the following:
 Inquire on their past projects, recommendations, future works that need to be
done, problems encountered, limitations and coverage of works
 Inquire about present projects (if possible)
 See their facilities, library, and laboratory
 Try to interview their staff and personnel
G. Evaluation of Existing System/ Software

Literature or background of the study will:

 Reveal investigations similar to your study, how other researchers approach the
problem
 Suggest method or technique of dealing with problems…suggest approach and
strategies
 Reveal sources of data
 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 of similar technologies or solutions
to a particular problem domain

“ … are by no means sufficient in themselves, but with these aids as a nucleus and with genuine
interests in the subject you will have no troubles in developing the knowledge you need.” –Shaw
4.0 Theoretical Framework

The theoretical foundations in computer science that are necessary to accomplish the objectives
set need to be discussed thoroughly and cited accordingly. It is a structure that holds together/
supports the fundamental principles of the study and is required to give legitimate basis defining
the area of research.

Examples:

1. For Games Software: game trees, search algorithms.

 2. For Information Systems: general systems theory, transaction processing systems, human
computer interface, etc.

3. For CAIs, ICAIs, ITSs: learning theories, testing theories, assessment theories, etc.

4. For Expert Systems: search engines, knowledge bases, etc.

5.0 Data Gathering Procedures and Analysis of Outputs

This section discusses procedures on gathering data such as interviews, survey/questionnaires,

etc. It also includes tryouts and other validation procedures, observation techniques,
distribution and collection of questionnaires and whichever approach(es) is/are to be employed
is/are described. At each procedure, an accompanying output should also be described. If
needed, statistical treatment of data using statistical formulas and procedures are described. All
gathered outputs must be part of the appendix section. The following are some of the sample
gathered outputs:

 organizational structure
 transcript of interview
 observation notes
 sample questionnaire/ survey form
 sample forms and reports
 others

6.0 Documentation of the Current System

This section should provide necessary information on the current situation/system such as its
nature, its description, users/beneficiaries, etc.

6.1 Description of the Current System

Complete discussion of the different processes and procedures involved in the system
must be presented in this section. The physical environment and layout of the system
must be properly described and discussed in this section. Problems and issues
experienced in the current system must also be cited.
 Specific analysis tools should be used to illustrate the existing system and the
requirements of the project. The analysis tools that may be used are:

 Hierarchical Input-Output (HIPO) Charts

 Data Flow Diagrams
 Entity-Relationship Diagram
 System Flowchart

6.2 Hardware and Equipment Setup

This section enumerates and discusses the purpose and function of the different
hardware resources and equipment used in implementing and executing the current
system. Physical layout of the equipment must also be provided in this section.

6.3 Software and Applications being used

This section enumerates and discusses the purpose and function of the different
software resources and applications used in implementing and executing the current
system. Tools and applications used as support in generating reports, storing of data and
other system activities must also be cited.

6.4 Personnel

Users and other personnel involved in the current system must be properly identified
and discussed in this section. Responsibilities and functions of such must also be
presented.

7.0 System Design Specification

This section should provide models that depict information (data and control) flow and content
of the system under study, partition the system functionally and behaviorally, and depict the
essence of what must be built. This section should also provide the overall specifications and
functional requirements of the software to be developed.

7.1 Architectural Design

This section presents the initial internal design of the system, by discussing its major
components and their interactions. These components include the software
components (e.g., modules, database systems, etc.), as well as the hardware
components (e.g., processors, devices, etc.). The components and their interactions are
graphically represented using design tools, such as hierarchical charts, structure charts
or object models. Data flow diagrams may also be included to show how information
passes among processes.

7.2 System Functions

 This section provides a listing of all the functions that must be performed or delivered
by the system, and a description of each. Screen designs may be included, to help
visualize the function being discussed. Usually, the functions are based on the menu and
toolbar options. If a function generates reports, the report formats must be included in
this section.

8.0 Systems Implementation

Systems Implementation is the stage during which the system is actually built, tested and
implemented/ installed based upon the designs conceived in the earlier phases.

8.1 Programming Considerations, Issues and Tools

This section should concentrate on identifying hardware and software tools which must
be utilized in developing the actual system. Issues, concerns and problems encountered
during development are also discussed.

8.2 System Requirement Specification

This section discusses the hardware and software resources needed to implement and
to execute the system. If the system has a special set of target users, this section also
includes the user specification (e.g., educational level, experience, and technical
expertise). For certain uncommon resources, a discussion of why such resources are
necessary must also be included.

8.2.1 Hardware Requirements

8.2.2 Software Requirements
8.2.3 Human Resource Requirements

This section should provide discussion on the following:

 Who will use the system?
 Will there be several types of users?
 What is the skill level of each type of user?
 What kind of training will be required for each type of user?
 How easy will it be for a user to understand and use the system?
 How difficult will it be for a user to misuse the system?

8.3 Implementation Set-up

This section describes everything about how the system is to interact with its
environment. Included are the following kinds of items:

a. Physical Environment
 Where is the equipment to function?
  Is there one or several locations?
 How much physical space will be taken up by the system?
 Are there any environmental restrictions, such as temperature, humidity, or
magnetic interference?
 What are the requirements for power, heating, or air-conditioning?

b. Interfaces
 Is the input coming from one or more other systems?
 Is the output going to one or more other systems?
 Is there a prescribed way in which the data must be formatted?
 Is there a prescribed medium that the data must use?

c. Functionality
 What will the system do?
 When will the system do it?
 How and when can the system be changed or enhanced?
 Are there constraints in execution speed, response time, or throughput?
d. 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 calculations be made?
 How much data flows through the system?
 Must any data be retained for any period of time?

e. Security
 Must access to the system or to information be controlled?
 How will one user’s data be 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.4 Testing Activities

After developing the system, testing must be performed to find and remove errors from
a program. Different testing activities must be performed to check correctness and
reliability of a system. Test data must be prepared, run through the program and the
results compared to the existing data by the old system.

In this section, different testing activities must be discussed thoroughly and results must
be analyzed and documented.

 System Function
 Test Data
 Results and Observations

8.5 Installation Processes

 This section should discuss conversion planning and activities from the existing system
to the new or improved system. There are three basic approaches used in converting to
a new system: an immediate/ direct changeover, a gradual, step-by-step changeover, or
a parallel system changeover. This section should discuss what type of installation or
conversion approach will be used in the study and the different activities or process that
will be performed to complete installation must be identified and discussed thoroughly.

9.0 Conclusion and 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
aesthetic, those that announce the results on an investigation, and those that present a decision
concerning a course of action. Also, it may be numbered with respect to problems and sub-
problems in the study.

10.0 Recommendation

This section should furnish future undertakings based on the analysis and conclusion of the
study. It may also recommend potential applications of the study, other solutions, enhancement
and/ or developments related to the study.