1 / 30

CS 501: Software Engineering

CS 501: Software Engineering. Lecture 16 Object Oriented Design I. Administration. The Waterfall Model. Requirements. Requirements Analysis. System design. Design. Program design. Implementation. Coding. Unit & Integration Testing. System Testing. Acceptance Testing.

margot
Download Presentation

CS 501: Software Engineering

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. CS 501: Software Engineering Lecture 16 Object Oriented Design I

  2. Administration

  3. The Waterfall Model Requirements Requirements Analysis System design Design Program design Implementation Coding Unit & Integration Testing System Testing Acceptance Testing Operation & Maintenance

  4. Program Design • The task of program design is to represent the software • system functions in a form that can be transformed into • one or more executable programs. • Given a system architecture, the program design specifies: • computers and networks • programs, components, packages, classes and class hierarchies • interfaces, protocols • security mechanisms, operational procedures

  5. The Importance of Modeling • A model is a simplification of reality. • We build models so that we can better understand the system we are developing. • We build models of complex system because we cannot comprehend such a system in its entirety. Models can be informal or formal. The more complex the project the more valuable a formal model becomes. BRJ

  6. Principles of Modeling • The choice of what models to create has a profound influence on how a problem is attacked and how a solution is shaped. • Every model can be expressed at different levels of precision. • The best models are connected to reality. • No single model is sufficient. Every nontrivial system is best approached through a small set of nearly independent models. BRJ

  7. The Unified Modeling Language UML is a standard language for modeling software systems • Serves as a bridge between the requirements specification and the implementation. • Provides a means to specify and document the design of a software system. • Is process and programming language independent. • Is particularly suited to object-oriented program development.

  8. Useful Texts Grady Booch, James Rumbaugh, Ivar Jacobson, The Unified Modeling Language. Addison-Wesley 1999. Grady Booch, Object-Oriented Analysis and Design with Applications, second edition. Benjamin/Cummings 1994. Rob Pooley, Perdita Stevens, Using UML Software Engineering with Objects and Components. Addison-Wesley 1999.

  9. Rational Rose Rational Rose is a system for creating and managing UML diagrams. It is available on all Computer Science Department computers. See: http://adm/Software/purify_install.htm for installation instructions.

  10. Notation: Classes name attributes operations Window origin size open() close() move() display() A class is a description of a set of objects that share the same attributes, operations, relationships and semantics.

  11. The HelloWorld Example class HelloWorld paint() name operations

  12. Notation: Grouping and Annotation Business rules A package is a general-purpose mechanism for organizing elements into groups. return copy of self A note is a symbol for rendering constraints and comments attached to an element or a collection of elements.

  13. g.drawString ("HelloWorld", 0, 10)" Abstraction for HelloWorld class HelloWorld paint() name annotation operations

  14. HelloWorld paint() Class Diagram Applet Note that the Applet and Graphics classes are shown elided. generalization dependency Graphics

  15. Class Inheritance Diagram Object Panel interface Component ImageObserver Applet Container HelloWorld

  16. applet awt lang Packaging Classes java HelloWorld package Graphics

  17. Notation for Classes and Objects Objects Classes anObject:AnyClass AnyClass attribute1 attribute2 operation1() operation2() or :AnyClass or anObject or The names of objects are underlined. AnyClass

  18. The "Hello, World" Implementation import java.awt.Graphics; class HelloWorld extends java.applet.Applet { public void paint (Graphics g) { g.drawString ("Hello, World!", 10, 10); } } Example from: BJR

  19. Notation: Interface ISpelling An interface is a collection of operations that specify a service of a class or component, i.e., the externally visible behavior of that element.

  20. Notation: Collaboration & Use Case Chain of responsibility A collaboration defines an interaction, i.e., a society of roles and other elements that work together to provide some cooperative behavior. Place order A use case is a description of a set of sequence of actions that a system performs that yields an observable result.

  21. Notation: Active Class EventManager eventlist suspend() flush() An active classis a class whose objects own one or more processes or threads and therefore can initiate control activity.

  22. orderform.java Notation: Component & Node A component is a physical and replaceable part of a system that conforms to and provides the realization of a set of interfaces. Server A node is a physical element that exists at run time and represents a computational resource.

  23. Notation: Behavioral Things:Messages & States display An interaction is a behavior that comprises a set of messages exchanged among a set of objects within a particular context to accomplish a specific purpose. Waiting A state machine is a behavior that specifies the sequence of states an object or an interaction goes through during its lifetime in response to events.

  24. Notation: Relationships A dependency is a semantic relationship between two things in which a change to one may effect the semantics of the other. 0..1 * employer employee An association is a structural relationship that describes a set of links, a link being a connection among objects.

  25. Relationships Parking 1 0 ... 1 Parking Space location is_available()

  26. Notation: Relationships (continued) child parent A generalization is a specialization/generalization relationship is which objects of the specialized element (child) are substitutable for objects of the generalized element (parent). A realizationis a semantic relationship between classifiers, wherein one classifier specifies a contract that another classifier guarantees to carry out.

  27. Diagrams in UML A diagram is the graphical representation of a set of elements, usually rendered as a connected graph of vertices (things) and arcs (relationships). • Class diagram shows a set of classes, interfaces, and collaborations with their relationships. • Object diagram shows a set of objects and their relationships. • Use case diagram shows a set of use cases and actors (a special kind of class) and their relationships.

  28. Diagrams in UML (continued) Interaction diagram shows an interaction, consisting of a set of objects and the relationships, including the messages that may be dispatched among them. => A sequence diagram emphasizes the time ordering. => A collaboration diagram emphasizes the structural organization of the objects that send and receive messages.

  29. Example: A Sequence Diagram libMem: LibraryMember theBook:Book BookBorrower theCopy:Copy borrow(theCopy) okToBorrow borrow borrow

  30. Diagrams in UML (continued) • Statechart diagram shows a state machine consisting of states, transitions, events, and activities. • Activity diagram is a statechart diagram that shows the flow from activity to activity within a system. • Component diagram shows the organization and dependencies among a set of components. • Deployment diagram shows the configuration of processing nodes and the components that live on them.

More Related