Department of Computer Science &
Engineering
LAB REPORT
B.Tech. (Computer Science and Engineering)
Student Name: - Mayank Pant
Enrollment Number: - 1800102263
Subject Name: - Software Engineering
Subject Code: - CS217
Group: - CSE-2
Year/Sem: - 2nd/4th
INTEGRAL UNIVERSITY
LUCKNOW
Dasauli, Kursi Road, PO Basha-226026
Experiment – 01
Objective:
• Role of data modeling in system analysis phase
• Modeling Data Flow Diagrams
• Identify external entities and functionalists of any system
• Identify the flow of data across the system
• Represent the flow with Data Flow Diagrams
Figure 1: Context-level DFD for Library Information System
Figure 2: Level 1 DFD for Library Information System
Draw the DFD for the DFD for Social Networking
site:
Experiment No-02
Objective:
• E-R Modeling from the Problem Statements.
• Identify entity sets, their attributes, and various relationships.
• Represent the data model through ER diagram.
From a given problem statement we identify the possible entity sets, their attributes, and
relationships among different entity sets. Once we have these information, we represent them
pictorially, called an entity-relationship (ER) diagram.
Graphical Notations for ER Diagram
Term Notation Remarks
Name of the set is
Entity set written inside the
rectangle
Name of the attribute is
Attribute
written inside the ellipse
Roll is the primary key;
Entity with
denoted with an
attributes
underline
Weak entity set
Name of the relationship
Relationship set is written inside the
diamond
Term Notation Remarks
Related enity sets
A person can own zero
Relationship or more cars but no two
cardinality persons can own the
same car
Relationship with
weak entity set
Case Study
1 : A Library Information System for Institute:
Figure 1: "Member" entity set
Figure 2: "Book" entity set
Figure 3: Relationships among different entity sets
Exercise:Draw an ER diagram for the cab booking application:
Experiment No-03
Objectives: UML Use Case Diagram
• Study about use case diagram
• Deign use case diagram for given problem
Login
Registered User Search
Check out item
Browse
Manage titles Return item
Borrower
Librarian Manage items
Make reservation
Mange borrowers
Cancel Reservation
Master Librarian Manage librarians
Figure-1-Use-case diagram of a library.
Exercise: Design use case diagram for online shopping. With detail
description of use case.
Experiment No-04
Objectives:
• Study about Class and Object Diagram
• Deign use case diagram for given problem
Class Diagram:
Figure-1:Class Diagram Representation
UML Object Diagram:
Exercise:
1. Design Class and Object Diagram for University.
Object Diagram of University
Experiment No-05
Objectives:
• Study about Deployment Diagram and Component Diagram
• Deign Deployment and Component diagram for given
problem
The different ways to draw a component's name compartment
The additional compartment here shows the interfaces that the Order component provides and
requires:
A component diagram that shows how the Order System component depends on other
components
An example of a subsystem element
Case Study
The following diagram is component diagram of a Store
Case Study
Design deployment diagram for the university information system.
Experiment No-06
Objectives:
• Study about State Chart and Activity Diagrams
• Deign Activity Diagrams and State Chart Diagrams for given
problem
An Example of state chart diagram is:
Exercise:
1. Design State Chart and Activity diagram for the ATM system
State Chart Diagram of ATM Machine
Activity Diagram of ATM Machine
Experiment No-07
Objectives:
• Study about Interaction Diagram
• Study about Sequence and Collaboration Diagrams
Sequence Diagram:
Example for the same is:
An example of the Student class used in a lifeline whose instance name is freshman
An example of messages being sent between objects
A segment of a UML 1.x sequence diagram in which the addStudent message has a guard
A sequence diagram fragment that includes an option combination fragment
Case Study
Following diagram show sequence Diagram of Order Management System of a
retail shop. The sequence diagram is having four objects (Customer, Order,
Special-order and NormalOrder).
Case Study
Following diagram show collaboration Diagram of Order
Management System of a retail shop.
