Assignment 2: Creating A Use Case - Week 4 And Worth 150 Poi

Assignment 2 Creating A Use Casedue Week 4 And Worth 150 Points

Refer to the RMO CSMS marketing subsystem shown in Figure 3-11 on pages 79-80 of your textbook. Write a two to three (2-3) page paper in which you: Using Microsoft Visio or an open source alternative such as Dia, create a use case graphic rendering that shows all actors and all use cases for the RMO CSMS marketing subsystem. Provide a narrative describing your diagram that includes: an overview of the diagram and an analysis of the actors. Use at least three (3) quality resources outside of the suggested resources in this assignment. Note: Wikipedia and similar websites do not qualify as quality resources.

Your assignment must follow these formatting requirements: be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions. Include a cover page containing the title of the assignment, your name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required page length. Include charts or diagrams created in Visio or an open source alternative such as Dia. The completed diagrams/charts must be imported into the Word document before the paper is submitted.

Paper For Above instruction

The purpose of this assignment is to develop a comprehensive understanding of system stakeholders, functional requirements, and the application of use case modeling in systems analysis and design. Specifically, it entails creating a visual representation of the RMO CSMS marketing subsystem's use cases and actors, accompanied by a detailed narrative analysis.

To start, an accurate use case diagram must be produced using tools like Microsoft Visio or Dia. This diagram should encompass all relevant actors—entities that interact with the system—and all use cases, depicting their relationships and interactions. The actors involved typically include internal users, such as marketing staff, and external entities like clients or partners. For the RMO CSMS marketing subsystem, key actors might include the Marketing Manager, Sales Representatives, Customers, and System Administrators.

The diagram should clearly illustrate the use cases associated with each actor. Examples of such use cases could involve creating marketing campaigns, generating sales reports, managing customer data, and updating system information. By visually mapping these interactions, one gains a clearer understanding of the system’s functional scope and stakeholder engagement.

Following the diagram, a comprehensive narrative is required. This narrative should begin with an overview of the diagram, explaining the overall structure, the purpose it serves, and how the actors and use cases interrelate. This overview helps contextualize the system's operational landscape. Next, the analysis of actors should delve into their roles, responsibilities, and the significance of their interactions with the system. For instance, the Marketing Manager may oversee campaign strategies and approval processes, while Customers may access the system to review marketing materials or provide feedback.

An in-depth discussion of the use cases should also be included, emphasizing their relevance to the system’s objectives and how they facilitate business processes. For example, the process of creating a marketing campaign involves multiple steps and interactions that enhance the company’s outreach capabilities. This analysis not only highlights system functionalities but also illustrates stakeholder needs and system design considerations.

To enrich the analysis, at least three credible external resources should be incorporated. These might include scholarly articles on use case analysis, industry standards for systems modeling, or case studies demonstrating successful implementation of similar subsystems. The references should be properly cited according to APA formatting standards.

In conclusion, this assignment synthesizes the technical process of creating a use case diagram with the analytical task of understanding stakeholder roles and system functionalities. The resulting diagram and narrative should offer a comprehensive perspective on the RMO CSMS marketing subsystem’s operations, aligned with principles of systems analysis and design.

References

• Cockburn, A. (2000). Writing effective use cases. Addison-Wesley Professional.
• Fowler, M. (2004). UML distilled: A brief guide to the standard object modeling language (3rd ed.). Addison-Wesley Professional.
• Jacobson, I., Douglass, M., Rumbaugh, J., & Booch, G. (1999). The unified software development process. Addison-Wesley.
• Larman, C. (2004). Applying UML and patterns: An introduction to object-oriented analysis and design and iterative development (3rd ed.). Pearson Education.
• ”Use case modeling techniques,” IEEE Software, vol. 23, no. 2, pp. 66-67, 2006.
• Pressman, R. S. (2014). Software engineering: A practitioner's approach (8th ed.). McGraw-Hill Education.
• Jacobson, I., Christerson, M., Jonsson, P., & Övergaard, G. (1992). Object-oriented software engineering: A use case driven approach. Addison-Wesley.
• Booch, G., Rumbaugh, J., & Jacobson, I. (2005). The UML user guide (2nd ed.). Addison-Wesley.
• Hetzel, W. C. (2007). I. Software requirements and specifications. IEEE Software, 24(3), 42-49.
• Sommerville, I. (2010). Software engineering (9th ed.). Pearson Education.