ICT310: DATABASE System Analysis and Design Report, ATMC, 2019

This report presents a comprehensive analysis of DATABASE system analysis and design, focusing on the application of System Development Life Cycle (SDLC) and Agile methodologies to the CONTROLLER project. The report begins by detailing the six core processes of the SDLC: planning, analysis, design, building, testing, and deployment and maintenance, explaining their relevance to the CONTROLLER project. It then contrasts the SDLC with Agile methods, outlining the six phases of Agile project management and highlighting the benefits of an iterative approach. The report further includes detailed use case modeling, event tables, use case diagrams, and use case descriptions to illustrate the functionalities of the CONTROLLER project. Finally, the report incorporates domain and design class diagrams to provide a visual representation of the system's structure and components, offering a complete overview of the project's analysis, design, and potential implementation using both SDLC and Agile approaches.

Running head: DATABASE
System Analysis and Design
Name of Student
Name of University
Author Note

1
DATABASE
Part A: Essay
Qiestion1: Essay
a). The system development life cycle (SDLC) can be described as a systematic approach of
explicitly breaking down the work into a number of phases, required for implementation of new
information system or modification of an existing information system. There are six core
processes linked with a SDLC approach (Isaias and Issa 2015). Each of the core processes in
SDLC approach are distinct from each other. The six processes of SDLC include, planning,
analysis, design, building, testing, Deployment and Maintenance. These core processes are
identified in relation to the controller project. The six processes of the SDLC approach are
indicated as follows-
1. Planning: In the planning phase of the SDLC approach, the main requirements linked with the
project is identified to understand the key inputs needed in the project (Alshamrani and Bahattab
2015). The planning process is mainly carried out by the project manager and the information
that are identified in this phase generally helps in conducting the feasibility analysis of the
project. The planning phase therefore identifies the main requirements of the project that are
analyzed in the next phase of project lifecycle (Rastogi 2015). The main risks associated with
any particular project are identified in the planning phase of any project. The information related
to project requirement along with the risks and the issues in the project helps in development of a
proper project plan. Planning one crucial need of project implementation as it documents the
approaches and the plan which will be followed for project implementation.
2. Analysis: After completion of the planning phase, the project moves on to the analysis phase.
Requirements analysis phase is linked with the defining the specifications of the project (Ali

2
DATABASE
2017). The analysis phase is directly linked with the planning phase that is already being
completed in a project. The analysis phase deals with examination of the main requirements
gathered for execution of the project and checks whether the plan that is prepared is capable of
implementation of the entire project (Satzinger, Jackson and Burd 2011). The analysis phase is
particularly important as it ensures that the undertaken project is ready to move into the design
phase. Special focus is provided to the requirements analysis phase as it documents the main
project requirements that are needed to be designed and developed when the project is in its
building phase.
3. Design: The design phase is important for a system development as in this particular phase the
design for building the system is developed. The design phase for execution of the project is
directly linked with definition of the major architectural modules of the product along with the
project communication (Velmourougan et al. 2014). The internal design of all the modules
associated with the building of a system is correctly defined in the design phase of the project.
4. Building: The building phase of the software development life cycle project is linked with the
actual implementation of the undertaken project. For software development projects, this stage is
linked with generation of the code of the software that is to be developed. For coding, the
developers need to follow the approved project plan along with the coding guidelines.
5. Testing: After completion of the building stage this phase tests the software that is coded. This
stage is linked with identification of the defects in the project so that the issues that are faced in
the project can be easily reported and fixed (Khan and Khan 2014). The testing phase is
important as it checks whether the project has reached the defined quality standard.

3
DATABASE
6. Deployment and Maintenance: The deployment and the maintenance phase of the project is
associated with formal deployment of the product that is being developed (Satzinger, Jackson
and Burd 2011). The deployment stage marks the end of the project which is followed by regular
maintenance.
The above discussed points indicate the six core processes linked with SDLC. These core
process relates to the CONTROLLER project.
b). The above section has identified the six core processes linked with SDLC model. Certain core
process activities are needed to be defined for each of the identified processes to complete the
undertaken CONTROLLER project as per plan.
1. In the planning phase, the major requirements of the CONTROLLER would be identified and
documented. The activity that is linked with the planning phase involves development of a
project plan, which should be approved prior to project implementation.
2. In the Analysis phase, the basic requirements of the CONTROLLER project are analyzed and
the plan developed for the project is amended accordingly.
3. The design phase is linked with development of the use case and class diagrams to provide the
team with an idea of the main functionalities of the project. Apart from that, another major
activity of the project design phase is development of the initial plan for the project.
4. The Building phase deals with coding the CONTROLLER project as per the requirements that
are identified at the start. It is one of the most important phases of project execution and the core
activity of this process is coding the CONTROLLER project.

4
DATABASE
5. The Testing phase follows the building phase of the project. The testing phase in important for
uncovering the bugs and the issues linked with the project and is further important for validating
if the initial requirements of the project is fulfilled.
6. The main activity of the final stage of the SDLC model is to deploy or launch the software that
is developed. This stage is also linked with the maintenance stage. The successful completion of
the testing phase is necessary to complete the deployment and the launch of the PROCESSOR
Project. With the successful launch of the project, the project can be marked as completed.
b). Agile methods can be applied for implementation of the CONTEOLLER project. Agile
Project Management or APM is an iterative approach for planning and guiding a project, such as
development of an information system. The iterations in APM is mainly referred to a single
development life cycle. Agile project method involves execution of a project in small sections
called iteration. Thus, each iteration is linked with a single development life cycle. After
completion of each iteration, the product that is being developed is reviewed to identify the
potential bugs in the project. If any issues in the execution of the project is observed, those issues
are rectified at once prior to moving to the next iteration.
The concept of agile in relation to the information system project involves execution of
the project in in iterative approach that guides the execution of the entire project (Conforto et al.
2014). The agile method is considered to be one of the most promising methods of execution of
the project as per the requirements of the clients. It is easier to manage different projects by
breaking it into several stages that generally involve constant collaboration with the stakeholders
and continuous improvement in the project as per the feedback of the clients.

5
DATABASE
In agile methodology as well, there are six phases, which ascertains successful execution
of a project (Dybå, Dingsøyr and Moe 2014). These six phases include, the concept phase, the
inception phase, the iteration and construction phase, the release phase, the production phase and
the retirement phase. The six phases mainly concludes the full agile process.
The CONTROLLER project, if implemented by making use of the agile methodology, it
can be guaranteed that the all the requirements specified by Roger will be fulfilled. The
CONTROLLER project will be implemented in sprints which indicate that a particular activity
will be completed and reviewed (Hoda and Murugesan 2016). In APM methodology, during the
execution of a sprint, the customer is expected to step back for allowing space to the project team
(Špundak 2014). However, at the end of the sprint, the project team releases the sprint to the
customers for their feedback. If any negative feedback comes, the project is revised accordingly.
In the concept phase of agile methodology, the viability of the project is envisioned and
prioritized. In the inception phase, the project team is formed to discuss the initial requirements
of the project. The iteration phase is the project phase that deals with the project development
work and the entire work is completed in an iteration basis (Serrador and Pinto 2015). The
release phase of project implementation further deals with effective quality testing, training and
documentation of the project that are needed to be executed. The production phase generally
keeps a track of the project that is being implemented and in this stage, the project is optimized
to eliminate the uncertainties in the project (Stare 2014). The retirement phase is the final phase
of agile methodology that indicates the end activities of the project.
The above discussed six phases concludes a full method life cycle in agile. If the
CONTROLLER project is executed by making use of the agile methods, the project will move

6
DATABASE
through the above discussed phases. If this method is applied, the CONTROLLER project can be
completed as per the expectation of Roger.
Part B - Modelling and Diagramming
Question 2: Use Case Modelling
a) Event Table
Event Event
Type
Trigger Source Activity/Use
Case
System
Response/
Output
Destination
Set up
business
Entity
Details
Primary The need of
Data Backup
IT team
of YITSC
Client
details and
Server
details
Client and
server
details are
registered
Recording
business
entity
details
Record
Details
Primary Validation of
the server
and client
Data host
Controller
Computer
details
System
validation
Computer
Back up
Data
Primary Client
requesting
data back up
Client Request
from client
Data
Backed up
Server
Stop Primary Identification IT Team Error Terminatio Computer

7
DATABASE
Service of Error YITSC recorded n
Spot Error Primary Evaluation
by File
transfer
Activity Log
File
transfer
Activity
Log
Spots Error Terminatio
n
Server
Run
Application
for Host
Client
server
backup
Primary Evaluation
of the entire
data backup
process
Processor Host Client
server
backup
Application
Successful
Data
backup
Controller
Storing
Client
Details
Primary Setting up
the business
entity details
IT Team Store Client
Details
Data Back
up
Controller
Storing
Server
Detail
Primary Setting up
the business
entity details
IT Team Store Server
Detail
Data Back
up
Controller
b). Use Case Diagram-

8
DATABASE
Figure 1: Use Case Diagram
(Source: Created by Author)
c). Use Case Description
Use Case Field Description
Use case name Store Business Entity details
Scenario The IT team of YITSC wants to store the
business entity details
Triggering Event Data back up
Brief Description The IT team of YITSC will at first store the

9
DATABASE
business entity details along with the server
and client details for data back up in server
Actors IT team of YITSC, client and server
Related Use Cases It is related to Back up of Data
Stakeholders IT team of YITSC, Roger
Pre-conditions The controller should function normally
No error should be spotted
Post Conditions The details should be stored in correct format
Flow of Activities Actor System
IT team of YITSC Records Data
Client Sends data for back
up to server
Exception Condition 1. An error is spotted
2. The process is terminated automatically
after 6 months
Question 3: Domain Modelling
a). Domain Model Class Diagram-

10
DATABASE
Figure 2: Illustrating Domain Model Class Diagram of CONTROLLER Process
(Source: Created by Author)
b) Design Class Diagram
Figure 3: Illustrating the Design Class Diagram
(Source: Created by Author)

11
DATABASE
References
Ali, K., 2017. A Study of Software Development Life Cycle Process Models. International
Journal of Advanced Research in Computer Science, 8(1).
Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall
model, spiral model, and Incremental/Iterative model. International Journal of Computer
Science Issues (IJCSI), 12(1), p.106.
Conforto, E.C., Salum, F., Amaral, D.C., Da Silva, S.L. and De Almeida, L.F.M., 2014. Can
agile project management be adopted by industries other than software development?. Project
Management Journal, 45(3), pp.21-34.
Dybå, T., Dingsøyr, T. and Moe, N.B., 2014. Agile project management. In Software project
management in a changing world (pp. 277-300). Springer, Berlin, Heidelberg.
Hoda, R. and Murugesan, L.K., 2016. Multi-level agile project management challenges: A self-
organizing team perspective. Journal of Systems and Software, 117, pp.245-257.
Isaias, P. and Issa, T., 2015. Information system development life cycle models. In High Level
Models and Methodologies for Information Systems (pp. 21-40). Springer, New York, NY.
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.
Rastogi, V., 2015. Software development life cycle models-comparison,
consequences. International Journal of Computer Science and Information Technologies, 6(1),
pp.168-172.