1 / 10

Requirements Engineering Processes

Requirements Engineering Processes. Requirements engineering process. Requirements elicitation and analysis. Feasibility study. Requirements specification. Requirements validation. Feasibility report. System models. User and system requirements. Requirements document.

ludwig
Download Presentation

Requirements Engineering Processes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirements Engineering Processes

  2. Requirements engineering process Requirements elicitation and analysis Feasibility study Requirements specification Requirements validation Feasibility report System models User and system requirements Requirements document See also the spiral model on page 144

  3. Feasibility studies • “Does the system contribute to the overall objectives of the organization?” • “Can the system be implemented using current technology and within given cost and schedule constraints?” • “Can the system be integrated with other systems which are already in place?” (should take about 2-3 weeks)

  4. Requirements elicitation and analysis • Some difficulties: • Stakeholders in general don’t know what they want from a computer system except for “general statements” • Requirements are expressed using terms that are specific to the domain (not necessarily familiar for the SE) • Different stakeholders => different set of requirements • Some requirements may be influenced by “political factors” • Some requirements are sensitive to economical and business changes

  5. Requirements elicitation and analysis – Process activities • Requirements discovery: view points, scenarios, interviews • Requirements classification and analysis: clustering into functional / non-functional, use cases • Requirements prioritization and negotiation: back to customer • Requirements documentation

  6. Requirements validation • Validity checks • Consistency checks • Completeness checks • Realism checks • Verifiability checks

  7. Requirements validation - techniques • Requirements review • Step by step reading of requirements • Check for: • Verifiability • Comprehensibility • Traceability • Adaptability • Prototyping • Test-case generation

  8. Requirements management • With the system in use new requirements can appear: • New needs and priorities • Changes on the support balance • Adaptation to end-user needs • Business and technical changes

  9. Requirements management • Requirements can be classified into: • Enduring requirements: relate to core activities of the organization (more stable) • Volatile requirements: relate to external factors and minor activities (susceptible to be changed) • Mutable: related to the environment of the system • Emergent: resulting from ‘learning’ the system • Consequential: following the introduction of the system • Compatibility: related to external systems

  10. Requirements change management • Problem analysis and change specification • Change analysis and costing • Change implementation

More Related