0% found this document useful (0 votes)
48 views11 pages

Project Overview: General Guidelines

The project requires students to act as systems analysts for a real organization. As analysts, students will: 1) Find a willing organization and conduct requirements modeling and analysis; 2) Use fact-finding techniques like interviews and documentation review to understand the organization's current systems and needs; 3) Develop a logical design for a solution to meet the organization's system requirements.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
48 views11 pages

Project Overview: General Guidelines

The project requires students to act as systems analysts for a real organization. As analysts, students will: 1) Find a willing organization and conduct requirements modeling and analysis; 2) Use fact-finding techniques like interviews and documentation review to understand the organization's current systems and needs; 3) Develop a logical design for a solution to meet the organization's system requirements.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 11

Project Overview

The project requirement for Systems Analysis, Design, and Prototyping intends to
expose the students to real-life situations, acting as systems analysts. As systems
analysts, the students are expected to:
1. Look for a viable organization willing to share its time, as the students
conduct requirement modeling and system analysis;
2. Conduct fact-finding techniques such as interview, document
gathering, observation, or survey to understand the predicament of
the organization while using their existing procedures and systems.
3. Develop a logical design of the solution to the organizations system
needs

General Guidelines:
- Use the following:
o Short bond paper
o Font Arial 11
o Line spacing 1.5
o Alignment Justify
o Page Margin - Left 1.5; Top, Right, Bottom 1
o Page number placed at the upper-right corner (Arial 9)
- Diagrams (Figures and Tables) must be properly labeled. Label for Table is
placed above the table. Label for Figure is placed below the table. Diagrams
must include explanation or description.
- Include Table of contents, List of Tables and List of Figures. These must be in
separate pages. Please see the sample below.
<<LIBRARY SYSTEM FOR ____ >>

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

Semester, School Year


TABLE OF CONTENTS
Chapter

I. PROJECT OVERVIEW
Project Background ...........................................................
Objectives of the Project ...........................................................
Statement of Work
Scope of the Project ...........................................................

II. ANALYSIS OF EXISTING AND RELATED SYSTEM


Review of Existing Systems ...........................................................
Review of Related Systems ...........................................................
Operational Definition of Terms..........................................................

III. RECOMMENDED SOLUTION


A. Overview of the Recommended System ...........................................
B. System Design ...........................................................
1. System Framework ...........................................................
2. User Overview
3. Data Flow Diagram ...........................................................
Bibliography ...........................................................

APPENDICES
Schedule Estimates ...........................................................
- Gantt Chart
- PERT
Fact-Finding Techniques ...........................................................
- Transcript of Interview
- Gathered Documents (e.g. reports, sample receipts or any transaction slip,
picture(company location, etc), DTI permit, Mayors Permit and others
LIST OF TABLES

NUMBER TITLE PAGE

1 .....................
2 .....................

3 .....................
4 .....................
5 .....................
6 .....................
7 .....................

LIST OF FIGURES

NUMBER TITLE PAGE

1 .....................
2 .....................

3 .....................
4 .....................
5 .....................
6 .....................
7 .....................
DISCUSSION OF THE DOCUMENTATION FORM

Chapter 1 PROJECT OVERVIEW


Project Background
This section includes a short narrative background of the project. It
gives the reader an introduction on how the project came about and discusses
the general problems that it intends to concentrate on. This will give a short
discussion on the nature of the company being studied.

Objectives of the Project


General Objective
State the main goal of your project is to provide a solution to the
problems stated in the Project Background. Logically, this should capture the title
of the research.

Example:
The general objective of this project is to develop a preventive
maintenance and monitoring system that will facilitate better monitoring
measures to ensure high-quality services of all buses of Five Star Incorporated.

Specific Objectives
The specific objectives of the project are the following:
To design a prototype that will ..
To develop a system that will
To test and evaluate the acceptability of the system in
terms of functionality, reliability, usability and so on by
gathering feedback from prospective users and technical
experts.

Statement of Work
Scope of the Project
The scope of the project means coming to a common
understanding of its major boundaries and the business
functions it encompasses. Example: an inventory system
may INCLUDE raw materials and finished goods
inventory, but to EXCLUDE cash flow. Or an enrollment
system may or may not include accounting system,
student record management system, etc. It includes the
agreed activities that the team has to undertake and
deals with how each deliverable is prepared and
presented. For example, your group is commissioned to
develop a Library System for Matalino University. The
University has existing student database; hence, the
team might ask the client whether will they utilize the
existing database, then the development of the new
database is NOT covered in the scope of the project.
Now, if the group is required to develop an independent
database, database development will be part of the
scope of the project plus the clients database
requirements and specifications.

Chapter 2 ANALYSIS OF EXISTING AND RELATED SYSTEMS

Review of Existing System


This section presents the exiting or current system. This
will allow them to present the gaps/problems in the existing system in
detail. It should contain the System Description, Process Flow (DFD).

Review of Related Systems


After presenting the Review of Existing System, the team
should also discuss other systems that are related to their proposed
system. This section should present the features of the related
systems that are benefit that are beneficial for the proposed project.
Related systems are systems that are available in the market or
systems that had been implemented in a company.

Data Flow Diagram


Develop Context, Diagram 0 and Child diagrams
describing the current system. Each figure must include explanation.

System Design
Is a graphical representation of the interaction between
different users and the system modules.
Sample System Framework for a Library System

Operational Definition of Terms


Define terminologies based on how they are used in the
study. Terminologies are alphabetically arranged. The definition of
each term is presented in a paragraph format with the first line of the
definition, intended. (The different criteria in the evaluation sheet
should also be defined here.)
APPENDICES
A. Schedule Estimate
Gantt Chart of activities from System Planning to System Implementatiom
Month Month Month Month Month
ACTIVITIES Year Year Year Year Year
Week Week Week Week Week Week Week Week Week Week Week Week Week Week Week Week Week Week Week Week
1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Activity 1

Activity 2

Activity 3

PERT
The activities in the Gantt chart should be converted into its equivalent PERT diagram
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)
-
-
Project Requirements
#1 Company Information
Name of the Company: ________________________________________________
Nature of Business: ___________________________________________________
Address: ___________________________________________________________
Contact Information:
Name of Contact Person: ______________________________________
Position in the Company: ______________________________________
Telephone Number
Office landline: ___________________
Mobile:__________________________
Computerized system(s) being used:
Comments
System
Strength Weakness

Possible system to be developed:


System Reason for Development

Note:
Final Project Documentation shall include Chapters 1 to 3 and the
necessary appendices.

You might also like