System Analysis and Design Solution Template Assignment

System Analysis and Design Solution Template
Module title: System Analysis and Design
Coursework 2: Review and Evaluation
1

Explain your role as a system analyst in context of the system you
designed in first assignment. 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)
System analyst is the person who uses the analysis and design
techniques in order to solve the business problems by improving the
technology. Being a system analyst the system design and framework
have been developed according to the system requirements (Panchal,
and et.al., 2018). There are various roles of the business analyst
which includes understanding the required improvements within the
system, designing of the system according to such requirements and
training of the staff in order to use the features and functionalities of
the same. Object oriented approach is used for the modelling of a
software or application and this is basically used at the beginning of the
system development life cycle. OO approach is the user friendly and
also it cannot understand the programming language or code to
implement such changes within the system. It either uses CBD
(Component based development) or RAD (Rapid Application
Development) approach during the development and analysis of the
system
Also in analysis phase, Object oriented models are mainly used in
order to fill the gap which has been raised between the problem and
the solution (Kobayashi, Matsumoto and Fukushige, 2018). This
approach is mainly used in the designing phase in order to refine the
classes, attributes, methods and structures that are identified during
the analysis phase, user interface, and backend data base of the
Library system management within QAHE university. The OO approach
allows the system annalist to handle all the operations and functionality
during the development, designing and maintenance of the system in
order to offer the improved features and functionalities. Along with
this, Object oriented approach mainly focus towards the structure and,
Prisyazhnyuk and Prisyazhnyuk, 2018). The Object oriented model is
beneficial to develop the effective software in may different ways
such as:
 This models allows the software developer to build the extra
featured system or implement the changes within the lower cost.
 This approach also allows the reuse of the components that are
used earlier to develop the software.
 In order to configure the large Library management system
within QUHE university, OO approach helps the software
developer to simplify the problems of integrated components.
 As the distributed system consists of multiple features and
functionalities in order to facilitate the library functions among
the students of the university. Therefore the Object oriented
model will simplify the such functionalities of the system.
However this approach also consists of some negative points which
2

may be considered as the disadvantages in in using OO approach
during the development of the system. Such disadvantages are
described below:
 data security is considered to be one of the major drawback of
using OO approach during the system development life cycle.
 Data is mainly exposed to whole program which can also be
considered as one of the disadvantage.
UML (Unified Modelling language) is a general purpose modelling
language which represents all the actors within their respective roles
and actions within the system. It helps in understanding and visualising
a system through a structure or a framework (Torre and et.al., 2018). It
also helps in understanding all the phases of the software development
life-cycle which displays the information flow of the system between
various stakeholders. Some benefits are:
 It is a convenient and effective way to of interaction between the
different stakeholders of the system.
 It also supports rage of applications.
 It is also used to represent the structural and behavioural aspects
of the system (Alsyouf, Al-Alami and Saidam, 2015).
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? Remember to
justify your answers (500 words)
During the development of the Library management system, various
lessons helps us in understanding the requirement of system
development life cycle. In order to develop a system design for Library
management system within the QAHE university, various requirement
has been analysed to make the effective system (Torre and et.al.,
2018). There are various key lessons which have helped me to create a
library management system which allow the university members to
efficiently record, issue and delete the book when not available in
stock. Various things that have been learnt from the development of
the system are:
 It will allow the administrator to record the details of the Library
book along with the detail of the author, publisher, title.
 It also help in learning about the function which facilitate about
the functionality which helps in efficiently adding a new item and
removing the book from the list if not available.
 It has been also useful in developing a function which helps in
adding the dues of the student if the book cannot be returned on
a due date (Stark, 2015).
 It also help in accessing the data regarding the loaned details of
student as to notify that how many times the same book is issued
over a specified period of time so that resources can be easily
3

accessible to the library management people.
A system development methodology can be referred as a framework
which is mainly used to structure, plan and control the process of
developing a information system (Wiesner, Nilsson and Thoben, 2017)
. In order to develop a Library management system within QAHE
university, there was Spiral Model which allow the software developer
to follow the development of the given software iteration that is based
on the project risk(Soja and et.al., 2015). This methodology is used in
developing a software because it can corporate the Waterfall,
Prototyping and incremental methodologies and also provides the
guidance in order to identify that which model best suits for the
software iteration.
According to me, there are various areas which needs a proper
improvements, if I get the opportunity to improve the Library
management system. I found that there is a no option and function
provided in the system, for the system generated suggestions to
recommend the similar books as a substitute which the user usually
search in the Library management system.
In addition, one more improvement I would like to explore within
the library system. It is online advance payment system, which will be
mandatory for the user in order to access any book. This function will
ultimately reduce the chances of dues. Also, if a person cannot return
the book on time and will never approach the library management
within 15 days then, the advance amount will be forfeit that particular
amount.
4

REFERENCES
Books and Journals
Panchal, D. and et.al., 2018. Fuzzy methodology application for
failure analysis of transmission system. International Journal of
Mathematics in Operational Research. 12(2). pp.220-237.
Kobayashi, H., Matsumoto, T. and Fukushige, S., 2018. A simulation
methodology for a system of product life cycle
systems. Advanced Engineering Informatics. 36. pp.101-111.
Kaganovich, A.A., Prisyazhnyuk, S.P. and Prisyazhnyuk, A.S., 2018.
An object-oriented information model for territorial system
management. GeoJournal. pp.1-7.
Torre, D. and et.al., 2018. A systematic identification of consistency
rules for UML diagrams. Journal of Systems and Software. 144.
pp.121-142.
Stark, J., 2015. Product lifecycle management. In Product lifecycle
management (Volume 1) (pp. 1-29). Springer, Cham.
Wiesner, S., Nilsson, S. and Thoben, K.D., 2017. Integrating
requirements engineering for different domains in system
development–lessons learnt from industrial SME
cases. Procedia CIRP. 64. pp.351-356.
Soja, P. and et.al., 2015. Determinants of enterprise system
adoption across the system lifecycle: Exploring the role of
economic development. Information Systems
Management. 32(4), pp.341-363.
Alsyouf, I., Al-Alami, A. and Saidam, A., 2015. Implementing product
design development methodology for assessing and
improving the performance of products. International
Journal on Interactive Design and Manufacturing
(IJIDeM). 9(3). pp.225-234.
5