System Analysis and Design

This document discusses the System Analysis and Design of the CONTROLLER project, including the SDLC lifecycle and Agile methodology. It also includes modelling and diagramming of the project, such as the event table, use case diagram, use case description, domain model class diagram, and class diagram. The essay explains the six core processes of SDLC and how they were applied to the CONTROLLER project. It also discusses the Agile methodology and how it can be used in the CONTROLLER project. The document includes references for further reading.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author’s note

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Part A – Essay..................................................................................................................................2
Part B - Modelling and Diagramming.............................................................................................6
Event Table:.....................................................................................................................................6
Use Case Diagram:..........................................................................................................................8
Use Case Description:......................................................................................................................8
Domain Model Class Diagram:.....................................................................................................10
Class Diagram:...............................................................................................................................11
References:....................................................................................................................................12

2SYSTEM ANALYSIS AND DESIGN
Part A – Essay
The process of SDLC includes a series of processes that are required while producing a
software with high quality and low cost within the shortest possible time (Mishra and Dubey
2013). The entire process of SDLC includes a structured plan depending upon the way by which
the software would be developed, altered, maintained while replacing the existing software
system (Kaur and Sengupta 2013). The core process that falls under the process of SDLC
lifecycle includes-
1. Identifying the current problems
2. Planning the requirements
3. Designing the requirements
4. Building the actual code
5. Testing the deficiencies and defects
6. Deploying the system
7. Maintaining the functioning of the software with the latest updates.
As per the case study based on the CONTROLLER project is concerned, the SDLC
lifecycle can be applied effectively following its core six processes.
In the first process, the current problem that is identified with the CONTROLLER project
is related to the backing up data in a secured way which was the legal requirement identified for
the Trust Account Management. In this case the organization was unsure about the way by which
they should provide backup to the data of the clients as many of them prefer to use the cloud-
based platform while some of them preferred to backup their data to their own server.

3SYSTEM ANALYSIS AND DESIGN
In the next stage after figuring out the problem, the organization came up with the series
of requirements that would help them in meeting up the basic client’s requirements and pointed
out the requirements which includes the client system where all the data that needs immediate
backup will get stored, a server backup application that store the data that are received from the
client backup application, and a controller that would be remotely set up to run the server backup
application while help in running the client backup application simultaneously
In the corresponding stage of the process, the senior partner of the company along with
his team member successfully designed and tested the applications that are required for CLIENT
and the SERVER. Here they adapted the rsync open source application that will take care of the
transferring of all the data while preparing them for backup. The designed stage also included
working on a secured virtual private networking system that will work between the CLIENT,
SERVER as well as between the CONTROLLER.
In the building phase, the senior partner who was accountable for the entire system
development, represented the way by which the centralized system would work while defining
the ways by which the controller would process while storing each and every entities of the
business.
A detailed testing is thus carried out by the way the system would process data backup
within the organization in a secured way and finally the system was deployed within the
organizations data backup process (Khan and Khan 2014).
The Agile methodology is referred to the process which is applied in the course of
continuous based iteration of the testing and development done in the making of a software-
based application project. The methodology focuses on the development and testing procedures

4SYSTEM ANALYSIS AND DESIGN
that are applied during the software development lifecycle based on the project (Abrahamsson et
al. 2017). The activities can be evaluated as concurrent in nature unlike the Waterfall model.
The software development process that follows the Agile methodology gives stress and focus on
the on basically four main values.
The values are as follows:
i. The interactions of the individual and of the project team are more emphasized on
the process and the tools.
ii. The comprehensive documentation is paid less attention than the current working
software (Kruchten 2013).
iii. The agile methodology emphasizes on the collaborations done with customer than
on the negotiation on the contract.
iv. The methodology believes in structures which are responsive to the required
changes than the structure that always follows a plan.
The agile methodology is the type of methodology where the requirements and the
outputs develop by the collaborative nature that takes place between the project team or the self-
organizing based cross functional team (Dingsøyr and Moe 2013). The procedure and the steps
of the agile methodology enable the methodology to produce and deliver the end result values or
the outputs faster in time than the other methodologies. The output is received with a higher
quality that has the ability to respond to the required changes. The Agile methodologies have
been differentiated in many parts for the development of the project as per the requirements. The
Scrum and the Kanban methodologies are the two main and largely used methodologies under
the agile methodology for the development of a software-based project.

5SYSTEM ANALYSIS AND DESIGN
The entire CONTROLLER project will be developed successfully using the Agile
Methodology where each of the project details will be broken down into smaller parts till its
delivery. Maintaining the agile project methodology within the overall CONTROLLER project
will help the organization to bring in the changes that are required for backing up the data within
the entire system in a secured way Applying the Agile project methodology in the
CONTROLLER project will help Roger and his team to ensure the working principle of the
overall CONTROLLER service as per the requirements of the system maintaining the estimated
budget for the development of the system. Using the Agile methodology within the entire project
will thus help the team to respond to any changes over the flow of plan that was designed during
the SDLC stages.

6SYSTEM ANALYSIS AND DESIGN
Part B - Modelling and Diagramming
Event Table:
Event Event
Type
Trigger Source Use Case System
Respons
e
Destin
ation
Adding
Business
Client
Entry Client request to
register into the
system
Business
client
Register
Business
Entity
The
Identifica
tion
number
of
Business
Entity
YITSC
Adding
Supplier
Entry New supplier
details stored in
system
Supplier Register
Business
Entity
Supplier
ID
YITSC
Adding
Host
Controller
Entry Supplier add new
host controller
into system
Supplier Add New
Host
Controller
New
storage
location
available
for
hosting
Supplie
r
Customer Request Customer want Business Request Backup Busines

7SYSTEM ANALYSIS AND DESIGN
Request
Data
Backup
to store data into
servers
Client Storage Task
Details
s Client
Customer
Store Data
Storage Customer sends
data to server
Business
Client
Store Data
into Server
Storage
status
Supplie
r
File
transfer
activity log
Response System sends a
file transfer
activity log after
client store data
into server
System Receive File
Transfer
Activity
Log
Email
sent to
Roger
Control
ler
Email
Notification
Response System sends a
mail to roger
after a log is
created
Controller Send Email
Notification
Summary
Report
Roger
Backup
Task Create
Task System create a
backup task
when customer
request for data
storage
Controller Create
Offsite
Backup
Task
Storage
start and
interval
date
Control
ler

8SYSTEM ANALYSIS AND DESIGN
Use Case Diagram:
Figure 1: Use Case Diagram
(Source: Created by Author)
Use Case Description:
Use Case Name Create Offsite Backup Task
Use Case ID Controller_UC_01
Scenario After business client send a request for storage, the controller create a
backup task which will monitor and guide the client data storage
activities
Triggering event Backup Task Create

9SYSTEM ANALYSIS AND DESIGN
Brief description The business client needs to send a request to YITSC in order get
permission for storing data into storage. In response to the request, he
controller search for available storage and create backup task which has
start date and interval of storage
Actors Controller
Related use cases Request Storage
Stakeholders Business Client, YITSC and Supplier
Preconditions The business client data must be stored into the system already
Postconditions A backup task start date and interval is created
Flow of Activities Actor System
Business client send request YITSC teach check client
existence
Controller create backup task with
start and interval
Exception handling 1. Client has already reached backups limit
2. Client is blacklisted

10SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram:
Figure 2: Domain Model Class Diagram
(Source: Created by Author)

11SYSTEM ANALYSIS AND DESIGN
Class Diagram:
Figure 3: Class Diagram
(Source: Created by Author)

12SYSTEM ANALYSIS AND DESIGN
References:
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Dingsøyr, T. and Moe, N.B., 2013. Research challenges in large-scale agile software
development. ACM SIGSOFT Software Engineering Notes, 38(5), pp.38-39.
Kaur, R. and Sengupta, J., 2013. Software process models and analysis on failure of software
development projects. arXiv preprint arXiv:1306.1068.
Khan, M.E. and Khan, F., 2014. Importance of software testing in software development life
cycle. International Journal of Computer Science Issues (IJCSI), 11(2), p.120.
Kruchten, P., 2013. Contextualizing agile software development. Journal of Software: Evolution
and Process, 25(4), pp.351-361.
Mishra, A. and Dubey, D., 2013. A comparative study of different software development life
cycle models in different scenarios. International Journal, 1(5), pp.64-69.