SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD

stormy avatar
stormy
28 diapositives · 618 Views · Aug 08, 2014

Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD. Software process model. Modeling. A model is an abstract view of a system We create a model to gain better understanding of an entity, for example a model of a plane is a small plane.

#structured vs. object oriented analysis and design sad vs. ooad #structured vs. object oriented analysis and design sad vs. ooad ppt #powerpoint #presentation
Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD - slide 1
01 / 28Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
1 / 17

Télécharger la présentation

Structured Vs. Object Oriented Analysis and Design SAD Vs. OOAD
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Structured Vs. Object Oriented Analysis and DesignSAD Vs. OOAD

  2. Software process model

  3. Modeling • A model is an abstract view of a system • We create a model to gain better understanding of an entity, for example a model of a plane is a small plane. • When the entity is software, the model takes a different form.

  4. A software Model A software model must be capable of representing : • the information that the software transforms, • the functions that enable the transformation to occur, and • the behavior of the system as the transformation takes place.

  5. Structured Analysis Vs. Object Oriented Modeling 1-Behavioural Models: Data processing models that show how data is processed as it moves through the system (Data Flow Diagram -DFD and Entity Relation diagram- ER). Will be covered in this course 2- OR Object Models: Use case diagrams and Class diagram. Focus on Objects rather than data or process Covered in previous course

  6. Object Oriented Analysis and Design OOAD

  7. Commonly used UML diagram types • Activity diagrams, which show the activities involved in a process or in data processing . • Use case diagrams, which show the interactions between a system and its environment. • Sequence diagrams, which show interactions between actors and the system and between system components. • Class diagrams, which show the object classes in the system and the associations between these classes. • State diagrams, which show how the system reacts to internal and external events.

  8. 1- Context Model for ATM Context models show what lies outside the system boundaries.

  9. 2- Interaction models A- Use case • A use case in the MHC-PMS

  10. 2- Interaction modelsB- Sequence diagrams • Sequence diagrams are part of the UML and are used to model the interactions between the actors and the objects within a system. • A sequence diagram shows the sequence of interactions that take place during a particular use case or use case instance. • The objects and actors involved are listed along the top of the diagram, with a dotted line drawn vertically from these. • Interactions between objects are indicated by annotated arrows.

  11. Ex: Sequence diagram for View patient information

  12. 3- Structural modelsA- Class diagrams • An association is a link between classes that indicates that there is some relationship between these classes. • When you are developing models during the early stages of the software engineering process, think of objects represent something in the real world, such as a patient, a prescription, doctor, etc.

  13. Ex: Classes and associations in the MHC-PMS

  14. Ex:The Consultation class

  15. 4- Behavioral models • Behavioral models are models of the dynamic behavior of a system as it is executing. They show what happens or what is supposed to happen when a system responds to a stimulus from its environment.

  16. 4- Behavioral modelsA- Data-driven modeling – Activity diagram • Many business systems are data-processing systems that are primarily driven by data. They are controlled by the data input to the system, with relatively little external event processing. • Data-driven models show the sequence of actions involved in processing input data and generating an associated output. • They are particularly useful during the analysis of requirements as they can be used to show end-to-end processing in a system.

  17. Data-driven modeling • Data flow diagrams (DFDs) may be used to model the system’s data processing. • These show the processing steps as data flows through a system. • UML does not support DFDs . UML use activity diagram instead.

  18. Ex: An activity model of the insulin pump’s operation

  19. 4- Behavioral models B- Event-driven modeling - State diagram • Event-driven modeling shows how a system responds to external and internal events.

  20. Ex: State diagram of a microwave oven

  21. Structures Analysis and DesignSAD

  22. Ex: DFD Context diagram shows the system boundaries, external entities that interact with the system, and major information flows between entities and the system.

  23. Structures Analysis Vs. Object Oriented

  24. Comparison

  25. We can always use a tool to draw any model

  26. What is CASE? • CASE (Computer Aided Software Engineering) • Programs used to support software process activities such as system modeling, debugging, and testing • Some CASE tools include automatic code generation from diagrams.

  27. References • http://www.slideshare.net/mksaad/structure-vs-object-oriented-analysis-and-design • Sommerville, Ian ,“Software Engineering”, 9th edition, PEARSON