System Analysis and Design Solution Template

System Analysis and Design Solution Template
Academic year and term: 2017/2018 – Semester-2, Year 1
Module title: System Analysis and Design
Module code: QAC020C154S
Module Convener: Hassan Baajour
Module Tutor:
Student Id:
Deadline: 07/08/18 (no later than 2pm).
Coursework 2: Review and Evaluation
1

Explain your role as a system analyst in the project. Explain how did you use the OO
approach in designing the system and clarify the benefits of using the relevant UML
diagrams in your design. Remember to address the advantages and disadvantage of OO
paradigm and give examples as appropriate and cite your work properly.
As a system analyst in the project, the primary responsibilities included the system
modeling, behaviour analysis, and requirements analysis for the information system to be
developed for the football club. It was necessary to ensure that the functional and non-
functional requirements of the project were clearly understood and explained so that the
design and development team members could adequately design and develop the system as
per the specification. The object-oriented modeling approach was used in modeling the
system behaviour with the aid of the system models and diagrams. The first and the
foremost was the use case diagram in which the system behaviour was graphically
represented in the form of actors and their corresponding actions. The use case description
were also included so that the developers and designers could understand the
functionalities to be implemented and the depdencies associated (Broeze et al., 2004). The
functional and non-functional requirements had to be analyzed as a part of the
responsibilities. There were several requirements gathering techniques that were used to
collect the information sets. These techniques included interviews, brainstorming sessions,
observations, domain analysis, questionnaires, and group discussions to gather the data
sets. As a system analyst, the analytics was performed on these data sets to provide the list
of the functional and non-functional aspects. The class diagram and interaction diagrams
were also prepared and modeled to represent the relationship between the system modules
and entities.
There were benefits of UML diagrams and OO concepts in the project as the system
relationships, dependecies, and behaviour was modeled. There was extensive clarity that
was provided and added to the project with the aid of these diagrams and models which
further simplified the system design and development activties. There were a lot many
functional and non-functional specifications that were associated with the system. The use
of objects made sure that the role of each of the entities and the relationship between these
entities could be easily explained and represented (Lee and Youn, 2016). System security
was one of the essential system qualities that had to be maintained and the object oriented
concepts as encapsulations and data hiding provided the developers with the ability to keep
the condifential and private data hidden. Modularity is one of the essential concepts of
2