Requirement Engineering Tutorial (MMMTU) Dr.

Akshi Kumar, Goldsmiths

Requirement Engineering Tutorial Worksheet: Management System Development

Objective:
This worksheet is designed to guide students through the process of developing a management
system, focusing on requirement engineering aspects such as use case diagrams, data flow diagrams
(DFD), entity-relationship (ER) diagrams, and the software requirements specification (SRS)
document.

Project Ideas:
Select one of the following management system projects to develop:
1. University Course Registration System
2. Hospital Management System
3. Library Management System
4. Inventory Management System
5. E-Commerce Website System
6. Hotel Reservation System
7. Event Management System
8. School Management System
9. Restaurant Ordering System
10. Transport Management System

Requirements Engineering Tasks:

Task 1: Use Case Diagram
• Objective: Identify and visualize the interactions between users (actors) and the system.
• Instructions:
1. List all actors (e.g., students, professors, administrators) involved in the system.
2. Identify key use cases (actions or processes) actors perform (e.g., enrolling in
courses, managing inventory).
3. Draw a use case diagram showing actors and their interactions with the system.

Task 2: Data Flow Diagram (DFD)

• Objective: Map out the flow of information within the system.
• Instructions:
1. Identify the main processes (e.g., registration, order processing) in the system.
2. Determine data stores (databases or repositories where information is kept).
3. Draw the DFD showing how data moves between processes and data stores.

Task 3: Entity-Relationship (ER) Diagram

• Objective: Define the data model and the relationships between data entities.
• Instructions:
1. List all entities (e.g., Students, Courses, Orders) in the system.
2. Identify relationships between entities (e.g., Students enroll in Courses).
3. Draw the ER diagram, including entities, their attributes, and relationships.

Task 4: Software Requirements Specification (SRS) Document

• Objective: Document comprehensive and detailed requirements for the system.
• Instructions:
1. Introduction: Provide an overview of the system and its objectives.
Requirement Engineering Tutorial (MMMTU) Dr. Akshi Kumar, Goldsmiths

2. System Overview: Describe the general functions and operations of the system.
3. Functional Requirements: Detail each function the system must perform.
4. Non-Functional Requirements: Specify security, performance, and usability criteria.
5. Data Requirements: Outline the data to be stored and processed by the system.
6. Constraints and Assumptions: Note any limitations or assumptions affecting system
design.
7. Appendices: Include use case diagrams, DFDs, and ER diagrams.

Submission Guidelines:
• Compile your findings and diagrams into a comprehensive report.
• Ensure clarity, accuracy, and completeness in each section of the worksheet.

Here are ten management system project ideas that encompass these aspects, each with a brief
description of potential components to include in the requirement engineering phase:

1. University Course Registration System

• Use Case Diagram: Includes actors like students, professors, and administrators with
use cases such as enrolling in courses, managing course lists, and generating
timetables.
• DFD (Data Flow Diagram): Illustrates the flow of information between entities such
as student details, course details, and registration records.
• ER Diagram (Entity-Relationship Diagram): Shows entities like Students,
Courses, and Enrollments and their relationships.
• SRS (Software Requirements Specification): Detailed requirements including
functional, non-functional, performance, security, and usability criteria.

2. Hospital Management System

• Use Case Diagram: Actors include patients, doctors, nurses, and admin staff with use
cases for appointment booking, patient record management, and billing.
• DFD: Depicts data flow between patient records, appointment schedules, and billing
details.
• ER Diagram: Highlights entities such as Patients, Doctors, Appointments, and
Payments.
• SRS: Includes system scope, functional and non-functional requirements, data
security, and privacy requirements.

3. Library Management System

• Use Case Diagram: Actors are members, librarians, and administrators with use
cases for borrowing books, returning books, and managing inventory.
• DFD: Shows the flow of information for book loans, returns, and inventory updates.
• ER Diagram: Represents entities like Books, Members, Loans, and Returns.
• SRS: Details on system functionality, user interface requirements, performance
metrics, and backup procedures.

4. Inventory Management System

• Use Case Diagram: Includes actors such as stock manager, sales personnel, and
suppliers with use cases for stock entry, sales update, and order supplies.
• DFD: Illustrates data flow for inventory updates, sales records, and supply orders.
Requirement Engineering Tutorial (MMMTU) Dr. Akshi Kumar, Goldsmiths

• ER Diagram: Shows entities like Products, Sales, Suppliers, and Stock.

• SRS: Comprehensive requirements on inventory tracking, reporting features, data
integrity, and user access controls.

5. E-Commerce Website System

• Use Case Diagram: Actors include customers, sellers, and site administrators with
use cases for product browsing, placing orders, and managing listings.
• DFD: Depicts information flow for order processing, payment transactions, and
product listing updates.
• ER Diagram: Highlights entities such as Customers, Orders, Products, and Sellers.
• SRS: Detailed requirements including website functionality, payment security,
customer privacy, and system scalability.

6. Hotel Reservation System

• Use Case Diagram: Actors are guests, hotel staff, and managers with use cases for
booking rooms, managing reservations, and processing payments.
• DFD: Illustrates data flow between guest bookings, room availability, and billing.
• ER Diagram: Represents entities like Guests, Rooms, Bookings, and Payments.
• SRS: Includes detailed specifications on booking processes, room allocation logic,
payment processing, and customer service features.

7. Event Management System

• Use Case Diagram: Includes actors such as event organizers, participants, and
vendors with use cases for event creation, registration, and vendor management.
• DFD: Shows data flow for event scheduling, participant registration, and vendor
contracts.
• ER Diagram: Highlights entities like Events, Participants, Organizers, and Vendors.
• SRS: Detailed requirements on event scheduling, participant engagement, vendor
coordination, and security measures.

8. School Management System

• Use Case Diagram: Actors include students, teachers, parents, and administrators
with use cases for attendance tracking, grade reporting, and timetable management.
• DFD: Depicts information flow for student records, class schedules, and report cards.
• ER Diagram: Shows entities like Students, Classes, Teachers, and Grades.
• SRS: Comprehensive requirements on student information management, academic
performance tracking, and communication features.

9. Restaurant Ordering System

• Use Case Diagram: Includes actors like customers, kitchen staff, and cashiers with
use cases for placing orders, preparing food, and processing payments.
• DFD: Illustrates data flow for order entry, preparation tracking, and billing.
• ER Diagram: Represents entities such as Orders, Menu Items, Customers, and
Payments.
• SRS: Detailed specifications on order processing, menu management, customer
service, and payment security.
Requirement Engineering Tutorial (MMMTU) Dr. Akshi Kumar, Goldsmiths

10. Transport Management System

• Use Case Diagram: Actors are passengers, drivers, and route managers with use
cases for booking rides, scheduling routes, and managing vehicles.
• DFD: Shows data flow for ride booking, vehicle tracking, and route planning.
• ER Diagram: Highlights entities like Vehicles, Routes, Bookings, and Passengers.
• SRS: Includes detailed requirements on booking systems, vehicle maintenance
tracking, route optimization, and safety protocols.

x------------------------------------------------------------------------------------------------------------------------x