Lab File

Of
Software Engineering
[IT301]

Submitted To
Amity University Uttar Pradesh

In partial fulfilment of the requirements for the award degree of

Bachelor of Technology
In
Computer Science and Engineering

Guided By:
Dr.VasudhaVashisht

Submitted By:
Apar Bhatnagar
A2305220404
6CSE-6Y

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

AMITY SCHOOL OF ENGINEERING AND TECHNOLOGY
AMITY UNIVERSITY UTTAR PRADESH
NOIDA (U.P)
 INDEX
Sr. Aim of the Experiment Date Remarks Faculty
No. Signature

01 Draw an ER Diagram of Online Voting 06th Jan 2023

System.

02 Draw a Class Diagram for the Making of 13th Jan 2023

an Animation Movie.

03 Draw a Use-Case Diagram for a Digital 27th Jan 2023

Alarm.

04 Draw a State Machine Diagram for Online 03rd Feb 2023

Course Registration.

05 Draw a Sequence Diagram for Student 10th Feb 2023

Examination Process.

06 Draw a State Machine Diagram of 4 17th Feb 2023

Queens.

07 Draw 0- & 1- & 2-level DFDs of 03rd Mar 2023

Amizone.

08 Making as SRS of Online Flight Ticket 10th Mar 2023

Booking System.

09 Draw a Collaboration Diagram of 24th Mar 2023

Employee Management System

10 Component/Deployment 31st Mar 2023

 UML Diagram-1
ER DIAGRAM
An Entity-Relationship (ER) diagram is a graphical representation of entities and their
relationships to each other. ER diagrams are commonly used in database design to model the
relationships between different tables or entities in a database.The basic components of an ER
diagram are entities, attributes, and relationships. Entities represent objects or concepts, such
as customers, products, or orders. Attributes describe the characteristics of an entity, such as
the customer's name or address. Relationships describe the connections between entities, such
as the relationship between a customer and an order.ER diagrams typically use symbols to
represent entities, attributes, and relationships. The most common symbols are:

• Entity: represented by a rectangle with the entity name inside.

• Attribute: represented by an oval with the attribute name inside, connected to its
associated entity.

• Relationship: represented by a diamond with the relationship name inside, connected

to the entities it connects.

Software Used: https://www.diagrams.net/blog/move-diagrams-net.

Problem Statement:- Draw a ER Diagram for making of an ONLINE VOTING SYSETM.

Problem Description:
The diagram shows the following entities and their relationships:

1. Voter: This entity represents the users who participate in the voting system. Each user
has a unique ID, a name, an email address, and a password.
2. Election Manager: This entity represents the election being held. It has a unique ID, a
name, a description, a start date, an end date, and a status indicating whether the election
is currently open or closed.
3. Candidates: This entity represents the candidates running for a particular election. Each
candidate has a unique ID, a name, a photo, a description, and a reference to the election
they are running in.
 UML Diagram-2
Class Diagram
The purpose of class diagram is to model the static view of an application. Class diagrams are
the only diagrams which can be directly mapped with object-oriented languages and thus
widely used at the time of construction. The purpose of the class diagram can be summarized
as –

Ø Analysis and design of the static view of an application.

Ø Describe responsibilities of a system.
Ø Base for component and deployment diagrams.
Ø Forward and reverse engineering.

Software Used: https://www.diagrams.net/blog/move-diagrams-net.

Problem Statement:- Draw a Class Diagram for making of an animation movies

Problem Description:-Making an animated film is a long process that involves huge teams
of different artists to contribute towards each frame. I have identified few Classes as a team
required for production of movies and its sub classes having people required in that particular
team they have certain Tasks as there function That are included in my class diagram as below
 UML Diagram-3
Use Case Diagram
A use case diagram is a type of diagram in the Unified Modeling Language (UML) that
represents the interactions between actors (users or other systems) and a system under
consideration. Use case diagrams help to identify the functionality provided by the system, the
actors that interact with the system, and the relationships between them.

A use case diagram typically consists of the following elements:

Ø Actors: These are the external entities that interact with the system. Actors can be
users, other systems, or even physical devices.
Ø Use cases: These represent the functionality provided by the system. Each use case
describes a specific goal or task that the system can perform.
Ø Relationships: These show the connections between actors and use cases. There are
two types of relationships: associations and generalizations. An association is a
connection between an actor and a use case, while a generalization represents a
relationship between two use cases, where one use case is a more specific version
of another.
Software Used: https://www.diagrams.net/blog/move-diagrams-net

Problem Statement:- Draw a Use Case Diagram for Digital alarm

Problem Description:
 UML Diagram-4
STATE MACHINE DIAGRAM
A state machine diagram, also known as a state chart diagram, is a type of behavioral diagram
in UML (Unified Modeling Language) that shows the different states an object can be in and
the transitions between those states.

The diagram is made up of rectangular boxes representing states, arrows representing

transitions between states, and labels on the arrows indicating the triggering event for the
transition. The state machine diagram is useful for modeling the behavior of an object,
system, or process over time.

Software Used: https://www.diagrams.net/blog/move-diagrams-net

Problem Statement:- Draw state machine diagram for online course.

Problem Description:-
 UML Diagram-5
SEQUENCE DIAGRAM
A sequence diagram is a type of interaction diagram in Unified Modeling Language (UML)
that shows the sequence of messages exchanged between objects in a system or application. It
is used to model the dynamic behavior of a system and to visualize how objects interact with
each other over time.

In a sequence diagram, the objects participating in the interaction are shown as vertical
lifelines or bars. Messages exchanged between objects are represented by arrows, with the
arrowhead pointing from the sender to the receiver of the message. The sequence of messages
is shown on the vertical axis of the diagram, with time moving from top to bottom.

Software Used: https://www.diagrams.net/blog/move-diagrams-net.

Problem Statement:- Draw a sequence diagram for student examination process.

Problem Description:
 UML Diagram-6
STATE MACHINE DIAGRAM
A state machine diagram, also known as a state chart diagram, is a type of behavioral diagram
in UML (Unified Modeling Language) that shows the different states an object can be in and
the transitions between those states.

The diagram is made up of rectangular boxes representing states, arrows representing

transitions between states, and labels on the arrows indicating the triggering event for the
transition. The state machine diagram is useful for modeling the behavior of an object,
system, or process over time.

Software Used: https://www.diagrams.net/blog/move-diagrams-net.

Problem Statement: Draw a State Machine Diagram of 4 Queens.

Problem Description:
 UML Diagram-7
LEVEL 0 DFD
A Level 0 DFD (Data Flow Diagram) is a high-level view of a system or process. It shows the major
processes in the system and the data flows between them, but it doesn't go into detail about what
happens within each process. In a Level 0 DFD, the system is represented as a single process, with
inputs and outputs shown as data flows. The inputs represent data coming into the system, while the
outputs represent data leaving the system. The data flows show how the inputs are transformed into
outputs through the different processes in the system.The Level 0 DFD is useful for providing an
overall view of the system, helping to identify the main inputs, outputs, and processes involved. It can
also help to identify any areas where the system may be inefficient or where improvements could be
made.

LEVEL 1 & 2 DFD

Level 1 DFD is the first level of decomposition of a system or process, which breaks down
the system into its major processes. The Level 1 DFD shows the main processes in the system
and the data flows between them. It provides an overview of the system and serves as a
starting point for further decomposition.Level 2 DFD is the second level of decomposition of
a system or process. It breaks down the processes identified in the Level 1 DFD into smaller,
more detailed processes. The Level 2 DFD shows the processes within each major process, as
well as the data flows between them. It provides a more detailed view of the system than the
Level 1 DFD and can help identify areas where improvements can be made to the system.

Software Used: https://www.diagrams.net/blog/move-diagrams-net.

Problem Statement: Draw 0 level, 1&2 LEVEL DFD of amizone.

Problem Description:
 UML Diagram-8
SRS
SRS stands for "Software Requirements Specification." It is a document that outlines the
requirements and specifications for a software project. The purpose of an SRS is to define in
detail what the software is expected to do, how it will function, and what features it will have.
It typically includes sections on functional requirements, non-functional requirements, user
interface design, system architecture, and testing requirements. The SRS serves as a contract
between the development team and the client or stakeholders, ensuring that everyone is on the
same page regarding what the software should accomplish. It is an important document in the
software development process, as it provides a roadmap for the project and helps ensure that
the final product meets the desired specifications.

Software Used: https://www.diagrams.net/blog/move-diagrams-net.

Problem Statement: Making as SRS of Online Flight Ticket Booking System.

Problem Description:
 UML Diagram-9
COLLABORATION DIAGRAM
A collaboration diagram, also known as a communication diagram, is a type of interaction
diagram that illustrates how objects interact with each other to achieve a specific task or goal.
In a collaboration diagram, objects are represented as rectangles, and the interactions between
them are shown as labeled arrows or lines.

The focus is on the messages that objects send to each other, rather than the sequence in
which they occur. Collaboration diagrams are useful for visualizing the interactions between
objects in complex systems, and for identifying potential bottlenecks or communication
issues. The collaborations are used when it is essential to depict the relationship between the object.
Both the sequence and collaboration diagrams represent the same information, but the way of
portraying it quite different. The collaboration diagrams are best suited for analyzing use cases.

Following are some of the use cases enlisted below for which the collaboration diagram is
implemented:

1. To model collaboration among the objects or roles that carry the functionalities of use
cases and operations.

2. To model the mechanism inside the architectural design of the system.

3. To capture the interactions that represent the flow of messages between the objects
and the roles inside the collaboration.

4. To model different scenarios within the use case or operation, involving a

collaboration of several objects and interactions.

5. To support the identification of objects participating in the use case.

Software Used: https://www.diagrams.net/blog/move-diagrams-net.

Problem Statement:- Draw a Collaboration Diagram of Employee Management System.

Problem Description:

The Employee Management System allows an organization to keep track of their employees, including
their personal information, job details, salary, and performance. The system has different user roles such
as HR, Manager, and Employee, each with their own set of functionalities.

The HR can add, edit and delete employee records, as well as create job postings and manage
employee benefits. The manager can view and update the employee records of their respective
teams, assign tasks and monitor their progress, and evaluate their performance. The employee
can view their personal information, salary, and benefits, as well as submit leave requests and
access their task list.The system also generates reports and analytics to help the management
make informed decisions about their employees and the organization as a whole.
 UML Diagram-10
DEPLOYMENT DIAGRAM
A UML deployment diagram is a diagram that shows the configuration of run time processing
nodes and the components that live on them. Deployment diagrams is a kind of structure
diagram used in modeling the physical aspects of an object-oriented system. They are often be
used to model the static deployment view of a system (topology of the hardware).

Problem Statement: To create a deployment diagram for a sensor-based system.

Problem Description:

A sensor-based system typically consists of a network of sensor nodes that collect data from
the environment and transmit it to a central server or processing node for analysis and
decision making. The deployment diagram for such a system would show the physical
components and their connections.

The sensor nodes are represented by rectangular boxes, and the central server or processing
node is represented by an oval shape. The sensor nodes are connected to the central server or
processing node via a sensor network.

Each sensor node contains a sensor processor that processes data from the sensor and
transmits it to the central server or processing node. The central server or processing node
contains a data store where the data from the sensor nodes is stored for further analysis and
decision making.