JSS Academy of Technical Education, Noida Department Of Information Technology
EXPERIMENT 1
Aim: To identify the Functional and Non-functional Requirements from Problem Statement.
Assignment:
1. Prepare a problem statement for the project identified by you.
2. Identify the functional requirements from the problem statement 3. Identify the non-
functional requirements from the problem statement.
Project title: ATTENDANCE MANAGEMENT SYSTEM
Problem Statement:
The goal is to create an attendance management system solution that conducts tracking, monitoring, and
compiling daily student attendance data through an online medium. It enables the faculty to record and
maintain 100% accurate student attendance reports, attendance history, absentee records, & other
activities within a few clicks. It generates daily attendance reports that help the faculty to track student’s
presence with high accuracy and efficiency. Student attendance system helps teachers to mark online
attendance of students during class & reduce manual work. It can be used to track student's attendance,
absentee record, attendance history & other related documents. Student attendance software allows you
to record & manage daily student attendance to speed up the daily attendance process.
Functional Requirements:
1. Adding a new student.
2. Use the system to attend classes.
3. Report students.
4. Faculty receives report.
5. Students missed classes
6. Student missed two classes or more
7. Faculty checks the report and attendance control panel page
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Non-Functional Requirements:
1. Performance
2. Reliability
3. Availability
4. Security
5. Maintainability
Self-Evaluation:
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Experiment 2
AIM: To Develop Use Case Model for a problem.
BRIEF DESCRIPTION: To model a system the most important aspect is to capture the dynamic
behaviour. To clarify a bit in details, dynamic behaviour means the behaviour of the system when
it is running /operating. So only static behaviour is not sufficient to model a system rather dynamic
behaviour is more important than static behaviour. In UML there are five diagrams available to
model dynamic nature and use case diagram is one of them. Now as we have to discuss that the
use case diagram is dynamic in nature there should be some internal or external factors for
making the interaction. These internal and external agents are known as actors. So use case
diagrams are consists of actors, use cases and their relationships. The diagram is used to model
the system/subsystem of an application. A single use case diagram captures a particular
functionality of a system. So to model the entire system numbers of use case diagrams are used .
EXERCISE#1
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
PROJECT: ATTENDANCE MANAGEMENT SYSTEM
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Self-Evaluation
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
EXPERIMENT 3
AIM: To model Activity Diagram for a given problem.
Brief Description:
Activity diagrams show the process from the start (the initial state) to the end (the final state).
Each activity diagram includes an action, decision node, control flows, start node, and end node.
Exercise 1:
• Problem Statement 1: Consider a bulb with a push down switch. The bulb initially remains off. When
the switch is pushed down, the bulb is on. Again when the switch is pushed up, the bulb turns off. The
lifecycle of the bulb continues in this way until it gets damaged.
• Solution:
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
PROJECT- ATTENDANCE MANAGEMENT SYSTEM
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Self-Evaluation
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
EXPERIMENT 4
AIM: To model Class Diagram for a given problem.
Brief Description: A class diagram uses Unified Modelling Language (UML) to show
the classes, attributes, methods (or operations), and their relationships to each
other in the system. Class diagrams prove valuable in object-oriented modelling.
Class diagrams can be used to model the data structure or to design a system in
detail.
● Problem Statement 1: A web browser is a software that helps us access a resource
(web page) available on the World Wide Web and identified by a URL. A web
browser consists of different sub-components, which can be primarily categorized
into browser rendering engine, and browser control. The rendering engine is
responsible for displaying a requested page in the web browser. The rendering
engine itself is quite a complex piece of software, which knows how to display a web
page based on the HTML elements present in the page, and CSS rules defined (if
any). Today browsers are not only limited to displaying text and images, but can
provide access to audio and video components also. The web browser control, too,
consists of several sub-components including navigation, window control, event
handlers, page display. The navigation control aids users to request for web pages
(resources) by specifying a URL, navigate to other resources through internal and
external hyperlinks, move across pages visited earlier. Event handlers are
responsible to identify the kind of activity that user is trying to do, and perform it.
For example, when a user clicks on a hyperlink, event handlers identify the URL of
the target resource, and delegate loading of the resource to other components. A
resource that has been retrieved by the web browser is then displayed in its page
display area. Window control, in association with the rendering engine, helps in
controlling various aspects of page display like changing font-size, resolution, and
so on, apart from resizing or closing the window. Represent the above problem with
a class diagram. In particular.
• Represent the individual classes
• Represent how browser rendering engine, and browser control are related to web
browser class .
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Solution
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
PROJECT- ATTENDANCE MANAGEMENT SYSTEM
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Self-Evaluation
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
EXPERIMENT 5
AIM: Draw the sequence diagram for the given scenarios.
Brief description: A sequence diagram is a useful tool for documenting a system’s needs
and fleshing out its architecture. Because it depicts the interaction logic between the items
in the system in the time order in which they occur, the sequence diagram is quite valuable.
The designed sequence diagram for student attendance management system gives you the exact scenario
when the project is in use. This design presents the actual sequence of events and interactions between the
user and the project. It uses symbols to represent the included objects and their roles in the attendance
management system sequence diagram.
PROJECT- ATTENDANCE MANAGEMENT SYSTEM
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Self-evaluation:
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
EXPERIMENT 6
AIM: Draw the collaboration diagram.
Brief description: the collaboration diagram is used to show the relationship between
the objects in a system. Instead of showing the flow of messages, it depicts the
architecture of the object residing in the system as it is based on object-oriented
programming. An object consists of several features. Multiple objects present in the
system are connected to each other. The collaboration diagram, which is also known as a
communication diagram, is used to portray the object's architecture in the system.
PROJECT- ATTENDANCE MANAGEMENT SYSTEM
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
EXPERIMENT 7
AIM: Draw the state chart diagram.
Brief description: They define different states of an object during its lifetime
and these states are changed by events. State-chart diagram describes the
flow of control from one state to another state. States are defined as a
condition in which an object exists and it changes when some event is
triggered.
PROJECT- ATTENDANCE MANAGEMENT SYSTEM
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
Self-evaluation:
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
JSS Academy of Technical Education, Noida Department Of Information Technology
EXPERIMENT 8
AIM: Draw the component diagram.
Brief description: A component diagram breaks down the actual system under development
into various high levels of functionality. Each component is responsible for one clear aim within
the entire system and only interacts with other essential elements on a need-to-know basis.
PROJECT- ATTENDANCE MANAGEMENT SYSTEM
Software Engineering Lab (KCS 651) Anviksha Singh 2100910130025
