CASE STUDY 1

SYSTEM ANALYSIS AND DESIGN

Date: 02/11/2006
Note: Draw E-R Diagram, Data Flow diagrams (Context Level Diagram and
explode it into further levels of DFD) for the following case study of Library
Management System.
The Computer Science Department has a library wit ha collection of around 3000 books
relevant to the study of Computer Science and Engineering.
Every book in the library is identified through its Catalogue Number. The library
maintains a book Catalogue (ISBN, Title, Author, Publication House, etc.). It also records
the total number of book possessed by the library. For purchasing books, the library first
prepares a list of books based on recommendations from the staff. Then the list is revised
based on approval from the Head of Department (HOD). The library then obtains the
books from the approved vendors, assigns catalogue numbers to them, updates Book
Catalogues and other records and forwards the bill to the HOD for payment.
For availing the facilities of the library a student needs to enroll enroll with it. For
enrollment, a student has to present his Student-ID card. The ID card has the information
for identifying and contacting a student besides his admission and course details. The ID
Card is also used to ascertain that the student is currently a student of Computer Science
Department. Then the student is enrolled with the library and is granted membership
through the issuance of a library card the valid for the current academic year. The library
verifies the valid-member status by using the library card number index into the
enrollment file.
The students submit issue-requests by providing catalogue number of the book. When a
student requests for a book to be issued, the students valid member status and
availability of a copy of the book are checked. If a copy of the book is available with the
library it is lent to the students, the transaction is recorded and the library card of the
student is withheld. The library maintains a record of issuance and returns (Catalogue
Number, library card number, date of issue, date of return, amount of fine) of books. A
student can borrow only one book at a time for one week. The student can get back his
library card on return of the book. Books returned late, attract a fine of one rupee per day.
Record of fine collection is maintained to generate useful statistics.

CASE STUDY 1

SYSTEM ANALYSIS AND DESIGN

Date: 02/11/2006
Note: Draw E-R Diagram, Data Flow diagrams (Context Level Diagram and
explode it into further levels of DFD) for the following case study of Airline
Reservation System.
Budget Air is a low fare Indian domestic airline that is gradually expanding its
operations. Currently it has a fixed weekly schedule of direct flights between a few cities
in India. The airline has a system that maintains necessary records of flights schedules
and corresponding fares and supports customer activities like planning journey,
reservation and cancellation and also maintains necessary databases.
The system helps customer in planning their journeys. On accepting a route from a user,
the system gives the schedules for the entire week for that route. On selecting a schedule
with schedule-ID and the date of journey, the system gives number of seats available and
the fare per ticket.
For reservation, a customer chooses schedule and mentions the date of journey and the
number of seats. The system checks for availability of seats for the journey and the seats
are reserved if available and tickets with ID number are issued on accepting passenger
details and actual fare payments from the customers.
As per airlines policy no refund is given for request made for cancellation after the
departure of flights. On receiving the request for cancellation of tickets, it is required to
verify that the date and time of journey is not earlier than the current date and time. The
tickets with ID number are marked as cancelled. The customer is paid due refund and a
receipt for cancellation. The seat numbers of those tickets are marked as available for
reuse on the schedule.
[Following terms are used to describe the system:
1. Aircraft: Type of plane. Eg: AIRBUS 320, BOIENG 737, etc.
2. Flight: Unique plane, Eg: Flight # BA123 is a unique plane of type AIRBUS
320 and BA321 is another flight of type AIRBUS 320.
3. Route: Unique combustions of origin and destination. Eg: MUMBAI to
DELHI is one route whereas DELHI to MUMBAI is another route.
4. Schedule: Prefix program describing the flight, the route, departure and
arrival times and the day of operation. Eg: The program that on Fridays,
BA123 flies from MUMBAI 7:00 AM to reach DELHI 8:00 am is a schedule.
5. Journey: Specific instance of a schedule. Eg: On 5th of May 2006 BA1234
make a journey leaving MUMBAI at 7:00 AM and reaching DELHI at 8:00
AM. ]