1. On the File menu, point to New, point to Software, and then click UML Model Diagram.

2. In the tree view (tree view: Displayed in a window in the UML Navigator, a hierarchy in which each UML element or view (diagram) is represented by an icon. The UML template automatically creates a tree view of your model.), right-click the package or subsystem in which you want to include a use case diagram (use case diagram: A diagram that shows the external actors who will interact with your system and how they will use it. The diagram consists of a system boundary, actors, use cases, and use case relationships (communicates, uses, and extends).), then point to New, and then click Use Case Diagram.

A blank page appears, and the UML Use Case stencil becomes the top-most stencil. The workspace displays 'Use Case' as a watermark. An icon representing the diagram is added to the tree view.

 Note   If the tree view is not visible, on the UML menu, point to View, and then click Model Explorer.

3. Drag the System Boundary shape onto the drawing page.

System Boundary shape

ShowIndicate a system boundary in a use case diagram

1. In a use case diagram (use case diagram: A diagram that shows the external actors who will interact with your system and how they will use it. The diagram consists of a system boundary, actors, use cases, and use case relationships (communicates, uses, and extends).) , drag a System Boundary shape onto the drawing page.

2. Double-click the shape, and then type a new name for the system or press the DELETE key to delete the existing name. Click outside the shape on the drawing page.

3. To resize the system boundary, select the shape, and then drag a selection handle.

4. Drag Use Case shapes from the Use Case stencil and place them inside the system boundary, and then drag Actor shapes to the outside of the system boundary.

Use Case shape

Actor shape

5. Use Communicates shapes to indicate relationships between use cases and actors.

Communicates shape

ShowIndicate a relationship between an actor and a use case

1. In a use case diagram (use case diagram: A diagram that shows the external actors who will interact with your system and how they will use it. The diagram consists of a system boundary, actors, use cases, and use case relationships (communicates, uses, and extends).), drag a Communicates shape onto the drawing page.

2. Glue one endpoint End point image, which is plus sign in a green squareof the Communicates shape to a connection point Connection point image - blue Xon an Actor shape. Glue the other endpoint to a connection point on a Use Case shape.

3. If you want to add an arrow to indicate the flow of information, do the following:

· Double-click the Communicates shape, then, under Association, click the end you want to edit, and then click Properties.

· In the Association End category, check IsNavigable, click OK, then click OK again.

· Right-click the Communicates shape and click Shape Display Options. Under End options, select End navigability, and then click OK.

6. Use Uses and Extends shapes to indicate the relationships between use cases.

ShowIndicate a uses relationship between two use cases

1. In a use case diagram (use case diagram: A diagram that shows the external actors who will interact with your system and how they will use it. The diagram consists of a system boundary, actors, use cases, and use case relationships (communicates, uses, and extends).), drag a Uses relationship shape onto the drawing page.

2. Glue the Uses endpoint without an arrowhead to a connection point Connection point image - blue Xon the Use Case shape that uses the behavior of the other use case.

3. Glue the Uses endpoint (with an arrowhead) to a connection point on the use case being used.

4. Double-click the Uses shape to open the UML Generalization Properties dialog box. Add property values, and then click OK.

ShowIndicate an extends relationship between two use cases

5. In a use case diagram (use case diagram: A diagram that shows the external actors who will interact with your system and how they will use it. The diagram consists of a system boundary, actors, use cases, and use case relationships (communicates, uses, and extends).), drag an Extends shape onto the drawing page.

6. Glue the Extends endpoint End point image, which is plus sign in a green squarewithout an arrowhead to a connection point Connection point image - blue Xon the use case providing the extension.

7. Glue the Extends endpoint with an arrowhead to a connection point on the base use case.

8. Double-click the Extends shape to open the UML Generalization Properties dialog box. Add the property values, and then click OK.

7. Double-click any shape (except the System Boundary shape) to open its UML Properties dialog box where you can add a name, attributes, operations, and other property values.

8. Save the diagram.

Use case diagram example

Show AllShow All

Hide AllHide All

"Use case diagram defining the system boundary, and how the actors outside it affect the use cases it contains"

Callout 1Defining the system boundary (system boundary: In a use case diagram, a boundary surrounding the use cases that indicates the system. You can resize the system boundary by dragging a selection handle on the System Boundary shape.) determines what is considered external or internal to the system.

Callout 2An actor (actor: In a use-case diagram, a representation of a role played by an outside object. One physical object, therefore, may be represented by several actors. A communicates relationship indicates how an actor participates in a use case.) represents a role played by an outside object. One object may play several roles and, therefore, is represented by several actors.

Callout 3A communicates relationship (communicates relationship: In a use case diagram, a relationship that defines how an actor participates in a use case. You can add an arrow to the relationship to indicate the direction the information flows.) illustrates the participation of the actor in the use case.

Callout 4A use case (use case: In a use case diagram, a representation of a set of events that occurs when an actor uses a system to complete a process. Normally, a use case is a relatively large process, not an individual step or transaction.) is a set of events that occurs when an actor uses a system to complete a process. Normally, a use case is a relatively large process, not an individual step or transaction.

 

1.2.1 Profile Competitor Strategies and Predicted Moves (20 Points)

Company

Strategic Intent

Market Share Objective

Competitive Position / Situation

Strategic Posture

Competitive Strategy

Andrews

Strongly committed to low-end segment and significant market capture.

Market share leader.

High capacity, excellent alignment with strategy.

Successful execution through addition of capacity.

Focused Low-Cost

1.2.2 Predict Competitor’s Next Moves (20 Points)

· Andrews will continue its aggressive pursuit of the _______ and may begin a price war with other competitors, namely ____ and _____ in the ______ market. The company will continue to ________ production, particularly in ____ segment. It is possible that they will also introduce a new product based on ______. Andrews is likely to re-evaluate forecasting methods as it had excess inventory last year.

System

University Registration System

Student

Use Case

Bursar's Office

Registration Clerk

Instructor

Class Registration

Registration for Special Class

Prereq courses not completed

Student Billing

«extends»

«extends»

-End1

*

-End2

*

-End3

*

-End4

*

-End5

*

-End6

*

-End7

*

-End8

*

-End9

*

-End10

*

Get help from top-rated tutors in any subject.

Efficiently complete your homework and academic assignments by getting help from the experts at homeworkarchive.com