1 / 18

Chapter 13

Chapter 13. Object-Oriented Techniques. O bject oriented programming (Booch 1991). A major factor in the invention of Object-Oriented approach is to remove some of the flaws encountered with the procedural approach. .

len
Download Presentation

Chapter 13

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 13 Object-OrientedTechniques

  2. Object oriented programming (Booch 1991) A major factor in the invention of Object-Oriented approach is to remove some of the flaws encountered with the procedural approach.  • In OOP, data is treated as a critical element and does not allow it to flow freely. • It bounds data closely to the functions that operate on it and protects it from accidental modification from outside functions. • OOP allows decomposition of a problem into a number of entities called objects and then builds data and functions around these objects. • A major advantage of OOP is code reusability.

  3. Some important features of Object Oriented programming • Emphasis on data rather than procedure • Programs are divided into Objects • Data is hidden and cannot be accessed by external functions • Objects can communicate with each other through functions • New data and functions can be easily added whenever necessary • Follows bottom-up approach Source: http://www.startvbdotnet.com/oop/default.aspx

  4. Concepts of OOP ObjectsClassesData Abstraction and EncapsulationInheritancePolymorphism Source: www.bilmuh.gyte.edu.tr/.../icpp_oop1.html

  5. Object-Orientation OOP Tutorial : http://homepages.north.londonmet.ac.uk/~chalkp/proj/ootutor/objects.html

  6. Object-Orientation

  7. Object-Orientation

  8. Unified Modelling Language (UML) • The Unified Modeling Language (UML) is a standard  language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems. • The UML is a very important part of developing object oriented software and the software development process.  • The UML uses mostly graphical notations to express the design of software projects.  Using the UML helps project teams communicate, explore potential designs, and validate the architectural design of the software.

  9. The primary goals in the design of the UML

  10. Each UML diagram is designed to let developers and customers view a software system from a different perspective and in varying degrees of abstraction. UML diagrams commonly created in visual modeling tools include: Use Case Diagram Class Diagram Interaction Diagram State Diagram Activity Diagram Physical Diagram UML Diagrams

  11. displays the relationship among actors and use cases Use Case Diagram Use cases are used in almost every project.  They are helpful in exposing requirements and planning the project. During the initial stage of a project most use cases should be defined, but as the project continues more might become visible.  http://pigseye.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/use_case.htm

  12. models class structure and contents using design elements such as classes, packages and objects. It also displays relationships such as containment, inheritance, associations and others Class diagram Class diagrams are used in nearly all Object Oriented software designs. Class diagrams are use to describe the Classes of the system and their relationships to each other. Classes are composed of three things: a name, attributes, and operations.

  13. Class diagram

  14. displays the time sequence of the objects participating in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects). Sequence Diagram

  15. displays the sequences of states that an object of an interaction goes through during its life in response to received stimuli, together with its responses and actions Statechart Diagram

  16. displays a special state diagram where most of the states are action states and most of the transitions are triggered by completion of the actions in the source states. This diagram focuses on flows driven by internal processing Activity Diagram

  17. UML Modeling Tools • Rational Rose • Enterprise Architect • Select Enterprise • Visual CASE

  18. End of Chapter 13 Thank You for Your Attention

More Related