Requirements Engineering Overview
32 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 do user requirements specifically describe?

  • The services the system should provide (correct)
  • System performance and reliability standards
  • Detailed information about system functions
  • Operational constraints for implementation

    • Which of the following best defines non-functional requirements?

  • Descriptions of services and responses to inputs
  • Statements detailing specific actions of the system
  • Constraints that apply to services or functions of the system (correct)
  • Requirements that focus on user interface design

    • Which characteristic ensures that requirements can be measured and tested?

  • Consistent
  • Realistic
  • Verifiable (correct)
  • Traceable

    • What is the primary goal of the feasibility study in requirements engineering?

    <p>To determine if the proposed system is achievable</p> Signup and view all the answers

    Why might different stakeholders have conflicting requirements?

    <p>They express requirements in their own terms</p> Signup and view all the answers

    Which of the following is not a characteristic of effective requirements?

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

    What can influence the requirements during the analysis process?

    <p>Organizational and political factors</p> Signup and view all the answers

    Which activity is a part of the requirements engineering process?

    <p>Requirements validation</p> Signup and view all the answers

    What is the purpose of throwaway prototyping?

    <p>To build a working model that helps users visualize requirements.</p> Signup and view all the answers

    Which of the following is NOT a classic elicitation technique?

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

    What is a characteristic of high-fidelity prototypes?

    <p>They usually depict the user interface in a dynamic format.</p> Signup and view all the answers

    Which technique involves simulating computer behavior by a person?

    <p>Wizard of Oz</p> Signup and view all the answers

    What is one advantage of using prototypes in system development?

    <p>They improve communication between customers and developers.</p> Signup and view all the answers

    What might be a disadvantage of using prototyping?

    <p>It can lead to developers becoming too attached to their prototypes.</p> Signup and view all the answers

    Evolutionary prototyping seeks to achieve which of the following?

    <p>Constant refinement of the prototype over time.</p> Signup and view all the answers

    During which phase of development is prototyping most likely to be utilized to validate specifications?

    <p>Middle stages.</p> Signup and view all the answers

    Which type of prototype is NOT typically interactive?

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

    What can a working or functional prototype demonstrate effectively?

    <p>Interaction issues and design progress.</p> Signup and view all the answers

    What is a primary disadvantage of using natural language for user requirements?

    <p>Ambiguity leading to different interpretations</p> Signup and view all the answers

    What does the Software Requirements Specification (SRS) represent?

    <p>What the system should do</p> Signup and view all the answers

    Which of the following is NOT a part of requirements validation?

    <p>Cost assessment</p> Signup and view all the answers

    What is the focus of requirements management planning?

    <p>Identifying changes and their impacts</p> Signup and view all the answers

    What do graphical models in requirements specification primarily help to represent?

    <p>Business processes and system interactions</p> Signup and view all the answers

    What type of viewpoint focuses on the domain characteristics that influence requirements?

    <p>Domain viewpoint</p> Signup and view all the answers

    Which component is a part of form-based specification?

    <p>Description of outputs and their destinations</p> Signup and view all the answers

    What does requirements elicitation aim to produce?

    <p>Statement of need and feasibility</p> Signup and view all the answers

    Which validation technique can help identify inconsistencies and omissions in requirements?

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

    Which aspect is emphasized by the requirements traceability policies?

    <p>Connection between requirements and their sources</p> Signup and view all the answers

    What is one of the key reasons requirements tend to be incomplete or inconsistent?

    <p>Business environment changes</p> Signup and view all the answers

    Which statement about scenarios in requirements gathering is true?

    <p>They describe real-life usage examples of the system.</p> Signup and view all the answers

    Which of the following is a benefit of using structured language in requirements specification?

    <p>Reduction of ambiguity</p> Signup and view all the answers

    What is the purpose of using prototypes in requirements elicitation?

    <p>To clarify and better define requirements</p> Signup and view all the answers

    Study Notes

    Requirements

    • User requirements describe the system’s expected services and operating constraints from a user perspective
    • System requirements provide detailed information on the system's functionalities, services, and operational constraints to be implemented
    • Functional requirements outline services, system reactions to specific input, and system behavior in specific situations
    • Non-functional requirements impose constraints (timing, performance, reliability, development process, standards) on the system's services or functions

    Requirements Characteristics

    • Requirements should be unambiguous, complete, consistent with company goals and other requirements, traceable, realistic, verifiable, and valid

    Requirements Engineering Activities

    • Activities include feasibility study, requirements elicitation and analysis, requirements specification, and requirements validation

    Problems with Requirements Elicitation and Analysis

    • Stakeholders may not know what they want, express requirements in their own terms, have conflicting requirements, or be influenced by organizational and political factors
    • Requirements can change during the analysis process

    Requirements Elicitation and Analysis Activities

    • Activities include discovery, classification and organization, prioritization and negotiation, and documentation

    Classic Elicitation Techniques

    • Techniques include interviews, research, questionnaires, observation, forms analysis, and prototyping

    Prototyping

    • A prototype is a model of a system's appearance or behavior, often depicting the user interface
    • Prototype fidelity can range from low fidelity (paper) to high fidelity (GUI)

    When to Use Prototyping

    • Before, during, or after the development process to achieve different objectives, such as gathering initial requirements or validating system specifications

    Prototyping Types

    • Paper prototyping involves drawings and cutouts to elicit UI content and organization
    • "Wizard of Oz" prototyping simulates computer behavior and explores interactivity
    • Mockups are non-functional user interfaces using GUI components to validate UI design
    • Working/Functional prototypes have functional GUI components to validate design and explore interaction issues

    Prototyping Techniques

    • Throwaway prototyping creates a simple working model to demonstrate requirements and facilitate accurate specification
    • Evolutionary prototyping builds a robust prototype in a structured manner, constantly refining it through functional prototypes

    Advantages of Prototyping

    • Reduces development time and cost, builds customer confidence, energizes communication, facilitates implementation, improves user satisfaction, exposes developers to enhancements

    Disadvantages of Prototyping

    • Can focus on aesthetics rather than functionality, create a false impression of ease of development, lead to developers becoming too attached to prototypes, or result in a prototype being prematurely put into production

    Other Discovery Approaches

    • Viewpoints structure requirements to represent different stakeholder perspectives
    • Scenarios are real-life examples of system usage, including starting situations, flow of events, potential problems, concurrent activities, and ending states
    • Use cases are a type of scenario

    Work Products after Requirements Elicitation

    • Outputs include a statement of need and feasibility, a defined scope, a list of stakeholders, a description of the technical environment, organized lists of requirements, and developed prototypes

    Requirements Specification

    • User requirements are typically expressed in natural language, which can be ambiguous, overly flexible, and lack modularity
    • System requirements are better represented with specialized notation such as graphical models, tables, and structured language

    Requirements Specification (Form-Based)

    • Form-based specifications include the function or entity definition, input and output descriptions, dependencies, pre- and post-conditions, and side effects

    Analysis Models

    • Graphical representations (context models, data-flow models, state-machine models, data models, object models) bridge the gap between analysis and design

    Software Requirements Specification (SRS)

    • The SRS is the official statement of system requirements, focusing on WHAT the system should do, not HOW it should be done

    IEEE Requirements Standard

    • Defines a generic structure for a requirements document, including introduction, general description, specific requirements, appendices, and an index

    Requirements Validation

    • Assesses the quality of requirements by checking them against characteristics, determining if they meet customer needs
    • Techniques include specification reviews, prototyping, and test case generation

    Requirements Management

    • The process of identifying, understanding, tracking, and controlling changes to system requirements
    • Requirements are inevitably incomplete and inconsistent, requiring change management, traceability policies, and CASE tool support

    Requirements Management Planning

    • Includes requirements identification, change management process, traceability policies (source, dependency, features, or design), and CASE tool support

    Studying That Suits You

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

    Quiz Team

    Related Documents

    IT313mid1.pdf

    Description

    This quiz covers the fundamental aspects of requirements engineering, including user and system requirements, functional and non-functional requirements. It also addresses the characteristics of effective requirements and the activities involved in the requirements engineering process. Gain insights into the typical challenges faced during requirements elicitation and analysis.

    More Like This

    Use Quizgecko on...
    Browser
    Open
    Browser
    Browser