1 / 29

Object Oriented Analysis and Design Using the UML

Object Oriented Analysis and Design Using the UML. Use Case Analysis Modified considerably by your Instructor. Objectives: Use-Case Analysis. Understand the purpose of Use-Case Analysis and where in the lifecycle it is performed

cyost
Télécharger la présentation

Object Oriented Analysis and Design Using the UML

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. Object Oriented Analysis and Design Using the UML Use Case Analysis Modified considerably by your Instructor

  2. Objectives: Use-Case Analysis • Understand the purpose of Use-Case Analysis and where in the lifecycle it is performed • Identify the classes needed to accommodate a use- case flow of events (Analysis Classes) • Distribute the use-case behavior to those classes, identifying responsibilities of the classes • The analysis classes and the initial use-case realizations are the key model elements that we develop in this activity.

  3. Use Case Analysis • The focus during Use-Case Analysis is on a particular use case. • In Use-Case Analysis, we identify the analysis classes and define their responsibilities. • (At this time, we speak of ‘responsibilities.’ (May even use the term, ‘services.’) Later, these might become ‘methods’ or ‘member functions.’ But that is a matter for implementation NOT initial design.) • The allocation of responsibility is modeled in use-case realizations that describe how analysis classes collaborate to perform (realize) use cases.

  4. Software Architecture Document – (don’t really have this one yet.) AnalysisClasses Design Model Use-Case Modeling Guidelines Supplementary Specifications Glossary Use-Case Model Analysis Model (optional) Use-Case Realization (developed) Use-Case Analysis Overview Use Case Analysis is performed By the Designer – once per Iteration per use case realization Use-Case Analysis

  5. Use Case Analysis - Purpose • To identify analysis classes which perform a use case’s flow of events • To distribute the use case behavior to those classes • Remember: domain entities do not contain behaviors… • Use case analysis result in logical abstractions with attributes and behaviors. • To identify the responsibilities, attributes and associations of the classes • Input Artifacts – see previous slide • Output Artifacts: • Analysis Classes • Analysis Model • Partially Developed Use-Case Realizations • Work toward Design Model (first cut, really)

  6. Use-Case Analysis Steps – Major ones • 1. Supplement the Use-Case Description • Will be changing some as we continue to examine our Use Cases and add alternative, exception, and other flows. • We modify as we learn more and analyze… • 2. For (each use-case realization) Do: • Study Use Case flow of events - identify analysis classes from the Use Case narrative. These consist of interface, control, & data classes. • Allocatebehaviors (responsibilities) to these classes. • These are the little things the class must do….in some cases, these are merely options afforded to the user like add new customer() or delete customer ()….display customer profile… • Distribute Use-Case Behaviors to Classes that you identify • DescribeAttributes (properties) of each analysis class. • Showassociations between the collaborating classes. • Let’s look at each of these two major items in particular….

  7. Use-Case Analysis Steps • 1. Supplement the Use-Case Description • Capture additional information in order to understand the required internal behaviors. • It is quite customary to make changes (or should be….) • This is part of the iterative process. Versioning of Use Cases. • This is why we spend so much time on getting those use cases right – recall, Use Cases drive the whole shooting match! • Update / collapse flows of events as needed • But this is difficult to do. Consider 

  8. Supplement the Use-Case Description  Sometimes the description of the use case is not sufficient for identifying analysis classes and their objects.  Remember, customer (who should be the responsible person for the use cases) doesn’t care about the inside of the system, so many details may have been left out – leaving the use case description like a black box. Many times we do not have enough detail. • The system retrieves and displays a list of current course offerings from the course catalog legacy database • given specific • parameters, such as... • The system displays a list of course offerings.

  9. Use-Case Analysis Steps • 1. Supplement the Use-Case Description • 2. For (each use-case realization), Do: •  Find Classes from Use-Case Behavior • May be easier now to identify our candidate analysis classes for the system • (candidate means ‘first cut;’ ‘possible’ classes) • Identify a set of candidate analysis classes capable of performing the behaviors (actions; ‘verbs’) described in the use case. • These are ‘responsibilities’ of these classes.

  10.  Find Candidate Classes from Behavior (1 of 2) • Will use three ‘divisions of responsibilities’ of the system to identify these classes. • Look for Classes that form: • The ‘boundary’ between the system and its actors • The ‘information’ the system uses • The ‘controllogic’ of the system • Will use ‘stereotypes’ to represent these classes. • (These are conveniences used during analysis some of which will disappear or be transitioned into different design elements during the design process when some of these classes become design or software classes..) • This approach leads to a more robust design, as these things are likely to change during design. This way we can isolate them according to their use in the application.

  11. <<boundary>> <<boundary>> <<control>> <<entity>> <<entity>> Find Classes From Use-Case Behavior • The complete behavior of a use case must be distributed to analysis classes • We must ‘identify’ these classes – give a name and briefly describe what they do in a few sentences.

  12. Kinds of Analysis Classes • The boundary between the system and its actors (interfaces… to end-users, external systems, devices…) • The information a system uses (data), and • The controllogic of the system (who does what) • So, we isolate the different kinds of concerns and use analysis classes to capture these responsibilities. • Eachcategory of analysis class has a typical set of duties & responsibilities

  13. <<boundary>> <<control>> <<entity>> What is an Analysis Class? Can use with the name of the stereotype In angle brackets or as symbols with unique icons.  Finding a candidate set of classes is the first part of transforming a mere statement of required behavior in a use case to a description of how the System will work. So, we start with Analysis Classes. Use-case behaviorcoordination System boundary System information

  14. Analysis Classes – an Early Conceptual Model • The analysis classes, taken together, represent an early conceptual model of the system. • This conceptual model evolves quickly and remains fluid for some time as different representations and their implications are explored. (Consider boundary classes that form a user interface…) • Analysis classes rarely survive into the design unchanged. (But some do!) Don’t spend a lot of time here. • Analysis classes allow us to distribute responsibilities some of which will be later reallocated. • Many analysis classes represent whole collaborations of objects

  15. Analysis Classes: A First Step Towards Executables Use Cases AnalysisClasses DesignElements Source Code Exec Use-Case Analysis (…from a structural perspective; static)

  16. <<boundary>> What is a Boundary Class? • Insulates the system from changes in the outside • Three types of Boundary Classes • 1. User interface classes – classes that facilitate communication with human users of the system • Menus, forms, windows, etc. User interface classes…. • 2. System interface classes – classes which facilitate communications with other systems. Very Important! • These boundary classes are responsible for managing the dialogue with the external system, like getting data from an existing database system or flat file… • Provide an interface to that system (like a VSAM file) • 3. Device Interface Classes – provide an interface to devices which detect external events – like a sensor or … One boundary class per use case/actor pair Analysis class stereotype

  17. <<control>> <<boundary>> <<boundary>> <<boundary>> Customer <<entity>> <<entity>> The Role of a Boundary Class • Actors can only communicate with boundary classes. • Boundary classes identify the system’s boundaries. External Database << boundary>> • Boundary class - used to model interaction between system’s surroundings • and its inner workings. • Boundary Classes model parts of the system that depend on its surroundings. • Entity and control classes model parts that are independent of system’s surroundings. • . Examples of boundary classes: Classes that handle GUI or communications protocols.

  18. Boundary Classes - more •  Identify boundary classes for actor interactions mentioned in the flow of events of the use-case •  Consider the sourcefor all external events and make sure there is a way for the system to detect these events (user inputs/responses, connecting to an external file, detecting a buzzer, detecting a thermostat value... •  Heuristic: initial identification of boundary classes: one boundary class per actor/use-case pair.

  19. Student Register for Courses Course Catalog System <<boundary>> RegisterForCoursesForm <<boundary>> CourseCatalogSystem Example: Finding Boundary Classes • One boundary class per actor/use case pair: Two boundary classes: • The RegisterForCoursesForm contains a Student's "schedule-in-progress". It interfaces • with the actor and displays a list of Course Offerings for the current semester from which • the Student may select specific courses to be added to his/her Schedule. (Note that • thisdescription comes directly from the use case specification. We capture that • behavior and encapsulate it (for now) into a boundary class with this description.) • The CourseCatalogSystem interfaces with the legacy system that provides the • unabridged catalog of all courses offered by the university.

  20. Boundary Class – As a User Interface class • 1. Concentrate: what information is presented to user • Do NOT concentrate on the UI details (windows, forms…) • Analysis Classes are meant to be a first cut at the abstraction of the system. • The boundary classes may be used as ‘holding places’ for GUI classes. (Addressed in more detail later in design) •  Do not do a GUI design in analysis, but isolate all environment-dependent behavior. (Likely you may be able to reverse engineer a GUI component and tailor it.) • If prototyping the interface has been done, these screen dumps or sketches may be associated with a boundary class. • Only model the key abstractions of the system like a form or profile…– not every button, list, etc. in the GUI.

  21. Boundary Classes – As External System and Device classes • 2-3. System and Device Interface Classes • Concentrate on whatprotocols must be defined • Note that your application must interface with an existing information source, like a RDBMS... • Do NOT concentrate on how the protocols will be implemented! Merely note that there is an interface. • If the interface to an existing systemor device is already well-defined, the boundary class responsibilities should be derived directly from the interface definition. • If there is a working communication with the external system or device, make note of it for later reference during design. (This is more than likely the case…)

  22. <<entity>> Business-Domain Model Glossary Architectural Analysis Abstractions What is an Entity Class? (recall: boundary, entity, control…) Keyabstractions of the system (What does that mean?) Analysis class stereotype Sources for entity Classes: Glossary Use-Case Flow of Events Domain Model Entity classes show the logicaldatastructure, which will help us understand what the system is supposed to offer to its users. Use Case things…… Environment Independent

  23. Entity Classes • Represent stores of information in the system • Used to represent the key concepts the system manages. (Core Abstractions) • The main responsibilities of entity classes are to store and manage information in the system. • Entity objects (instances of entity classes) hold and update information on some phenomenon, such as an event, a person, or some real-life object. • (Chapter advisor, memorabilia, university, student, correspondence_item, International_Secretary, Provider, Worker, account, inventory-item, …) • What are the ‘nouns’ in the use-case specification?? • Often persistent; may well come from domain model (business entities)

  24. <<boundary>> <<control>> <<boundary>> Customer <<boundary>> <<entity>> <<entity>> The Role of an Entity Class Entity objects can have complicated behavior; however, unlike other objects, this behavior is strongly related to the phenomenon the entity object represents. Entity objects are usually not specific to one use-case realization; The values of an entity object and their relationships are often given by an actor. Entity objects are independent of the environment (actors)

  25. Example: Finding Entity Classes • Use use-case flow of events, the domain model, and glossary as inputs. • The more of these you have the better you are! • Traditional, filteringnouns approach (but I’d recommend using classes from the domain model (business entities) as a starting place, if available) • Underline noun clauses in the use-case flow of events • Remove redundant candidates; Lots of synonyms! • Remove vague candidates • Remove actors (out of scope) • Remove implementation constructs • Remove attributes (save for later) • Lots of times, candidate ‘nouns’ may become ‘attributes’ in classes. (e.g. Student, gpa, major …) • Remove operations

  26. CourseOffering Schedule Student Example: Candidate Entity Classes • Register for Courses Use Case • Specific scenario? Likely, Create Schedule. A person enrolled in classes at the university A specific offering for a course including days of week and times The courses a student has selected for current semester Note: these are candidate (analysis) entity classes only. So far, they do not possess responsibilities, attributes, associations, etc…

  27. Candidate Entity Classes – Actors – same name? • Sometimes there’s a need to model information within the system. This is not the same as modeling the actor (actors are external. by definition) with the same name. • A course registration system maintains information about the Studentobjectwhich is independent of the fact that the Student also plays a role as an actor of the system. • Completelyindependent of each other • Studentclass (entity) will exist whether or not the student is an actor to the system.

  28. Account balance Superclass (parent) name number Withdraw() CreateStatement() Generalization Relationship Savings Checking Subclasses GetInterest() Withdraw() Withdraw() Review: Generalization (in entity classes) • One class shares the structure and/or behavior of one or more classes • “Is-a-kind of” relationship • In analysis, use sparingly • Inheritance relationships may be identified – especially in entity classes. In analysis, generalization should be used to model shared behavioral semantics only (that is, generalization that passes “is a kind of’ test) The use of generalization makes the definition of the abstractions easier to document and understand. When generalization is found, create a commonsuper-class that contains common attributes associations, aggregations, and operations

  29. Example: Generalization (Shared Semantics) Full-timeStudent Part-timeStudent name WithoutGeneralization name address address studentID studentID numberCourses gradDate Student name WithGeneralization address studentID ParttimeStudent FulltimeStudent maxNumCourses gradDate

More Related