ATMC ICT310 System Analysis and Design Task 2: SDLC Analysis Report

This assignment, focusing on ICT310 System Analysis and Design Task 2, provides a detailed exploration of the System Development Life Cycle (SDLC). The analysis begins with an overview of the system, emphasizing the importance of SDLC for Gabrielle, a YITSC partner, in managing operational functions. The paper delves into the six complex stages of the SDLC, including analysis and requirement gathering, system analysis, system design, coding, testing, and implementation. It also outlines core process activities such as planning, analysis, design, development, testing and integration, implementation, and maintenance. Additionally, the assignment discusses the Agile software development process, highlighting its ability to adapt to change and manage uncertain software issues, particularly in a business context. The document includes modeling and diagramming of events, use cases, and a use case description, providing a practical approach to understanding the SDLC.

ICT310
System Analysis and Design
Task 2

THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
Introduction/Overview of the system:
With basic understanding of project and event management, it is critical for Gabrielle
which is a business that is focused YITSC partner to have a comprehensive detail about Systems
Development Life Cycle. With interest on how to relate to the controller project, understanding
this process especially at the management level will pave way for a number of operational
concerns. First, it would offer a clear structure with which organizational functions would be
managed. This includes tracking employee performance from individual and departmental levels,
assessing the level of output in each organizational activity, tracking management functions,
tracking business activities as far as customers are involved, and many other roles. For a better
execution, it is necessary to understand a number of factors as far as the System Development
Life Cycle is concerned (Broad, 2013). One of the factors that must be well comprehended by
the management of the organization is the core processes that are involved in the entire life cycle
as far as controller projects are concerned. The second issues of concern that must be well
comprehended by the management of Gabrielle are the core process functions that are involved
in the cycle. The context of the paper reflects at the six complex stages that are involved in the
‘Systems Development Life Cycle for Gabrielle organization.
Systems Development Life Cycle (SDLC) Core Processes:
1. Analysis and requirement gathering
The first stage of the SDLC process is detailed gathering of the requirements and analysis
of related functions. The phase involves basic brainstorming and consists of a series of sub-
stages that must be handled with detailed care. Some of the sub-stages that are involved in this

process include feasibility analysis which is conducted to determine how much of the actual idea
on the ground can be put into visible action. It is necessary to have a clear plan on the desired
infrastructure of the software based on the specific organizational activities. Based on the fact
that Gabrielle is an open entity that is involved with many other business organizations, there is
need to come up with a clear map on what is actually need and the nature of interactions that take
place with the individual customer organizations (Broad, 2013). The aim of having this early
map is to ensure a better software infrastructure system that will offer the best customer
experience.
2. System analysis
System analysis is the second phase of the SDLC. At this stage, the entire system mapped
in stage one is defined in detail to offer a clear understanding of what it entails. At this level, a
detailed blue print of the various operational processes of the software system developed is
analyzed (Broad, 2013). If necessary, the system software at this stage may be further divided
into smaller portions for the sake of simplifying activities for developers, testers, designers, and
other professionals that may be involved in the cycle.
3. System design
System design is a critical stage of the SDLC. This determines the nature of activities that
will be managed by the software developed. In addition, it determines the kind of interface that
individual users will be involved while interacting with the organization. Physical integration is
performed for the sake of coming up with a clear image of what the infrastructure that is being
developed would look like (Kaur & Kaur, 2015). The process is managed with the help of a local
design system configured with professional system analysts. The designers or analysts that are

involved in this case work together with the use of specific software development tools to come
up with a unique system design that is consistent with the specific organizational functions of the
user entity.
4. Coding
At this stage, the software infrastructure is coded with the desired precision. The action
engages a team of software programmers assigned by the entity to work on the infrastructure and
from it come up with a targeted interface with which users and administrators would engage
with. Task allocation is very critical at this stage for programmers based on their unique test
skills (Kaur & Kaur, 2015). This is critical for the hiring organization as it allows completion of
the coding process in the most effective and efficient manner.
5. Testing
Testing of the designed software infrastructure is very critical. This is performed when
the software is ready. The system is sent to the testing department of the given organization
engaging a team of Quality Analyst. A series of tests are performed with the use of both manual
and automated testing tools to ensure that every component of the system based on specifications
that are provided by the user administrator have been configured effectively (Kaur & Kaur,
2015). If specific functions are not well configured, a detailed report would be provided and the
system sent back to programmers to ensure that such errors have been addressed immediately.
6. Implementation
This is the final stage of the SDLC. The software system is actively engaged through
running on various systems by individual users. If it proves to runs smoothly on the given

systems without any flaws, it is then made ready and considered ready for launch by the
organization. However, in the event of specific flaws, it is necessary to send it back to
programmers to ensure that all issues have been addressed. It is critical for the organization of
interest to ensure that a well-designed maintenance plan has been set in place (Kaur & Kaur,
2015). This will ensure that any instances of mechanical breakdowns have been addressed to
avoid compromising with the operational functions of the entire system.
SDLC Core process activities:
At the planning stage, the client organization needs to understand what they need from
the software system infrastructure. This involves understanding the specific needs of their clients
and their daily organizational functions. In addition, they must come up with a clear plan on their
desired interface system with which both administrators and customers would be interacting with
(McMurtrey, 2013). This is very critical as it defines the overall image with which their
organization would be publishing content for their customers such as advertisements and
company updates.
Analysis is very critical in the actual activities that are performed in the SDLC process.
At this stage, detailed analysis of the individual components of the software is highlighted. It is
upon the organization to give the team of programmers a clear breakdown of how they desire the
software system to reflect (McMurtrey, 2013). They must highlight specific entries and tabs that
are needed on the software based on the individual functional operations of the organization.
Gabrielle and their partners need to come up with a clear design that will affect the actual
interface that customers and other individual users will be engaging with. In this case, they offer
a clear mapping figure that will offer programmers a better channel of design when they are
implementing the actual software system. Most importantly, it must be well cited by the client

organization on the nature of design that is desired. If necessary, programmers may consider
offering samples of unique designs that have been previously completed to offer the organization
a better clue on what could be developed as well as what they would consider as their selection.
Development is very critical in the SDLC process and involves a number of activities. At
this level, software developers and programmers are actively engaged in the actual process of
designing a software system. The development process involves coding with the desired
functional units to come out with a clear interface that both administrators and other individual
users would be using (McMurtrey, 2013). For a better outcome, it is necessary to engage a team
of software developers and programmers that are well versed with the job to avoid errors that
would cost both time and money.
Testing and integration is very critical in the entire SDLC process. At this level, the
software system is channeled to the testing department and several tests done with the use of
both manual and automated systems. A clear audit of the process is the highlighted and the report
channeled to the management in question (Permatasari, 2017). With this, it then becomes
possible to highlighted specific errors that have been recorded and recommendations done on
how such errors can be eliminated.
Implementation of the software is done by several users on the ground. In this case,
several operations are performed including contacting customers on various ends, reaching out to
other organizations, designing a supply chain management system, sharing public information,
and many others (Permatasari, 2017). After this activity, it becomes public to the organization of
interest when the software system is finally launched for use.

Maintenance is one of the most critical activities in the SDLC process. While the
software system developed might be well configured to manage operational functions, it tends to
develop complications and system breakdowns as it ages. Therefore, designing a clear system of
maintenance will work to ensure that constant updates are done to more recent functions, and any
other breakdowns that may be experienced have been fully addressed by the technical
department.
Agile software development process:
The agile software development system is configured with a unique ability of creating
and responding to instances of change. It offers the provision of dealing with uncertain software
issues especially in a turbulent environment setting. In this case, it would offer a series of
abilities for the organization due to the fact that it functions with interactions of many other
business organizations. In this case, the agile system would offer a better platform in collection
of the most private information to gain a competitive mileage as far as the actual business
operations are concerned. For the case of this configuration, the design has been set to operate
more effectively that many other frameworks such as Extreme, Scrum, Feature-Driven
Development (FDD), and many others (Permatasari, 2017). It ability has been enabled through
formulation of specific frameworks and practices that are strictly based on the values and
principles that are highlighted in the Manifesto for Agile Software Development, bearing a total
twelve functional principals.
The Agile software development process lays keen focus on people and how they operate
on a daily basis. This ability and function is very critical when it comes to managing operational
activities that are connected with partner companies. In this case, solutions are evolved

effectively through collaboration between cross functional and self-departmental entities.
Basically, it offers a clear platform with which individual organizations that are connected to the
client organization can function based on their daily business functions. Effective
communication is a critical function that must be overseen on a daily basis. Customers have a
unique tendency of finalizing requirements before the actual development process begins. With
this platform, it is possible to foresee what customers think before engagement of business has
been initiated (Permatasari, 2017). Agile technology is the best chance that organizations can
have to ensure easily flow of business operations on a daily basis.
Part B - Modelling and Diagramming
Event Event Type Trigger Source Activity/Use
Case
System
Response/
Output
Destination
Set up business
entities
External
Event
User Initial
configuration
User
(YITSC
IT)
Setup
business
entities
List of stored
entities
User
Schedule backups External
Event
Scheduling of
backups
User Schedule
backups
Backup
schedule list
User
Time to Perform
backup
Temporary “Scheduled
Backup Time”
Create Offsite
Backup
Backup activity
log
CONTROLLER
Send Email to User State Event Backup
process
Completed
CONTR
OLLER
Send Email to
User
Summary
Report
User
Delete Scheduled
backups from
controller
External
Event
Service no
longer
required
User Remove
scheduled
backups
Deletion
confirmation
User

B. USE CASES DIAGRAM
c) Use Case Description
Title Create Offsite Backup Task
Actors System [Controller]
Preconditions A scheduled backup exists
Time for the scheduled backup has reached
Post conditions An offsite backup is created
A log of the backup progress has been sent to the controller
A summary report is sent to the user
Path 1. Check if it’s time for scheduled backup
2. Run backup process to an offsite location
3. Send notification log to the CONTROLLER
4. Controller receives final log and sends a summary to the user
Alternate path: 2.1 If backup fails send a notification to the controller

Question 3: Domain Modeling
a) Domain Model Class Diagram
B Design Class Diagram

References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Aljawarneh, S.A., Alawneh, A. and Jaradat, R., 2017. Cloud security engineering: Early stages
of SDLC. Future Generation Computer Systems, 74, pp.385-392.
Broad, J., 2013. Chapter 5-System Development Life Cycle (SDLC). Risk Management
Framework, pp.39-45.
Radack, S., 2009. The system development life cycle (sdlc) (No. ITL Bulletin April 2009
(Withdrawn)). National Institute of Standards and Technology.
Kaur, A. and Kaur, K., 2015. Suitability of existing software development life cycle (sdlc) in
context of mobile application development life cycle (madlc). International Journal of Computer
Applications, 116(19).
McMurtrey, M., 2013. A case study of the application of the systems development life cycle
(sdlc) in 21st century health care: Something old, something new?. Journal of the Southern
Association for Information Systems, 1(1).
Permatasari, R.D., 2017. Sistem Informasi Manajemen Aset dengan Metode SDLC (Software
Development Life Cycle) Studi Kasus STT Ibnu Sina Batam. Jurnal Teknik Ibnu Sina JT-
IBSI, 2(2).
Satzinger, J.W., Jackson, R.B. and Burd, S.D., 2011. Systems analysis and design in a changing
world. Cengage learning.