Department of Computer Science &

Engineering

LAB FILE
Software Engineering Lab
(KCS-651)

B.Tech 3rdYear (6th Semester)

Session 2022-23

Submitted to: Submitted By:

Ms. Roobal Yadav Name: Nikunj Kaushik

Associate Professor Roll No: 2002220100106

CSE Department Section: B

 LIST OF PROGRAMS

Sr. Name of Programs Date Sign.

No.

1. Prepare a SRS document in line with the IEEE

recommended standards.

2. Draw the use case diagram of book bank and specify

the role of each of the actors. Also state the
precondition, post condition and function of each use
case.
3. Draw the Activity Diagram
4. Draw the data flow diagram
5. Draw ER diagram
6. Identify the classes. Classify them as weak and strong
classes and draw the class diagram.
7. Draw the sequence diagram for any two scenarios

8. Draw the collaboration diagram.

9. Draw the state chart diagram.

10. Draw the component diagram.

11. Draw the deployment diagram.

 Program No.-1

AIM : Prepare a SRS document in line with the IEEE recommended standards.

AIRLINE RESERVATION SYSTEM

1.1 PROBLEMDEFINITION
Ticket reservation system for airlines has to be developed.
The system developed should contain the following features
1. The system should contain the followingfeatures
2. Search for information about the flight by means of flight number anddestination
3. While displaying information about the flight it has to provide availability ofseats.
4. While reserving tickets the system obtain following information from the user
Passenger Name, Sex, Age,Address.
Credit Card Number, Bank Name.
Flight number, Flight name, Date of Journey and number of tickets to be booked.
5. Based on the availability of tickets, the ticket has to be issued. The ticket issued
should contain the following information –ticket number, flight no, flight name,
date of journey, number of passengers, sex, age and departuretime.
6. Cancellation of booked tickets should beavailable.

2.1 SRS DOCUMENT FOR AIRLINE RESERVATIONSYSTEM

2.2 INTRODUCTION
2.1.1 Purpose

2.1.1.1 The purpose of this SRS is to describe the requirements involved in developing a
Airline Reservation system(ARS).
2.1.1.2 The intended audience is any person who wants to reserve or cancel tickets or to
check the availability of Airlinetickets
The product is titled Airline Reservation system(ARS).

2.1.2 Scope

2.1.2.1 The product will perform the following tasks

2.1.2.1.1 The software that is being developed can be used to check the
availability of the flight tickets for the specified flight, destination
and date ofjourney
2.1.2.1.2 If the tickets are available to the users needs and specification, then
the software provide a facility to book thetickets.
2.1.2.1.3 If the passengers wants to cancel the tickets, he can use the
cancellation module of the Airline ReservationSystem.
2.1.1 Definitions, Acronyms andAbbreviations
2.1.1.1 ARS: Airline ReservationSystem.
2.1.2 References
2.1.2.1 IEEE standard 830-1998 recommended practice for Software
RequirementsSpecifications-Description.

2.1.3 Overview
2.1.3.1 The SRS contains an analysis of the requirements necessary to help easy
design.
 2.1.3.2 The overall description provides interface requirements for the Airline
Reservation system, product perspective, hardware interfaces software
interfaces,, communication interface, memory constraints, product
functions, user characteristics and otherconstraints.
2.1.3.3 Succeeding pages illustrate the characteristics of typical naïve users
accessing the system along with legal and functional constraints enforced
that affect Airline Reservation system in anyfashion.

2.2 THE OVERALLDESCRIPTION

2.2.1 Productperspective
2.2.1.1 Hardwareinterfaces
2.2.1.1.1 Hard disk: The database connectivity requires a hardware configuration with a fast
database system running on high rpm hard-disk permitting complete data
redundancy and back-up systems to support the primary goal ofreliability.
2.2.1.1.2 The system must interface with the standard output device, keyboard and mouse to
interact with thissoftware.
2.2.1.2 Softwareinterfaces
2.2.1.2.1 Back End: MS Access 2007
2.2.1.2.2 Front End: Microsoft Visual Basic 6.0
2.2.1.3 Operations
2.2.1.3.1 The user mode enables the end-users to do the end user operations like checking the
availability, reserving and cancelling of flighttickets.
2.2.2 Product Functions
2.2.2.1 Viewing FlightDetails
The user must have the access up-to-date information about the flights including
2.2.2.1.1Flight number
2.2.2.1.2 FlightName
2.2.2.1.3 Flight route(Start and Destinationstations)
2.2.2.1.4 Flighttimings
2.2.2.1.5 Seatavailability.
2.2.2.2 ReservingTickets
The user must be able to reserve tickets after selecting
2.2.2.2.1Flight number
2.2.2.2.2 Flight Route
2.2.2.3 CancellingTickets
The user must be able to cancel tickets that he has earlier reserved by quoting the ticket
number, credit card number and bank name.
2.2.3 Usercharacteristics
2.2.3.1 The intended users of this software need not have specific knowledge as to what is the
internal operation of the system. Thus the end user is at a high level of
abstraction that allows easier, faster operation and reduces the knowledge
requirement of end user
2.2.3.2 The Product is absolutely user friendly, so the intended users can be the naïveusers.
2.2.3.3 The product does not expect the user to possess any technical background. Any
person who knows to use the mouse and the keyboard can successfully use
thisproduct.
2.2.4 Constraints
2.2.4.1 At the time of reservation, each user is provided a unique ticket number that must be
used for further operation like cancellation. Hence the user is required to
remember or store this numbercarefully.

2.3 SPECIFICREQUIREMENTS
2.3.1 Logical DatabaseRequirements
2.3.1.1 The system should contain databases that include all necessary information for the
 product to function according to the requirements. These include relations such as
flight details, reservation details, and cancellationdetails.
2.3.1.2 The user details refer to the information such as flight number and name, start and
destination stations, seatavailability.
2.3.1.3 Reservation details refer to personal information that is obtained from theuser
2.3.1.4 At the time of reservation, the passenger is provided a unique ticket no that could be
used at the time ofcancellation.
2.3.1.5 While displaying any information about the flight it has to provide the following
information
Flight no and name
Availability of seats for the particular flight
The flight timing
The passenger personal details should be obtained for reserving the tickets.

2.4 FRONT – ENDDESCRIPTION

The front-end for the Airline Reservation system (ARS) is designed using Microsoft
Visual Basic 6.0. The front-end contains a user- friendly interface. The first form contains a
welcome screen that provides an option for the user to select one of the following
Enquiry
Reservation
Booking details
Cancellation
In the Enquiry form the user can get details of the flight by means of either flight
name destination or date 0of journey. In the reservation form, there can book details by
entering the personal details. The ticket is displayed with details about the flight name and
number, number of passengers, ticket number, sex and age. The cancellation form helps the
user to cancel a ticket, which he had bookedearlier.

2.5 BACK – ENDDESCRIPTION

The Airline Reservation system consists of two tables. One contains the flight details
such as the flight name, flight number, destination, date of journey and seats available in each
class that is referred to during enquiry. The other table has the passenger details such as
name, age, sex, credit card number, and bank name. This table is referred to at the time of
reservation orcancellation.

2.6 DATASTRUCTURES

2.6.1. FLIGHTDETAILS
FIELD NAME TYPE CONSTRAINTS
ROUTE_NAME TEXT NOT NULL
FLIGHT_NO NUMBER NOT NULL
SEATS_AVAIL NUMBER
JOURNEY_DATE DATE/TIME
DEP_TIME DATE/TIME
ARR_TIME DATE/TIME
COST NUMBER

2.6.2. PASSENGERDETAILS
FIELD NAME TYPE CONSTRAINTS
TICKET_NO AUTONUMBER NOT NULL
NAME TEXT NOT NULL
GENDER TEXT
ADDRESS TEXT
CC_NO NUMBER NOT NULL
 BANK_NAME TEXT
NO_OF_TICKETS NUMBER

2.7 DATA FLOWDIAGRAM

3.0 TESTING:

FORM NAME INPUT EXPECTE ACTUAL STATUS

D OUTPUT OUTPUT
MAIN MENU FORM Menu Required Required Pass
Option Form must form was
bedisplayed displayed.
TICKET Flight route Flight seats Flight seats Pass
AVAILABILITY or Flight availability availability
FORM name must be are
displayed displayed.
RESERVATION Personal Ticket must Ticket was Pass
FORM details were be booked booked and
entered. and database database was
updated. updated.
CANCELLATION Ticket Ticket must Ticket was Pass
FORM number was be cancelled cancelled
entered. anddatabase anddatabase
must be Was updated.
updated
4.0 SAMPLE FORMS
 5.1 RESULT
Thus the online Airline Reservations System was implemented using the specified front end
and back end tools.

Program No. 2
Objective:-Draw the use case diagram and specify the role of each of the actors.
Also state the precondition, post condition and function of each use case.

Result:-

CASE Tool: StarUML

Use_Case Diagram:
The book bank use cases are:
1. book_issue

2. book_return

3. book_order

4. book_entry

5. searchbook_details

Actors Involved:
1. Student

2. Librarian
3. Vendor

UsecaseName : Search Book_Details

The librarian initiates this use case when any member returns or request the book and checking if the
book is available.

Precondition: The librarian should enter all Book details.

Normal Flow: Build message for librarian who search the book.
Post Condition: Send message to respective member who reserved the book.

UsecaseName : Book_ Issue

Initiated by librarian when any member wants to borrow the desired book. If the book is available, the
book is issued.

Precondition: Member should be valid member of library.

Normal Flow: Selected book will be issued to the member.
Alternative Flow: If book is not available then reserved book use case should be initiate. Post
Condition: Update the catalogue.

UsecaseName :Book_Order

Initiated by librarian when the requested book is not available in the library at that moment. The book is
reserved for the future and issued to the person when it is available.
Precondition: Initiated only when book is not available.
Normal Flow: It reserved the book if requested.
Post Condition :Mention the entry in catalogue for reservation.

UsecaseName :Book_Return
Invoked by the librarian when a member returns the book.
Precondition: Member should be valid member of library.
Normal Flow: Librarian enters bookid and system checks for return date of the book. Alternative Flow:
System checks for return date and if it returned late fine message will be displayed. 12
 Use Case diagram for Book Bank System

Use Case diagram for Book Bank System

Program No. 3
Objective:-Draw the activity diagram for ATM, discuss two activities for the same.
Result:-

Activity diagrams are graphical representations of workflows of stepwise activities and actions
withsupport for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams
can be used to describe the business and operational step-by-step workflows of components in a
system. An activity diagram shows the overall flow of control. An activity is shown as an rounded box
containing the name of the operation.
This activity diagram describes the behaviour of the system.

Activity1:
Activity2
 Program No.-4

AIM: Draw the Data Flow Diagram.

DFD

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through an

information system. DFDs can also be used for the visualization of data processing
(structured design). On a DFD, data items flow from an external data source or an internal
data store to an internal data store or an external data sink, via an internalprocess.

A DFD provides no information about the timing or ordering of processes, or about whether
processes will operate in sequence or in parallel. It is therefore quite different from a
flowchart, which shows the flow of control through an algorithm, allowing a reader to
determine what operations will be performed, in what order, and under what circumstances,
but not what kinds of data will be input to and output from the system, nor where the data
will come from and go to, nor where the data will be stored (all of which are shown on a
DFD).

It is common practice to draw a context-level data flow diagram first, which shows the
interaction between the system and external agents which act as data sources and data sinks.
On the context diagram (also known as the Level 0 DFD) the system's interactions with the
outside world are modeled purely in terms of data flows across the system boundary. The
context diagram shows the entire system as a single process, and gives no clues as to its
internal organization.

Customer

Context Diagram (level 0)

This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the detail
of the system being modeled. The Level 1 DFD shows how the system is divided into sub-systems
(processes), each of which deals with one or more of the data flows to or from an external agent, and
which together provide all of the functionality of the system as a whole.

Level-1 DFD
This could continue to evolve to become a level 2 diagram when further analysis is required.

DFD Diagram Notation

1. Create three processes(Process order,Ship Good, Issue Receipt) in the centre as shown below.
2. Create external entity customer
3. Create three databases Inventory ,Customer, Transaction.
4. After that we will connect them.
DFD Diagram
 Program No.-5
AIM: Draw the ER Diagram

ER Diagram

ER Model is represented by means of an ER diagram. Any object, for example, entities,

attributes of an entity, relationship sets, and attributes of relationship sets, can be represented
with the help of an ER diagram.

Entity
Entities are represented by means of rectangles. Rectangles are named with the entity set
they represent.

Attributes

Attributes are the properties of entities. Attributes are represented by means of ellipses.
Every ellipse represents one attribute and is directly connected to its entity (rectangle). If the
attributes are composite, they are further divided in a tree like structure. Every node is then
connected to its attribute.

 Composite attributes are represented by ellipses that are connected with anellipse.

 Multivalued attributes are depicted by doubleellipse.

 Derived attributes are depicted by dashedellipse.

Binary Relationship and Cardinality

A relationship where two entities are participating is called a binary relationship.
Cardinality is the number of instance of an entity from a relation that can be associated with
the relation.

 One-to-one − When only one instance of an entity is associated with the relationship,
it is marked as '1:1'. The following image reflects that only one instance of each
entity should be associated with the relationship. It depicts one-to-onerelationship.

 One-to-many − When more than one instance of an entity is associated with a

relationship, it is marked as '1:N'. The following image reflects that only one
instance of entity on the left and more than one instance of an entity on the right can
be associated with the relationship. It depicts one-to-many relationship.
  Many-to-one − When more than one instance of entity is associated with the
relationship, it is marked as 'N:1'. The following image reflects that more than one
instance of an entity on the left and only one instance of an entity on the right can be
associated with the relationship. It depicts many-to-onerelationship.

 Many-to-many − The following image reflects that more than one instance of an
entity on the left and more than one instance of an entity on the right can be
associated with the relationship. It depicts many-to-many relationship.

Participation Constraints

 Total Participation − Each entity is involved in the relationship. Total participation

is represented by doublelines.

 Partial participation − Not all entities are involved in the relationship. Partial
participation is represented by singlelines.

Library Management System

ER Diagram For Library Management System
 Program No. 6
Objective:-. Identify the classes. Classify them as weak and strong classes and

draw the class diagram.

Result:-

The class diagram, also referred to as object modeling is the main static analysis diagram. The main
task of object modeling is to graphically show what each object will do in the problem domain. The
problem domain describes the structure and the relationships among objects.

The LMS system class diagram consists of four classes:

1. Student

2. Book

3. Issue

4. Return

5. Vendor

6. Details
1) Student:
It consists of twelve attributes and three operations. The attributes are enrollno, name, DOB,
fathername, address, dept name, batch and book limits. The operations of this class are addStInfo(),
deleteStInfo(), modifyStInfo().
2) Book:
It consists of ten attributes and four operations. This class is used to keep book information such as
author, title, vendor, price, etc
3) Issue:
It consists of eight attributes and two operations to maintain issue details such as, issue date, accno of
issued book, name of the student who borrowed book.
4) Return:
It consists of eight attributes and two operations to maintain issue details such as, issue date, accno of
issued book, name of the student who borrowed book.
5) Students:
The attributes of this class are name, dept ,year ,bcode no The operation is display students().
6) Detail:The attributes of this class are book name, author, bcode no The operations are delete
details().
Class Diagram For Book Bank System
Class Diagram For Book Bank System
 Program No. 7
Objective:-Draw the sequence diagram for any scenario.

Result:-
A sequence diagram represents the sequence and interactions of a given USE-CASE or scenario.
Sequence diagrams can capture most of the information about the system. Most object to object
interactions and operations are considered events and events include signals, inputs, decisions,
interrupts, transitions and actions to or from users or external devices.
An event also is considered to be any action by an object that sends information. The event line
represents a message sent from one object to another, in which the “form” object is requesting an
operation be performed by the “to” object. The “to” object performs the operation using a method
that the class contains.
It is also represented by the order in which things occur and how the objects in the system send
message to one another.
 Program No.8
Objective: Draw the collaboration diagram.
Result:
Collaboration Diagrams describe interactions among classes and associations. These interactions
are modeled as exchanges of messages between classes Through their associations. Collaboration
diagrams are a type of interaction Diagram.
Collaboration diagrams contain the following elements.
Cass roles: which represent roles that objects may play within the interaction.
Association roles: which represent roles that links may play within the interaction.
Message flows: which represent messages sent between objects via links. Links transport or
implement the delivery of the message.

24 | P a g e
Collaboration Diagram For Book Issue & Return
 Program No. 9
Objective: Draw the state chart diagram.

Result:

It consists of state, events and activities. State diagrams are a familiar technique to describe the
behavior of a system. They describe all of the possible states that a particular object can get into and
how the object's state changes as a result of events that reach the object.

State Chart Diagram for BookBank System

 Program No. 10
Objective: Draw the component diagram.

Result:

Component diagrams describe the organizations and dependencies among software

Implementation components. These diagrams contain components, which represent Distributable
physical units, including source code, object code, and executable code. These are static
implementation view of a system.

Component diagram contains

▪ Components

▪ Interfaces

▪ Dependency, generalization, association, and realization relationships. Like all other diagrams
component diagrams contains notes and constraints.
 Program No. 11
Objective:- Draw the deployment diagram

Result:-
Deployment diagrams are used to visualize the topology of the physical components of a system
where the software components are deployed.

These Diagrams contain components and nodes, which represent processing or computational
resources, including computers, printers, etc.

Deployment Diagram for Book Bank System