1. Requirements Specification Activities CSCI 4320

2. Requirements Elicitation (E1)  Pair up with a classmate and role-play requirements elicitation for a piece of software.  One student thinks of a familiar software package. The other student asks questions concerning the functionality of the software.  When the second student is satisfied that he is sufficiently familiar with the software, he should describe the software in terms of informal scenarios.  The first student should then rate the accuracy of the second students understanding

3. Requirements Elicitation (E2)  Pair up with a classmate. One student should sketch the design of a house on a piece of paper and describe the house to the second student in strictly functional terms This house allows someone to prepare a meal while interacting with guests and provides private sleeping accommodations for one couple and two individuals NOT: This house has a kitchen that is open to the living room and 3 bedrooms on the second floor.  The second student draws the house based on the functional description

4. TickTackToe -1  Create a requirements specification for a computer-based game of ticktacktoe.  Address A list of activities that should be supported by the final system human-computer interface description

5. Evaluating the Requirements Specification  A dangerously wrong response to requirements specification is to take it at face value and not engage the end user in continuing dialogue to flesh out details and find errors

6. Evaluating the Requirements Specification  The specification must be clarified for ambiguities, errors or implicit assumptions  Professionals in different backgrounds have different vocabularies  Implicit assumptions may not translates to professionals in different fields.  The software development team must make a list of questions

7. TickTacToe - 2  Exchange your ticktactoe specifications with one of your classmates.  How did your specifications differ from your classmate’s?  Elaborate on the comparative strengths and weaknesses of each specification

8. TicTacToe - 3  Create a series of questions that will clarify the ticktacktoe specification written by your classmate.  Exchange lists of questions with your classmates.

9. TickTackToe -4  Based on the questions written by your classmate in response to your TickTackToe requirements statement, revise your specification

10. Summary Points  Requirements specification must be correct, complete, unambiguous, and verified  Specifications must be verified by the client and development team