Object-Oriented Analysis Models – Rumbaugh, Booch, Coad-Yourdon, and Shlaer-Mellor Method. The Coad/Yourdon method: simplicity, brevity, and clarity—keys to successful Describing and comparing object-oriented analysis and design methods. Object-oriented methodologies of Coad and Yourdon and Booch: Coad and Yourdon methodology has been used to analyse the inventory problem, and then .
|Published (Last):||13 May 2013|
|PDF File Size:||20.79 Mb|
|ePub File Size:||17.77 Mb|
|Price:||Free* [*Free Regsitration Required]|
Object-oriented analysis – Peter Coad, Edward Yourdon – Google Books
Typically, a subject would represent the top level of a gen-spec or a whole-part class tree. For this reason, subject diagrams are useful as a ‘top-level’ view to guide the programmer through to more detailed class diagrams analysus each ‘subject’ area. This would be a useful analytical approach for a project I am currently working on it is a rather large problem domain. In the book, a notation is suggested for use along anaysis the analysis approach as it was recognised that an analytical method needs a supporting notation for it to be practical.
My first thought was for component diagramsbut I have always viewed components as principally an implementation concern rather than part of the problem domain.
Whilst the component definitions will usually coincide with natural divisions in the problem domain, it seems incorrect to be talking about interfaces etc. I also considered package diagrams but this also seems inappropriate.
I use package diagrams as part of deciding how the components are to be grouped in terms of the source code repositories; this is closely related to my deployment strategy as each package will be intended for deployment to a particular server. There’s no specific granularity for a block – it could be another system, a subsystem, component, class, and so on.
If you want to stay within UML, I wouldn’t dismiss package diagrams so quickly. What you are describing could be viewed, from one perspective, as a “package”. Scott Ambler’s discussion of package diagrams in Agile Modeling supports this perspective, as well.
Components of a Class Diagram
Personally, I don’t have a problem mixing notations. A viewpoint shows the design from the perspective of a particular stakeholder, using one or more views. Views can be in any form, but are usually graphical and sometimes tabular with supporting text.
The standard says that “only standardized and well-established i. If your audience will understand the Coad-Yourdon notation or you can point them toward a reference source that they naalysis easily obtain, use that notation.
Home Questions Ofiented Users Unanswered.
CPSC Coad and Yourdon’s Method for Object-Oriented Design
Considerations thus far My first thought was for component diagramsbut I have always viewed components as principally an implementation concern rather than part of the problem domain. Marvin 4 I don’t have any particular aversion to orisnted notations; as long as complexity is minimised.
Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name.