Software Development Methodology

Software Development Methodology
Table of content
Executive Summary ....................................................................................... 2
System Description .................................................................................. ......2
Scope .............................................................................. ..........................2
Feasibility Analysis ...................................................... ..................................3
Requirement specification .............................................................................. ..4
Assumption ................................................................................. ..............4
Case Diagrams .................................................................................. .........5
Context model .................................................................................. ..........5
Architectural Design .................................................................................. ...6
Hardware specifications .................................................................................7
Class Diagram .................................................................................. ......... 8
Interface Design .................................................................................. .......9
Business process model .................................................................................9
Sequence Diagrams .................................................................................. ...10
Interaction Diagrams .................................................................................. 12
State Diagrams .................................................................................. .......14
Conclusion .................................................................................. ............15
Reference .................................................................................. .............16

Specification Document
Executive Summary
Software saves a lot of time not only to the client but also to the management team in Allure PTY
limited company. Allure PTY is a startup company which whose vision is to sell shares to the
clients. We need to create a software that helps the company achieve better results within the
shortest time possible with minimum effort on it.
System Description
In our software we should make sure that a client receives real time notification about the market
improvement and their balance in the account. If they have less balance in the account then they
should be notified so that they can deposit the funds to the account for the account managers to
purchase the shares. This kind of notification helps clients in taking an advantage of the market by
purchasing cheap share from the company. They should also receive a tax report for every month
and also on yearly basis.
It should also ease the work of the account managers so that whenever they interview new clients
they store the information on the client’s profile. This information will in turn be used to determine
the equities each will have and there risk profiles. The client’s profile also helps in matching the
account manager to be assigned.
Scope
The software will ease the work of the funds manager which is currently time consuming. The
software should automatically buy parcel and keep the number of shares in each parcel and the date
they were purchased. The total tax will be calculated based on the age of the parcel for each client
in the company. Whenever a sell order is executed by the account managers, the system should
deduct it from the old parcel and if it’s not enough it deducts it from the older parcel. The software
should also have a place for storing client’s parcel and make it available for the account managers
and the client. The system should finally calculate dividends based on the shares each client hold in
the company. The dividends are deposited in the client’s portfolio which will eventually be used for
generating tax reports and send to the client’s account. It should also be used for purchasing new
shares in the company by the account managers.

Feasibility analysis
Feasibility analysis determines strengths and weaknesses for a software to be developed in a
company [1],[4],[12]. It also helps in determining risks involved in developing the software as well
as all the assets required to develop it. There are three types of feasibility;
a) Technical feasibility. Focuses on the technical needs to build a software.
b) Economic feasibility. This involves cost for developing a software [2]
c) Operational feasibility. Focuses on the fitness of the proposed software in a company.
d) Schedule feasibility. Focuses on the time taken to complete the development of the project.
Requirements specification
(i) Functional
The client receives real time notification about the market improvement and their balance in the
account. If they have less balance in the account then they should be notified so that they can
deposit the funds to the account for the account managers to purchase the shares. This kind of
notification helps clients in taking an advantage of the market by purchasing cheap share from the
company. They should also receive a tax report for every month and also on yearly basis. [3]
(ii) Non Functional
The software should automatically buy parcel and keep the number of shares in each parcel and the
date they were purchased. The total tax will be calculated based on the age of the parcel for each
client in the company. Whenever a sell order is executed by the account managers, the system
should deduct it from the old parcel and if it’s not enough it deducts it from the older parcel. The
software should also have a place for storing client’s parcel and make it available for the account
managers and the client. The system should finally calculate dividends based on the shares each
client hold in the company. The dividends are deposited in the client’s portfolio which will
eventually be used for generating tax reports and send to the client’s account. It should also be used
for purchasing new shares in the company by the account managers [5].

Assumptions
a) Technology to be used.
b) Facilities to be used for instance data centers
c) Infrastructure for instance network [6]
d) Design approaches
e) Business context
f) Budget of developing the software [7]
g) Methodology to be used
Case Diagrams
Case diagrams are used to demonstrate different ways in which users can interact with the system. It
summarizes how users interact with the system. Actors are the users that are expected to interact
with the system. It can be a person an organization or another system accessing the developed
system. They are external objects giving or taking away data from the system.
Sign in diagram
Sign up diagram