Petrie Electronics implemented its Customer Relationship Management (CRM) system, No Customer Escapes last week. But like any system, the Change Management team receives a request for a change to the system. The Project Manager reviews the change request, and realizes an alternative development method is needed to analyze and design the changes to the system. An object oriented method must be selected, but it seems Use Cases were not created when the system was first developed. The Project Manager knows the benefits of Use Cases and assigns our team to create one using Unified Modeling Language (UML) notation.
- In Week 7, we learned some alternative system development life cycle (SDLC) methods, object-oriented analysis and design, and agile methods.
- eIn order to implement our CRM system, we will need to create a Use-Case Diagram illustrating the four processes the CRM system identified in our book.
- Create a use case for the CRM system. Visio is suggested, but you can use any Microsoft 2013 application. In order to use Visio 2013, select software on the template page and then click UML use case. Then click create. You will be able to complete the use case diagram.
- You will need to include the four processes of record customer activities, send promotions, generate point redemption coupons, and generate customer reports processes.
- You will need to include all four actors.
- The customer is a source and a sink and should be shown as one actor on our use case.
- The three data stores will be the other actors.
- Customer activity records
- Marketing database
- Product database
The text for this course is: Essential of Systems Analysis and Design, 6th Edition