The key aspects in a methodology are the concepts on which it is founded, a process or set of activities where the concepts are used and finally a notation. and Yourdon methodology has been used to analyse the inventory problem, and then Booch following Coad and Yourdon method, the graphical notation. The Coad and Yourdon Method – Download as Powerpoint Presentation .ppt /. pptx), PDF File .pdf), Text File .txt) or view presentation slides online.
|Published (Last):||21 May 2012|
|PDF File Size:||11.97 Mb|
|ePub File Size:||11.44 Mb|
|Price:||Free* [*Free Regsitration Required]|
For this reason, subject diagrams are useful as a ‘top-level’ view to guide the programmer through to more detailed class diagrams for 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.
Yourdon and Coad Design Software with Rich Examples and Templates
In the book, a notation is metjod for use along with 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 meyhod this also seems inappropriate. I use package diagrams as part of deciding xnd 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 Coax discussion of package diagrams in Agile Modeling supports this perspective, as well. 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.
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 mixed 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.