Sei sulla pagina 1di 3

Kingfisher School of Business and Finance

Lucao District, Dagupan City


First Semester, A.Y. 2016-2017

BUSINESS
REQUIREMENTS
ANALYSIS

Prepared by:
Batac, Andre O. (Leader)
Ambrosio, Joana Grace
Bautista, Gina D.
Padilla, Desserie E.
Tique, Donna T.
Ubando, Hazel Jane M.
Vila, Nicole V.

Prepared for:
Mr. Moises A. Almendares, CPA
(IT15 Instructor)

October 2016

A. Introduction
Understanding user requirements is an integral part of information systems

design and is critical to the success of interactive systems. It is now widely

understood that successful systems and products begin with an understanding of

the needs and requirements of the users.

B. Requirements Description

Students designated as group accountants participating in the annual Market

Day event whose tasks involves the preparation of weekly Financial Statements

operate by keeping entirely written source documents such as receipts and

inventory lists want to ease their work by making use of a computer system wherein

they could record their transactions so as to lessen the papers they have to keep

and to avoid loss of data written only on pieces of paper. The users need to be

capable of:

Accessing the parts of the system containing data and fill-up forms

relevant to their positions and needs;


Inputting transactions in an orderly and chronological fashion;
Updating the data initially entered so as to aid users with Financial

Statement preparation and support decision-making concerning internal

affairs; and
Limiting data revision privileges so as to prevent fraud and misstatement

of figures and other relevant data stored in the information system.

C. Pattern for Stakeholder Requirements Description

The legend for the information listed below is as follows:

BP Business Process

ITP IT Process
A Activities
F Functions

*Note: This section involves the identification of the business processes, the IT
processes that support each of the business processes, the activities involved in each IT
process, and the functions in relation to each activity.

BP1: Accounting Process Automation


ITP1: User management process
A1: User activity
F1: Appoint specific users
F2: Train selected users
F3: Keep an eye on the performance of the selected users
F4: Remove previously selected users if proven ineffective
F5: Re-appoint new users then proceed to F2 onwards
ITP2: Inventory Management Process
A2: Counting activity
F1: Matching documents
F2: Recording invoices
F3: Add purchases
F4: Delete lost inventorys data
F5: Determine ending inventory
F6: Determine cost of goods sold
ITP3: Financial Statement Process
A3: Recording and Communicating Activity
F1: Input relevant data in the system
F2: Verify if all data entered are correct and are in line with current

transactions
F3: Integrate stored figures into ready-to-present formats
F4: Communicate results

D. Summary

Through this simple business processes pattern in our requirements analysis,

we have addressed common problems experienced by those who are in need of the

system, such as those who are having difficulty with delegating personnel to handle

an internal system, where we present the first business process in Part C along with

its correlated sub-processes and activities; dilemmas with keeping their system in

line and updated with current data pertinent to operations and reporting, which is

addressed in the second business process; and lastly, the most bothersome of them

all, which is the processing of Financial Statements itself, which needs ample time in

order to be represented faithfully.

Potrebbero piacerti anche