About Requirements Analysis | Requirements Analysis: From Business Views to Architecture


Team-Fly

	Requirements Analysis: From Business Views to Architecture By David C. Hay
	Table of Contents

	Chapter 2. Managing Projects

About Requirements Analysis

Once a strategy has defined projects and articulated the vision and mission of the overall effort, requirements analysis performs the following processes for each project:

Process One: Define Scope : Re-examine the scope given to the project by the strategy phase. Does it still make sense? Determine how big the project is. Confirm what data categories will be covered, and what functions. Confirm what part of the organization will be addressed.
Process Two: Plan the Analysis : Lay out the steps specifically , identifying who will do each and defining how you will know if each is done successfully.
Process Three: Gather Information : Meet with the people who will own the system. They are the ultimate source of all your information about the company and what it should do.
Process Four: Describe the Enterprise : Use the modeling techniques described elsewhere in this book to portray the six dimensions of the enterprise: what data, how it is processed , where things are done, who plays what roles in the enterprise, when events take place that trigger activities, and why the enterprise is constrained the way it is.
Process Five: Take Inventory of Current Systems : While requirements analysis, for the most part, is not concerned with technology or current systems, it is useful to know what exists, and what roles technology plays in the current operation of the enterprise. While the other analysis steps are being done, this is a good time to take stock of current systems and what they are used for.
Process Six: Define What is Required of a New System : This is the "requirements" part of requirements analysis. What motivated this project? What specifically would make people's lives and work easier? What kinds of technology look promising ?
Process Seven: Plan for Transition : If a system that is built based on this analysis is at all significant, it will change the infrastructure of the organization. In addition to the mechanics of installing a new system, transition will entail extensive education and training, and it will probably involve organizational changes as well. Planning for this should begin during the requirements analysis phase.

These processes are described in more detail in the following sections.


Team-Fly

Top