System Analysis and Design: Mohd Shoaib Ahmad 752/IT/14 IT Section 1 IV Semester

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 31

System Analysis

and
Design

Mohd Shoaib Ahmad


752/IT/14
IT section 1
IV Semester
Index
S.no Topic Sign
1. Result Management System (SRS)

2. Ordering System (DFD)

3. Distance education university (DFD)

4. Automated Library Management System(Use case and


DFD)

5. Online airline reservation system (use case)

6. Railway Reservation System (use case and DFD)

7. Online Job Portal (ER Diagram and DFD)

8. Nsit Attendance System (ER Diagram and DFD)

9. Online Shopping System(ER Diagram and DFD)

10. Online Ticket Booking- BUS (ER Diagram and DFD)

11. Online Hotel Management System (ER Diagram and


DFD)

12. Library Management System(Data Dictionaries)


EXERCISE 4:
Nsit wants to develop software for automated library management system. A problem
statement needs to be developed by the students. The problem statement gives the overview of
existing system and broad expectations from new software system.

Write and draw the following documents for the above problem:

1. Problem statement
2. Use case diagram
3. DFD (upto level 2)

Solution:
1.) PROBLEM STATEMENT

The purpose of the LIBRARY MANAGEMENT SYSTEM is mainly to provide automation to the
library. The categories of users provided are:
LIBRARIAN: He can read or write the information about any member and can update, delete
or create a membership plan.
MEMBER: He can get a book issued.
The Scope of the application is wide and can be used with any education institute and also
can be used in offices with the necessary modifications done.

With this application, the manual application is converted into automated online
application. For example purposes, customized data is being used for this purpose. The user
will not have the privilege to enter the data about the books.
The three major components in the application are:
-LOGIN
-ISSUE/BORROW BOOK
-BALANCE DUES
LEVEL 0

LEVEL 1
LEVEL 2
Inquiry for Membership

Request for Book Issue

Request for Book Return

Search Book

Issue Membership Card

Cancel Membership

Issue Book

Return Book

Maintain Book Record

Update Member Detail


EXERCISE 5:
Consider an online airline reservation system. You may want to check the airline web sites to
get idea.

1. Identify the actors for online airline reservation system. Explain the relevance of each
actor.
2. One use case is to make a flight reservation. List four additional use cases at a
comparable level of abstraction. Describe each use case with exceptional flow.
3. Prepare a Use-Case diagram for an online airline reservation system. Write Use-Case
description of each Use-Case.
4. Identify at least four states of ticket object and draw the state transition diagram for the
same.

Solution:
I. The actors are :
1. Reservation clerk:
the reservation clerk carries out the required tasks corresponding to the
reservation
2. Admin:
Administers the website and maintains confidential login information.
3. Passenger:
the passenger visits the site for booking/cancelling tickets
II. The 5 Use Cases are:
1. Maintaining Login Details
2. View flight details
3. View flight status
4. Flight Reservation
5. Ticket cancellation
6. Report Generation

Use Case Descriptions:

1. Maintaining Login Details:


On the request of this use-case the passenger creates a login id for himself and
logs in before the reservation procedure.
Exception- When the User enters wrong password.
2. View Flight Details:
On the request of this use-case the system can have status of the seats available
for the passenger.
Exception: When the entered Flight Id is wrong.
3. View Flight Status:
On the request of this use-case the system gives the details about the required
flight.
Exception- When the flight corresponding to the entered Flight Id has been
cancelled under to certain circumstances.
4. Flight Reservation:
On the request of this use-case the system can add,
update the tickets to be reserved.
Exception- When the payment process does not get completed
5. Cancellation Tickets:
On the request of this use-case the system can cancellation of the unwanted
tickets.
Exception- When the cancellation is applied less than 36 hours before the flight
departure.
6. Report Generation:
Provision for generation of various reports.

III. USECASE DIAGRAM:

Report Generation

Admin
Login

Passenger

View Flight Details

Reservation Clerk View Reservation


Status

Flight Reservation

Ticket cancellation
IV. State Transition Diagram for Ticket:

Cancel

Make
Pay money
Reservation
Made Paid Cancel/
Refund

Generate Ticket
Cancelled
by
customer
Cancel/
Used Ticketed Refund
Destroy Give Ticket

EXERCISE 6: A railway authority desired to automate all operations of ticket management for all
scheduled trains. The system consists facilities for:

a) Ticket generation
b) Cancellation
c) Rescheduling

Write and draw following documents for above problems:

a) Problem statement
b) Use case diagram
c) Data flow diagram

Solution:

PROBLEM STATEMENT

A software has to be developed for automating the manual railwayreservation system. The
system should have distributed functionalities asdescribed below:-

1.RESERVE SEAT
A passenger should be able to reserve a seat in the trainspecified by him if available. For this he
has to fill a reservation form with thedetails about his journey. The clerk checks for the
availability of the seat in thetrain and if the seat is available then he makes entries regarding
train name,train number, date of journey, boarding station, destination. The passenger isthe
asked to pay the fair .After making payment the passenger can collect theticket from the clerk.

2.CANCEL RESERVATION
There may arise a case when the passenger wants to cancel his reservation .For this he has to fill
acancellation form providing all the details about the ticket reserved byhim. The clerk then
checks for the entries from the database and cancelsthe reservation finally returning the ticket
amount with some deduction

3.UPDATE TRAIN INFORMATION & REPORT GENERATION


Onlythe Administrator has the right to make changes in train details(trainname, train no.
etc.).The system should also be able to generate reportwhen needed in the form of reservation
charts , train schedule charts etc.

4.LOGIN
Only the user with specified login id & password can getaccess to the system. This provides
security from unauthorized access.

5.VIEW RESERVATION STATUS & TRAIN SCHEDULE


All the usersshould be able to see the information about the reservation status & trainschedule,
train name, train number etc.

Use Case Diagram


DFD

LEVEL 0
LEVEL 1
EXERCISE 7: Draw the ER diagram and the data flow diagrams (upto 2 levels) Online Job Portal.

Solution:

ER Diagram
DFD
LEVEL 2
EXERCISE 8: Draw the ER diagram and the data flow diagrams (upto 2 levels) NSIT Attendance
Management system.

Solution:

ER Diagram
DFD
LEVEL 0

LEVEL 1

LEVEL 2
EXERCISE 9: Draw the ER diagram and the data flow diagrams (upto 2 levels) online shopping
System.

Solution:

ER Diagram
DFD
LEVEL 0

LEVEL 1
LEVEL 2

1. For 2.0
2. For 4.0

3. For 5.0
EXERCISE 10: Draw the ER diagram and the data flow diagrams (upto 2 levels) Online Ticket
booking system.

Solution:

ER Diagram
DFD

LEVEL 0
EXERCISE 11: Draw the ER diagram and the data flow diagrams (upto 2 levels) online hotel
management system.

Solution:

ER Diagram
DFD

LEVEL 0
LEVEL 1
LEVEL 2
EXERCISE 12: Create Data Dictionaries for the any two flows of Library Management System.

Solution:

Author Table

Field Name Data Type Size Null Description

Author_id navchar 10 Not Primary key


Author_name Navchar 50 Not
Address Navchar 200
Phone Navchar 10
Fax navchar 10
Email navchar 20

Author Table Details

 Author table is connected with the Author form.


 In this table included field name, data type, size of the
character, end description.
 In the Author form included Author-id, Author-name, Address,
phone number, fax, Email.
 Author-id used for Primary key
 Author information is available for in this table.

Publisher Table

Field Name Data Type Size Null Description

Publisher_id navchar 10 Not Primary key


Publisher _name Navchar 50 Not
Publishing year Date/time Not
Publisher_edition Navchar 10 Not
Address navchar 200 Not
Phone navchar 10 Not
Fax navchar 10
email navchar 20

Publisher table Details

 Publisher table is connected with the Publisher form.


 In this table included field name, data type, size of the
character, end description.
 In the Publisher form included Publisher-id, Publisher-name,
Publisher-Year, Publisher-Edition ,Address ,Phone number ,fax
, email.
 Publisher-id used for Primary key.
 Publisher-information is available for in this table.

You might also like