ABES Institute of Technology

Ghaziabad
Affiliated to Dr. A.P.J. AKTU, Lucknow

LAB MANUAL
Department of Computer Science & Engineering
Subject Name: Software Engineering Lab
Subject Code: KCS 651
Session: 2020-21
Semester: 6th

Name:AMAN
Roll No.:1829010022

1
Institute Vision To be leading institution in technical education providing education and
training enabling human resource to serve nation and world at par with
global standards in education

Institute 1) Developing state of art infrastructure which also includes

Mission establishment of centre of excellence in pursuit of academic and
technical excellence

2) Valuing work force inculcating belongingness and professional

integrity

3) To develop human resource to solve local, regional and global

problems to make technology relevant to those who mean it most

Department To provide excellence by imparting knowledge to the learners

Vision enabling them to become skilled professionals to be recognized
as a responsible citizen.

Department 1)
Mission
Provide quality education in the field of computer science and
2) engineering through experienced and qualified faculty
members.
Motivate learners for higher studies and research oriented
3) activities by utilizing resources of Centers of Excellence.
Inculcate societal values, professional ethics, team work, and
leadership qualities by having exposure at National and
International level activities.

2
 Program Educational Objectives (PEOs)
Graduates of the program are expected to be employed in IT industry or
PEO1
indulge in higher studies and research.
Graduates of the program are expected to exhibit curiosity to learn new technologies and
PEO2
work with ethical values and team work.
Graduates of the program are expected to design and develop innovative solutions related
PEO3
to real world problems of the society.
Program Outcomes (PSOs)
Solve complex problems using data structures and other advanced suitable algorithms.
PSO 1

Interpret fundamental concepts of computer systems and understand its hardware and software
PSO 2
aspect.
Analyze the constraints of the existing data base management systems and get experience on
PSO 3
large-scale analytical methods in the evolving technologies.
Develop intelligent systems and implement solutions to cater the business specific
PSO 4
requirements.
Program Specific Outcomes (POs)
PO1 Engineering knowledge

Problem analysis
PO2

PO3 Design/development of solutions

PO4 Conduct investigations of complex problems

PO5 Modern tool usage

PO6 The engineer and society

PO7 Environment and sustainability

PO8 Ethics

PO9 Individual and team work

PO10 Communication

PO11 Project management and finance

PO12 Life-long learning

3
 Course – B.Tech

Course Outcomes (COs)

Academic Year Class/Semester Course Name Course Code
6th
2020-21 Software KCS-651
Engineering Lab
After the successful completion of the course students will be able:
to prepare SRS document based on real time problems.
CO1

to learn and design behavioural model of real time problems.

CO2

to learn and design structural model of real time problems.

CO3

( AMAN & 1829010022)

4
 A. LIST OF EXPERIMENTS

Lab No. Name of experiment

1 Define the Problem Statement of your project

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

3 Draw the ER Diagram.

4 Draw the Flow Charts.

5 Draw the Data Flow Diagram (Level 0,1)

6 Draw the Use case Diagram.

7 Draw the Activity Diagram.

8 Prepare test cases for testing the system using

5
 EXPERIMENT No.-1

BANK MANAGEMENT SYSTEM

Aim: - Define Problem statement and Project scope of Bank Management System.
Theory: This system provides the basic services to manage bank accounts at a bank. Bank has
many branches, each of which has an address and branch number. A client opens accounts at a
branch. Each account is uniquely identified by an account number; it has a balance and a credit
or overdraft limit. There are many types of accounts, including: A mortgage account, a chequing
account, and a credit card account. It is also possible to have a joint account.
Information objective: Bank Management System would be able to maintain information and
able to keep records of that particular event.

Problem Definition:
Although the basic type of services offered by a bank depends upon the type of bank and the
country, services provided usually include: Taking deposits from their customers and issuing
current or checking accounts and savings accounts to individuals and business. Extending loans
to individuals and business, Cashing cheque. Facilitating money transact ions such as
wire transfer and cashiers cheque, Consumer & commercial financial advisory services,
f i n a nc i a l t r a ns a c t io n c a n be p e r fo r me d t hr o u g h ma n y d i f f e r e nt channels.

Motivation behind this project:

To develop a system that will overlook the activities going transaction the particular bank without
manual processing. All transaction will be updated automatically by using the information stored
in record. The main motive behind this project is to develop a system which will able to handle the
overall tasks going inside the institutions without much effort.

Overview of Bank Management System

There are various job positions within bank institutions. These positions are as follows:-
1) Customer Service Position
2) Mid Management Position
3) Executive Level Position
 Customer Service Position consists of a bank teller, bank marketing representative.
Mid Management Position consists of internal auditor, data processing officer etc.
Executive Level Position consists of loan officer, branch manager etc.

Bank Teller
Bank tellers are the first line of advertising for a bank.
Tellers must be friendly and have an attitude of service.
Tellers are responsible for basic account transactions such as servicing savings and checking
accounts and providing account details to customers.
Bank Marketing Representative
A bank marketing representative is an individual who markets banking products to
customers.
Products range from checking accounts and savings accounts to CD and special deposit
accounts.
The bank marketing representative is also responsible for understanding the strategic plan for
marketing various products and implementing plans for the bank.
Internal Auditor
Audit is extremely important in banking environments.
The internal audit position is considered a midlevel management position that ensures the bank
is following compliance and regulatory laws concerning bank operations and procedures.
The internal auditor is the individual responsible for creating audit programs for all areas of
operations.
Positions under the scope of internal auditor are Financial Auditor and Information Systems
Auditor.
Information Systems Auditor monitors data processing, data security and disaster recovery
strategies for the bank.
Branch Manager
 Branch managers are assigned by midlevel or executive management to drive-through bank
operation.
Branch managers create branch work schedules for personnel, provide a budget to executive
management concerning resources and ensure that bank policies are followed at the branch
level.
A branch manager can work from the main bank and have several branch banks assigned
under her supervision.
Provides training, coaching, development and motivation

Loan Officer
Meets with applicants to obtain information for loan applications and to answer questions
about the process.
Analyze applicants' financial status, credit, and property evaluations to determine feasibility
of granting loans.
Explain to customers the different types of loans and credit options that are available, as well
as the terms of those services.
Obtain and compile copies of loan applicants' credit histories, corporate financial statements,
and other financial information.
Review and update credit and loan files.
Data Processing Officer
The data processing officer (DPO) is responsible for the operation, maintenance and security
of the bank information systems and offline terminals or devices not attached to the system.
At the end of a daily processing cycle, the DPO ensures the general ledger account is
balanced.
The officer also ensures that daily transaction exception reports are created for managerial
review.
The DPO is responsible for creating security profiles for employees.
Scope of the project:
This project can be implemented in any bank by fulfilling basic requirements.
Conclusion: This Bank Management System will provide the transaction going inside the bank
without manual processing. All information will be updated automatically by using the
information stored in the system files.
 Experiment No. 2

Program Name: Prepare the SRS document in line with the IEEE recommended standards.

Theory Concepts: A software requirements specification (SRS) is a description of a software system to

be developed. It lays out functional and non-functional requirements, and may include a set of use cases that
describe user interactions that the software must provide.

Software requirements specification establishes the basis for an agreement between customers and contractors
or suppliers (in market-driven projects, these roles may be played by the marketing and development divisions)
on what the software product is to do as well as what it is not expected to do. Software requirements
specification permits a rigorous assessment of requirements before design can begin and reduces later redesign.
It should also provide a realistic basis for estimating product costs, risks, and schedules.

The software requirements specification document enlists enough and necessary requirements that are required
for the project development. To derive the requirements we need to have clear and thorough understanding of
the products to be developed or being developed. This is achieved and refined with detailed and continuous
communications with the project team and customer till the completion of the software.

Implementation:

SRS For Railway Reservation System: Introduction

Purpose

The purpose of this source is to describe the railway reservation system which provides the train timing details,
reservation, billing and cancellation on various types of reservation namely,

• Confirm Reservation for confirm Seat.

• Reservation against Cancellation.

• Waiting list Reservation.

• Online Reservation.

• Tatkal Reservation.

6
SCOPE
“Railways Reservation System” is an attempt to simulate the basic concepts of an online Reservation system.
The system enables to perform the following functions:

● SEARCH FOR TRAIN

● BOOKING OF A SELECTED TRAIN
● PAYMENT
● CANCELLATION
● PASSENGER AND REVENUE ENHANCEMENT
● IMPROVED AND OPTIMIZED SERVICE

OBJECTIVE

General Objective:

Software has to be developed for automating the manual Railway Reservation System.

Specific Objectives:

Some of the Specific Objectives of the system are listed below:

● RESERVE SEATS – Reservation form has to be filled by passenger. If seats are available entries like
train name, number, destination are made.
● CANCEL RESERVATION- The clerk deletes the entry in the System and changes in the
Reservation Status.

● VIEW RESERVATION STATUS-The user need to enter the PIN number printed on ticket

OVERVIEW

The remaining sections of this document provide a general description, including characteristics of the users
of this project, the product's hardware, and the functional and data requirements of the product. General
description of the project is discussed in section 2 of this document. Section 3 gives the functional
requirements, data requirements and constraints and assumptions made while designing the E-Store. It also
gives the user viewpoint of product. Section 3 also gives the specific requirements of the product. Section 3
also discusses the external interface requirements and gives detailed description of functional requirements.
Section 4 is for supporting information.

7
REFERENCES

Some of the references used for preparing the vision document include:

1. IEEE document for Software Requirements Specifications

2. Wikipedia

FUNCTIONAL REQUIREMENTS
1. Login and registration: This function allows a new user to register himself on the railway reservation
system and lets him login on the system using the username and password supplied during registration.

2. History of booking: This function allows a registered user to view all the booking and transactions
allotted to him during booking the ticket.

3. Check PNR status: It allows the user to check the status of his reserved birth using the PNR no. allotted
to him during booking the ticket.

4. Seat Availability: This function lets the user check the availability of seats in the train selected by
user.
5. Search: It allows user to view all the trains that are running from the source station to the destination
on the given date as entered by user during form filling.

6. Live station: This function list all the trains leaving or going to the specified station as supplied by the
user.

7. Booking: The user supplies all the information in the railway reservation form and can book his ticket.

8. Ticket cancellation: This function allows user to cancel his reservation whether the user status is
confirmed or waiting.

9. Running status: It is used to spot our train. The user enters a train number and we get to know details
like the current station where the train is, delay, and expected time of arrival.
INTERFACES REQUIREMENTS:

USER INTERFACE

Keyboard and mouse

HARDWARE INTERFACE

8
 For the hardware requirements the SRS specifies the logical characteristics of each interface b/w the software
product and the hardware components. It specifies the hardware requirements like memory restrictions, cache
size, the processor, RAM size etc... those are required for the software to run.

Minimum Hardware Requirements

Processor Pentium III

Hard disk drive 40 GB

RAM 128 MB

Cache 512 kb
Preferred Hardware Requirements

Processor Pentium IV

Hard disk drive 80 GB

RAM 256 MB

Cache 512 kb

SOFTWARE INTERFACE

● Any window based operating system with DOS support are primary requirements for software
development. Windows XP, FrontPage and dumps are required. The systems must be connected via
LAN and connection to internet is mandatory.

Nonfunctional Requirements
Security:

The system use SSL (secured socket layer) in all transactions that include any confidential customer
information. The system must automatically log out all customers after a period of inactivity. The system
should not leave any cookies on the customer’s computer containing the user’s password. The system’s back-
end servers shall only be accessible to authenticated management.

Reliability:

The reliability of the overall project depends on the reliability of the separate components. The main pillar of
reliability of the system is the backup of the database which is continuously maintained and updated to reflect

9
 the most recent changes. Also the system will be functioning inside a container. Thus the overall stability of
the system depends on the stability of container and its underlying operating system.

Availability:
The system should be available at all times, meaning the user can access it using a web browser, only restricted
by the down time of the server on which the system runs. A customer friendly system which is in access of
people around the world should work 24 hours. In case of a of a hardware failure or database corruption, a
replacement page will be shown. Also in case of a hardware failure or database corruption, backups of the
database should be retrieved from the server and saved by the Organizer. Then the service will be restarted. It
means 24 x 7 availability.

Conclusion
This SRS document is used to give details regarding Railway Reservation System. In this all the functional
and non-functional requirements are specified inorder to get a clear cut idea to develop a project.

Output / Conclusion: SRS is developed as per requirements

10
 3.ER- DIAGRAM

1/1
 4. FLOW CHART

1.
2.

1/1
5.Draw the data flow diagram (level 0,1)
LEVEL 0
LEVEL -1
6. Draw the use case diagram
7. Draw the activity diagram
 TEST CASE

For Admin  Verify Admin login with valid and Invalid data
 Verify admin login without data
 Verify all admin home links
 Verify admin change password with valid and invalid data
 Verify admin change password without data
 Verify admin change password with existing data
 Verify admin logout

For new Branch  Create a new branch with valid and invalid data
 Create a new branch without data
 Create a new branch with existing branch data
 Verify reset and cancel option
 Update branch with valid and invalid data
 Update branch without data
 Update branch with existing branch data
 Verify cancel option
 Verify branch deletion with and without dependencies
 Verify branch search option

For New Role  Create a new role with valid and invalid data
 Create a new role without data
 Verify new role with existing data
 verify role description and role types
 Verify cancel and reset option
 Verify role deletion with and without dependency
 verify links in role details page

For customer & Visitors  Verify all visitor or customer links

 Verify customers login with valid and invalid data
 Verify customers login without data
 Verify banker's login without data
 Verify banker's login with valid or invalid data

For New users

 Create a new user with valid and invalid data
 Create a new user without data
 Create a new user with existing branch data
 Verify cancel and reset option
 Update user with valid and invalid data
 Update user with existing data
 Verify cancel option
 Verify deletion of the user