1 / 17

Requirement Discipline

Requirement Discipline. Spring 2006/1385 Semester 1. Outline. Key Concepts Requirements Discipline Requirements Management Requirements Workflow Artifacts. Key concepts. Feature An externally observable service provided by the system which directly fulfills a stakeholder need.

cheche
Download Presentation

Requirement Discipline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirement Discipline Spring 2006/1385 Semester 1

  2. Outline • Key Concepts • Requirements Discipline • Requirements Management • Requirements Workflow • Artifacts Sharif Univ. of Tech.

  3. Key concepts • Feature • An externally observable service provided by the system which directly fulfills a stakeholder need. • Requirement • A requirement describes a condition or capability to which a system must conform. • Software Requirement • Taking a requirement into the software world that would need some new software needs. • Stakeholder • represents an interest group whose needs must be satisfied by the project. • anyone who is materially affected by the outcome of the project. Sharif Univ. of Tech.

  4. Key concepts (Cont.) • Actor: • Informally, any thing have some interactions with the system. • Use Case: • A sequence of actions a system performs that yields an observable result of value to a particular actor. • Use-case model: • Communication medium between customer, user and system developer. • It consists of use-cases, actors and there relations. • Use-case specification shows that how the system interacts with the actor and what the system does. Sharif Univ. of Tech.

  5. Requirements Discipline Sharif Univ. of Tech.

  6. Discipline : • A discipline provides a view into the underlying process elements within RUP from the perspective of a general discipline of skills. • Each discipline describes a set of associated activities and artifacts based around a common skillset. • IntroductionPurpose of the discipline and relationships to other disciplines. • Conceptskey concepts that are important in order to understand the discipline. • WorkflowA typical sequence of events • Activity Overview activities and roles in the discipline. • Artifact Overview artifacts that are produced in this discipline • Guidelines Overview More detailed explanations Sharif Univ. of Tech.

  7. Requirements Discipline • To establish and maintain agreement with the customers and other stakeholders on what the system should do. • To provide system developers with a better understanding of the system requirements. • To define the boundaries of (delimit) the system. • To provide a basis for planning the technical contents of iterations. • To provide a basis for estimating cost and time to develop the system. • To define a user-interface for the system, focusing on the needs and goals of the users. Sharif Univ. of Tech.

  8. Requirement • Requirement: a condition or capability to which the system must conform. • Types of Requirements (FURPS+): • Functionality • Usability • Reliability • Performance • Supportability • design constraints, implementation requirements, interface requirements, physical requirements. Sharif Univ. of Tech.

  9. Requirements Management • A systematic approach to finding, eliciting, documenting, organizing and tracking the changing requirements of a system. • Collecting requirements difficulties: • Requirements are not always obvious, and can come from many sources. • Requirements are not always easy to express clearly in words. • There are many different types of requirements at different levels of detail. • The number of requirements can become unmanageable if not controlled. • Requirements have unique properties or property values. For example, they are neither equally important nor equally easy to meet. • Requirements change. Sharif Univ. of Tech.

  10. Requirements Workflow Sharif Univ. of Tech.

  11. Workflow Details  • Analyze the Problem • Gain agreement on the problem being solved, • Identify stakeholders, • Define the system boundaries, and • Identify constraints imposed on the system. • Understand Stakeholder Needs • collect and elicit information from the stakeholders of the project in order to understand their needs. • defining the high-level features Sharif Univ. of Tech.

  12. Workflow Details (cont.) • Define the System • high-level analysis on the results of collecting stakeholder requests. • Refine the Vision to include the features • Refine the use-case model, to include outlined use cases. • Manage the Scope of the System • Prioritize features and requirements. • Define the set of use cases that represent some significant, central functionality. Sharif Univ. of Tech.

  13. Workflow Details (cont.) • Refine the System Definition • Describe the use case's flow of events in detail. • Detail Supplementary Specifications. • Develop a Software Requirements Specification, if more detail is needed, and • Model and prototype the user interface. • Manage Changing Requirements • Restructure the use-case model. • Redefine requirements attributes. • Evaluate change requests and determine their impact on the existing requirement set. Sharif Univ. of Tech.

  14. Understand Stakeholder Needs Techniques • Interviews • Requirement workshop • Brain-storming and idea reduction • Use-case workshop • Storyboarding • Role playing • Review of existing requirements Sharif Univ. of Tech.

  15. Artifacts • Glossary. • Vision. • Requirements Management Plan. • Supplementary Specifications. • Requirements Attributes. • Software Requirements Specification. Sharif Univ. of Tech.

  16. Homework • مفهوم traceability را توضيح دهيد. (اين تمرين بايد بطور دستی نوشته شده باشد و پرينت قابل قبول نمی‌باشد.) Sharif Univ. of Tech.

  17. Thanks Please take a look at Rational Unified Process documents

More Related