requirements:requirements

no way to compare when less than two revisions

Differences

This shows you the differences between two versions of the page.


Previous revision
Next revision
—requirements:requirements [2023/03/25 09:18] – Henrik Yllemo
Line 1: Line 1:
 +~~NOCACHE~~
  
 +====== Requirements management ======
 +
 +Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome (product or service) should conform.
 +
 +
 +Requirements management is an essential component of the Application Lifecycle Management (ALM) process. It involves gathering requirements from stakeholders, documenting the requirements, tracking changes to the requirements, and ensuring that the requirements are met during software development and testing. The benefits of requirements management in ALM include ensuring that the software application is aligned with the business needs, reducing the risk of errors and delays, improving collaboration and communication among stakeholders, and improving the overall quality of the software application. 
 +
 +  * documenting
 +  * analyzing
 +  * tracing
 +  * prioritizing
 +  * agreeing
 +
 +Examples of requirements management:
 +  * Collecting and documenting software requirements from stakeholders, such as users, customers, and subject matter experts.
 +  * Analyzing and prioritizing requirements based on their importance, feasibility, and impact on the system.
 +  * 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, modifying existing ones, and removing unnecessary ones.
 +  * 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, including developers, testers, project managers, and customers, to ensure that everyone is aligned with the project goals.
 +  * Ensuring that the requirements are well-defined, clear, and testable, and that they meet regulatory and compliance standards.
 +
 +  * Non-functional requirement (NFR)
 +  * Epic - feature - story - task
 +
 +----
 +
 +
 +  * TOGAF ADM Architecture Requirements Management
 +  * https://www.pmi.org/learning/library/effective-requirements-management-project-success-8181
 +  * 
 +
 +
 +
 +
 +
 +
 +
 +{{wp>Requirements_management}}
 +
 +  * [[kb:dikw_pyramid]]
 +
 +
 +===== Agile Requirements  =====
 +  * [[SAFe Requirements Model]]
 +  * [[Agile Requirements Modeling]]
 +
 +
 +{{:requirements:agile_requirements_almbok.com.png?400|}} {{:requirements:agile_requirements_value_stream_almbok.com.png?400|}}
 +
 +===== Cone of Uncertainty  =====
 +  * [[kb:cone_of_uncertainty|Cone of Uncertainty]]
 +
 +{{ :requirements:cone_of_uncertainty_almbok.com.png?|}}
 +
 +  * http://www.agilenutshell.com/cone_of_uncertainty
 +  * [[kb:dunning-kruger_effect]]
 +===== Requirements analysis =====
 +{{wp>Requirements_analysis}}
 +
 +===== Taxonomy of Requirements  =====
 +  * [[taxonomy:taxonomy_of_requirements|Taxonomy of Requirements]]
 +
 +Functional vs non-functional requirments
 +  * https://www.altexsoft.com/blog/business/functional-and-non-functional-requirements-specification-and-types
 +  * 
 +
 +
 +<callout type="primary" title="Information Management Body of Knowledge (IMBOK) " >
 +
 +[[https://www.imbok.info/|{{:method:pasted:20200907-132211.png}}]]
 +\\
 +The IMBOK process areas are:
 +  * **Projects:** Adding new capacity, software, and hardware to information systems
 +  * **Business Change:** Evaluating information to drive improvements in processes 
 +  * **Business Operations:** The day-to-day of a business. These will guide improvements based on updates to processes, and will hopefully increase benefits.
 +  * **Performance Management:** Trying to ensure operations are running at peak capacit
 +\\
 + <btn icon="fa fa-book">[[https://www.imbok.org/|IMBOK.org]]</btn>
 +
 +</callout>
 +===== Requirements traceability =====
 +{{wp>Requirements traceability}}
 +==== Disciplines & Methodologies ====
 +{{topic>method?requirements&simplelist&nodate&nodesc&nouser&sort}} 
 +==== Tools & Technologies ====
 +{{topic>tools?requirements&simplelist&nodate&nodesc&nouser&sort}} 
 +==== Links ====
 +{{topic>links?requirements&simplelist&nodate&nodesc&nouser&sort}} 
 +
 +{{topic>kb?requirements&simplelist&nodate&nodesc&nouser&sort}} 
 +
 +
 +
 + 
 +<callout title="External links:">
 +  * https://www.pmi.org/learning/library/effective-requirements-management-project-success-8181
 +  * https://www.projectmanagement.com/blogs/285716/Requirements
 +  * https://www.pmi.org/pmbok-guide-standards/practice-guides/requirements-management
 +  * https://www.requirementsmanagementtools.com/
 +  * 
 +</callout>
 +
 +
 +{{tag>governance skill dx devx}}
  • requirements/requirements.txt
  • Last modified: 2023/05/01 18:13
  • by Henrik Yllemo