Summary Requirements Engineering Fundamentals A Study Guide for the Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant

A snapshot of the summary - Requirements Engineering Fundamentals A Study Guide for the Certified Professional for Requirements Engineering Exam - Foundation Level - IREB compliant Author: Klaus Pohl Chris Rupp ISBN: 9781457111921

• 1 Introduction and Foundations

• What are quality requirements?
  

  1. A quality requirement is a requirement that pertains to a quality concern that is not covered by functional requirements
  2. @ The desired qualities of the system, e.g. (ISO 25010):
     

  • Detailing functionalities (securaty, accurateness)
  • Reliability
  • Useability
  • Efficiency
  • Changeability
  • Portability
    
• What is a constraint
  

  A constraint is a requirement that limits the solution space beyond what is necessary for meeting the given functional requirements and quality requirements.
  
• What is Requirement Engineering
  

  Requirements engineering is a systematic and disciplined approach to the specification and management of requirements with the following goals:
  

  1. knowing the relevant requirements, achieving a consensus among the stakeholders about these requirements, documenting them according to given standards and managing them systematically;
  2. understanding and documenting the stakeholders desires and needs, then specifying and managing the requirements to minimize the risk of delivering a system that does not meet these desires and needs.
     
• What is a stakeholders
  

  A stakeholder of a system is a person or an organisation that has an (direct or indirect) influence on the requirements of the system.
  
• Characteristics of the requirements engineer
  

  The requirements engineer must have: domain knoledge, process knowledge, IT know-how;
  Above all, good communication skills are essential: verbal, in writing.
  Additionally, the requirements engineer must possess certain soft skills: analytical thinking, empathy, conflict resolution, moderation, self-confidence, ability to convince.
  

• 1.1.1 Figures and Facts from Ordinary Projects

• Symptoms of poor requirements engineering

  1. Unused system
     
  2. User dissatisfaction with developed system
     
  3. Unmet stakeholder requirements
     
  4. Unwanted features gettingimplemented
     
  5. Work executed through workarounds
  6. Unclear incomplete or wrong requirements lead to development of wrong solutions.
     
  7. Costs of fixing errors increase exponentially with each project phase.

• 1.1.2 Requirements Engineering - What Is It?

• What is a requirement

  1. A condition or capability needed by a user to solve a problem or achieve an objective;
  2. A condition of capability that must be met or possessed by a system component to satisfy a contract, standard, specification or other formally imposed documents;
  3. A documented representation of a condition of capability as in (1) or (2).
  4. A requirement may be unstated, implied by or derived from other requirements, or directly stated and managed.
  5. Requirements describe, but not limited to, past, present and future conditions or capabilities in an enterprise, organizational structures, roles, processes, policies, rules and information systems.
• Four core activities of requirements engineering

  1. Elicitation (Obtain requirements form stakeholders)
  2. Documentation (elicited requirements are described adequately)
  3. Validation & Negotiation (guarantee that predefined quality criteria are met, documented requirements must be validated and negotiated)
  4. Management
• Requirements engineering consists of two parts, which?

  1. Requirements development (gericht op identificeren, verzamelen en ontwikkelen van requirements van de stakeholder)
  2. Requirements management (beheren van de requirment van creatie tot uitfaseren)
• What are the different levels of requirements?

  • Business - VB: Wat heeft het bedrijf nodig, een CRM systeem
    
  • Stakeholders - VB: Wat zijn de wensen van de stakeholders; tester/ gebruiker etc.
    
  • Solution - VB: Functioneel / Non-Functioneel
    

  • Transition