Use Cases and SRS Documents properly.pptx

Use cases and srs documents

1. USE CASES AND SRS DOCUMENTS PRESENTED BY: SOWMIYA K R O DEEPA SRI ANUSHA T DHARSHINI T

2. Introduction to Use Cases Definition of Use Cases Use cases describe user interactions with a system to achieve specific goals. Importance of Use Cases They provide insights into system functionality from a user's perspective. 1 2 Components of Use Cases Includes title, actors, preconditions, event flow, postconditions, and error paths. 3

3. Introduction to SRS Documents Definition of SRS A comprehensive description of the intended software's purpose and environment, outlining functional and non-functional requirements. Purpose of SRS Serves as a contract between stakeholders and developers to ensure clear understanding of expected capabilities and limitations. 1 2 SRS Structure Includes sections on introduction, overall description, specific requirements, use cases, and user interface requirements. 3

4. Real-time Example 1: E-commerce Platform 1 User Selects Items Adds to Cart 2 Completes Purchase 3

5. Real-time Example 2: Hospital Management System This use case outlines the comprehensive process patients go through to book a doctor appointment, coupled with essential system requirements that enhance user experience and system integration. 1 Book Doctor Appointment The process a patient follows to schedule an appointment Role-based Access Details requirements for user access levels 2 Appointment Reminders Notifications for upcoming appointments 3 Integration with Healthcare Systems Holistic view of patient data across systems 4

6. Real-time Example 3: Mobile Banking Application Use Case Transfer Funds - Initiate a fund transfer via the app. 1 2 3 SRS Excerpt Specifies security measures for safe transactions. Key Features Authentication protocols, transaction limits, notification system.

7. Benefits of Using Use Cases Enhanced Communication Use cases facilitate better communication among stakeholders, developers, and project managers by providing a shared understanding of system functionality. Improved Requirement Gathering They help identify missing requirements by clarifying user interactions and highlight system usage, ensuring a comprehensive requirements process. User-Centric Design Use cases promote a user-centric approach in designing systems, improving usability and satisfaction. 1 2 3

8. Benefits of Using SRS Documents 1 Clear Specifications SRS documents provide clear and concise project specifications, reducing the chances of misunderstanding between stakeholders and developers. 2 Scope and Budget Management They help in defining project scope, which in turn aids in accurate budgeting and resource allocation for development. 3 Facilitates Testing A well-developed SRS provides a basis for creating test cases, ensuring that the final product meets specified requirements and functions as intended.

9. Common Challenges Ambiguity in Requirements Use cases and SRS documents can sometimes contain ambiguous descriptions, leading to different interpretations by developers. 1 2 3 Scope Creep Projects may experience scope creep when new features are added outside the initial use cases or SRS, complicating timelines and budgets. Stakeholder Involvement Lack of stakeholder engagement during the creation of use cases and SRS documents can result in missing critical requirements.

10. Best Practices for Creating Use Cases 1 Engage Stakeholders Early Involve stakeholders during the use case development process. 2 Iterate and Revise Regularly review and update use cases throughout the project. 3 Keep it Simple and Clear Use plain language to make use cases easily understandable.

11. Best Practices for Writing SRS Documents Be Specific Clearly define each requirement in measurable terms to avoid ambiguity and enable effective implementation and testing. Prioritize Requirements Rank requirements based on importance and impact on system performance to focus development efforts. Maintain a Version Control System Use version control to track changes in SRS documents, ensuring all stakeholders have access to the latest information.

12. Conclusion on Use Cases and SRS Documents Use cases and SRS documents are essential tools that ensure clear communication, alignment of expectations, and successful project outcomes in software development. Students are encouraged to practice creating use cases and SRS documents for different projects to enhance their understanding and skills in software requirements management. Recap of Importance Use cases and SRS documents ensure clear communication and alignment of expectations. 1 2 Encouragement to Practice Students are encouraged to practice creating use cases and SRS documents for better skills.

13. Multiple Choice Questions(1) 1 What is a primary function of use cases? A) To define software features B) To capture user interactions C) To estimate project costs D) To create marketing strategies 3 What is a key benefit of use cases? 5 Why is an SRS document essential? A) It defines business goals B) It serves as a contract C) It provides marketing strategies D) It reduces project costs 2 What does an SRS document include? A) Only functional requirements B) Technical specifications only C) Both functional and non-functional requirements D) User testimonials 4 Which of the following is a common challenge in creating use cases? A) Too many developers involved B) Lack of feedback from users C) Clarity of user actions D) Specificity of requirements 6 How should use cases be written? A) As technical documentation B) As simple and clear descriptions C) With extensive jargon D) In a formal tone only A) They replace the need for testing B) They improve stakeholder communication C) They limit project scope D) They focus solely on coding

14. Multiple Choice Questions(2) 1 What role do use cases play in user-centric design? A) They avoid user input B) They enhance user experience understanding C) They focus solely on developers D) They replace UI design 3 What practice helps mitigate scope creep? A) Regular updates to use cases B) Limiting stakeholder engagement C) Ignoring new requirements D) Focusing solely on initial planning 2 What is the effect of ambiguity in requirements? A) It leads to clear interpretations B) It ensures everyone is on the same page C) It can cause project misunderstandings D) It simplifies the testing process 4 What document serves as a basis for creating test case? A) Project plan B) Use cases document C) SRS document D) User guide

15. Answers to Multiple Choice Questions(1) Question 1 Answer: b Question 4 Question 2 Answer: b Answer: c Question 5 Answer: b Question 3 Answer: b Question 6 Answer: b

16. Answers to Multiple Choice Questions(2) Question 7 Answer: b Question 9 Answer: a Question 8 Answer: c Question 10 Answer: c

17. THANK YOU