Professional Documents
Culture Documents
Learning Outcomes
By the end of this lecture, YOU should be able to:
define RE and describe activities undertaken in RE development define RE and describe activities undertaken in RE Management Identify the good RE practices within the respective subcomponents of RE development
Requirements Engineering
Requirements Development
Requirements Mgt
Elicitation
Analysis
Specification
Validation
Requirements Development
Involves: Identifying the products expected user classes Eliciting needs from user class Understanding user tasks, goals and business objectives Analyzing user information, distinguishing task goals, functional and non-functional requirements Transforming user needs to requirements specification
Requirements Management
Is the establishing and maintaining an agreement with the customer on the requirements for the software project The agreement is embodies in the written requirement specification Req. Mgt. Activities : Define requirements baseline Review proposed changes Incorporate approved requirements Keeping project plans Tracing individual requirements, from design to source code Tracking requirements status
Fred Brooks, "No Silver Bullet :Essence and Accidents of SE", IEEE Computer,1987 Author of The Mythical Man-mon
Creeping User requirements Ambiguous requirements Gold plating Minimal Specification Overlooked user classes Inaccurate Planning
Complete no missing requirements or necessary information Consistent no conflict among requirements Modifiable requirements revisions possible and history of revision maintained. Traceable traceable requirements can be linked backward to its origins and forward to the design element
Define change control process Establish change control board Perform change impact analysis Baseline and control versions of requirements Maintain change history Track requirements status Measure requirements volatility Use a requirements management tool Create requirements traceability matrix
Fundamentals of Requirements Engineering #
Define requirements evelopment process Define vision and scope Identify user classes Select product champions Establish focus groups Identify use case Identify system events and responses Hold facilitated elicitation workshops Observe user performing jobs Examine problem reports Reuse requirements
Fundamentals of Requirements Engineering #
References
Software Requirements; Karl E. Wiegers; 2nd Edition; 2003