SRE Presentation

SOFTWARE REQUIREMENTS
ENGINEERING
感谢您下载包图网平台上提供的 PPT 作品，为了您和包图网以及原创作者的利益，请勿复制、传播、销售，否则将承担法律责任！包图网将对作品进行维权，按照传播下载次数进行十倍的索取赔偿！
ibaotu.com
By
Muhammad Aamir
WAQAR AHMAD
 Requirement Evolution
• Requirement evolution refers to the changes that occur in software

requirements throughout the software development lifecycle.
• It is crucial to understand and manage requirement evolution to ensure the

ibaotu.com
success of a software project.
• Factors influencing Requirement Evolution:

• Changing business needs
• Stakeholder feedback
• Technological advancements
• Legal or regulatory changes
Process of Requirement Evolution
• Elicitation: Gathering initial requirements from stakeholders.
• Analysis: Understanding and refining requirements to ensure clarity and

feasibility. 感谢您下载包图网平台上提供的 PPT 作品，为了您和包图网以及原创作者的利益，请勿复制、传播、销售，否则将承担法律责任！包图网将对作品进行维权，按照传播下载次数进行十倍的索取赔偿！
ibaotu.com
• Documentation: Documenting requirements in a clear and concise manner.
• Validation: Validating requirements with stakeholders to ensure they meet their

needs.
• Evolution: Continuously reviewing and updating requirements throughout the

development process.
Challenges for Managing Requirement Evolution
• Scope Creep: Risk of continuous expansion of project scope with evolving
requirements.
• Communication Issues: Ensuring clear communication between stakeholders and

team members.
ibaotu.com
• Managing Stakeholder Expectations: Balancing conflicting needs and priorities of

different stakeholders.
• Maintaining Traceability: Difficulty in tracking changes and their implications across

project artifacts.
• Risk Management: Identifying and mitigating risks associated with evolving

requirements.
Strategies for Managing Requirement Evolution
• Continuous Stakeholder Engagement: Regularly involve stakeholders to
understand evolving needs.
• Prioritization Techniques: Focus on delivering high-priority features first while

allowing less critical requirements to evolve.
ibaotu.com
• Prototyping and Rapid Iteration: Use prototypes and MVPs to gather feedback and
validate requirements early.
• Change Management Processes: Establish clear processes for evaluating and

implementing requirement changes.
• Risk Management: Anticipate and mitigate risks associated with requirement

changes.
 Requirement Traceability
• Requirement traceability is the ability to track and manage the life of a

requirement from its inception to its fulfillment.
• It ensures that each requirement is linked to its origin and can be traced
ibaotu.com
throughout the software development lifecycle.
• It is a documented thread that provides forward and backward visibility into

all activity surrounding each requirement (including design, development,
testing, and support).
Importance of Requirement Traceability
• Enhances communication and understanding among stakeholders.
• Helps in managing changes effectively by understanding the impact on related

requirements.
ibaotu.com
• Improves overall software quality and reduces risks associated with incomplete or
misunderstood requirements.
Components of Requirement Traceability
• Forward Traceability: Tracing requirements from their origin to

implementation.
• Backward Traceability: Tracing implementation back to the original

ibaotu.com
requirements.
• Bi-directional Traceability: Ensuring consistency between forward and

backward traceability.
Methods for Requirement Traceability
• Manual Methods: Using spreadsheets, documents, or matrices to manually

track requirements and their relationships.
ibaotu.com
• Automated Tools: Utilizing specialized software tools to automatically manage

and trace requirements throughout the development process.
Challenges and Best Practices
• Challenges: Keeping traceability up-to-date, managing changes, ensuring

completeness and accuracy.
ibaotu.com
• Best Practices: Establishing clear and consistent requirements, maintaining

documentation, utilizing automated tools, involving stakeholders throughout the
process.
 Requirement Management
• Requirement Management is the process of documenting, analyzing,

prioritizing, and tracking requirements throughout the software development
lifecycle.
ibaotu.com
• It ensures that all stakeholders are on the same page regarding what
needs to be developed and guides the development team in building the
right software.
• Effective requirement management is crucial for project success as it helps

in delivering a product that meets customer expectations, within budget and
on time.
Key Aspects of Requirement Management
• Requirements Elicitation: Gathering and understanding the needs and expectations
of stakeholders.
• Requirements Analysis: Examining and refining gathered requirements for clarity,

completeness, and consistency.
ibaotu.com
• Requirements Prioritization: Determining the importance and urgency of each

requirement to guide development efforts.
• Requirements Traceability: Establishing and maintaining links between

requirements and related artifacts to ensure alignment throughout the project.
• Requirements Validation: Ensuring that the developed software meets the specified
requirements and fulfills the needs of stakeholders.
Importance of Requirement Management
• Customer Satisfaction: Meeting customer needs leads to satisfaction and

loyalty.
• Cost and Risk Reduction: Clear requirements minimize rework and project
ibaotu.com
delays, reducing costs and risks.
• Stakeholder Communication: Well-managed requirements facilitate

collaboration and alignment among stakeholders.
Best Practices in Requirement Management
• Early Stakeholder Engagement: Involve stakeholders throughout the

process for comprehensive understanding.
• Clear Communication: Use straightforward

ibaotu.com
language to minimize
misunderstandings.
• Prioritization: Rank requirements to focus efforts on crucial features.
• Traceability: Establish links between requirements and related artifacts for

better management.
• Regular Validation: Periodically review requirements with stakeholders to

ensure relevance and accuracy.
 Requirement Prioritization
• Requirement prioritization is the process of arranging software

requirements in order of importance for implementation.
ibaotu.com
• It helps in allocating resources effectively and ensuring that the most

crucial features are developed first.
• Prioritization ensures that the limited time and resources available are
utilized efficiently to meet the project goals.
Methods of Requirement Prioritization
• MoSCoW Method:
• Must Have: Critical requirements necessary for basic functionality.
• Should Have: Important but not critical requirements.
• Could Have: Desirable features but not essential.
• Won't Have (this time): Requirements deferred to future releases.
ibaotu.com
• Value-Based Prioritization:
• Evaluates requirements based on their value to stakeholders.
• Involves analyzing benefits, costs, risks, and dependencies associated with each
requirement.
• Pairwise Comparison:
• Involves comparing each requirement against every other requirement to determine
relative priorities.
Challenges of Requirement Prioritization
• Ambiguity:
• Lack of clarity in requirements can lead to difficulty in prioritization.
• Requirements might overlap or contradict each other.
ibaotu.com
• Stakeholder Alignment:
• Different stakeholders may have conflicting priorities.
• Balancing diverse viewpoints and interests can be challenging.
Best Practices for Requirement Prioritization
• Involving Stakeholders:
• Engage stakeholders early and continuously throughout the process.
• Gather input from various perspectives to ensure alignment.
ibaotu.com
• Regular Review:
• Revisit prioritization regularly to accommodate changes in project goals and priorities.
• Prioritize based on current business needs and market trends.
• Documentation:
• Document the rationale behind prioritization decisions.
• Maintain transparency and ensure alignment with project objectives.
 Trade-off Analysis
• Trade-off analysis is like comparing different choices to see what you gain
and lose with each.
ibaotu.com
• It helps you make smart decisions by understanding the trade-offs between

different options.
• For example, in software development, it might mean choosing between

adding more cool features to an app or keeping costs low.
Process of Trade-off Analysis
• Identify Requirements: Gather all the requirements for the software project from stakeholders.
• Analyze Requirements: Evaluate each requirement to understand its significance and potential impact
on the project.
• Identify Trade-offs: Determine the relationships between different requirements and potential trade-offs
ibaotu.com
that may arise.
• Assess Options: Explore various options to address conflicting requirements and consider their
implications.
• Make Decisions: Based on the trade-off analysis, make informed decisions to select the most suitable
solution.
• Communicate Findings: Clearly communicate the trade-offs and decisions to stakeholders to ensure
alignment and understanding.
Example
• Scenario: Developing a mobile app for a retail store.
• Trade-off: Trade-off between adding more features for enhanced user experience and
keeping development costs within budget.
ibaotu.com
• Analysis: Adding more features may increase user satisfaction but could also lead to
higher development costs and longer time to market.
• Decision: Prioritize features that provide the most value to users while staying within
budget constraints.
 Risk Analysis
• Risk analysis is the process of identifying, assessing, and prioritizing

potential risks that may occur during the software development process.
ibaotu.com
Common Risks in Software Requirements Engineering:
• Unclear or changing requirements.

• Inadequate stakeholder involvement.
• Miscommunication among team members.
• Technology limitations or dependencies.
• Unrealistic project timelines or budgets.
How to Perform Risk Analysis
• Identify Risks: Brainstorm potential risks that may arise.
• Assess Risks: Evaluate the likelihood and impact of each identified risk.
ibaotu.com
• Prioritize Risks: Rank risks based on their severity and potential impact on the
project.
• Develop Mitigation Strategies: Develop strategies to mitigate or minimize

the impact of identified risks.
 Impact Analysis
• Impact analysis is the process of evaluating the effects of a proposed
change or addition to software requirements.
• It helps in understanding how a change in one requirement may affect

other requirements, modules, or components of the software.
ibaotu.com
Why is Impact Analysis Important?
• Helps in managing changes effectively by identifying potential risks and conflicts early in the
development process.
• Facilitates better decision-making by providing insights into the costs, resources, and time required
for implementing changes.
• Minimizes the likelihood of introducing errors or defects into the software during the development
cycle.
How is Impact Analysis Conducted?
• Analyzing dependencies: Identify relationships between different

requirements, modules, and components.
ibaotu.com
• Assessing risks: Evaluate the potential impact of changes on functionality,

performance, and other quality attributes.
• Prioritizing changes: Determine the order in which changes should be

implemented based on their importance and impact.
 Interaction b/w Requirement & Architecture
• Requirements: These are the needs and expectations from the software
system, stated by stakeholders. They define what the software should do and how it
should behave.
• Architecture: This is the blueprint or structure of the software system. It outlines

how different components of the system will work together to fulfill the
ibaotu.com
requirements.
• Interaction: Requirements drive architecture. They influence the decisions made

during the design of the system's architecture.
• Understanding Needs: Architecture must reflect the requirements accurately to

ensure that the final product meets stakeholders' needs.
• Feedback Loop: There's a continuous interaction between requirements and

architecture. As requirements evolve, the architecture must adapt, and vice versa.
Importance of Interaction
• Alignment: Ensures the software architecture aligns with requirements.
• Validation: Helps in validating requirements and system design.
• Risk Reduction: Identifies and mitigates potential risks early on.

ibaotu.com
• Traceability: Establishes clear traceability between requirements and architecture.
• Enhanced Communication: Facilitates better communication among stakeholders.
• Overall Success: Leads to successful delivery of a system meeting stakeholder

needs.
Hasta la Vista
ibaotu.com
Grazie

SRE Presentation

Uploaded by

Copyright:

Available Formats

SRE Presentation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRE Presentation

Uploaded by

Copyright:

Available Formats

SOFTWARE REQUIREMENTS

• Requirement evolution refers to the changes that occur in software

• It is crucial to understand and manage requirement evolution to ensure the

success of a software project.

• Factors influencing Requirement Evolution:

• Analysis: Understanding and refining requirements to ensure clarity and

• Documentation: Documenting requirements in a clear and concise manner.

• Validation: Validating requirements with stakeholders to ensure they meet their

• Evolution: Continuously reviewing and updating requirements throughout the

• Communication Issues: Ensuring clear communication between stakeholders and

• Managing Stakeholder Expectations: Balancing conflicting needs and priorities of

• Maintaining Traceability: Difficulty in tracking changes and their implications across

• Risk Management: Identifying and mitigating risks associated with evolving

• Prioritization Techniques: Focus on delivering high-priority features first while

• Change Management Processes: Establish clear processes for evaluating and

• Risk Management: Anticipate and mitigate risks associated with requirement

• Requirement traceability is the ability to track and manage the life of a

throughout the software development lifecycle.

• It is a documented thread that provides forward and backward visibility into

• Enhances communication and understanding among stakeholders.

• Helps in managing changes effectively by understanding the impact on related

• Forward Traceability: Tracing requirements from their origin to

• Backward Traceability: Tracing implementation back to the original

• Bi-directional Traceability: Ensuring consistency between forward and

• Manual Methods: Using spreadsheets, documents, or matrices to manually

• Automated Tools: Utilizing specialized software tools to automatically manage

• Challenges: Keeping traceability up-to-date, managing changes, ensuring

• Best Practices: Establishing clear and consistent requirements, maintaining

• Requirement Management is the process of documenting, analyzing,

• Effective requirement management is crucial for project success as it helps

• Requirements Analysis: Examining and refining gathered requirements for clarity,

• Requirements Prioritization: Determining the importance and urgency of each

• Requirements Traceability: Establishing and maintaining links between

• Customer Satisfaction: Meeting customer needs leads to satisfaction and

delays, reducing costs and risks.

• Stakeholder Communication: Well-managed requirements facilitate

• Early Stakeholder Engagement: Involve stakeholders throughout the

• Clear Communication: Use straightforward

• Prioritization: Rank requirements to focus efforts on crucial features.

• Traceability: Establish links between requirements and related artifacts for

• Regular Validation: Periodically review requirements with stakeholders to

• Requirement prioritization is the process of arranging software

• It helps in allocating resources effectively and ensuring that the most

• It helps you make smart decisions by understanding the trade-offs between

• For example, in software development, it might mean choosing between

that may arise.

• Scenario: Developing a mobile app for a retail store.

• Risk analysis is the process of identifying, assessing, and prioritizing

Common Risks in Software Requirements Engineering:

• Unclear or changing requirements.

• Identify Risks: Brainstorm potential risks that may arise.

• Develop Mitigation Strategies: Develop strategies to mitigate or minimize

• It helps in understanding how a change in one requirement may affect

Why is Impact Analysis Important?

• Analyzing dependencies: Identify relationships between different

• Assessing risks: Evaluate the potential impact of changes on functionality,

• Prioritizing changes: Determine the order in which changes should be

• Architecture: This is the blueprint or structure of the software system. It outlines

• Interaction: Requirements drive architecture. They influence the decisions made