CIS 510: Advance System Analysis

910 Words4 Pages
Week 4: Assignment 2: Creating a Use Case By Christie Greene CIS 510: Advance Systems Analysis and Design Instructor: Dr. Richard Brown July-29-2014 Assignment 2: Creating a Use Case Abstract Requirements modeling process begins with the concept of use cases. This is an activity performed by a system usually in response to a request by a user. Two techniques recommended for identifying use cases are known as the user goal technique and the event decomposition technique. On a daily basis, we are all actors in various use case diagrams as we go about completing our daily tasks and objectives in our homes and offices to name a few. The analyst focuses on one type of user at a time so…show more content…
Use case diagram is good at grasping the whole of system requirements. A Use case diagram consists of the following elements. 1. Actor (stick man) Use case (oval) 2. System boundary (rectangle surrounding use cases) 3. Association (line between use case and actor) A standard use case diagram is used to analyze requirements of a new system at the beginning of the system analysis. A standard use case diagram is very easy to describe, since its notation is simple (Kawabata, Kasahara and Itoh et al., 2007). The diagram in this research is for RMO CSMS marketing subsystem. In this use case diagram there are two actors, merchandising and marketing. A user goal technique was used by RMO to identify the four use cases inside the automation boundary. There are no external events because no event occurs outside the system since there is no external agent. Also, there is no > relationship in this use case diagram since no one use case is stereotypically included within the other use case. Further inspection of the diagram shows that a state event will occur when the Merchandising actor tries to add/update accessory package and there are missing accessory to complete the…show more content…
Taking a closer look at what elements constitute a use case diagram, the links between an actor and a use case are called associations. In table 1.1 the writer identifies two actors for the RMO CSMS marketing subsystem, merchandising and marketing. The various roles these actors represent are the actual business roles of users in a given system. To manage the subsystem, the actor (merchandising) needs to have the ability to add/update production information and add/update accessory package. The actor (marketing) needs to have the ability to also add/update production, add/update promotion and add/update business partner link. Table 1.1 illustrates the use case and user/actors for the CSMS marketing subsystems. [pic] Table 1.1 In most systems, the collaboration task is where two or more actors work exchanging and sharing resources is observed. In order to analyze the actors’ efficiency, it is effective to analyze the system from the viewpoints of the collaboration

More about CIS 510: Advance System Analysis

Open Document