[II] OVERVIEW OF SYSTEM ANALYSIS AND DESIGN
Requirements describe the ‘what’ of a system not the ‘how’. The first phase of a typical project is scope definition. The purpose of scope definition is to see whether the problem is worth looking at or not and establishing the size and boundaries of the project, the project vision, any constraints or limitations, the required project participants and finally the budget and schedule.
One important outcome of scope definition is a PROBLEM STATEMENT. The problem analysis phase studies the existing system and analyses the findings to provide the project team with a more thorough understanding of the problem. The participants included in requirements determination phase are primarily system users and system analyst. To produce a business requirement statement, system analyst works closely with system users to identify needs and priorities. This information is collected by way of interviews, questionnaires, and facilitated meeting.
Requirement determination is software engineering task that bridges the gap between system level requirements and software design.
Requirement determination is done to clearly understand the customer’s requirement and to systematically organize these requirements into a specification document.
Typically, requirements must also be prioritized. Priorities serve two purposes :
- If project time lines become stressed, requirement priorities can be used to rescope the project.
- Priorities can frequently be used to define iterations of design and to create staged releases or versions of the final project.
One of the most common complaint about new systems and applications is that they don’t really satisfy the user’s needs. This usually happens when system designers and builders becomes preoccupied with the technical solution before fully understanding the business needs.