2.2.

Goal Service Model Analysis

Our group try to implements one of the SOMA technique which is the Goal Service
Model Analysis to define the services of the application.

Goal and Sub goals KPIs Services

1. To keep track of money of the Keeping the records on how
user and give the views on what much the balance insert in the
the user spend his/her money system and the purchases made
by the user on various
categories.
1.1. User must have an account User has account. User can
that is maintained by system. Any manage his categories. User can
activities in the account must be enter purchases. User can view
kept and recorded. The purchases reports based on their needs.
made based on categories and
must be reported to users.
1.1.1. User can have an account System must provide account - Register user
management o Create user
o Create account

1.1.2. User can have his own User can manage his own - Manage Categories
categories categories that is unique for o Add category
himself
1.1.3. User can track his own User can insert transaction of - Insert purchase
purchases. purchases. transactions
o Insert transaction
o Insert item

1.1.4. User can have reports on System provides user with two - Generate Reports
his previous purchases. types of reports that are by o Report by
Transaction date and category. transaction date
 o Report by category

2.3. Functional Requirements

Functional requirements describe the behaviors (functions or services) of the system that
support the user’s goals, tasks or activities. We defined the functional requirements from
the services that is provided by Goal Services Model Analysis. The functional
requirements of our application are,

1. Register a new User for a new Account

Users need to create a new account before they can add balance and keep record
of their purchase transactions.

2. Login User

System has to make sure that the user is the user that have authorization to access
the system so the user must be authenticated by login process.

3. Add balance to the account

Users need to add balance before they can put input purchases that they already
made.

4. Create Item Category

Users can have their own item categories for items that they entered. The category
is personalized for users for their own using.

5. Create Transactions

User can Add item name, price, description and the purchase date in the
transaction.

6. View Reports

a. View all transaction by transaction date

b. View Transaction by category

2.4. Non Functional requirements
Non-functional requirements include the constraints and qualities of the application.

1. User Location varies

a. Web based system

The user of the system expect to be able to keep track of his/her money in
the pocket anywhere he is as long as there is an internet connection for
accessing the system. For accomplishing these objectives, the system is
created on web based architecture systems.

2. Security

a. User Authentication

To ensure the security of the user, the system needs to authenticate on

every user before the user can access the system. The way to do this is to
make sure that the user needs to login first. The user information will be
saved in session.

b. Encrypting password in the database

For completely protecting the user’s information from outside or from the
system’s administrator itself, the system encrypt the password when
storing into the database. So even if the administrator of the system open
and retrieve the data on the database, password information of the user is
in encrypted format and cannot be stolen.

c. HTTPS

For securing the systems we need to implements the HTTPS protocol to

make sure that the information given by the user is secure and can not be
used by other person who is not authorized to access those information.

3. Performance

a. Separating the Database layer with the Business layer and Application
layer.

The architecture of the system needs to be design with clear separation

between Application Layer, Business Layer and Database Layer. To
implement this architecture we put the database in one machine separated
in one machine and the application and business layer will be put in 2