CSS/422 Software Architecture

    

CSS/422 USE CASE DIAGRAM CSS422 WEEK 1
CSS/422 USE CASE DIAGRAM CSS422 WEEK 1
CSS/422 Select an internet-accessible website in which you, as an end user, can perform multiple functions.
CSS/422 Select an internet-accessible website in which you, as an end user, can perform multiple functions.

CSS/422 Week 1

Everything listed for Week 1 is Included in Purchase!!

 

ADD: Overview and Stakeholder Identification

Includes Option #1

Includes Option #2

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.
Create the following sections of the Architecture Design Document (ADD) in a 3- to 4-page Microsoft Word document, using the Customer Relationship Management (CRM) system described in the Assignment Background document:
• Overview section:
      • Create an overview of the existing CRM system.
      • State the issues.
      • Identify the goals to modernize the existing system.

• Stakeholder identifications section:
      • Create a table including at least 6 stakeholders of the system (including internal and

   external users).
      • Summarize each, including why they are stakeholders.
      • For those users with functional use of the CRM, list one or more uses that they would

          have for the system. This need not be an exhaustive list, but you are looking for the

          core features of the CRM to be included.
Incorporate the two sections into a single document in Microsoft Word.
As this document is intended for a technical team, APA formatting is not required.
Submit your assignment.

 

 

 


CSS/422 CRM OVERVIEW, STAKEHOLDERS, DEVELOPMENT METHODOLOGY
CSS/422 SYSTEM REFERENCE GUIDE
CSS/422 SYSTEM REFERENCE GUIDE

CSS/422 Week 2

Everything listed for Week 2 is Included in Purchase!!

 

ADD: Use Case, User Stories, and Development Methodology
Includes Option #1 with MS Visio Diagram (Fully editable)

Includes Option #2 with (3) MS Visio Diagrams (Fully editable)
As you continue to develop your ADD in your role as a software architect, use the CRM system described in the Assignment Background document to create the following additional sections in a 3- to 4-page Microsoft Word document:
Use Case section:
      • Create a Use Case Diagram in Microsoft Visio for 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.
Incorporate the three sections into a single document in Microsoft Word separate from the document created in Week 1. As this document is intended for a technical team, APA formatting is not required.
Submit your assignment.

 

CSS/422 USE CASES, USER STORIES, COMPONENTS, AND CONNECTORS
CSS/422 SYSTEM REFERENCE GUIDE
CSS/422 USE CASES, USER STORIES, COMPONENTS, AND CONNECTORS

CSS/422 Week 3

Everything listed for Week 3 is Included in Purchase!!

 

ADD: Architectural Design, Architectural Patterns, Control Flow
Diagram
Includes Option #1

Includes Option #2

Includes 3 Control Diagrams - MS Visio (Fully editable) A+ Work!
As you continue to develop your ADD in your role as a software architect, use the CRM system described in the Assignment Background 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 document in Microsoft Word separate from the documents created in Weeks 1 and 2. As this document is intended for a technical team, APA formatting is not required.
Submit your assignment.

 

CSS/422 FUNCTIONAL REQUIREMENTS AND DESIGN DECISIONS
CSS/422 SYSTEM REFERENCE GUIDE QUALITY ATTRIBUTES
LDR/300 Your company's Vice President of Human Resources has approached your team for assistance in recruiting and developing your organization's future leaders.

CSS/422 Week 4

Everything listed for Week 4 is Included in Purchase!!

 

ADD: Quality Attributes and Views

Includes Option #1 with 3 MS Visio Diagrams (Fully Editable)

Includes Option #2 with 4 MS Visio Diagrams (Fully Editable)

As you continue to develop your ADD in your role as a software architect, use the CRM system described in the Assignment Background document, along with any additional research, to create the following additional sections in a 4- to 5-page Microsoft Word
document:
• Quality Attribute section:
      • Create a quality attribute tradeoff matrix to balance quality attributes for this

          system.
      • Describe the reasons of the trade-off in the paragraph after the matrix.
Views section:
      • Create a physical view of the system in Microsoft Visio.
      • Create a logical model view of the system in Microsoft Visio.
      • Create a process view of the system in Microsoft Visio.
Note: Refer to the diagrams presented in the Pluralsight videos and textbook readings from this and previous weeks as a guide for creating these artifacts.
Incorporate the two sections into a single document in Microsoft Word separate from the documents created in Weeks 1 through 3. As this document is intended for a technical team, APA formatting is not required.
Submit your assignment.

 

CSS/422 WEEK 5 SYSTEM MODELING
CSS/422 PUBLIC CLOUD PRESENTATION
CSS/422 WEEK 5 As a team, finalize the Architectural Design Document (ADD) by creating system modeling diagrams.
COMING SOON!

CSS/422 Week 5

Everything listed for Week 5 is Included in Purchase!!

 

Architecture Design Document

As you finalize your ADD in your role as a software architect, use the CRM system described in the Assignment Background document to complete the two tasks below:
TASK 1:
Create the following, additional sections in a 2- to 3-page Microsoft Word document:
• Technology section:
      • Identify the technologies used in the architecture.
      • Provide reasons for using the technologies. For example, Oracle SOA solution is

          chosen for the SOA architecture but also because the company has a license for

          the product.
• Cloud Migration section - Your company is considering a move to Microsoft Azure or

Amazon Web Services to host the CRM:
      • Identify the pros and cons of migrating to the cloud comparing hosting solution.
      • Present the result slide/picture/diagram with bullet items.

TASK 2:
Combine all sections from Weeks 1 through 5 into a single, 12- to 16- page Microsoft Word document. Address all previous feedback before submitting the final Architecture Design Document (ADD). As this document is intended for a technical team, APA formatting is not required.
Submit your assignment.