The UML Provides Standardized Diagrams State State State State Use-Case Use-Case Use-Case Use-Case Activity Diagrams Activity Diagrams Diagrams Diagrams Diagrams Diagrams Class Diagrams Class Diagrams Diagrams Diagrams Diagrams Diagrams Use-Case Use-Case Use-Case Use-Case Use-Case Diagrams Use-Case Diagrams Diagrams Diagrams Diagrams Diagrams Scenario Scenario Scenario Scenario Sequence Diagrams Sequence Diagrams Diagrams Diagrams Diagrams Diagrams Scenario Scenario Scenario Scenario Collaboration Diagrams Collaboration Diagrams Diagrams Diagrams Diagrams Diagrams Models Deployment Deployment Diagrams Diagrams State State State State Object Diagrams Object Diagrams Diagrams Diagrams Diagrams Diagrams State State State State State Diagrams State Diagrams Diagrams Diagrams Diagrams Diagrams Component Component Component Diagrams Component Component Diagrams Component Diagrams Diagrams Diagrams Diagrams • In building visual models, many different diagrams are needed to represent different views of the system. (different views to different stakeholders). • Use Case Diagrams (ahead) – illustrate user interactions with the application. • Activity Diagrams illustrate the flow of events in a Use Case (all scenarios). • Class diagrams represent logical structure, while Interaction Diagrams illustrate behavior (show how objects collaborate via message passing to provide features (responsibilities) of the objects.. • Other diagrams are used to illustrate other viewpoints necessary in some (but not all) circumstances, such as the State Diagrams, Deployment diagrams, … Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 6
View full slide show




The UML Provides Standardized Diagrams (Views) Use-Case Use-Case Use-Case Use-Case Activity Diagrams Activity Diagrams Diagrams Diagrams Diagrams Diagrams State State State State Class Diagrams Class Diagrams Diagrams Diagrams Diagrams Diagrams Use-Case Use-Case Use-Case Use-Case Use-Case Diagrams Use-Case Diagrams Diagrams Diagrams Diagrams Diagrams Scenario Scenario Scenario Scenario Sequence Diagrams Sequence Diagrams Diagrams Diagrams Diagrams Diagrams Models Scenario Scenario Scenario Scenario Collaboration Diagrams Collaboration Diagrams Diagrams Diagrams Diagrams Diagrams Deployment Deployment Diagrams Diagrams State State State State Object Diagrams Object Diagrams Diagrams Diagrams Diagrams Diagrams State State State State State Diagrams State Diagrams Diagrams Diagrams Diagrams Diagrams Component Component Component Component Diagrams Component Diagrams Component Diagrams Diagrams Diagrams Diagrams • In building visual models, many different diagrams are needed to represent different views of the system. (different views to different stakeholders). • Use Case Diagrams (ahead) – illustrate user interactions with the application. • Activity Diagrams illustrate the flow of events in a Use Case (all scenarios). • Class diagrams represent logical structure, while • Interaction Diagrams illustrate behavior (show how objects collaborate via message passing to provide features (responsibilities) of the objects.. • Other diagrams are used to illustrate other viewpoints; e.g. State Diagrams, Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 19 6
View full slide show




The UML Provides Standardized Diagrams (Views) Use-Case Use-Case Use-Case Use-Case Activity Diagrams Activity Diagrams Diagrams Diagrams Diagrams Diagrams State State State State Class Diagrams Class Diagrams Diagrams Diagrams Diagrams Diagrams Use-Case Use-Case Use-Case Use-Case Use-Case Diagrams Use-Case Diagrams Diagrams Diagrams Diagrams Diagrams Scenario Scenario Scenario Scenario Sequence Diagrams Sequence Diagrams Diagrams Diagrams Diagrams Diagrams Models Scenario Scenario Scenario Scenario Collaboration Diagrams Collaboration Diagrams Diagrams Diagrams Diagrams Diagrams Deployment Deployment Diagrams Diagrams State State State State Object Diagrams Object Diagrams Diagrams Diagrams Diagrams Diagrams State State State State State Diagrams State Diagrams Diagrams Diagrams Diagrams Diagrams Component Component Component Component Diagrams Component Diagrams Component Diagrams Diagrams Diagrams Diagrams • In building visual models, many different diagrams are needed to represent different views of the system. (different views to different stakeholders). • Use Case Diagrams (ahead) – illustrate user interactions with the application. • Activity Diagrams illustrate the flow of events in a Use Case (all scenarios). • Class diagrams represent logical (static) structure • Interaction Diagrams illustrate behavior (show how objects collaborate via message passing to provide features (responsibilities) of the objects.. Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 19 4
View full slide show




Diagrams Are Views of a Model A model is a complete description of a system from a particular perspective In the Unified Process, We use UML to provide nine different diagrams and five (4+1) major views: Use Case View, Logical View, Process View, Implementation View, and Deployment View Explain: Activity Activity Diagrams Diagrams Scenario Scenario Scenario Scenario Diagrams Sequence Diagrams Sequence Diagrams Diagrams Diagrams Diagrams Scenario Scenario Scenario Scenario Diagrams Collaboration Diagrams Collaboration Diagrams Diagrams Diagrams Diagrams 19 Use-Case Use-Case Diagrams Diagrams State State State State Diagrams Class Diagrams Class Diagrams Diagrams Diagrams Diagrams Models Deployment Deployment Diagrams Diagrams Models are more inclusive than Views. State State State State Diagrams Object Diagrams Object Diagrams Diagrams Diagrams Diagrams State State State State Diagrams State Diagrams State Diagrams Diagrams Diagrams Diagrams Component Component Component Diagrams Component Component Diagrams Diagrams Component Diagrams Diagrams Diagrams Know these!!!!! 15
View full slide show




Diagrams Are Views of a Model A model is a complete description of a system from a particular perspective We use UML to provide nine different diagrams and five (4+1) major views: Use Case View, Logical View, Process View, Implementation View, and Deployment View Explain: Activity Activity Diagrams Diagrams Scenario Scenario Scenario Scenario Diagrams Sequence Diagrams Sequence Diagrams Diagrams Diagrams Diagrams Scenario Scenario Scenario Scenario Diagrams Collaboration Diagrams Collaboration Diagrams Diagrams Diagrams Diagrams Unified Software Practices v 5.0 - D Copyright  1998 Rational Software, all rights reserved State State State State Diagrams Class Diagrams Class Diagrams Diagrams Diagrams Diagrams use-case use-case Diagrams Diagrams State State State State Diagrams Object Diagrams Object Diagrams Diagrams Diagrams Diagrams State State State State Diagrams State Diagrams State Diagrams Diagrams Diagrams Diagrams Models Deployment Deployment Diagrams Diagrams 17 Component Component Component Diagrams Component Component Diagrams Diagrams Component Diagrams Diagrams Diagrams Know these!!!!!
View full slide show




Models and Essential Diagrams model is a complete scription of a system om a particular rspective Use Case Use Case Diagrams Sequence Diagrams Diagrams Scenario Scenario Diagrams Collaboration Diagrams Diagrams Scenario Scenario Diagrams Statechart Diagrams Diagrams UML Overview Use Case Use Case Diagrams Use Case Diagrams Diagrams State State Diagrams Class Diagrams Diagrams Models Activity Diagrams State State Diagrams Object Diagrams Diagrams State State Diagrams Component Diagrams Diagrams Component Component Diagrams Deployment Diagrams Diagrams See Scotch Ambler’s page for a complete list of UML 2 diagrams” http://www.agilemodeling.com/essays/umlDiagrams.htm
View full slide show




Operating Modes C Examples  C – programming msp430x14x.h /************************ * STATUS REGISTER BITS ************************/ #define #define #define #define #define #define #define #define #define C Z N V GIE CPUOFF OSCOFF SCG0 SCG1 0x0001 0x0002 0x0004 0x0100 0x0008 0x0010 0x0020 0x0040 0x0080 /* Low Power Modes coded with Bits 4-7 in SR */ /* Begin #defines for assembler */ #ifndef __IAR_SYSTEMS_ICC #define LPM0 CPUOFF #define LPM1 SCG0+CPUOFF #define LPM2 SCG1+CPUOFF #define LPM3 SCG1+SCG0+CPUOFF #define LPM4 SCG1+SCG0+OSCOFF+CPUOFF /* End #defines for assembler */ #else /* Begin #defines for C */ #define LPM0_bits CPUOFF #define LPM1_bits SCG0+CPUOFF #define LPM2_bits SCG1+CPUOFF #define LPM3_bits SCG1+SCG0+CPUOFF #define LPM4_bits SCG1+SCG0+OSCOFF+CPUOFF  … #include "In430.h“ #define LPM0 _BIS_SR(LPM0_bits) #define LPM0_EXIT _BIC_SR(LPM0_bits) #define LPM1 _BIS_SR(LPM1_bits) #define LPM1_EXIT _BIC_SR(LPM1_bits) #define LPM2 _BIS_SR(LPM2_bits) #define LPM2_EXIT _BIC_SR(LPM2_bits) #define LPM3 _BIS_SR(LPM3_bits) #define LPM3_EXIT _BIC_SR(LPM3_bits) #define LPM4 _BIS_SR(LPM4_bits) #define LPM4_EXIT _BIC_SR(LPM4_bits) #endif /* End #defines for C */ /* /* /* /* /* /* /* /* /* /* Enter LP Mode 0 */ Exit LP Mode 0 */ Enter LP Mode 1 */ Exit LP Mode 1 */ Enter LP Mode 2 */ Exit LP Mode 2 */ Enter LP Mode 3 */ Exit LP Mode 3 */ Enter LP Mode 4 */ Exit LP Mode 4 */ /* - in430.h Intrinsic functions for the MSP430 */ unsigned short _BIS_SR(unsigned short); unsigned short _BIC_SR(unsigned short); CPE 323 23
View full slide show




    Guidance on Façade Iteration Develop an Overall Use Case Model (all application Use 1. Cases and Actors). (System Level Graphical Use-Case Model) 2. Develop Façade Use Case Descriptions and associated Use Case Diagrams for each Use Case cited in the System Level Use-Case Model. Use template in notes. Develop Façade Use Cases using the Kulak and Guiney book. Again, see power point lectures for required attributes. See examples of ‘reasonable’ student Use Cases examples posted. Use Rose (Use Case View) for your System Level use-case model and all of your individual use-case diagrams (one per use-case). Link the Use Case Specification text (that is, the use-cases) into Rose and ensure these descriptions are on the CD you turn in for grading. (More to be discussed: You may need to use Requisite Pro. Additional information: Visual Modeling book and Rose Basics (see power point lecture slides for examples on including your Use Cases in your Rose Model in the Use Case View.)
View full slide show




  EVALUATION RUBRIC DEVELOPED Below Expectations (1-2 Pts) Meets Expectations (3-4 Pts) Exceeds Expectations (5-6 Pts) POINTS Aspects of background or relevant external environment variables not discussed. Research is not thorough or is missing completely. Identified target market(s) do not follow clearly from any research presented. Provides analysis of all relevant background including competition and external environment. Some research undertaken to support analysis. Target market(s) identified. Could be clearer how research led to target market. Background is comprehensively examined and assessed. Competition, external environment, and any other relevant issues thoroughly researched and discussed. Research clearly supports target market(s) choice.   Objectives Communication objectives do not flow clearly from situation analysis. One or more objective may be difficult to measure, vague, and/or not clearly distinct from Marketing objectives. Complete communication objectives presented and follow reasonably well from situation analysis. Comm objectives are generally measurable and are distinguished from Marketing objectives. Communication objectives are clearly stated and flow fully and naturally from results of situation analysis. Objectives are specific, distinct from Marketing objectives, and measurable.   Message Strategy Basis of positioning is either missing or not presented clearly. If positioning is discussed, not clear what the connection between it and message strategy are. Message strategy is presented and positioning discussed but relationship between positioning platform and message strategy may not be totally clear. Message strategy is clearly presented and positions the product effectively. Positioning platform well-thought through and relationship between positioning and message are clear.   Media Strategy Important elements of media strategy may be missing. No clear connection between media & message strategies. Media strategy is presented and explained. Media strategy is reasonably consistent with message strategy. Media strategy is clearly presented. Media strategy supports and enhances message.   Other Plan Elements IMC plan omits one or more additional element that would contribute effectively. Appropriate public relations, direct marketing, Internet, sales promotion or support media are missing. IMC plan includes some additional elements that are appropriate. May include public relations, direct marketing, Internet, sales promotion or support media. IMC plan includes all additional elements that are appropriate (public relations, direct marketing, Internet, sales promotion, support media). Additional elements are clearly blended into positioning/message strategy.   Integration Lack of consistent message across two or more elements causes understanding of IMC to be questioned. Elements of IMC plan illustrate reasonable consistency and demonstrate understanding of the concept of IMC. The concept of IMC is clearly promoted and demonstrated through the consistent message woven throughout plan elements.   Budget Budget fails to clearly account for all plan items, does not support objectives, or is missing altogether. Full budget is presented and appears to support the plan’s objectives. All plan items accounted for in budget. Budget carefully and fully details each plan element. Supports stated objectives and is reasonable given any existing constraints.   Effectiveness Plan for measuring effectiveness of IMC plan is weak. Method choice questionable or plan is missing altogether. Plan for measuring effectiveness is presented. Choice of methods is reasonable. Measurement of all elements of IMC plan is clearly accounted for. Measurement methods are chosen/designed to produce clear results.   Situation Analysis
View full slide show




Deliverable #4 Full Use Cases Model & Activity Diagrams due: 11/14 (Wednesday) – Start of Class   Management Folder: Executive Summary, Team and Individual Logs, Team Num File, SQA Report as usual, and the Statement of Work (SOW) Artifacts Folder:      1. Focused Use Case Descriptions and associated Use Case Diagrams for each Use Case. Use Rose (Use Case View) and Requisite Pro* Use Kulak and Guiney book (Use Cases); Visual Modeling book and Rose Basics (power point slides for examples.) *CEN 6016 Students only 2. Activity Diagrams: Each Use Case is to be accompanied by an Activity Diagram that indicates flow for all paths in the Use Case 3. Traceability Matrices (forward and backward) features  Use Cases  Revisit Deliverable 3 Folder. Document artifacts changed. Include (name) any changes to Deliverable 3 artifacts in Deliverable 4 Executive Summary. Then, of course, include these changes in Deliverable3Revisited folder.  Your Use Case Diagrams for individual use-cases) will likely be supplemented with Included or Extended Use Cases, as appropriate. Redo your Use Case Model (Overall) for the Application. This is the System Use Case Model. Be certain also to view the new sample SOW link on my web page. This is a good template and contains guidance on the individual logs as well. (Individual logs may be included in a single folder in the Management Folder, if desired). 
View full slide show




Flow-tools Contains • • • • • • • • • • • flow-capture flow-cat flow-dscan flow-expire flow-export flow-fanout flow-filter flow-gen flow-header flow-import flow-mask • • • • • • • • • • flow-merge flow-nfilter flow-print flow-receive flow-report flow-send flow-split flow-stat flow-tag flow-xlate 18
View full slide show




Use Cases  Steps  Extract actors and use cases    Draw use case diagram     Add more relationships, secondary uses cases, secondary actors Complete Refine use cases    Main scenarios Refine use case diagram   Main uses cases and actors Don’t worry about completeness … will refine later on Describe every use case   Nouns that perform actions or respond to actions are actors Verbs or action nouns (registration, enrollment, etc …) are usually use cases Alternative scenarios Complete Iterative development process
View full slide show




Objectives  Define the elements of the use case model. – – – –  Use cases Actors Relationships Use case diagrams Add diagrams to the Use Case View. – – Link documentation Link flow of events
View full slide show




Deliverable #3: New Artifacts  2. Develop Façade Use Case Specification.  Develop an overall Use Case Diagram (all application Use Cases and Actors). Similar to Business Use Case Model but icons are a little different.     This is sometimes called the system level use case model. This should be a single page of actors and use cases. Examples of all these can be found in Use Case book and Visual Modeling book. Develop Façade Use Case Specifications and associated Use Case Diagrams for each Use Case. (See examples)   Use Requisite Pro and Rational Rose (Use Case View) for your models. Link the Use Case Specifications captured in Requisite Pro and onto Rational Rose. Use the Façade Use Cases templates from the Kulak and Guiney book. Again, see power point lectures for required attributes. (See examples of ‘reasonable’ student Use Cases posted on my web page.)
View full slide show




Use Cases      A use case is a flow of events in the system, including interaction with actors It is initiated by an actor Each use case has a name Each use case has a termination condition Graphical Notation: An oval with the name of the use case ReportEmergency Name of Use Case Actors: Description of Actors involved in use case) Entry condition: “This use case starts when…” Flow of Events: Free form, informal natural language Exit condition: “This use cases terminates when…” Exceptions: Describe what happens if things go wrong Special Requirements: NFR, Constraints Use Case Model: The set of all use cases specifying the complete functionality of the system Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 37
View full slide show




What is an Activity? (concluded) • • • Activity Diagrams are used to describe activities – Activity Diagrams are useful for describing complicated methods – Activity Diagrams are useful for describing use cases, since, after all, a use case is an interaction, which is a form of activity Using Activity Diagrams with Use Cases – Start with a coarse-grained use case, which is composed of subordinate use cases – For the complicated subordinate use cases, use Activity Diagrams rather than Use Case Diagrams Activity Diagrams are like Flow Charts, but Flow Charts are usually limited to sequential activities while Activity Diagrams can show parallel activities as well 5
View full slide show