Carefully read the following part of a synopsis of a framework for the comparison of objectoriented analysis method, written by Simon McGinnes. A Framework for The Comparison of Object-Oriented Analysis Methods A comparative framework is presented which can be used to contrast many aspects of systems analysis and design methodologies. The framework focuses on the utility of methods for requirements analysis and high-level design of business information systems, and consists of more than fifty key questions which help to delineate the areas of divergence and commonality between methods. The questions are grouped so as to allow high-level method selection, feature analysis and detailed examination of notations and techniques. The framework is suitable for evaluating and comparing both conventional and object-oriented methodologies. Previous comparisons of information systems methodologies are examined and were used to refine the set of key questions. A large number of object-oriented methodologies are reviewed, and similarities and differences between the methodologies are summarized. Four chosen methodologies (by Coad and Yourdon, Rumbaugh et al, Henderson-Sellers, and Wirfs - Brock et al) are examined in depth. A detailed case study, using a realistic business-oriented application, is presented for each of the four methodologies, which are then evaluated and compared using the new comparative framework. A discussion is given of insights gained from the comparison. It is found that, despite reports to the contrary, the object-oriented analysis methodologies show remarkable similarity in techniques and scope to existing 'structured' methodologies. The object-oriented approach offers the potential for more 'natural' and intuitive conceptual models. However, key questions are raised about the philosophical basis of applying the object-oriented approach to systems analysis From the given synopsis, (a) Develop a Class Diagram that represents the given case study. Indicate classes, associations and multiplicity on your class diagram. You do not need to show the attributes and operations. Ensure that you use navigability to show the direction on the associations.
Carefully read the following part of a synopsis of a framework for the comparison of objectoriented analysis method, written by Simon McGinnes.
A Framework for The Comparison of Object-Oriented Analysis Methods
A comparative framework is presented which can be used to contrast many aspects of
systems analysis and design methodologies. The framework focuses on the utility of methods
for requirements analysis and high-level design of business
of more than fifty key questions which help to delineate the areas of divergence and
commonality between methods. The questions are grouped so as to allow high-level method
selection, feature analysis and detailed examination of notations and techniques. The
framework is suitable for evaluating and comparing both conventional and object-oriented
methodologies. Previous comparisons of information systems methodologies are examined
and were used to refine the set of key questions. A large number of object-oriented
methodologies are reviewed, and similarities and differences between the methodologies are
summarized. Four chosen methodologies (by Coad and Yourdon, Rumbaugh et al,
Henderson-Sellers, and Wirfs - Brock et al) are examined in depth. A detailed case study,
using a realistic business-oriented application, is presented for each of the four methodologies,
which are then evaluated and compared using the new comparative framework. A discussion
is given of insights gained from the comparison. It is found that, despite reports to the contrary,
the object-oriented analysis methodologies show remarkable similarity in techniques and
scope to existing 'structured' methodologies. The object-oriented approach offers the potential
for more 'natural' and intuitive conceptual models. However, key questions are raised about
the philosophical basis of applying the object-oriented approach to systems analysis
From the given synopsis,
(a) Develop a Class Diagram that represents the given case study. Indicate classes,
associations and multiplicity on your class diagram. You do not need to show the
attributes and operations. Ensure that you use navigability to show the direction on the
associations.
Step by step
Solved in 2 steps with 1 images
