Use Case section:

Create a Use Case Diagram in MicrosoftVisiofor the "to-be" system. The use case diagram must show the major uses of the new system. Include at least 7 use cases and at least 3 actors in your diagram. User Stories section: Create user stories for the use cases you identified above. Development Methodology section: Indicate how this system will be implemented through a methodology (Agile, Lean, Waterfall, etc.). Explain how the development methodology impacts your architectural decisions.

ASSIGNMENT BACKGROUND: You, as a software architect, are assigned to modernize a CRM (Customer Relationship Management) system for your employer. The key driver behind this system is to attain and retain customers through its relationship with them. The problems your company face are as follows: Your company produces products, but it is having trouble finding the target market for these products. Your company also has no way to market products to prospective customers. The customers your company has attracted are often unsatisfied and do not issue repeat business to the company. On a positive note, your company has workable systems in existence: Sales Order system is fine, but lead generation and marketing is non-existent Accounting Inventory Customer service call tracking Unfortunately, none of these systems talk to each other. There is no synergy within the organization integrating the systems with one another. In addition to solving these internal problems, the company wishes to address the following requirements: Simplify and ease integration with existing systems Expand the system into other areas Provide mobile access for customers and potential customers. The company will interact with customers in this way, and, more importantly, customers can interact with the company Mine its massive databases for analytical purposes Secure the system since the last data breach at the company tarnished its image and resulted in hundreds of thousands of stolen credit card numbers

What kind of information is needed?