Sie sind auf Seite 1von 7

SYSTEM ANALYSIS AND DESIGN

DOCUMENT OUTLINE
CHAPTER I THE PROBLEM
Introduction. What is the current situation of businesses in
doing business transactions that are related to what your
proposed system is supposed to be doing. Discuss the
current problems, threats, or opportunities associated with
this current scenario. Introduce the chosen company and cite
examples that encapsulate the relevance of this particular
study in helping the company improve its business
processes.

Statement of the problem. What are the problems of the


company in their day-to-day business transactions? Identify
these problems and explain why they are such by giving
real-life examples.

Project Goals. What are the goals of this software project?


Is it to help the business increase profit? By how much? Is it
to speed up the process throughput? By how much?

System Objectives. Identify the objectives of your


proposed system as ways to address the problems stated in
the Statement of the Problem. Does the system aim to
provide a database to systematize the recording and
retrieval of information?

Scope and Limitation. Discuss the boundaries of your


proposed system.
Definition of Terms. Identify technical or key terms used in
your study and provide the OPERATIONAL definition of these
terms as they are supposed to be treated in this particular
context.

User Requirements Definition. What does the user want


the system to do? List down these requirements.
CHAPTER II DATA COLLECTION AND ANALYSIS
Company Profile. Include history, vision, mission, goals and
objectives. Include the organizational chart. Discuss the
business environment including the products, processes,
clientele, and competitors.

Description of the Existing System. Identify the


transactions that are happening in the company based on
the focus of your study. Describe the real-life scenario of
these transactions.

Data Flow Diagram (DFD) of the existing system. Create a


Context Flow Diagram, and Level 0 diagram for the existing
system.

Results of the Company Interview (Summary)

Result of the Survey. Company employees and clients


should be given a set of closed-type of questions to define
the problems in the business processes.

Document Analysis. Gather business documents and


forms used in the actual business transactions such as
logbooks, receipts, manuals, etc that are relevant to your
study. Analyze the importance and adequacy of these
documents in the current system. Are they necessary? Are
they sufficient?
CHAPTER III ANALYSIS OF SYSTEMS ALTERNATIVES
Provide at least 3 alternatives that you can do to solve the
problems of the company. Each alternative discussion
should include feasibility studies (technical, economical
and operational feasibility), Cost and Benefit Analysis
(CBA), software and hardware requirements, GANTT chart,
data flow diagrams (context flow diagram, diagram zero
and child diagram).
CHAPTER IV RECOMMENDED ALTERNATIVE
State the recommended alternative and explain why you
have opted for this solution.

CHAPTER V SYSTEM DESIGN


Functional Requirements. Specify functionalities per
module. What are the activities present in each module of
your proposed system?

Non-functional Requirements. List down other


requirements that are necessary for the system to operate
normally.

Use Case Diagram

Entity-Relationship Diagram

Data Dictionary
Prototypes Specification (detailed design of input/output
forms)
CHAPTER VI SOURCE CODE
CHAPTER VII USERS MANUAL
APPENDICES
Letters for the company, grammarian, IT consultant and
computer vendors
Company forms (Sample forms)
Price lists from the computer vendors
Results of the company interview (unedited)
Questionnaire for survey
Curriculum Vitae of proponents
Notes:

Documentation should be placed in A4-sized bond paper;


computerized

During preliminary checking documents should be


enclosed in a white, transparent folder with black slide.
During the pre-defense and final defense the submitted
document should be ring bound, cover page: white;
spring: black

Font: Arial, Times New Roman, Courier New or Tahoma

Heading size: 14, bold

Sub-heading: 13
Paragraphs: 12
Page numbers should be shown on center bottom of the
page

Margin: Top, Right and Bottom: 1 ; Left: 1.5

During the pre-defense and final defense, groups must


prepare a slide presentation which will show the company
background, the existing manual system, the system
alternatives and the recommended alternative. This slide
presentation should be allocated 10 minutes. The system
presentation will be given 15 minutes.

The presenters should be in their formal attire or in proper


uniform.
Holy Child of College of Davao
Information Technology Department
E. Jacinto Street, Davao City

[Date]

[Name of Company - bold]


[Address of Company]

Madame/Sir:

Part of the schools requirement for completion of the Subject Course IT413 Systems
Analysis and Design for its BS Information Technology students is to develop a
workable Database System for an existing business establishment in Davao City.

The objective of the database project is to allow the students to simulate a real world
project, i.e. to complete a database project from conceptualization stage to the final
implementation stage with proper documentation.

On this regard, may I request your permission in behalf of my students to allow them to
interview any of your staff, and secure information about your establishment such as
data sheets, transaction procedures / invoices, organizational charts, et al which they
would need in completing their database project.

We assure you that whatever information they may collect shall be kept in utmost
confidentiality and a copy of the final database project be furnished to you as well.

Thank you.

Very truly yours,

Karen B. Jabido, CoE


IT Instructor

For Students: [Name of Student]


[Name of Student]
[Name of Student]

Agreed to and Accepted:

____________________ [by date leave this blank]

Das könnte Ihnen auch gefallen