Or you may Purchase Tutorials by the Week below.    

CSS/422 Week 1

Everything listed for Week 1 is Included in Purchase!!

ADD: Overview and Stakeholder Identification

Includes Option #1

Includes Option #2

Includes Option #3

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.

Discussion Question: Role of IT

3 Answers Included

Discuss the role of a software architect in shaping and delivering business goals. What is the relationship among software, applications, technology, and solutions architecture, and how are they important to those working in the realm of systems development to meet business goals? 

Discussion Question: System Complexity

3 Answers Included

Discuss examples of inherent difficulties in software intensive systems and include an explanation of the job or role who needs this information. How does accessing requirements in architectural design decisions influence management of the system complexity?

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)

Includes Option #3 with Microsoft Word document
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.

Discussion Question:  Impact of Architects and Architecture in Project Life Cycle

3 Answer options Included

Discuss the role and impact of architects and architecture in the project life cycle. How can architectural viewpoints be developed through the use of diagramming tools? 

Discussion Question:  Agile and Traditional Development Methodologies

3 Answer options Included

Based on this week's readings, discuss component-based, distributed, and SOA-based architecture. How are they similar? How do they differ?

CSS/422 Week 3

Everything listed for Week 3 is Included in Purchase!!

ADD: Architectural Design, Architectural Patterns, Control Flow Diagram
Includes Option #1 with 3 Control Flow Diagrams in MS Visio (Fully Editable!)

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.

Discussion Question:  System Components and Architectural Design

3 Long Answer options Included

Discuss architectural design based on architectural decisions.

Share the components of a well-known system that would be familiar to your classmates. How do the components communicate (connect) to one another?

Discussion Question:  Architectural Design

3 Long Answer options Included

Research different architectural frameworks as applied to the architectural design decision process. Discuss the architectural design decision process. How do architectural frameworks differ in the design decision process? 

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.

Discussion Question: Quality Attributes

3 Answer options Included

Discuss how quality attributes affect software architecture. How can you model design decisions for quality attributes through UML?

Discussion Question: Data Model

3 Answer options Included

Discuss tools and techniques that architects use to create a data model, which is the abstract model that organizes the data elements. You may wish to consider XML models, ER diagrams, data flow diagrams, etc. 

CSS/422 Week 5

Everything listed for Week 5 is Included in Purchase!!

Individual: Architecture Design Document

Includes Option #1 with MS Visio Diagram (Fully Editable)

Includes Option #2

Refer to the following Individual Assignments:

• Week 1 - ADD: Overview and Stakeholder Identification
• Week 2 - ADD: Use Case, User Stories, and Development Methodology
• Week 3 - ADD: Architectural Design, Architectural Patterns, Control Flow Diagram
• Week 4 - ADD: Quality Attributes and Views

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:

Other Sections Not Included in the Week 5 Tutorials, ONLY the Week 5 Section is included.
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.

Discussion Question: Zachman and TOGAF Framework

3 Answer options Included

Based on this week's Pluralsight videos, discuss the Zachman framework, TOGAF framework, the 4+1 View Model, and the Views and Beyond approach. How are the frameworks different from each other? How are they the same?

Discussion Question: Cloud Computing and the Enterprise

3 Answer options Included

Based on this week's Pluralsight videos, discuss how cloud computing impacts the enterprise. How does it impact systems development?