System Analysis and Design

This document provides an overview of system analysis and design, including use case diagrams, conceptual class diagrams, and interaction diagrams. It explains the purpose and components of each diagram and how they contribute to the development of a system. The document also includes examples and explanations of the diagrams in the context of an online library system.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author’s note:

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Use Case Diagram:......................................................................................................................2
2. Conceptual Class Diagram:.........................................................................................................6
3. Interaction Diagrams:..................................................................................................................8
3.1 Sequence Diagram:................................................................................................................8
3.1 Collaboration Diagram:.........................................................................................................9
3.1 Activity Diagram:................................................................................................................10
Bibliography:.................................................................................................................................13

2SYSTEM ANALYSIS AND DESIGN
1. Use Case Diagram:
In UML (Unified Modelling Language), a use case diagram is required for adding current
system user (actors). Apart from this, it also highlights their interaction with the system (Soares
2017). Use case diagrams are required for discussion with system or applicants with which user
can interact with the system. The main focus on the system application is to provide help to the
entities. UML is a well-known toolkit which is required for building diagrams. Use case
diagrams provides oval shape where stick figures represent the actors (Cunha, Garis and Riesco
2015). The actors aim to take part in the system for creating a line between actor and use case.
The major components of Use diagram are
Actors: User tends to interact with the given system. An actor in Use case can be
anything like person, organization or outside system that can interact with the application or
system. There can be any external objects which produces or consumes data.
System: The consequence of interaction and action tend to lie between the given actor
and system (Osman and Chaudron 2018). In many cases, system may be also referred to a
scenario.
Goals: It is the end result in most of use case. A successful diagram aims to describe
various kind of activities and variants which is required for reaching a particular goal.
The overall notation of Use case is very much straightforward and does not require any
kinds of symbol like other UML diagram.
Use Cases: The horizontal shaped oval represents different uses which a user may have.
Actors: Stick figures aims to represent the people who employ the use case.

3SYSTEM ANALYSIS AND DESIGN
Association: It is the line or connection between actors of the use case diagram (Septian,
Alianto and Gaol 2017). In some of the complex diagram, it is very much important to
understand the actors that are associated within a Use case.
System boundary boxes: A box is nothing but a proper system which tends to scope up
with all the use case. All the required use cases are considered to just outside the box which is
outside the scope of the system.
Packages: A UML shape helps the user to put various elements on a single group.
Figure 1: Use Case Diagram of ICIMS
(Source: Created by Author)

4SYSTEM ANALYSIS AND DESIGN
Use Case Name Request to enroll
Use Case ID Stu_uc_01
Actors Student
Stakeholders ICIMS
Associated Use Cases Enroll Student
Pre-condition The student should have minimum qualification for applying to
course
Activities User System
Student open website
Student request to enroll for
course
System check course availability
System provide enrolment form
Student enroll for course System send request to admin
Admin allow enrolment Inform student
Post-conditions The student cannot enroll for another course until current one is
complete
Exception Student is expelled
Student has failed in course
Use Case Name Mark Assignment
Use Case ID Tutot_UC_02
Actors Tutor
Stakeholders Tutor, Admin, Student and ICIMS

5SYSTEM ANALYSIS AND DESIGN
Associated Use Cases None
Pre-condition Tutor must be assigned to the assignment class
Activities User System
Tutor open Moodle
Tutor open assignment section System show details of student
submission
Tutor mark assignment System store mark
System send data to ICIMS
Tutor review mark
Post-conditions Marks are shared with the system by Moodle
Exception Examination is cancelled
Review Grades: Admin can review the grades of the student using ICIMS. The actor for
this use case is Admin. There is no associated use case with it. The precondition for this use case
is that course’s all assignments must be marked by the tutor. The post condition is that admin
cannot change grade.
Record, Delete, Search and Update Staff Data: Admin can do authorized operation on
the stored staff data in the ICIMS. The actor for this use case is Admin. There is no associated
use case with it. The precondition for this use case is that admin must be logged in to the system.
The post condition is that admin changed, stored or searched staff data.

6SYSTEM ANALYSIS AND DESIGN
Record, Delete, Search and Update Student Data: Admin can do authorized operation
on the stored student data in the ICIMS. The actor for this use case is Admin. There is no
associated use case with it. The precondition for this use case is that admin must be logged in to
the system. The post condition is that admin changed, stored or searched Student data.
Record, Delete, Search and Update Course Data: Admin can do authorized operation on
the stored Course data in the ICIMS. The actor for this use case is Admin. There is no associated
use case with it. The precondition for this use case is that admin must be logged in to the system.
The post condition is that admin changed, stored or searched Course data.
Track Attendance: Admin can do track or monitor the attendance data of student for all
the course stored in the ICIMS database. The actor for this use case is Admin. Associated use
case with it is Record/Update Student Attendance. The precondition for this use case is that
admin must be logged in to the system. The post condition is that admin all the attendance data is
available on the admin screen.
2. Conceptual Class Diagram:
Class Diagram is considered to be as one of the useful kind of diagram in UML which is
needed for mapping out the structure of the system (Uke and Thool 2016). It is done by modeling
various classes, operation and attributes, and relationship between various objects. UML is
considered to be as a standardized model which is required for object-oriented programming
approach. Classes are considered to be building block of objects while class diagrams are
considered to be building blocks of UML. The shape of the class comprises of rectangle along
with three rows. The top part of this rectangle comprises of class name, middle row is all about
attributes and bottom parts expresses the method of operation of class (Storrle 2016). Both

7SYSTEM ANALYSIS AND DESIGN
classes and subclasses are collectively considered for establishing relationship between each of
given objects.
Figure 2: Conceptual Class Diagram of ICIMS
(Source: Created by Author)
The conceptual class diagram presented in the figure 2 shows the student registration,
attendance and marking related information. The class diagram consist of association,
generalization and composition relationship mainly. The generalization has been shown using the
course class. It has been assumed that classes are of two types such as full time course and part
time course. The full time course starts in specific quarter of a year. On the other hand, the part
time class starts at any time and lasts for few weeks. These child class has its own set of
attributes that forces to include generalization. The student can register for course. The register()
method declared in the course class. The register() method also calls the approve() method of
admin class to confirm an enrolment. The attendance will be tracked using the assignment for
which the class is held and the specific student attending the class. The status attribute state
whether the student was in the class or was abscent.

8SYSTEM ANALYSIS AND DESIGN
3. Interaction Diagrams:
UML interaction Diagram aims to provide a much high level of abstraction of given
model. It is considered to be as one of the variants of activity diagram where nodes tend to
interact. The diagram aims to provide an overview of the flow of control of interaction which
highlights the flow of activity between the diagrams (Soares 2017). Interaction diagram
comprises of two kind of diagrams that is sequence diagram and a collaboration diagram.
3.1 Sequence Diagram:
Sequence diagram comes up with some basic objects It is very much important to have an
understanding with respect to time sequence for the flow of message in any sequence diagram.
The flow of message in sequence diagram is method or way to call for an object.

9SYSTEM ANALYSIS AND DESIGN
Figure 3: Sequence Diagram of ICIMS
(Source: Created by Author)
The sequence diagram is created for showing the objects of ICIMS system interact with
each other dynamically for processing student enrolment. The student object has been shown as
an actor object as student refers to a human being who manually input data. Now, the lifeline
starts with student request for enrolment in a course. The message is sent to the course object.
The course object then triggers the courseAvailability() method. This method checks whether
the sits of this course is full or available. If the course is available then the object class calls the
admin object. This object also refer to a human that controls various inputs and outputs of
ICIMS. The object then calls for method checkStudentQualification, that check if student
qualification is adequate for the selected course. If the qualification matches with the
requirement then admin approves the request and a slot is booked for the student. This
information is then sent to the student.
3.1 Collaboration Diagram:
The second kind of interaction diagram is collaboration diagram. In this, method call
sequence is indicated by the help of numbering based technique. The number helps in having an
idea that how call sequence is indicated by numbering based techniques (Cunha, Garis and
Riesco 2015). Method calls are considered to be very much similar to that of sequence diagram.
Sequence diagram does not provide any idea with respect to object organization. On the contrary,
collaboration diagram provides an idea with respect to object organization.

10SYSTEM ANALYSIS AND DESIGN
Figure 3: Collaboration Diagram of ICIMS
(Source: Created by Author)
The collaboration diagram is a static interaction diagram. This diagram shows the
communication among the objects of the system. The ICIMS system objects for student
enrollment are student, admin and course. Like the sequence diagram, student first request for
enrolment in a specific course. This is shown using ‘1: register()’ message. The Course then
checks for available sits for the course like sequence diagram. This is done in the course object.
The course object then connects to admin object which check for qualification of the student.
The qualification must satisfy the minimum requirement for getting enrollment in the course.
However, based on the competition and other factors, the admin can manually set the
qualification for course enrolment. If the student qualification matches with the set requirements,
then the student is allowed to be registered for the course. In this case, admin object calls the
allow() method for confirming the enrolment as per system standard and protocol.
3.1 Activity Diagram:
Activity diagram along with Use case diagram is known as behavior diagram that
describes a list of things happening in the system. Stakeholders come up with various issues that

11SYSTEM ANALYSIS AND DESIGN
are difficult to manage, so it needs to be communicated to executives with proper clarity (Osman
and Chaudron 2018). Activity diagrams help the manager and executive of an organization to
understand different process and behavior.
Figure 3: Activity Diagram of ICIMS

12SYSTEM ANALYSIS AND DESIGN
(Source: Created by Author)
The activity diagram showed in the figure 3, is created based on the information gained
from sequence and collaboration diagram. The use case of Request to enroll and Enroll Student
allows has been a great source of information for identifying the static structure of the system.
This static structure provides a great understanding of what the basic elements of the process will
be. The dynamic structure has been a great way of understanding how the elements connects to
each other. The activity diagram starts with student requesting for course enrolment. This
suggests that static and dynamic, both the patterns are followed in the activity diagram.

13SYSTEM ANALYSIS AND DESIGN
Bibliography:
Afanasyev, A.N., Voit, N.N., Voevodin, E.Y. and Gainullin, R.F., 2015, October. Control of
UML diagrams in designing automated systems software. In 2015 9th International Conference
on Application of Information and Communication Technologies (AICT) (pp. 285-288). IEEE.
Bashir, R.S., Lee, S.P., Khan, S.U.R., Chang, V. and Farid, S., 2016. UML models consistency
management: Guidelines for software quality manager. International Journal of Information
Management, 36(6), pp.883-899.
Cunha, A., Garis, A. and Riesco, D., 2015. Translating between Alloy specifications and UML
class diagrams annotated with OCL. Software & Systems Modeling, 14(1), pp.5-25.
Faitelson, D. and Tyszberowicz, S., 2017, May. UML diagram refinement (focusing on class-and
use case diagrams). In Proceedings of the 39th International Conference on Software
Engineering (pp. 735-745). IEEE Press.
Gogolla, M., Hilken, F., Niemann, P. and Wille, R., 2017, July. Formulating model verification
tasks prover-independently as UML diagrams. In European Conference on Modelling
Foundations and Applications (pp. 232-247). Springer, Cham.
Granda, M.F., Condori-Fernández, N., Vos, T.E. and Pastor, O., 2016, June. Mutation operators
for UML class diagrams. In International Conference on Advanced Information Systems
Engineering (pp. 325-341). Springer, Cham.
Knapp, A., Mossakowski, T. and Roggenbach, M., 2015. Towards an Institutional Framework
for Heterogeneous Formal Development in UML. In Software, Services, and Systems (pp. 215-
230). Springer, Cham.

14SYSTEM ANALYSIS AND DESIGN
Osman, H. and Chaudron, M.R., 2018. Correctness and Completeness of CASE Tools in Reverse
EngineeringSource Code into UML Model. GSTF Journal on Computing (JoC), 2(1).
Robles, G., Ho-Quang, T., Hebig, R., Chaudron, M.R. and Fernandez, M.A., 2017, May. An
extensive dataset of UML models in GitHub. In Proceedings of the 14th International
Conference on Mining Software Repositories (pp. 519-522). IEEE Press.
Septian, I., Alianto, R.S. and Gaol, F.L., 2017. Automated Test Case Generation from UML
Activity Diagram and Sequence Diagram using Depth First Search Algorithm. Procedia
computer science, 116, pp.629-637.
Setyautami, M.R., Hähnle, R., Muschevici, R. and Azurat, A., 2016, September. A UML profile
for delta-oriented programming to support software product line engineering. In Proceedings of
the 20th International Systems and Software Product Line Conference (pp. 45-49). ACM.
Soares, J.A.C., 2017. Automatic model transformation from UML sequence diagrams to
coloured petri nets.
Storrle, H., 2016, September. Diagram Size vs. Layout Flaws: Understanding Quality Factors of
UML Diagrams. In Proceedings of the 10th ACM/IEEE International Symposium on Empirical
Software Engineering and Measurement (p. 31). ACM.
Torre, D., Labiche, Y., Genero, M. and Elaasar, M., 2018. A systematic identification of
consistency rules for UML diagrams. Journal of Systems and Software, 144, pp.121-142.
Torre, D., Labiche, Y., Genero, M., Baldassarre, M.T. and Elaasar, M., 2018, May. UML
diagram synthesis techniques: a systematic mapping study. In 2018 IEEE/ACM 10th
International Workshop on Modelling in Software Engineering (MiSE) (pp. 33-40). IEEE.

15SYSTEM ANALYSIS AND DESIGN
Uke, S. and Thool, R., 2016. UML based modeling for data aggregation in secured wireless
sensor network. Procedia Computer Science, 78, pp.706-713.