Scribd
Upload
37 views3 pages

Current Environment: Background of The Study System Objectives Significance of The Study Proposal

This document provides an overview and requirements for a new system. It begins with background information on the organization and current processes. The document then outlines 12 sections for requirements, including: [1] input and output needs; [2] data requirements supported by a data model and dictionary; [3] suggested technologies. The requirements specify functions for the new system and how it will transform inputs to outputs.

Uploaded by

Gene Kyle Sardido
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
37 views3 pages

Current Environment: Background of The Study System Objectives Significance of The Study Proposal

This document provides an overview and requirements for a new system. It begins with background information on the organization and current processes. The document then outlines 12 sections for requirements, including: [1] input and output needs; [2] data requirements supported by a data model and dictionary; [3] suggested technologies. The requirements specify functions for the new system and how it will transform inputs to outputs.

Uploaded by

Gene Kyle Sardido
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Introduction

Background of the Study


System Objectives
Significance of the Study
Proposal

1. Current Environment
This section consists of four subsections of brief descriptions that provide understanding of the
context for the proposed effort.

This System allows your personal and customers to see the data they need in real time.

1.1 Organization Profile

Relevant information about the organization, mission, locations, numbers, and type of personnel,
and relationships or interfaces with other organizations and entities, as they relate to the system
task.

1.2 Business Functions

A high-level picture of the processes and procedures by which information is currently handled
by the owner/user in the area being automated or modified. The timing of critical processes
should also be discussed, e.g., if there are any processes dependent on other processes being
previously completed, these dependencies should be noted. For example, if time sheets are due
on the 15th of the month, and there is an audit step to ensure all time sheets have been keyed prior
to running a system job that cuts the checks, the audit step must be run after the 15th and prior to
the system job being run.

1.3 Component or System Description

A brief introduction to the component or system that is covered by the specification. This
section should be brief, since it is included only to help the reader quickly understand what is
being specified.

A context diagram should be included to assist in positioning the proposed component or system.

1.4 Deficiencies

This subsection portrays any problems experienced by the owner/user with the current process.
2. Requirements
This section consists of twelve subsections. This section states the functions required of the
software in quantitative and qualitative terms, and what the system must do to completely fulfill
the owner/user=s expectations. The requirements should answer the following questions:

$ How are inputs transformed into outputs?


$ Who initiates and receives specific information?
$ What information must be available for each function to be performed?

Each paragraph (or group of paragraphs) should contain a reference identifying the source of the
requirement. Each requirement (sentence or paragraph) should be numbered, using a numbering
scheme that allows for inserting additional requirements later, e.g., FUNC-01, or A-1.1, etc.
Only one requirement should be defined per numbered item.

Each requirement should be classified as one of the following:

1 Mandatory Absolutely essential feature; project will be canceled if not


included
2 Required Individual features are not essential, but together they affect the
viability of the project.
3 Desired Nice-to-have feature; one or more of these features could be
omitted without affecting the project viability.
2.1 Input and Output Requirements

Provide a description of all manual and automated input requirements for the software product
such as data entry from source documents and data extracts from other applications, as well as all
output requirements for the software product such as printed forms, reports, display screens, files
and other work products the system will process and produce.

2.2 Data Requirements

Identify the data elements and logical data groupings that will be stored and processed by the
software product. Include archiving data requirements and sensitivity of data.

This section is supported by a data model. An accompanying data dictionary should be included
in an appendix.

2.3 Suggested Technologies


3. Design Phase
3.1 User Interface, Input and Output forms
3.2 Data Design
ERD
Normalized Tables
3.3Table Definitions

You might also like