Downloaded 5,527 times
- 1 / 113
- 2 / 113
- 3 / 113
- 4 / 113
- 5 / 113
- 6 / 113
- 7 / 113
- 8 / 113
Most read - 9 / 113
- 10 / 113
- 11 / 113
- 12 / 113
- 13 / 113
- 14 / 113
- 15 / 113
- 16 / 113
- 17 / 113
- 18 / 113
- 19 / 113
- 20 / 113
![Create curriculumSelect courses to teachCreate Activity Diagram for registration systemRegistrarProfessorcatalogMail catalog Place catalog to studentsin bookstoreOpen registration[ Registration time period expired ]SwimlanesClose registration48](/proxy?url=https%3A%2F%2Fimage.slidesharecdn.com%2Fsadvsooad-100513043350-phpapp01%2F85%2FStructured-Vs-Object-Oriented-Analysis-and-Design-48-320.jpg)
![54public class BlogAccount { // Attribute introduced thanks to the association with the BlogEntry classprivate BlogEntry[] entries; // ... Other Attributes and Methods declared here ...}public class BlogEntry{ // The blog attribute has been removed as it is not necessary for the // BlogEntry to know about the BlogAccount that it belongs to. // ... Other Attributes and Methods declared here ...}](/proxy?url=https%3A%2F%2Fimage.slidesharecdn.com%2Fsadvsooad-100513043350-phpapp01%2F85%2FStructured-Vs-Object-Oriented-Analysis-and-Design-54-320.jpg)
![61public class MessageReceiver{public void foo( ) { // Do something inside foo. }}public class MessageCaller{ private MessageReceivermessageReceiver; // Other Methods and Attributes of the class are declared here // The messageRecevier attribute is initialized elsewhere in // the class. public doSomething(String[] args) { // The MessageCaller invokes the foo( ) methodthis.messageReceiver.foo( ); // then waits for the method to return // before carrying on here with the rest of its work }}](/proxy?url=https%3A%2F%2Fimage.slidesharecdn.com%2Fsadvsooad-100513043350-phpapp01%2F85%2FStructured-Vs-Object-Oriented-Analysis-and-Design-61-320.jpg)
Skip to main content
Uploaded byMotaz Saad
Structured Vs, Object Oriented Analysis and Design
This document discusses structured vs object-oriented analysis and design (SAD vs OOAD) for software development. It outlines the phases and modeling techniques used in SAD like data flow diagrams, decision tables, and entity relationship diagrams. It also outlines the phases and modeling techniques used in OOAD like use cases, class diagrams, sequence diagrams, and state machine diagrams. The document compares key differences between SAD and OOAD, discusses textbooks on software engineering and UML, and references papers on using UML in practice and evaluating the impact and costs/benefits of UML in software maintenance.
