The Analysis Phase is the third phase in the Systems Development Life Cycle but most system development methodologies contain some type of analysis phase. It is during the Analysis Phase that the current system and the problem deficiency or new requirement that is driving the development is studied in detail. The focus during the analysis phase is on what is needed and not how the needs are met. Determining how the needs are met would be determined during the Design Phase. We feel that the Object Oriented Analysis and Design will be the most beneficial for your needs, but we have included an example of a structured analysis within the familiar System Development Life Cycle (SDLC) that we implemented in our company.
Before the introduction of Object Oriented Analysis and Design, most Information Systems professionals were taught that the classical waterfall development life cycle was the proper way to approach software engineering and that "top level decomposition of processes was a practical way of handling large software development projects" (2).
These traditional methods built the foundation of modern software practices, and yet this foundation is being shaken by object oriented analysis and design.
Structured systems development began in the 1960s with the concept of systems development life cycle. In the 1970s, process-oriented structured methodologies were developed to promote a more effective analysis and design technique (2i). "The so-called structured revolution was based on computer program structures, with separate program steps (processes) and data" (2).
In the 1980s, planning and modeling of data began to play a more important role in development, resulting in data-oriented methodologies such as information engineering. "Although the data-oriented methodologies made better use of the powerful database models that were evolving, when it came to design, data methodologies still relied on process decomposition and simply mapped processes...