As you continue to develop your ADD in your role as a software architect, use the CRM system described in the
document, along with any additional research, to create the following additional sections in a 3- to 5-page Microsoft® Word document:
- Architectural Design Decisions section:
- Identify the drivers and constraints for the architectural designs.
- Architectural Patterns section:
- Identify the architectural pattern(s) used in the “to-be” architecture.
- Control Flow Diagram section:
- Create the Control Flow Diagram in Microsoft® Visio® for 3 of the use cases identified in Week 2.
Incorporate the three sections into a single Microsoft® Word document separate from the documents created in Weeks 1 and 2. As this document is intended for a technical team, APA formatting is not required.
23 Version X
CSS/422 Version 11
Throughout this course, you will leverage concepts learned in class along with previous program material to 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
· 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 Architectural Design 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 Design Decisions (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.
Copyright © XXXX by University of Phoenix. All rights reserved.
Copyright © 2018 by University of Phoenix. All rights reserved.