create architectural artifacts for a Customer Relationship Management (CRM) system

create architectural artifacts for a Customer Relationship Management (CRM) system. The background for this assignment is as follows:
Resources: Materials presented throughout the course, course text, Microsoft® Visio®.
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
By the end of the course, you will produce an architectural design document for this development project. The ArchitecturalDesign Document (ADD) includes the following sections:
• Overview (Week 1)
• Stakeholder Identification (Week 1)
• Use Cases (Week 2)
• User Stories (Week 2)
• Development Methodology (Week 2)
• Architectural DesignDecisions (Week 3)
• Architectural Patterns ( Week 3)
• Control Flow Diagram (Week 3)
• Quality Attributes (Week 4)
• Views (Week 4)
• Technology (Week 5)
• Cloud Migration (Week 5)
Begin thinking about the situation and the end product. In-depth knowledge of a CRM is not required for this assignment. You may wish to preview the deliverables for the upcoming weeks to ensure you understand the artifacts your team will produce.

Click Here For More Details on How to Work on this Paper......
Need a Professional Writer to Work on this Paper? Click Here and Get this Essay Done ………