Automated object-oriented requirements analysis and design
John A. D. Anderson, Lance Holland, Jane Mcdonald, Elaine Scranage · 1989
This paper describes the results of the first phase of a Computer Sciences Corporation Internal Research & Development project that establishes a comprehensive object-oriented life-cycle methodology for Ada software system design.The Object-Oriented Requirements Analysis and Design (OORA/D) methodology incorporates the results of current object-oriented development techniques and is being applied to the development of an integrated life-cycle support system. Inadequacies of Traditional Analysis TechniquesSoftware requirements analysis is traditionally based on defining and decomposing the processes necessary to accomplish a task or function in a system.Each of these processes is further decomposed into lower-level processes, and the data that flow into and out of these processes are analyzed and documented using Data Flow Diagrams and a Data Dictionary.This approach results in a singular functional view of the system requirements that is inadequate to express the information necessary to construct a software solution to the problem.Agresti [1] suggests that no single view of a complex object should be expected to be satisfactory: "The most obvious analogy is with the multiple representations used in architecture.A scale model or artist's rendering of a building, which may be appropriate to show the planning commission, is not the