Center for Industrial Technology and Enterprise

San Jose, Cebu City

CITE Online Application

REQUIREMENTS SPECIFICATIONS

Jake Quimbo
Romnick Revalde
Emmanuel Broniola
ITP 3E
 Chapter 1 Introduction

1.1 Purpose

This software is an add on to the official website of CITE. The primary objective of this

software is to provide efficiency in both part of the applicants and CITE. This software lets

the applicants have the application filed online.

1.2 Scope
The project is known us Enfants Du Mekong Inventory System(EDMIS). This software
encompasses the following general functionalities:
• Efficient Working Environment - EDMIS provides an efficient working environment
for administrators (e.g. librarians, etc) to lend items to its host just by interacting on
the software functions (either by clicking on the GUI or by encoding phrases to the
system).
• Dynamic GUI Interaction – Administrators would be able to interact with the system
dynamically through the user-friendly GUI which also guides the them all throughtout
the whole system.
• Dynamic Data Manipulation – EDMIS also has the capability to manipulate data
dynamically. If an administrator ask for a deletion or addition of an item to the
database, the software would be able to do so quickly. That’s is how it is being very
dynamic.

1.3 Project Constraints and Limitations

• This software is only intended to Enfants Du Mekong Usage.

• The software only supports administrator accounts only.

• The software has no network support.

Requirements Specifications 2
1.4 Hardware Requirements

• At least 128MB bytes of RAM

• At least 1G of hard disk

1.5 Software Requirements

Any Windows Platform

xampp (any version)

PHP 4

Browsers like Mozilla Firefox(3.0.7), Opera, Google Chrome, etc.

1.6 Definitions of Terms

Administrators – Power users who can only use this software . They all have the privileges

that the software can offer.

CakePHP – PHP framework used in the software.

1.7 References

Gscripts.net
En.wikipedia.org
Script.aculo.us
Cakephp.org

Requirements Specifications 3
 Chapter 2 System Analysis

Tables:

Users – Database table that is only used for logging in and out of administrators.

Requirements Specifications 4
 Categories – Database table for assigning groups to each item in the database.

Items – Database table used for storing item data and description.

The items table links with the category. An item in the items table belongs to a specific

category in the categories table. Each Category has many items in it.

2.1 System or Software Architecture

The major components of the software are:

• Users – By default, they are set to be administrators. Users are assigned to a specific

username and password which they use in order to login and use the software. They are

entitled to privileges like adding, deleting, editing, etc. of database data.

• Categories – These are names of groups of items in the database. A category could be

of any sort.

• Items – These are the core data which has a specific category in the database.

A discussion must follow to describe the interaction of the major components. )

2.2 Flowcharts (This includes the main flowchart of the system. Create the general flow of the

system and then have a detailed flowchart for each functionality. You can have subsections to

illustrate the flowcharts of the major functionalities. Please don’t forget to discuss each

flowchart. )

2.2.1 Functionality 1 Flowchart

2.2.2 Functionality 2 Flowchart

2.3 Data Flow Diagram (the succeeding sectioning is discretion of the Project Team. Please

consult your adviser on this.)

Requirements Specifications 5
2.4 Entity-Relationship Diagram

Requirements Specifications 6
 Chapter 3 Functional Requirements

(This chapter is a detailed description of the major functionalities of the system. This will give an

idea to the adviser and panel on what the software can do.)

3.1 Functionality 1 (describe the functionality in an inverted triangle style, meaning from

general to specific. For sub-functionalities under the main functionality you can create sub-

sections. Describe the purpose of each sub-functionality.)

3.1.1 Sub-functionality 1 (describe in detail the purpose of the functionality)

3.1.2 Sub-functionality 2

3.2 Functionality 2

3.3 Functionality 3

3.4 Functionality 4

Requirements Specifications 7
 Chapter 4 User Interface

(This chapter is a general description on how the graphical user interface of the system works. It

describes the controls (menus, dialogs, push buttons, radio buttons, etc.) to be used to implement

all the functional requirements in Chapter 3.

This will not apply to hardware projects. In lieu, your Chapter 4 is entitled Physical Layout. This

outlines the design of your project prototype or layout. Always include discussion after every

diagram.)

3.5 Main User Interface (The main user interface is the first graphical user display when you

run your software. It is advised that you already create this with the language that you are

going to use. If not possible, find a way to simulate the GUI using any graphics software like

Adobe Photoshop, etc. Have a short discussion after the main user interface.)

3.6 Control 1 (For the controls, you need to have a GUI display included. Just describe the

purpose of the controls. For example, for the Menus you need to list down the Main Menus

and create subsections for submenus. Relate each menu/submenu to the functionality describe

in Chapter 3. )

3.6.1 Sub-controls 1

3.6.2 Sub-controls 2

Requirements Specifications 8
3.7 Control 2 (the sectioning depends on the controls you are using. It is your discretion what

control to discuss in each section.)

3.8 Control 3

Requirements Specifications 9