Software Development Methodology

This document describes the software development methodology for Allure PTY limited company. It includes feasibility analysis, requirement specification, architectural design, hardware specifications, interface design, business process model, and state diagrams.

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

Context Model
The figure above illustrate the flow of shares
Leveled Set of Functional Models
The figure above illustrate how client order for a share
Design Document
Executive Summary
The software should be designed in such a manner that it saves a lot of time not only to the client
but also the whole management team of the company. It is a startup company which it’s 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 [9].
Architectural Design
Architectural design is used to represent the design of any software being developed [10]. It’s also
define as collection of software and hardware components to come up with a computer program to
solve a particular problem. For our case here it will be data centered as illustrated by the figure
below;
The
figure above shows how data is parsed in the company
Data can be parsed amongst the clients and the managers.

Hardware Specifications
a) Processor with 2 GHz
b) Minimum of 2 GB RAM
c) Internet connection
d) Minimum of 30 GB available disk space [11]
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. 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.

Detailed class Diagram
It is an object oriented design use to represent classes and how they relate with one another in the
program. Classes are denoted by boxes with class name at the top and it’s objects below the class
name. Under the class name there is attribute as well.
The figure above shows the detail class diagram for the software

Interface Design
(i) Wireframe Diagrams
It is the physical design of the expected software to be developed. It is visual representation of three
dimension objects for example the ones used in product design and development purposes. It is also
used to design 3D and 2D computer animations in web and applications development.
The figure above shows the prototype of the software to be developed

Business Process Models
This represent processes of enterprise so that one can analyze the current process in the system. It is
normally carried out by business analysts who normally provide solutions to problems involving
models.
Sequence
Diagrams

Login checker
Signup checker

System
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.
Interaction Diagrams
This is a group of objects that discuss how they collaborate to achieve one main purpose. The
diagrams below shows some examples and the messages being passed within those stated objects.
The interaction diagrams can be in UML form. It is used when you want to check on the behavior of
several diagrams.

Steps of signing up to the system
Steps of preparing shares for a client

State Diagrams
It is used to describe the expected behavior of the systems. The system should have a finite number
of states based on the system.

Figure above shows the state diagram for picking dates of the parcel
The
figure
above
shows
diagram
for login
process
The figure above is for clients logging in and adding balance to there accounts

The figure above is for booking appointment with the account manager
Conclusion
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. 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.
Reference

[1] J. Nielsen, "Ten usability heuristics of database," 2012, http://www.useit.com/papers/
heuristic/heuristic_list.html.
[2] Microsoft Corporation, "Site management cycle," 2013, http://msdn.microsoft.com/
library/en-us/comsrv2k/htm/cs_gs_concepts_ntqq.asp.
[3] C. Sherman, "Teoma vs. Google, round two," April 2, 2012,
http://searchenginewatch.com/searchday/02/sd0402-teoma.html.
[4] J. Raskin, "Looking for a humane interface: Will computers ever become easy to use?"
Communications of the ACM, vol. 40, no. 2, pp. 98-101, Feb. 2014.
[5] M. Phillips, "Reducing the cost of Bluetooth systems," Electronics & Communication
Engineering Journal, vol. 13, no. 5, pp. 204-208, Oct. 2011.
[6] H.L. O'Brien and E.G. Toms, "What is user engagement? A conceptual framework for
defining user engagement with technology," Journal of the American Society
for Information Science and Technology, vol. 59, no. 6, pp. 938-955, Apr. 2018.
[7] E.F. Vasechkina and V.D. Yarin, "Evolving polynomial neural network by means of
genetic algorithm: Some application examples," Complexity International, vol. 09,
2011, http://www.csu.edu.au/ci/vol09/vasech01/.
[8] O. Edelestein, E. Farchi, Y. Nir, G. Ratsaby, and S. Ur, "Multithreaded Java
program test generation," IBM Systems Journal, vol. 41, no. 1, pp. 111-125, 2012,
http://www.research.ibm.com/journal/sj/411/edelstein.pdf.
[9] R.R. Yager, "Multiple objective decision-making using fuzzy sets," International
Journal of Man-Machine Studies, vol. 9, no. 4, pp.375-382, Jul. 2014.
[10] K.-L. Wu, C.C. Aggarwal, and P.S. Yu, "Personalization with dynamic profiler,"
in Proceedings of the third international workshop on advanced issues of
e-commerce and web-based information systems, 2016, pp. 12-20.
[11] T. Hastie, R. Tibshirani, and J.H. Friedman, The elements of statistical learning:
Data mining, inference, and prediction, Springer Series in Statistics.
New York: Springer-Verlag, 2017.
[12] M.T. Maybury, "Intelligent user interfaces for all," in User interfaces for all:
Concepts, methods and tools, C. Stephanidis, Ed. Mahwah, NJ: Lawrence Erlbaum
Associates, 2018, pp. 65-80.
[13] ANSI T1.602-2010, Telecommunications-Integrated Services Digital Network
(ISDN) - Data-Link Layer Signaling Specification for Application
at the User-Network Interface.