Some of the Diagrams from Object-Oriented Software Engineering

Here is a view of the object-oriented software development process as described in Object-Oriented Software Engineering: A Use Case Driven Approach (1993) by Ivar Jacobson, Magnus Christerson, Patrik Jonsson, and Gunnar Overgaard.

The general process described in Object-Oriented Software Engineering goes from the requirements documentation to a finished and maintainable software product.

The Analysis Phase is intended for defining the requirements and the relationships between the required functions of the system.

The Design Phase takes the models and preparations of the Analysis phase and applies them in terms of the actual environment where the computer program will run, including such concerns as the computer operating system, programming language, and actual coding of the program.

The Testing Phase takes the program and tests it in terms of the requirements and as a total system.

Use Cases are part of the total process and help to bring about the proper functioning of the total system. Use cases are particular requirements of the system, specifying what users will want to accomplish with the system. For example, in an email program, one use case might be checking to see if you have mail. The use case begins as a statement of purpose and is eventually designed in terms of the particular functions that are required to complete the purpose.

The information is gathered from a number of topics in the book.

More information about Requirements Analysis
Designing the Use Cases
Object-Oriented Design for World-Wide Web Pages

JPF