Systems Design:Requirements Gathering
From GSLISWiki
Systems Analysis and Design: 1. Problem Definition | 2. Requirements Gathering / Requirements Analysis | Systems Design:Design | Systems Design:Development | Systems Design:Testing | Systems Design:Implementation | Systems Design:Maintenance
Contents |
[edit] The Requirements Gathering / Requirements Analysis Process
As Davis (1994) says, "Until you know what to do, there is little point in worrying about how to do it." (page 69). Therefore, Requirements Gathering (or Requirements Analysis) is the second phase in Systems Analysis and Design.
[edit] Information Gathering
- Study the present system
- Identify Processes
- Identify Fields/Data Objects
- Identify Boundaries
- Relate Processes, Data, Boundaries
- Identify Objects
- Document and organize documentation
- Define Data Elements
- Define Data Structures
From Davis (1994). Needs some work. Will include lessons from Participatory Design literature when reworking this section.
[edit] Methods
While methods are key to Requirements Gathering, this page currently simply contains links to other pages which describe the methods in more detail.
