Recently MeroSpark is lunched with more features and services, now you can ask your question, sell your books, share your notes and many more. Visit now and create your account to take full advantage of MeroSpark.

Requirements Elicitation and Analysis | Activity of Requirements Engineering Process

Download our Android App from Google Play Store and start reading Reference Notes Offline.

requirement elicitation and analysisRequirements Elicitation and Analysis,
Software Engineering Notes | Sixth Semester,
BSc.CSIT | Tribhuvan University (TU)

Requirement Elicitation and Analysis
In this activity, software engineers work with customers and system end users to find out about the application domain, what services the system should provide, required performance of the system, hardware constraints and so on. It may involve a variety of different kinds of people in an organization.

req. elicitation and analysis

  • Requirements Discovery
    It is the process of interacting with stakeholders of the system to discover their requirements. Domain requirements from stakeholders and documents are discovered.
  • Requirements classification and organization
    It takes the unstructured collection of requirements, groups related requirements, and organizes them into coherent clusters. Most common way of grouping requirements is, use a model of the system architecture to identify sub-systems and to associate requirements with each sub-system.
  • Requirements prioritization and negotiation
    It is concerned with prioritizing requirements and finding and resolving requirement conflicts through negotiation. Stakeholders meet and resolve differences and agree on compromise requirements.
  • Requirements Specification
    Requirements are documented and input into the next round of the spiral. Formal or informal requirements document may be produced.

Requirement elicitation and analysis is an iterative process with continual feedback from each activity to other activities. The process cycle starts with requirement discovery and ends with requirements documentation. The analyst’s understanding of the requirement improves with each round of the cycle. The cycle ends when the requirements document is complete.

(Visited 359 times, 1 visits today)

Posted By : Digvijay | Comment RSS | Category : Sixth Semester
Tag :

Post a Comment

Your email is never published nor shared. Required fields are marked *


Wordpress DMCA
Community | Toolbar | Android App | Founder/Developer : Hari Prasad Chaudhary | CSIT Portal Manager : Digvijay Chaudhary