Page 280 - Software and Systems Requirements Engineering in Practice

ç ç 3 O F T W A R E ç ç 3 Y S T E M S ç 2 E Q U I R E M E N T S ç % N G I N E E R I N G ç ) N ç 0 R A C T I C E

1, ʙ°ÓÊ œ˜VÕÀÀi˜ÌÊ, Ê>˜`Ê`iÛiœ«“i˜Ì

v $OMAIN EXPERTS AND OR CUSTOMERS REVIEW THE OUTPUTS OF BOTH
2% AND PROTOTYPE DEVELOPMENT AND THE FEEDBACK IS USED AS
INPUTS FOR BOTH PROCESSES
v 3IMPLICITY AND UNAMBIGUOUSNESS OF THE PRESENTATION REVIEWS
ARE IMPORTANT FOR SMOOTH PROGRESS OF THE PROTOTYPE
DEVELOPMENT AND REQUIREMENTS ENGINEERING PROCESSES !N
EXAMPLE COULD BE THE REVIEW OF THE OUTPUTS OF A 3CRUM SPRINT
AT THE END OF THE MONTH FOR A SET OF FEATURES IMPLEMENTED IN
THE PROTOTYPE USER INTERFACE 0ROTOTYPES ARE REVIEWED IN THE
CONTEXT OF RELEVANT AND AGREED UPON BUSINESS SCENARIOS AND
THE STAKEHOLDERS ARE EXPECTED TO PROVIDE SPECIFIC FEEDBACK
4HE FEEDBACK RELATED TO A REVIEW SHOULD BE AS FINE GRAINED AS
POSSIBLE PARTICULARLY IF SOME PROTOTYPE ASPECTS ARE REJECTED
v -ULTIPLE FUNCTIONAL PROPOSALS ARE ELABORATED BY THE
REQUIREMENTS ENGINEERS FOR REVIEW AND SELECTION BY THE
CUSTOMER END USER )N SOME CASES IT MAY BE MORE COST
EFFECTIVE TO CREATE CUSTOMIZED VERSIONS OF THE PROTOTYPE AND
MAKE A SELECTION AMONG THESE