CS510 Software Requirements and Specification Assignment 1 for Fall 2026 is built around a Smart Ride-Hailing System (SRHS) scenario. The assignment carries 20 marks and the due date is 5th November, 2026. The submission format is a Word document only. The solution file linked below classifies four statements, finds the quality flaws in three statements, and rewrites them into proper requirements.
What Does the Solution File Cover?
How Are S2, S5, S6 and S7 Classified?
S2 is a Functional Requirement: it describes a service the system must provide, letting a passenger search for available rides by distance, vehicle type, or driver rating. S5 is an Inverse Requirement: it states what the system must not do, hiding driver contact numbers from passengers after a ride is completed. S6 is a Design and Implementation Constraint: it fixes the technology and platform, Python with Django on Linux servers only. S7 is a Domain Requirement: it states a business rule from the ride-hailing domain, that no account may carry an overdue balance except VIP accounts, which may go negative up to $50. Each statement is also rewritten in the standard “The system shall…” form, the same skill tested in the CS504 Assignment 1 solution on requirement engineering.
Which Quality Rules Do S1, S3 and S4 Break?
S1 breaks Feasibility: a single basic web server cannot realistically process 10,000 ride requests per second. S3 breaks Consistency: one requirement prescribes two different date formats, mm/dd/YYYY and dd/mm/YYYY, and it also applies a date format to driver ratings, which are not dates at all. S4 breaks Verifiability: phrases such as easy to use and visually pleasing are subjective, so no test can decide whether the requirement is met. The CS507 Assignment 1 solution shows the same style of scenario based analysis for system requirements.
How Are the Faulty Requirements Rewritten?
Each faulty statement is rewritten so that it is measurable and free of contradictions. S1 is rewritten around suitably scaled server infrastructure at peak load instead of a single basic server. S3 is rewritten so that ratings are shown as numeric values and every date uses one format, dd/mm/YYYY. S4 is rewritten with a testable target: at least 90% of first-time users completing registration and ride booking without help during usability testing.
How Do You Download the Solution File?
You can download the complete solution file from Google Drive using the link below. It contains the scenario statements, the Question 1 classifications with standardized statements, and the Question 2 flaw analysis with rewrites. Fill in your own name and student ID in the blanks at the top before submitting.
Frequently Asked Questions
How do you tell a functional requirement from a domain requirement?
A functional requirement describes a service or behavior of the system itself, such as searching for rides. A domain requirement comes from the rules of the business area, such as account balance limits for VIP customers.
Why is a single basic server not feasible for 10,000 requests a second?
Because the load is far beyond what one basic machine can process in real time. A feasible requirement must match the capacity of the infrastructure it assumes, so the rewrite asks for suitably scaled servers.
What makes a requirement verifiable?
A requirement is verifiable when a test can clearly pass or fail it. Numbers, percentages, and defined formats are verifiable. Opinions such as easy to use or visually pleasing are not, because two testers can disagree.
Last updated: November 2026.
