CS0411- SOFTWARE ENGINEERING LAB
LABORATORY MANUAL
IV YEAR CSE
VII SEMESTER
ACADEMIC YEAR: 2012-2013
SCHOOL OF COMPUTER SCIENCE & ENGINEERING
SRM UNIVERSITY,
SRM NAGAR, KATTANKULATHUR-603203.
KANCHEEPURAM DISTRICT.
–
1
–
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Software Engineering Lab Manual: Library & Banking Systems, Exercises of Software Engineering
software engineering example 1 and 2 and 3 and 4 and 5
Typology: Exercises
2018/2019
1 / 46
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Software Engineering Lab Manual: Library & Banking Systems and more Exercises Software Engineering in PDF only on Docsity!
CS0411- SOFTWARE ENGINEERING LAB
LABORATORY MANUAL
IV YEAR CSE
VII SEMESTER
ACADEMIC YEAR: 2012-
SCHOOL OF COMPUTER SCIENCE & ENGINEERING
SRM UNIVERSITY,
SRM NAGAR, KATTANKULATHUR-603203.
KANCHEEPURAM DISTRICT.
SCHOOL OF COMPUTER SCIENCE & ENGINEERING
SRM UNIVERSITY,
SRM NAGAR, KATTANKULATHUR-603203.
SUBJECT : SOFTWARE ENGINEERING LAB SUBJECT CODE : CS
SEMESTER : VII CLASS : IV CSE HOURS / WEEK : 6 HOURS
EX. NO NAME OF THE EXPERIMENTS PAGE NO
1 Library^ Management^ System^ 1
Automated banking system 14
(^3) Airline reservation system 22
4 Employee^ management^ application^ 31
Hospital management Application 39
2.1.2 Scope
2.1.2.1 The product is titled Library Management System. 2.1.2.2 The product will perform the following tasks 2.1.2.2.1 Enquire about the availability of books. 2.1.2.2.2 Borrow books if available. 2.1.2.2.3 Return the borrowed books.
2.1.3 Definitions, Acronyms and Abbreviations
2.1.3.1 DDBMS – Database Management System.
2.1.4 References
2.1.4.1 IEEE standard 830-1998 recommended practice for Software Requirements Specifications-Description.
2.1.5 Overview
2.1.5.1 The SRS contains an analysis of the requirements necessary to help easy design.
2.1.5.2 The overall description provides interface requirements for the Library Management System, product perspective, hardware interfaces, software interfaces, communication interface, memory constraints, product functions, user characteristics and other constraints.
2.1.5.3 Succeeding pages illustrate the characteristics of typical naïve users accessing the system along with legal and functional constraints enforced that affect Library Management System in any fashion.
2.2 THE OVERALL DESCRIPTION
2.2.1 Product perspective 2.2.1.1 Hardware interfaces 2.2.1.1.1 Hard disk: The database connectivity requires a hardware configuration that is on-line. This makes it necessary to have a fast database system running on high rpm hard disk permitting complete data redundancy and back-up systems to support the primary goal of reliability. 2.2.1.1.2 The system must interface with the standard output devise, keyboard and mouse to interact with this software. 2.2.1.2 Software interfaces 2.2.1.2.1 Back End: MS-Access 2007 2.2.1.2.2 Front End: Microsoft Visual Basic 6. 2.2.1.3 Memory Constraints 2.2.1.3.1 No specific constraints on memory. 2.2.1.4 Operations 2.2.1.4.1 The software allows three modes of operations 2.2.1.4.1.1 Enquire about the availability and status of books. 2.2.1.4.1.2 By extracting the username and password the software allows the user to borrow a maximum of three books. 2.2.1.4.1.3 By extracting the username and password the software allows the user to return the borrowed books.
2.2.2 Product Functions 2.2.2.1.1 Enquire about the availability and status of books. 2.2.2.1.2 Search the availability of book by entering the title of the book. 2.2.2.1.3 Search the availability of book by entering the author of the book. 2.2.2.1.4 The software validates the authentic user by extracting their user name and password. 2.2.2.1.5 After the validation of the user software allows the user to borrow a maximum of three books based on the number of books which where already borrowed. 2.2.2.1.6 After the validation of the user software allows the user to return the books, which where borrowed.
2.4 FRONT – END DESCRIPTION
The library management system is automated library system where the user can
search for the book by either entering the details of the book or the author’s name. By
entering the username and the password the software, by checking the number of books
that are already borrowed enables us to borrow a maximum of three books. And by
entering the username and password (card number), which is unique, the user can return
the books.
2.5 BACK – END DESCRIPTION
The library management system consists of two tables. One contains the student
details such as the name, card number that is the password, title and the author of the
three books, which could be borrowed. The book details consist of the title of the book,
number of copies, author and the availability status.
2.6 DATA STRUCTURES
2.6.1. BOOK DETAILS
FIELD NAME TYPE CONSTRAINTS
REGISTER_NO NUMBER NOT NULL
BOOK_ID NUMBER NOT NULL
ISSUE_DATE DATE/TIME
RETURN_DATE DATE/TIME
BOOK_NAME TEXT
2.6.2. STUDENT DETAILS
FIELD NAME TYPE CONSTRAINTS
REGISTER_NO NUMBER NOT NULL
FNAME TEXT NOT NULL
LNAME TEXT
GENDER TEXT
DEPT TEXT
EMAIL TEXT
PASSWORD TEXT
NO_OF_BOOKS NUMBER
2.7 DATA FLOW DIAGRAM
4.0 SAMPLE FORMS
MAIN MENU FORM
MEMBERSHIP FORM
LOGIN FORM
BOOK ENQUIRY FORM
4.0 RESULT:
Thus the online Library System was implemented using the specified front end and
back end tools.
EX NO : 2
Date : AUTOMATED BANKING SYSTEM
1.0 PROBLEM DEFINITION
To develop an automated banking system, which is required to perform the following functions: 1.1 The customer logs into the system using card number and pin number. The system checks for validation. 1.2 The system queries the customer for the type of account either fixed deposit or credit account. After getting the type of account the system shows the balance left. 1.3 The system queries the customer for the transaction type either withdrawal or deposit and the required amount. The user enters the amount and the transaction if carries out
2.0 SRS DOCUMENT FOR AUTOMATED BANKING SYSTEM
2.1 INTRODUCTION
2.1.1 Purpose 2.1.1.1 The purpose of this SRS is to describe the requirements involved in developing an Automated Banking System (ABS). 2.1.1.2 The intended audience is any person who wants 2.1.1.2.1 To create account. 2.1.1.2.2 To withdraw or deposit either in fixed deposit or credit account.
2.1.2 Scope 2.1.2.1 The product is titled Automated Banking System (ABS). 2.1.2.2 The product will perform the following tasks 2.1.2.2.1 Allow a new user to create an account, either fixed or credit account by entering the details and by depositing an initial amount. 2.1.2.2.2 Allow the existing user to enter his account details like card number, pin number and account type to view his balance. 2.1.2.2.3 Allow the existing user to deposit an amount by entering the amount to be deposited after the balance had been viewed. 2.1.2.2.4 Allow the existing user to withdraw an amount by entering the amount to be withdrawn after the balance had been viewed. 2.1.2.2.5 The primary benefits expected of the system are: user friendly, continuous connectivity without failure, fault tolerant and involves lesser manpower.
2.1.3 Definitions, Acronyms and Abbreviations 2.1.3.1 ABS: Automated Banking System.
2.2.2.1.2 Customer address. 2.2.2.1.3 Required account type. 2.2.2.1.4 Pin Number. 2.2.2.1.5 Initial deposit.
2.2.2.2 Operating with created account The user should be able to operate with his new account after: 2.2.2.2.1 Entering card number. 2.2.2.2.2 Entering pin number. 2.2.2.2.3 Entering the account type, transaction type and amount involved in the transaction.
2.2.3 User characteristics 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ïve users. 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 this product.
2.2.4 Constraints: 2.2.4.1 At the time of creating the new account, each user gives a pin number and is provided with a unique card number that must be used for further transactions. Hence the user is required to remember or store these numbers carefully. 2.2.4.2 At the time of creating the new account, the initial deposit should not be less than the specified amount.
2.3 SPECIFIC REQUIREMENTS
2.3.1 Logical Database Requirements 2.3.1.1 The system should contain databases that include all the necessary information for the product to function according to the requirements. These include relations such as Customer Details and Account Details. 2.3.1.2 Customer details refer to the customer’s name and address. Account details of the customer include the card number, account type, transaction type and the pin number given by the user to be used at the time of the transaction at the bank.
2.4 FRONT – END DESCRIPTION
The front end for the Automated Banking System (ABS) 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 either crate a new account or to operate through an existing account. The “create account” module contains a provision to create a new account after collecting the customer name, address and other details. The card number and pin number of the user is obtained every time there is a transaction. The user is requested to select the required type of transaction and the amount involved in the transaction.
2.5 BACK – END DESCRIPTION
The Automated Banking System (ABS) database contains only one table. It correlates a unique card number, customer name, account type, pin number and the balance.
2.6 DATA STRUCTURES
2.6.1. ACCOUNT DETAILS FIELD NAME TYPE CONSTRAINTS NAME TEXT ACC_NO AUTONUMBER NOT NULL AGE NUMBER GENDER TEXT EMAIL TEXT PHONE_NO NUMBER PASSWORD TEXT BALANCE NUMBER
2.7 DATA FLOW DIAGRAM:
User
Enters a/c number + pin number
Displays report on a/c details
Enters details about new transaction
Generates error report
Display summary report Queries for details
Administrator
Database
Commits transaction
Checks for availability
Update