Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | requirements:requirements [2023/05/01 18:13] (current) – [Links] Henrik Yllemo | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~NOCACHE~~ | ||
+ | ====== Requirements management ====== | ||
+ | |||
+ | Requirements management is the process of documenting, | ||
+ | |||
+ | |||
+ | Requirements management is an essential component of the Application Lifecycle Management (ALM) process. It involves gathering requirements from stakeholders, | ||
+ | |||
+ | * documenting | ||
+ | * analyzing | ||
+ | * tracing | ||
+ | * prioritizing | ||
+ | * agreeing | ||
+ | |||
+ | Examples of requirements management: | ||
+ | * Collecting and documenting software requirements from stakeholders, | ||
+ | * Analyzing and prioritizing requirements based on their importance, feasibility, | ||
+ | * Tracing requirements to ensure that they are implemented correctly and meet the project goals. | ||
+ | * Managing changes to requirements throughout the development process, including adding new requirements, | ||
+ | * Defining test cases and scenarios based on the requirements to ensure that the system meets the expected behavior. | ||
+ | * Creating and maintaining a requirements management plan that outlines the process, tools, and responsibilities for managing requirements. | ||
+ | * Tracking requirements using a dedicated requirements management tool, such as JIRA, Trello, or ReqView, to ensure that they are completed on time and within budget. | ||
+ | * Conducting regular reviews and evaluations of the requirements management process to identify areas for improvement. | ||
+ | * Communicating requirements and changes to all stakeholders, | ||
+ | * Ensuring that the requirements are well-defined, | ||
+ | |||
+ | * Non-functional requirement (NFR) | ||
+ | * Epic - feature - story - task | ||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | * TOGAF ADM Architecture Requirements Management | ||
+ | * https:// | ||
+ | * | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | <panel type='' | ||
+ | Requirements management is the process of defining, documenting, | ||
+ | </ | ||
+ | Requirements management is important because it helps to ensure that software projects are delivered on time, within budget, and with the desired quality. It also helps to reduce rework, improve collaboration between stakeholders, | ||
+ | </ | ||
+ | Common techniques used in requirements management include stakeholder interviews, surveys, use cases, user stories, prototyping, | ||
+ | </ | ||
+ | Some common challenges associated with requirements management include changing requirements, | ||
+ | </ | ||
+ | Organizations can improve their requirements management process by establishing clear roles and responsibilities for stakeholders, | ||
+ | </ | ||
+ | Project managers play a critical role in requirements management by ensuring that requirements are clearly defined, prioritized, | ||
+ | </ | ||
+ | Agile methodologies can impact requirements management by emphasizing continuous delivery, frequent feedback, and collaboration between stakeholders. This can lead to more iterative and flexible requirements management processes that allow for more rapid changes and adjustments. | ||
+ | </ | ||
+ | Traceability is important in requirements management because it allows for the tracking of requirements from their origin through to their implementation and testing. This helps to ensure that requirements are properly prioritized and addressed throughout the project lifecycle. | ||
+ | </ | ||
+ | Requirements management can impact the overall success of a software project by ensuring that the project meets the needs and expectations of stakeholders, | ||
+ | </ | ||
+ | Tools and techniques used in requirements management include requirement management software, use cases, user stories, personas, flowcharts, traceability matrices, and prioritization matrices. | ||
+ | </ | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {{wp> | ||
+ | |||
+ | * [[kb: | ||
+ | |||
+ | |||
+ | ===== Agile Requirements | ||
+ | * [[SAFe Requirements Model]] | ||
+ | * [[Agile Requirements Modeling]] | ||
+ | |||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Cone of Uncertainty | ||
+ | * [[kb: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * http:// | ||
+ | * [[kb: | ||
+ | ===== Requirements analysis ===== | ||
+ | {{wp> | ||
+ | |||
+ | ===== Taxonomy of Requirements | ||
+ | * [[taxonomy: | ||
+ | |||
+ | Functional vs non-functional requirments | ||
+ | * https:// | ||
+ | * | ||
+ | |||
+ | |||
+ | <callout type=" | ||
+ | |||
+ | [[https:// | ||
+ | \\ | ||
+ | The IMBOK process areas are: | ||
+ | * **Projects: | ||
+ | * **Business Change:** Evaluating information to drive improvements in processes | ||
+ | * **Business Operations: | ||
+ | * **Performance Management: | ||
+ | \\ | ||
+ | < | ||
+ | |||
+ | </ | ||
+ | ===== Requirements traceability ===== | ||
+ | {{wp> | ||
+ | ==== Disciplines & Methodologies ==== | ||
+ | {{topic> | ||
+ | ==== Tools & Technologies ==== | ||
+ | {{topic> | ||
+ | ==== Links ==== | ||
+ | {{topic> | ||
+ | |||
+ | {{topic> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <callout title=" | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * | ||
+ | </ | ||
+ | |||
+ | |||
+ | {{tag> | ||
+ | |||
+ | |||
+ | === ## ToDo ## === | ||
+ | * FIXME - [[: | ||
+ | |||
+ | * Requirements Elicitation | ||
+ | * Requirements Analysis | ||
+ | * Requirements Specification | ||
+ | * Requirements Verification and Validation | ||
+ | * Requirements Traceability | ||
+ | * Requirements Prioritization | ||
+ | * Requirements Change Management | ||
+ | * Requirements Documentation | ||
+ | * Requirements Repository | ||
+ | * Requirements Metrics and Reporting | ||
+ | * Requirements Engineering | ||
+ | * Requirements Management Tools | ||
+ | * Requirements Collaboration | ||
+ | * User Stories | ||
+ | * Use Cases | ||
+ | * Business Process Modeling | ||
+ | * Stakeholder Management | ||
+ | * Requirements Negotiation | ||
+ | * Agile Requirements Management | ||
+ | * Requirements Management Process | ||
+ | * Requirements Management Plan | ||
+ | * Requirements Management Best Practices |