II.

ANALYSIS PHASE (new page)

A. Current System

A.1. Requirements Definition

Background

Magnegosyo Ta Day Program is primarily a project of Mayor Inday

Sara Duterte and is later revived by the Integrated Gender and

Development Division (IGDD) that extends help to women especially

those who are abused by their spouses. On a broad way, it provides

livelihood projects and loan applications for women to help economic

empowerment of women in Davao City.

The people behind the Magnegosyo Ta Day project doesn’t have a

system that will keep in track with their clients data, so the developers and

the working committee of the said project had discussed to develop a

system that will be an efficient and user friendly interface for the

management of the said project that will keep in track with the data of the

clients, the services that the clients may avail, the loan and payment they

may acquire and the milestones and outcome of the entire project they

availed.

A.2. Data Models (current Data flow diagrams including Context Diagrams and

Diagram 0, decision table)

(place diagrams here)

 A.3. Object Models

Use Case Diagram

(place diagrams here)

Class Diagram

(place diagrams here)

Sequence Diagram

(place diagrams here)

State-transition Diagram

(place diagrams here)

B. The Proposed System

B.1 Requirements Definition

Background

1. MAGNEGOSYO TA DAY is a system that is composed of

information system for the Integrated Gender and

Development Division. It is basically a system that will

provide an efficient and user friendly interface for the

management of the information system of Magnegosyo Ta

Day in a more comfortable, accurate and easier way.

2. MAGNEGOSYO TA DAY’s Capabilities:

- Provides summary for the client’s information

 - Accept client’s application

- Keep in track with the client’s data

Objectives

1. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

2. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

3. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

4. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

5. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

System Requirements (include output, input, process, performance,

control/security requirements)

Functional Requirements (what the system should do or provide for users;

functions of the system)

1 Add new records

2 Delete records

3 Enables to show up to date client information

4 The system has a log-in form to identify themselves using

the username and password

Nonfunctional Requirements (specifies criteria that can be used to judge the

operation of a system rather than specific behaviors)

1. User friendly interface

2. Efficient

3. It ensures that the data is protected from an unauthorized

user.
 B.2. Data Models (present Data flow diagrams including Context Diagrams and

Diagram 0, decision table)

(place diagrams here)

B.3. Object Models

Use Case Diagram

(place diagrams here)

Class Diagram

(place diagrams here)

Sequence Diagram

(place diagrams here)

State-transition Diagram

(place diagrams here)