Do Document Archaeology (Process Notes 2.1.6)
Document archaeology entails determining the underlying processes and requirements by inspecting the documents and files that the organization uses. It should not be used on its own as a requirements-gathering technique, but as a prelude to more
In document archeology, you begin by collecting samples of all documents,
Inspect the document (for simplicity's sake, the
For each noun, ask these questions:
These questions will not in
Make Requirements Video (Process Notes 2.1.7)
Video can be used to co-develop software. The users and developers participate in workshops and brainstorming sessions, and the proceedings are videoed. Interviews and on-site observations are also recorded. The videos are used to first record, and then confirm, the
Video can be used as an adjunct to interviewing and observing the users in their own workplace. Users have their own way of accomplishing
Video can also be used in a more structured way one business use case at a time. Select the business use case and ask the users to work through typical scenarios that they encounter with that activity. As they work, the users describe the special circumstances, the additional information they use, the exceptions, and so on. The shrugs, grimaces, gestures, and other body language that are normally lost when taking notes are faithfully recorded for later playback and dissection.
Run Use Case Workshop (Process Notes 2.1.8)
This workshop is
After the use case workshop, the requirements analysts go back to their offices and derive and specify the individual requirements from the knowledge in the use case scenarios.