BHARATI VIDYAPEETH'S COLLEGE OF ENGINEERING FOR

WOMEN.
Dhankawadi ,Pune – 411043
Department of Computer Engineering.

“Software Modelling And Architecture.”

Group Members:
Pongade Apurva Sanjay (3206)
Mahabare Shravani Ravindra(3231)
Karad Shruti Dipak(3233)
 01
Introduction
 INTRODUCTION
The Online Examination System is an electronic
application that helps colleges and institutions conduct
online exams efficiently. It allows students to remotely
access the exams and provides instant results. The
system reduces the time required for conducting
exams, checking answer sheets, and generating results.
It ensures secure storage of data on servers and offers
a client-server model for access. The purpose of this
project is to develop a web-based Online Examination
System that streamlines the exam process and benefits
both students and teachers. It saves time, ensures
accuracy, and provides better security and
transparency in examinations.
 02
SYSTEM
MODELING
 SYSTEM MODELING
• System engineering is a modeling process. Process is defined as
which serve the needs of the view under consideration.

• System modeling is the approach which is centrally oriented towards

visualizing plus software building.

• The system is a composition of hardware, software and the middle

between them; therefore, the system modeling enables the user to
visualize the whole software system.

• System modeling is a crucial part of production phase as it focuses

and provides aid to the construction and maintenance of the whole
system.
 03
UML MODELING
1. STRUCTURAL MODELING
Structural modeling describes the things in the system and their
relationships to other things. The
components are physical or conceptual which shows static part that
represents system modeling of the
system.
 CLASS DIAGRAM
• Static view of an application is a class diagram.
• The class diagram same attributes, operations, and
semantics which share objects collection is class diagram.
• In the proposed system used user, system,
database and task information are class names.
• The class diagram displays a collection of interfaces,
collaborations, classes and associations and constraints.
• Class diagram is also defined as structural
diagram.
 2. BEHAVIORAL MODELING

• The UML models of the dynamic part gives performance

more than time and space of the system it represents
behavioral modeling.

• It has two types of behavioral nature of the system.

• First in terms of exchanging of message which it

represents itself the system and second in terms of state
transition.
 USE-CASE DIAGRAM
• A use case diagram is used to gather system requirements, provide an
outside view of the system, and identify factors influencing it.
• Actors, such as users, the system, and the database, are involved in the
process.
• Actors interact with the system to invoke its functionalities.
• The diagram shows the relationships between actors and use cases,
indicating the frequency of interactions.
• Some rules for drawing a use case diagram include assigning
meaningful names, defining communication clearly, and using
appropriate notations.
• The diagram highlights the most significant interactions among
multiple interactions between use cases and actors.
 SEQUENCE DIAGRAM
• Sequence diagram shows exchanges of things through a set of
messages and also their relation among themselves.
• Sequence diagram accentuate the time ordering of messages
which emphasize sequence diagram.
• Figure shows the sequence diagram which is an interaction of
various objects in one another.
• It is also called entity diagram.
• A specific time sequence is used to assign each task to execute
sequence of messages in our system.
• This step wise execution shows overall flow to execute a
system one by one for task extraction
COLLABORATION DIAGRAM
• Collaboration diagram is a communication diagram that emphasizes
the structural organization of the objects that send and receive
messages.
• Figure shows the collaboration diagram for the system.
• It represents occurrences to specify classes or playing roles.
• A diagram is created for the system operation that relates to the
current development cycle.
• The below figure shows how relationship between two entities and
object.
 State chart diagram
• Modeling shows the system behavior in terms of transition between
states.
• Mainly emphasize the dynamic view of the system. During its lifetime
they define different states of an object. And these states are changed
by events.
• State chart diagram describes the flow of control from one state to
another state.
• Figure shows state chart diagram describes behavior of system. It
shows transition between two states in the Unified modeling language
(UML).
 ACTIVITY DIAGRAM
• Activity diagrams are used to represent the flow of activities within a
system.
• They visualize the sequence and parallel execution of activities, using
nodes and edges. Activities are represented by rounded rectangles and
can include different types of actions.
• CallBehaviorAction and CallOperationAction actions are used to
access behavior defined elsewhere.
• Activities can also be sub-structured, and parameters can be specified.
Incoming and outgoing objects serve as parameters and are depicted
on the rectangle.
ARCHITECTURAL MODELING
• Architecture of any system composed of physical components
and their functionality.
• Architectural modeling gives the system view in accordance
with architecture.
• Architectural model represents the overall framework of the
system.
• It contains both structural and behavioral elements of the
system.
• Architectural model can be defined as the blue print of the
entire system.
 COMPONENT DIAGRAM
• A component diagram shows the organizations and
dependencies among a set of components.
• A component diagram explains the static implementation view
of a system.
• Figure show the component diagram of online examination
system.
 DEPLOYMENT DIAGRAM
• A deployment diagram shows the configuration of run-time
processing nodes and the components that live on them.
• A deployment diagram depicts the static deployment view of
architecture.
• Figure shows hardware components (nodes) like user, system
and database in system and to deploy software components
running on each node.
 Conclusion
The software modeling and architecture project for the
online examination system successfully employed
various modeling techniques and architectural principles
to design a robust and efficient system. The activity
diagram was utilized to visualize the flow of activities
within the system, describing the sequence, parallelism,
and branching of activities. The system's architecture
was carefully planned, considering factors such as
scalability, security, and performance. Through the
modeling and architecture process, the project team was
able to create a well-structured online examination
system that meets the requirements of users and ensures
a smooth and reliable examination experience.