Requirements Engineering Overview
143 Questions
0 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the primary goal of requirements engineering?

  • To train stakeholders on system functionality
  • To create a marketing strategy for the product
  • To ensure the system meets the needs of its intended users (correct)
  • To minimize the costs associated with product development

    • Which of the following is NOT a reason why getting good requirements is difficult?

  • Requirements may change during the RE process
  • Stakeholders clearly articulate their needs (correct)
  • Organizational politics can influence requirements
  • Conflicting requirements may arise from different stakeholders

    • Who can be considered an internal stakeholder during the requirements engineering process?

  • Suppliers
  • Government officials
  • External customers
  • Project team members (correct)

    • What must be recognized to manage the different views of stakeholders effectively?

    <p>Multiple points of view</p> Signup and view all the answers

    What is the purpose of a Software Requirement Specification (SRS)?

    <p>To document customer requirements in technical language</p> Signup and view all the answers

    What is a significant responsibility of requirements engineering?

    <p>Categorizing stakeholder information to avoid conflicts</p> Signup and view all the answers

    Which stakeholder is primarily concerned with the system's maintainability?

    <p>Support engineer</p> Signup and view all the answers

    Which of the following is NOT a model used during the SRS stage?

    <p>Prototyping</p> Signup and view all the answers

    What validation technique involves systematic manual analysis of requirements?

    <p>Requirements reviews/inspections</p> Signup and view all the answers

    Which question is essential for clarifying the motivation behind a request in the requirements engineering process?

    <p>Who is behind the request for this work?</p> Signup and view all the answers

    How can requirements engineering help resolve conflict between stakeholders?

    <p>By identifying areas of commonality and conflict</p> Signup and view all the answers

    Which statement best describes functional requirements?

    <p>They define a function that a system must perform.</p> Signup and view all the answers

    Which of the following is a key aspect to validate in software requirements?

    <p>Testability of the requirements</p> Signup and view all the answers

    What type of requirements includes high-level statements of goals and objectives?

    <p>Business requirements</p> Signup and view all the answers

    What can result from poor requirement validation?

    <p>Illegal or impossible software solutions</p> Signup and view all the answers

    What does automated consistency analysis check for?

    <p>Consistency of structured requirements descriptions</p> Signup and view all the answers

    What do functional requirements describe?

    <p>They define the behavior of the system related to its functionality.</p> Signup and view all the answers

    Which of the following is NOT a category of non-functional requirements?

    <p>Performance qualities</p> Signup and view all the answers

    What is an example of an execution quality in non-functional requirements?

    <p>Security</p> Signup and view all the answers

    Which of these is a suggested source for requirements gathering?

    <p>Knowledge transfer from colleagues</p> Signup and view all the answers

    What does requirement management primarily address?

    <p>Managing changing requirements during system development</p> Signup and view all the answers

    Which of the following is identified as an evolution quality?

    <p>Maintainability</p> Signup and view all the answers

    How can previous bug reports contribute to current requirements?

    <p>They can transform into enhancement requests.</p> Signup and view all the answers

    Why is it important to document requirements?

    <p>To ensure clarity and facilitate review by knowledgeable team members.</p> Signup and view all the answers

    What does it mean for a requirement to be atomic?

    <p>It should be at a very low level of detail.</p> Signup and view all the answers

    What is a characteristic of a uniquely identified requirement?

    <p>It has a distinct identifier for clarity.</p> Signup and view all the answers

    Why is the requirement 'Students will be able to enroll to undergraduate and post-graduate courses' considered bad?

    <p>It is not atomic.</p> Signup and view all the answers

    Which of the following best describes a complete requirement?

    <p>It must include all relevant information.</p> Signup and view all the answers

    What is the implication of a requirement being consistent and unambiguous?

    <p>It should have a clear and singular meaning.</p> Signup and view all the answers

    What does it mean for a requirement to be traceable?

    <p>It has the ability to relate back to its origin.</p> Signup and view all the answers

    What does prioritization of requirements involve?

    <p>Determining the sequence of implementation based on significance.</p> Signup and view all the answers

    Which of the following is NOT a quality of good requirements?

    <p>Ambiguous</p> Signup and view all the answers

    What is the importance of prioritizing requirements in a project?

    <p>It provides a guideline for implementing the most critical requirements first.</p> Signup and view all the answers

    Why is it essential for requirements to be testable?

    <p>To quantify expectations and facilitate measurement of success.</p> Signup and view all the answers

    What is an example of a bad requirement based on testability?

    <p>Each page of the system will load in an acceptable time frame.</p> Signup and view all the answers

    How are requirements traceability and testing related?

    <p>Traceability ensures that all mappings of requirements to test cases are documented.</p> Signup and view all the answers

    Which priority level should the requirement 'register student' ideally have?

    <p>Priority 1</p> Signup and view all the answers

    What issue arises when a requirement states 'each page of the system will load in an acceptable time frame'?

    <p>It introduces ambiguity and increases testing efforts.</p> Signup and view all the answers

    What does good requirement prioritization involve?

    <p>Identifying critical tasks to ensure efficient project progression.</p> Signup and view all the answers

    What is a characteristic of a well-defined requirement?

    <p>It can be measured and verified.</p> Signup and view all the answers

    What is a key characteristic that each requirement should have?

    <p>Consistency and unambiguity</p> Signup and view all the answers

    Which statement best describes a conflict in requirements?

    <p>Some courses cater to both student types.</p> Signup and view all the answers

    What should be included in a well-defined requirement for traceability?

    <p>A mapping to a specific requirement ID</p> Signup and view all the answers

    What is a bad requirement example listed?

    <p>Maintain student information – mapped to BRD req ID?</p> Signup and view all the answers

    How can ambiguous requirements impact a project?

    <p>They can lead to inconsistent interpretations.</p> Signup and view all the answers

    What outcome is desired from converting bad requirements into good ones?

    <p>Clarity in course categorization.</p> Signup and view all the answers

    What is an essential quality of a requirement regarding its format?

    <p>It should be specific and easily understandable.</p> Signup and view all the answers

    A Software Requirement Specification (SRS) is created before collecting requirements from customers.

    <p>False</p> Signup and view all the answers

    Requirements validation ensures that all user demands will be feasible and legally acceptable.

    <p>False</p> Signup and view all the answers

    Functional requirements specify the functions that a system or system element must perform.

    <p>True</p> Signup and view all the answers

    Prototyping is a technique used for analyzing requirements by creating an executable model of the system.

    <p>True</p> Signup and view all the answers

    Nonfunctional requirements describe the characteristics that will meet the user's expectations.

    <p>True</p> Signup and view all the answers

    Automated consistency analysis checks for the correctness of unstructured requirements descriptions.

    <p>False</p> Signup and view all the answers

    Economic feasibility determines if a software can generate financial profits for an organization.

    <p>True</p> Signup and view all the answers

    Business requirements include detailed specifications for software implementations.

    <p>False</p> Signup and view all the answers

    The requirement elicitation and analysis phase involves gathering requirements only from existing systems.

    <p>False</p> Signup and view all the answers

    System requirements encompass both functional and nonfunctional requirements.

    <p>True</p> Signup and view all the answers

    Operational feasibility assesses how well the required software addresses business problems.

    <p>True</p> Signup and view all the answers

    The requirement management process occurs before the feasibility study.

    <p>False</p> Signup and view all the answers

    Technical feasibility evaluates current technologies to meet customer requirements.

    <p>True</p> Signup and view all the answers

    Requirement validation ensures that the gathered requirements are irrelevant to the problem.

    <p>False</p> Signup and view all the answers

    A successful solution has no measurable benefit to stakeholders.

    <p>False</p> Signup and view all the answers

    A feasibility study is designed to confirm reasons for developing software that are acceptable to users.

    <p>True</p> Signup and view all the answers

    A requirement must be uniquely identified to ensure clarity in references.

    <p>True</p> Signup and view all the answers

    Atomic requirements should combine multiple entities into a single statement.

    <p>False</p> Signup and view all the answers

    A requirement is complete if it includes all necessary details and information.

    <p>True</p> Signup and view all the answers

    The requirement 'Students will be able to enroll in undergraduate and post-graduate courses' is a good example of an atomic requirement.

    <p>False</p> Signup and view all the answers

    Each requirement should be testable to verify if it meets its intended purpose.

    <p>True</p> Signup and view all the answers

    A good requirement should be consistent and ambiguous.

    <p>False</p> Signup and view all the answers

    Prioritization of requirements involves ranking them based on their importance and urgency.

    <p>True</p> Signup and view all the answers

    All requirements should have the same ID to ensure easy tracking across different documents.

    <p>False</p> Signup and view all the answers

    A student can simultaneously enroll in both undergraduate and post-graduate courses.

    <p>False</p> Signup and view all the answers

    Every requirement should be consistent and unambiguous.

    <p>True</p> Signup and view all the answers

    Traceability in requirements means mapping each business requirement to its corresponding design requirement.

    <p>True</p> Signup and view all the answers

    A bad requirement may lack an associated requirement ID for traceability.

    <p>True</p> Signup and view all the answers

    The statement 'Some courses will be open to both under-graduate and post-graduate students' is a good requirement.

    <p>False</p> Signup and view all the answers

    Good requirements should not have any ambiguity.

    <p>True</p> Signup and view all the answers

    Each course must be categorized as either an undergraduate course or a postgraduate course.

    <p>True</p> Signup and view all the answers

    Maintaining student information without a requirement ID is a good practice.

    <p>False</p> Signup and view all the answers

    Functional requirements describe the behavior of the system as it relates to its functionality.

    <p>True</p> Signup and view all the answers

    Non-functional requirements are primarily concerned with specific behaviors of the system.

    <p>False</p> Signup and view all the answers

    Execution qualities in non-functional requirements can be observed at run time.

    <p>True</p> Signup and view all the answers

    Evolution qualities include observable metrics like security and usability.

    <p>False</p> Signup and view all the answers

    Requirements management is necessary due to the changing nature of business needs during development.

    <p>True</p> Signup and view all the answers

    Previous bug reports can provide valuable insights for current requirement gathering.

    <p>True</p> Signup and view all the answers

    It is unimportant to document sources of requirements.

    <p>False</p> Signup and view all the answers

    The priority of requirements remains constant throughout the development process.

    <p>False</p> Signup and view all the answers

    There is a mapping between system requirements and the code that implements those requirements.

    <p>True</p> Signup and view all the answers

    All requirements must have the same priority level during project planning.

    <p>False</p> Signup and view all the answers

    Each requirement should be testable in order to ensure clarity and feasibility.

    <p>True</p> Signup and view all the answers

    A good requirement example is 'each page will load in an acceptable time frame'.

    <p>False</p> Signup and view all the answers

    The requirement 'register student and enroll courses' is given a lower priority than 'maintain user information'.

    <p>False</p> Signup and view all the answers

    A requirement that specifies loading time in seconds is an example of a testable requirement.

    <p>True</p> Signup and view all the answers

    Good requirement prioritization does not impact the implementation process.

    <p>False</p> Signup and view all the answers

    Traceability exists between system requirements, integration requirements, and test cases.

    <p>True</p> Signup and view all the answers

    Functional requirements describe the behavior of the system.

    <p>True</p> Signup and view all the answers

    Non-functional requirements concern specific behaviors of the system.

    <p>False</p> Signup and view all the answers

    Execution qualities like security are observed at runtime.

    <p>True</p> Signup and view all the answers

    Requirement management typically ignores changes that occur during development.

    <p>False</p> Signup and view all the answers

    Documentation of requirements is unnecessary if the development team communicates well.

    <p>False</p> Signup and view all the answers

    Evolution qualities include maintainability and scalability.

    <p>True</p> Signup and view all the answers

    Analyzing previous system versions can provide insights for current requirements.

    <p>True</p> Signup and view all the answers

    Non-functional requirements are irrelevant to system performance.

    <p>False</p> Signup and view all the answers

    A requirement should be atomic, meaning it should be at a very high level of detail.

    <p>False</p> Signup and view all the answers

    Requirements must be uniquely identified to avoid confusion in reference.

    <p>True</p> Signup and view all the answers

    A complete requirement should provide all necessary information for implementation.

    <p>True</p> Signup and view all the answers

    The bad requirement 'Students will be able to enroll to undergraduate and post-graduate courses' is considered good because it addresses two entities simultaneously.

    <p>False</p> Signup and view all the answers

    A requirement can be considered complete if it lacks sufficient detail for implementation.

    <p>False</p> Signup and view all the answers

    Traceable requirements allow for easy identification of their origins and relationships.

    <p>True</p> Signup and view all the answers

    Consistent and unambiguous requirements can lead to different interpretations among stakeholders.

    <p>False</p> Signup and view all the answers

    Prioritized requirements help in managing scope and focus in a project.

    <p>True</p> Signup and view all the answers

    Economic feasibility determines whether software can generate financial profits for an organization.

    <p>True</p> Signup and view all the answers

    Requirement elicitation is the process of analyzing existing systems without engaging customers.

    <p>False</p> Signup and view all the answers

    Technical feasibility evaluates the technologies required to fulfill customer requirements within certain constraints.

    <p>True</p> Signup and view all the answers

    Operational feasibility assesses how well the software performs a single level of operations.

    <p>False</p> Signup and view all the answers

    The requirement management process only focuses on gathering new requirements.

    <p>False</p> Signup and view all the answers

    A complete requirement clearly outlines what is necessary without any ambiguities.

    <p>True</p> Signup and view all the answers

    Measurable benefit refers to the tangible advantages gained from the implementation of a solution.

    <p>True</p> Signup and view all the answers

    Continuous validation of requirements ensures that all user demands will be achievable and compliant.

    <p>False</p> Signup and view all the answers

    Software Requirement Specification (SRS) is created after collecting requirements from various sources.

    <p>True</p> Signup and view all the answers

    Prototyping is a technique used for validating software requirements by creating an executable model of the system.

    <p>True</p> Signup and view all the answers

    Requirements validation techniques only include automated consistency analysis.

    <p>False</p> Signup and view all the answers

    Non-functional requirements describe the system's characteristics that will meet business needs.

    <p>True</p> Signup and view all the answers

    Business requirements are solely focused on the technical aspects of the software project.

    <p>False</p> Signup and view all the answers

    Functional requirements outline the specific functions a system must perform.

    <p>True</p> Signup and view all the answers

    The systematic manual analysis of requirements is known as test-case generation.

    <p>False</p> Signup and view all the answers

    Ambiguities in software requirements can lead to misinterpretations and should be eliminated during validation.

    <p>True</p> Signup and view all the answers

    A good requirement must be consistent and unambiguous.

    <p>True</p> Signup and view all the answers

    Each requirement should be traceable to ensure proper mapping with corresponding requirements.

    <p>True</p> Signup and view all the answers

    A student can enroll in both undergraduate and post-graduate courses according to the requirements.

    <p>False</p> Signup and view all the answers

    The requirement 'Maintain student information – mapped to BRD req ID?' is an example of a good requirement.

    <p>False</p> Signup and view all the answers

    Mapping exists between system and integration requirements to the test cases that validate those requirements.

    <p>True</p> Signup and view all the answers

    The requirement 'maintain user information' is given the highest priority of 1.

    <p>False</p> Signup and view all the answers

    Conflicting requirements can create ambiguity in a project's scope.

    <p>True</p> Signup and view all the answers

    All requirements should be assigned the same priority for equal importance.

    <p>False</p> Signup and view all the answers

    Good requirements should be written in a way that they need no additional information to be understood.

    <p>True</p> Signup and view all the answers

    Every course is allowed to be categorized as both an undergraduate course and a post-graduate course.

    <p>False</p> Signup and view all the answers

    Each and every requirement must be non-testable to avoid complicating testing efforts.

    <p>False</p> Signup and view all the answers

    A requirement stating 'each page of the system will load in an acceptable time frame' is considered testable.

    <p>False</p> Signup and view all the answers

    Requirements should be maintained without concern for their mapping to other requirements.

    <p>False</p> Signup and view all the answers

    The good requirement 'register student and enroll courses pages' specifies a load time of 5 seconds.

    <p>True</p> Signup and view all the answers

    Requirements prioritization helps teams decide which requirements to implement first.

    <p>True</p> Signup and view all the answers

    Traceability within a project does not encompass the relationship between requirements and code.

    <p>False</p> Signup and view all the answers

    Study Notes

    Requirement Engineering

    • Requirement: A function, constraint, or other property that a system must provide to fulfill the needs of its intended user(s).
    • Requirement Engineering: The process of defining, managing, and testing system requirements systematically.

    Why Getting Good Requirements Is Hard

    • Stakeholders may not know exactly what they want.
    • Stakeholders often express requirements in their own terms.
    • Stakeholder groups may have conflicting requirements.
    • Organizational and political factors can influence the requirements.
    • Requirements can change throughout the development process.
    • New stakeholders or business environment shifts can emerge.

    Initiating the Requirements Engineering Process

    • Stakeholders: Anyone directly or indirectly benefiting from the system's development (e.g., top management, project team members, customers, government, contractors).
    • Internal stakeholders: Include company management, project team, managers, colleagues, and internal customers.
    • External stakeholders: Include government, contractors, suppliers, external customers, business managers, consultants, and engineers.

    Initiating Requirements Engineering Process - Multiple Points of View

    • Marketing perspective: Focuses on features and functions to attract potential customers, ensuring easy sales.
    • Business manager perspective: Values features within budget and ready to meet the market.
    • End-user perspective: Emphasizes learning ease and user-friendliness for optimal use.
    • Software engineer perspective: Emphasizes product functioning and infrastructure support.
    • Support engineer perspective: Prioritizes software maintainability.

    Work Toward Collaboration

    • Identify areas of commonality (agreed requirements) and conflict/inconsistency.
    • Business manager or senior technologist makes final decisions.

    Asking the First Questions

    • Who initiated the project request?
    • Who will use the system/solution?
    • What is the financial benefit of the solution?
    • Are there alternative solutions available?

    Asking the Right Questions (Next Set)

    • What business problems will the solution address?
    • What is the business environment where the solution will operate?
    • Does the solution address performance or productivity concerns?

    Asking the Right Questions (Final Set)

    • Are the questions relevant to the problem?
    • Are there too many questions being asked?
    • Can others provide relevant information?
    • Are there additional questions that need to be asked?

    Requirement Engineering Process

    • Feasibility Study: The objective is to justify the development of a software that is acceptable to all users, adaptable to change, and compliant with established standards.

      • Types of Feasibility: Technical (evaluates necessary technologies, time, budget); Operational (covers the software performing tasks at different levels); and Economic (determines whether the software generates financial benefit for the organization.)

    • Requirement Elicitation and Analysis: Gather the system requirements from customers, the users, and existing system processes. Analyze the requirements to identify inconsistencies, defects, omissions, and resolve conflicts.

    • Software Requirement Specification (SRS): The document created by the software analyst after gathering and analyzing requirements from various sources. The requirement must be written in technical language for the development team. Models like ER diagrams, DFDs, and FDDs are used for clarity.

    • Requirement Validation: Verify that the requirements are implementable, accurate, complete, clear and unambiguous.

      • Techniques: Requirements reviews/inspections; Prototyping; Test-case generation and Automated consistency analysis.

    Classification of Requirements

    • Business requirements: High-level statements of project objectives, goals, and needs.
    • User requirements: Specify what users expect from the solution.
    • System requirements: Describe the attributes of the solution (e.g., functional and non-functional requirements).
      • Functional requirements: Describe system functions and behaviors.
      • Non-functional requirements: Include operational aspects like security, performance, and maintainability

    Classification of Requirements (Continued)

    • Software requirements: Categorized into functional (defining the functionality of a system or subsystem) and non-functional (defining qualities or characteristics of the system instead of specific behaviors).
      • Execution qualities: Aspects like usability and security that can be observed during runtime.
      • Evolution qualities: Includes testability, maintainability, scalability, extensibility that are characteristics of the software system design, not directly observable in the executing system

    Functional vs. Non-Functional Requirements

    • Functional requirements: What the system must do, often described in use cases. They're considered mandatory.
    • Non-functional requirements: How the system should perform. They're not directly described in use cases. They're often quality attributes.

    Other Sources of Requirements

    • Knowledge transfer from colleagues/employees.
    • Discussion with business analysts, product managers, and project leads/developers.
    • Existing system/application analysis.
    • Review of past bug reports to identify areas of improvement.
    • Examination of past documentation about enhancements.
    • Analysis of industry knowledge.
    • Document the information gathered, review it, and share it with the team.

    Software Requirements Management

    • Managing changing requirements during development.
    • New requirements arise because of business changes or a better understanding of the system.
    • Priorities may change based on the development process and the business/technical environment.

    How to Analyze Requirements

    • Atomic: Each requirement must be independent—not divisible into smaller components.
    • Uniquely identified: Requirements should have unique identifiers to avoid overlap or confusion.
    • Complete: Detailed and comprehensive information.
    • Consistent and unambiguous: Requirements should be clear and free of conflicting or unclear information.
    • Prioritized: Requirements should have defined order of importance/implementation.
    • Traceable: Clear links between different levels of requirements (e.g., business, system, code).
    • Testable: Clearly defined criteria for verification and validation.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Related Documents

    Requirement Engineering Chapter 4 PDF

    Description

    Explore the fundamentals of Requirements Engineering, focused on defining, managing, and testing system requirements. Understand the challenges faced in gathering good requirements and the influence of stakeholders in the process.

    More Like This

    Use Quizgecko on...
    Browser
    Open
    Browser
    Browser