--- title: "Requirement alternatives and SRS document" subject: "Object Oriented Analysis and Design" chapter: 2 key: "semester_6/object_oriented_analysis_and_design:requirement-alternatives-srs-unified-process" source: https://www.bctengineer.com/q/semester_6/object_oriented_analysis_and_design/requirement-alternatives-srs-unified-process site: BCT Engineering --- # Requirement alternatives and SRS document Object Oriented Analysis and Design · Chapter 2: Object Oriented Analysis - Asked in: 2073 Bhadra, 3+5 marks - Video: [Software Requirements | Requirement Engineering | Feasibility Study, Elicitation, SRS, Validation](https://www.youtube.com/watch?v=JNLRXczA9Y0) — Gate Smashers - Page: https://www.bctengineer.com/q/semester_6/object_oriented_analysis_and_design/requirement-alternatives-srs-unified-process - Whole chapter: https://www.bctengineer.com/md/semester_6/object_oriented_analysis_and_design/chapter-2 ## Question What are requirements process alternatives before having OO Analysis? As you are already familiar with IOE exam processes, prepare a brief SRS document following unified process in OOAD. ## Short answer Alternatives include traditional SRS, structured analysis, prototyping, user stories, JAD workshops, and use-case-driven approaches. An SRS for IOE exam system following the Unified Process covers use cases like exam form submission, admit card generation, marks entry, result publication, with performance, security, and reliability non-functional requirements, and iterative development. ## Answer #### Requirement process alternatives before OO analysis Before OOA starts, requirements may be obtained and recorded in different ways, which are alternatives to (or inputs of) use cases: 1. **Traditional SRS (IEEE 830)** - A document listing functional and non-functional "The system shall ..." statements. 2. **Structured analysis** - Requirements as DFDs, data dictionary and process specifications. 3. **Prototyping** - Quick mock-ups shown to users to clarify requirements. 4. **User stories** (agile) - Short statements "As a ..., I want ..., so that ...". 5. **Joint Application Development (JAD) / workshops** - Requirements agreed in group sessions. 6. **Use case driven approach** - Used in the Unified Process; describes functionality as scenarios of actor-system interaction. 7. **Interviews, questionnaires, observation, document study** - the sources for all of them. #### Brief SRS following the Unified Process: IOE Exam Management System **1. Introduction** - 1.1 Purpose: Specify requirements for the system used by IOE to conduct examinations and publish results. - 1.2 Scope: Registration of exam forms, exam routine, roll number and admit card, marks entry and result publication. - 1.3 Definitions: ECD (Exam Control Division), Campus, Examiner. - 1.4 References: IOE examination rules, IEEE 830. **2. Overall description** - Product perspective: web-based, standalone with a central database. - Users (actors): Student, Campus Officer, Examiner, ECD Staff, Administrator. - Constraints: must support thousands of students concurrently on result day; data kept secure. - Assumptions: internet available at campuses. **3. Use cases (functional requirements)** - UC1 Submit Exam Form (Student). UC2 Generate Admit Card. UC3 Prepare Exam Routine (ECD). UC4 Enter Marks (Examiner). UC5 Process Result (ECD). UC6 Publish and View Result (Student). UC7 Manage Users (Admin). - Each use case has actor, pre-condition, main flow, alternate flows, post-condition (in detail document). **4. Supplementary (non-functional) requirements** - Performance: result page loads in under 3 s. - Security: role-based login; audit of mark changes. - Reliability: 99% availability in exam periods; daily backup. - Usability: usable on mobile browsers. **5. Domain model (glossary)**: Student, Exam, Subject, Mark, Result, Campus. **6. Iteration plan:** Iteration 1 - UC1, UC2; Iteration 2 - UC4, UC5; Iteration 3 - UC6, UC3. ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. Which is NOT an alternative way to gather or record requirements before OO analysis? A. User stories B. Prototyping C. Joint Application Development workshops D. Compiling the source code Answer: D. Compiling code is not a requirements technique; the others are listed alternatives (also SRS, structured analysis, interviews). (Key point: Requirement process alternatives) 2. What does the use case driven approach of the Unified Process describe? A. Functionality as scenarios of actor-system interaction B. Only the database schema C. Only non-functional requirements D. Hardware cost Answer: A. The Unified Process records functional requirements as use cases. (Key point: Use case driven approach) 3. Which sections make up the brief SRS? A. Only a glossary B. Only a cost table C. Introduction, overall description, use cases, supplementary requirements, domain model, iteration plan D. Only a test report Answer: C. The SRS covers introduction, overall description, use cases, supplementary (non-functional) requirements, domain glossary and iteration plan. (Key point: Parts of an SRS) 4. Which item belongs in the supplementary (non-functional) requirements? A. UC4 Enter Marks B. Result page loads in under 3 s and role-based login C. Student submits exam form D. Examiner actor Answer: B. Performance, security, reliability and usability go in the non-functional section; use cases are the functional part. (Key point: Supplementary requirements) ## Related in Object Oriented Analysis and Design - [Is OOP enough in OOAD](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Aoop-enough-in-ooad) — Object Oriented Analysis and Design, chapter 1 - [Types of models in OOAD](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Atypes-of-models-in-ooad) — Object Oriented Analysis and Design, chapter 1 - [OO design cycle vs conventional cycle](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Aoo-design-cycle-vs-conventional) — Object Oriented Analysis and Design, chapter 1 - [Requirement elicitation and system behavior](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Arequirement-elicitation-in-ooa) — Object Oriented Analysis and Design, chapter 2 - [Short note: Requirement gathering methods](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Ashort-note-requirement-gathering-methods) — Object Oriented Analysis and Design, chapter 2 - [Activities in OO system development](https://www.bctengineer.com/question.md?key=semester_6%2Fobject_oriented_analysis_and_design%3Aactivities-oo-system-development) — Object Oriented Analysis and Design, chapter 1 ## Related in other subjects - [Requirement gathering processes compared](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Arequirement-gathering-processes) — Software Engineering, chapter 1 - [Why an SRS is worth the early effort](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Asrs-justify) — Software Engineering, chapter 1 - [SRS and characteristics of a good SRS](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Asrs-characteristics) — Software Engineering, chapter 1 - [Requirement management process](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Arequirement-management) — Software Engineering, chapter 1