Scribd
Upload
13 views7 pages

SRE Lab Task 3

The document outlines the Software Requirements Specification (SRS) for the Alameen Railway Ticket Vending System (TVS), detailing its functional and non-functional requirements. It describes the system's capabilities for ticket purchasing, travel card management, and operator functions, emphasizing user accessibility and security. Additionally, it includes a breakdown of system features, user roles, and operational assumptions.

Uploaded by

Ehtisham Amjad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
13 views7 pages

SRE Lab Task 3

The document outlines the Software Requirements Specification (SRS) for the Alameen Railway Ticket Vending System (TVS), detailing its functional and non-functional requirements. It describes the system's capabilities for ticket purchasing, travel card management, and operator functions, emphasizing user accessibility and security. Additionally, it includes a breakdown of system features, user roles, and operational assumptions.

Uploaded by

Ehtisham Amjad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Software Requirements Engineering (Lab Task 3)

Submitted to
Dr. Naseer Jan
Submitted by
M Ehtisham Amjad (231996)
BSSE-IV-B

Question:
Alameen is a railway system that wants to install ticket vending machines (TVMs) on all rail stations in
Pakistan. The TVMs will allow the passenger to buy a ticket/pass using cash, coins, debit cards or credit
cards. The interface of the TVMs should make it very easy for the passengers to buy their tickets.
Besides the ticket/pass, the system should also support the card for traveling purposes. The card can be
charged, recharged, etc.
This system should be designed in such a way that the passenger first selects the ticket type, and
transaction mode and then gets a pass/ticket. Passengers can be adults, senior/disabled citizens, children
(5-14 years old), high school or college students. Ticket type can be either a two-hour pass, midday pass,
or AM pass (Monday through Friday from 09:30 am to 02:30 pm), a PM pass (noon through the end of
service on the date purchased), a day pass, a 7-day pass, or a 31-day pass. There will be no ticket fare for
senior or disabled citizens. The only thing they have to show during traveling is a valid ID and ticket.
The ticket fare for children (5-14 years old), and high school or college students will be reduced and
they will have to show a valid Id along with the ticket (reduced fare) to the ticket-checking authority.
The system should restrict unauthorized users from using the system. The system should be fast enough
that it should accept the input from the user in less than 1 second. The system should be fast enough to
print the ticket to the user within 3 to 5 seconds when user inserts all required information. The system
should be available 24 hours a day and 7 days a week. The system will also be used by the operator to
know the cash and coins inside the machine and withdraw or deposit cash when required. The system is
designed in such a way as to allow the admin to generate reports. The reports include how many tickets
are sold, the number of transactions, cash or coins collected, change fares, and cash or coins dispensed.
To understand the operation of Ticket Vending Machines (TVMs) and how to purchase a ticket through
TVMs, please watch the following short tutorials as listed below:
[1] Daily News Pakistan, “How to use ZU card for Peshawar BRT?|[available Online]
https://www.youtube.com/watch?v=9BEglyg538o [Accessed 11/3/2025].

[3] CMTA, Capital Mass Transit Authority, [available online] https://cmta.com.pk/ [Accessed
11/3/2025]
[2] Dart Dallas, “How to use a DART TVM” [available Online] https://www.dart.org/fare/general-fares-
and-overview/fares/ticket-vending-machine [Accessed 11/3/2025].

a. What are the functional and non-functional requirements in above-mentioned case study?
b. Draw the use case diagram for above-mentioned scenarios
c. List down the nouns, noun phrases, and verbs
d. Draw UML domain model
Reply:
Software Requirements Specification (SRS) for Alameen Railway Ticket Vending
System
1. Introduction
The Alameen Railway Ticket Vending System (TVS) is a self-service ticketing solution for railway
stations across Pakistan. It enables passengers to purchase tickets, manage travel cards, and make secure
transactions while ensuring smooth operations for operators and administrators. This document outlines
its functional, non-functional, and operational requirements.
2. Scope
The TVS provides:
 Passengers – Ticket purchases, fare adjustments, multiple payment methods.
 Operators – Cash inventory monitoring, deposits/withdrawals.
 Administrators – Reports on sales, transactions, and system errors.
 System Features – Secure payments, 24/7 operation, integration with external databases

3. Definitions, Acronyms, and Abbreviations

● TVS: Ticket Vending System


● TVM: Ticket Vending Machine
● SRS: Software Requirements Specification
● IEEE: Institute of Electrical and Electronics Engineers
● ID: Identification Document
● GUI: Graphical User Interface
● API: Application Programming Interface

4. References

● IEEE Std 830-1998 – IEEE Recommended Practice for Software Requirements Specifications.
● Industry standards on data privacy and payment security.
● Related documentation for external payment gateways and ID verification systems.

5. System Overview
Feature Description
Ticketing & Passes Purchase various ticket types, print receipts.
Travel Cards Recharge, balance inquiries, transaction history.
Fare Adjustments ID-based discounts for seniors, students, disabled.
Payments Cash, coins, debit/credit cards supported.
Monitoring Operators track cash levels, enable maintenance mode.
Feature Description

Reports & Security Transaction logs, encrypted data, multi-factor authentication.


6. Users & Assumptions
 Passengers – General public with a user-friendly interface.
 Operators – Trained personnel handling maintenance & cash.
 Administrators – IT staff managing security, audits, and reports.
 Assumptions – Requires stable power/network, compliance with security standards, and seamless
third-party integration.
7. Functional Requirements
1. Ticket Selection & Purchase
1. Display available ticket options and fares.
2. Allow passengers to select multiple tickets.
3. Include "Select Ticket Type" and "Choose Payment Method" options.
2. Payment Processing
1. Accept cash, coins, and card payments.
2. Validate payments before issuing tickets.
3. Include "Insert Payment" use case.
3. Ticket Issuance
1. Dispense printed tickets within 3–5 seconds.
2. Generate digital receipts for electronic payments.
3. Extend "Print/Dispense Ticket" use case.

4. Travel Card Management

1. Support travel card recharges and balance inquiries.


2. Update balance immediately after transactions.
3. Include "Charge/Recharge Travel Card" use case.
5. Fare Adjustments & ID Validation
1. Validate ID for discounted fares (seniors, students, disabled).
2. Adjust fares based on user category.
3. Include "Validate ID" use case.
6. Operator Functions
1. Monitor cash/coin levels in real time.
2. Perform cash deposits and withdrawals.
3. Include "Monitor Cash/Coins" and "Withdraw/Deposit Cash" use cases.
7. Reporting & Maintenance
1. Generate reports on ticket sales and transactions.
2. Enable maintenance mode for diagnostics.
3. Include "Generate Reports" and "Enter Maintenance Mode" use cases.
8. Error Handling & Notifications
1. Detect transaction errors and printer malfunctions.
2. Provide clear notifications with solutions.
3. Extend "Display Error/Notification" use case.
8. Non-Functional Requirements
1. Performance
1. Process inputs within 1 second, issue tickets within 3–5 seconds.
2. Availability & Reliability
1. Ensure 99.9% uptime, with backup recovery mechanisms.
3. Usability
1. rovide an intuitive GUI with clear on-screen instructions.
4. Security & Access Control
1. Implement multi-factor authentication for operators/admins.
2. Encrypt all sensitive data (payments, IDs).
5. Scalability & Maintainability
1. Modular architecture for easy updates.
2. Support expansion to multiple railway stations.
6. Localization & Multilingual Support
1. Support English and Urdu with dynamic switching
7. Logging & Audit
1. Maintain detailed logs of transactions and security events.
9. Extraction of Nouns, Noun Phrases, and Verbs
9.1 Nouns and Noun Phrases
 Nouns:
1. system, ticket, pass, card, cash, coins, machine, transaction, payment, error, log, report,
user, interface, maintenance, backup.
 Noun Phrases:
1. Ticket Vending Machine
2. travel card
3. valid ID
4. ticket/pass
5. payment method
6. cash/coin monitoring
7. ticket sales report
8. audit log
9. user interface
10. maintenance mode
11. error notification
12. transaction processing
9.2 Verbs
 Verbs:
1. select
2. purchase
3. insert
4. print
5. dispense
6. charge
7. recharge
8. validate
9. restrict
10. accept
11. monitor
12. withdraw
13. deposit
14. generate
15. process
16. log
17. rollback
18. display
19. manage
20. integrate
21. authenticate
10. Use Case Diagram
 Page Turn Over

You might also like