System Analysis and Design Solution Template

This solution template discusses the role of a system analyst in a project, OO approach in designing the system, and benefits of using UML diagrams. It also covers key lessons learned from the project and suggests a suitable software development methodology to use. The text includes references and is written in APA style.

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. (500 words)
The object oriented development is used for the development of a softeare in multiple stages and
in the priliminary stage of the development process the requirement of the software is analyzed.
The system analyst works with the development team for defining the purpose of the system and
the details needed for the implementation of the software is ignored in this priliminary stage. A
model is created without the implementation of the constraints and the technology needed for
the development of the project. For the development of the model different diagrams such as use
case, collaboration, system sequence and activity diagram are used. The objects are identifid with
the details such as behaviour, attributes and interracton between them (Gulia and Choudhury
2016). In the object oreineted analysis method the requirements are elicited and specified for the
development of the conceptual model. The requirements are described with the means of the use
case diagram and the conceptual model is created for the identification of the main objects
needed for the development of the project. After the identification of the objects they are refined
and their relationships and behaviour are demonstrated with the means of simple diagram such
as activity or system sequence diagram.
The sequence diagram is also known as event diagram and used for the demonstration of the
interaction of the classes and objects for a particular scenario and manages the sequence
messages that are needed to be exchanged with the different objects for the management of the
scenario (Buede and Miller 2016). For the development of the sequence diagram a use case
diagram is needed to be created and used for creating a logical view of the system.
The interraction of the object for a particular use case is demonstrated using the collaboration
diagram and it helps in clarification of the roles of the object for the management of the flow of
the information.
The objects are defined with the help of the class diagram and the conceptual model is mapped to
the class diagram for the demonstration of the behaviuor, interraction and attributes. The classes
are described with the help of the class diagram.
The flow of the data packet between the process and the system is demonstrated with the help of
the activity diagram.
There are several advantage of using the object oriented development for the development of a
software project and are given below:
 The changes in the requirement of the project can be managed with adding minimum cost
in the development of the project.
 The components used in the project can be reused and integrated with the other
components for getting the required result and thus reduces the time needed for the
completion of the project (Iqbal and Bajwa 2016).
 It is possible to simplify the problem and reduce the complexity of the project
The following are disadvantages of the object oriented development approach:
 The size of the program are much larger and it needs more memory
 It needs much planning for writing a single code and the coders needs much time for
writing the codes
 It is a slower process due to its large size and more resource demanding
List the key lessons you learned from this project. Clarify what would you do differently if
you repeat it and how you can improve the areas which did not go well. Suggest a suitable
Software Development Methodology to use to develop the system you designed?
2

Remember to justify your answers (500 words)
From the project of system analysis and design we have learned the use of different UML design
techniques that can be used for the development of a software or an information system. The
report is completed after researching on the different approach of software development and
identification of the flow of messages between the system components used for the development
of the solution. The design model is created for adding details and help the programmer to
develop the codes and reduce the error in the final build product.
For the project where the requirement is well understood the spiral model can be implemented
because it would help the project team members to develop the project within minimum cost and
time. For the improvement of the areas a risk assessment should be don and the alternatives of
the project should be identified (Abrahamsson et al. 2017). The spiral model can incorporate the
different models based on the scenario and can be highly customized and it can provide guidance
to the development team for the accommodation of the changes in the development of the
project.
For the improvement of the project a meeting must be arranged with the stakeholders and a brain
storming session should be arranged such that new ideas can be used for the development of the
project. The improvement can also be made after the deployment of the project from the
maintenance phase based on the feedback given by the user.
For the development of the software the incremental model is proposed because it can help in
reducing the risk of uncertainty and changes in the final project. The risk is eliminated by breaking
the project in smaller segments and thus it becomes easy for the development team to change it
during the development process(Stark 2015). The incremental model uses a series of mini
waterfall model where the phases of the waterfall model are followed for the development of the
small segment of the project. It have the potential for exploiting the knowledge that is gained
during the development of the previous segment and add it for the development for the later
segments. The model posses a moderate control on the development of the project and this is
used for the documentation and reviewing the approval of the project. Concrete evidence can be
provided to the stakeholders regarding the status of the project and reduces the risk of
integration of data (Butterfield et al. 2016). The series of implementation can help in quicker
delivery of the product release and the implementation of the later segments helps in
identification of the incremental changes and isolating the issue for making adjustment in the final
product such that there is no negative impact on the organization.
References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
3

methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Buede, D.M. and Miller, W.D., 2016. The engineering design of systems: models and
methods. John Wiley & Sons.
Butterfield, R., Maksuti, S., Tauber, M., Wagner, C. and Bicaku, A., 2016. Towards
Modelling a Cloud Application's Life Cycle. In 6th International Conference on Cloud
Computing and Services.
Fuggetta, A. and Di Nitto, E., 2014, May. Software process. In Proceedings of the on Future
of Software Engineering (pp. 1-12). ACM.
Gulia, S. and Choudhury, T., 2016, January. An efficient automated design to generate
UML diagram from Natural Language Specifications. In Cloud System and Big Data
Engineering (Confluence), 2016 6th International Conference(pp. 641-648). IEEE.
Iqbal, U. and Bajwa, I.S., 2016, August. Generating UML activity diagram from SBVR rules.
In Innovative Computing Technology (INTECH), 2016 Sixth International Conference on(pp.
216-219). IEEE.
Śniegula, A. and Glinka, K., 2017. Usability Testing in Web Development Life
Cycle. Przedsiębiorczość i Zarządzanie, 18(4, cz. 1 Agile Commerce-świat technologii i
integracji procesowej), pp.131-145.
Stark, J., 2015. Product lifecycle management. In Product Lifecycle Management (Volume
1) (pp. 1-29). Springer, Cham.
4