Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
59 views

Lab 2 Database

This document describes a laboratory exercise on requirement analysis and data modeling for a railway reservation system. The student identified 7 functional requirements for the system including allowing customers to book tickets and check their PNR. An entity relationship diagram with entities like user, customer, train, and booking was created to model the data requirements. The diagram showed relationships like a user managing trains and a customer requesting a booking. The student analyzed how properly identifying requirements helps create an efficient software solution for the client.

Uploaded by

Pritam Das
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
59 views

Lab 2 Database

This document describes a laboratory exercise on requirement analysis and data modeling for a railway reservation system. The student identified 7 functional requirements for the system including allowing customers to book tickets and check their PNR. An entity relationship diagram with entities like user, customer, train, and booking was created to model the data requirements. The diagram showed relationships like a user managing trains and a customer requesting a booking. The student analyzed how properly identifying requirements helps create an efficient software solution for the client.

Uploaded by

Pritam Das
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Name: Pritam Das Roll Number: 17ETCS002130

Laboratory 2
Title of the Laboratory Exercise: Requirement analysis and data modelling
1. Introduction and Purpose of Experiment
The requirements analysis phase produce both data requirements and functional
requirements. The data requirements are used as a source of database design and should be
specified as detailed and complete form as possible. In data modelling, the designers first
create a conceptual model of how data items relate to each other. By doing this lab,
students will be able to perform data modelling of the application.

2. Aim and Objectives


Aim
 To analyse the given application and create a data model
Objectives
At the end of this lab, the student will be able to
 Identify functional and data requirements from problem statement
 Create a data model from the data requirements

3. Experimental Procedure
 Read the problem statement and identify requirements
 Perform data modelling
 Document the requirements and ER diagram

4. Question
Students have to choose one of the following problem statements and develop the software
solution. The Course leader is the customer. Contact the Course leader for any clarifications.
1. Student enrolment system
2. Automobile sales system
3. Railway reservation system
Perform the following based on the problem statement you have chosen
a. Analyse the given application and list the functional and data requirements
b. Perform data modelling based on the identified data requirements
As my registration number is 17ETCS002130 so I have to do documentation for 3rd problem.
5. Calculations/Computations/Algorithms
Functional requirements describe required behaviour in terms of required activities, such as
Name: Pritam Das Roll Number: 17ETCS002130

reactions to inputs, and the state of each entity before and after an activity occurs. Functionality
includes:
–What will the system do?
–When will the system do it?
–Are there several modes of operation?
–What kind of computation/data transformation must be performed?
–What are the appropriate reactions to possible stimuli?
Functional requirements for the railway reservation system are:
𝐹𝑅_1: the application should allow user to access to all the bookings that customers are doing and
manage it.
𝐹𝑅_2: the application should allow customer to enter date and route of the journey.
𝐹𝑅_3: the application should show all the trains for the entered date.
𝐹𝑅_4: the application should allow customer to book the tickets after entering all the details (name, age,
gender, contact number).
𝐹𝑅_5: the application should send confirmation mail/text to the customer that will contain seat number,
PNR is ticket is confirmed else booking status.
𝐹𝑅_6: the application should allow customer to check PNR.
𝐹𝑅_7: the application should allow customer to cancel the tickets and process refund.
6. Presentation of Results

fig 2.1 –ER Diagram for Railway Reservation System DB


This is ER diagram for railway reservation system. This conceptual model has many entities
as use, customer, train, payment, confirmation mail etc. it is representing attributes of all
Name: Pritam Das Roll Number: 17ETCS002130

the entity and relationship between the entities.


Relationships between entities are:
 User does log-in
 User manages train/station/customer
 Customer does customer log-in
 Customer requests booking
 Customer provides journey detail
 Booking require journey detail/payment
 Payments results confirmation mail
7. Analysis and Discussions
Analysing the requirements of the software which client wants helps to create an efficient
software for the client. The requirements of the application need to be identified and
elicited so that the solution covers all aspects. The method and feasibility of implementing
the requirements is analysed, for example for the applications like railway ticket booking the
user must be given an option of cancellation for his booking and thus, the requirements like
this must be planned ahead properly. Entity Relationship Diagram, also known as ERD is a
type of structural diagram for use in database design. An ERD contains different symbols and
connectors that visualize two important information: The major entities within the system
scope, and the inter-relationships among these entities.
8. Conclusions
The requirements for the given application i.e. online train ticket booking was analysed and
then grouped into functional requirements. The various aspects of the application working
were touched and the important ones are noted into the functional requirements in a
proper order of their action. The ER diagram for the given railway ticket booking application
was created successfully. The entities of the ER diagram were identified such as user, train
and booking. The entities or the attributes of each entity were also identified and displayed
in the diagram.
9. Comments
1. Limitations of Experiments
a) Loss of information content: Some information be lost or hidden in ER model
b) Limited relationship representation: ER model represents limited relationship as compared to
another data models like relational model etc.
c) No representation of data manipulation: It is difficult to show data manipulation in ER model.
d) Popular for high level design: ER model is very popular for designing high level design
Name: Pritam Das Roll Number: 17ETCS002130

e) No industry standard for notation


2. Limitations of Results
As most of the entity and relationships icons are interconnected so sometimes it’s quite complex to
understand. It doesn’t represent the data flow which is very important for conceptual model.
3. Learning happened
We learnt
a) the process of collecting requirement for an application
b) how to collect data and its attribute for the model
c) how to draw an ER diagram
d) what is the importance of an ER diagram
4. Recommendations
a) Make sure that each entity only appears once per diagram.
b) Name every entity, relationship, and attribute on your diagram.
c) Examine relationships between entities closely. Are they necessary? Are there any relationships
missing? Eliminate any redundant relationships. Don't connect relationships to each other.
d) Try to draw different UML diagrams also which will help in understanding data flow in the system.

You might also like