CSS 422 Experience Tradition/newtonhelp.com

1
CSS 422 Experience Tradition/newtonhelp.com
2
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 1 Individual Use Case Diagram
• CSS 422 Week 2 Team CRM Overview, Stakeholders,
  Development Methodology
• CSS 422 Week 2 Individual System Reference Guide
  Software Architecture Comparison
• CSS 422 Week 3 Team Use Cases, User Stories,
  Components and Connectors

3
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 2 Individual System Reference Guide
  Software Architecture Comparison
• You have been called upon to put together some
  reference materials for other groups to follow,
  since up until now they have not created any
  formal architectural documents.
• Create a System Reference Guide for your employer
  in three parts over

4
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 2 Team CRM Overview, Stakeholders,
  Development Methodology
• As a team, develop the first three sections of
  the Architectural Design Document (ADD) in
  Microsoft Word. Summarize these sections in 150
  to 175 words.
• In the ADD, label this section Overview. Create
  an overview of the CRM system

5
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 3 Individual System Reference Guide
  Diagramming
• You have been called upon to put together some
  reference materials for other groups to follow,
  since up until now they have not created any
  formal architectural documents. As a continuation
  from Week Two, continue to create a System
  Reference Guide for your employer.

6
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 3 Learning Team Use Cases, User
  Stories, Components and Connectors
• As a team, develop the next three sections of the
  Architectural Design Document (ADD).
• In the ADD, label this section Use Cases.
  Develop at least three use cases this week.
  First, develop a

7
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 4 Individual System Reference Guide
  Quality Attributes
• Complete the System Reference Guide for your
  employer, and include an architecture for a new
  employee website. First, identify the quality
  attributes that lead to the architecture, then
  create a high-level architectural diagram related
  to the qualities you identified for this
  assignment. When finished, combine these with the
  documents created in Weeks Two and Three.

8
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 4 Team Functional Requirements and
  Design Decisions
• As a team, develop the next two sections of the
  Architectural Design Document (ADD). The summary
  of this section should total 150 to 175 words and
  will include a matrix.
• In the ADD, label this section Functional
  Requirements.

9
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 5 Individual Public Cloud
  Development Presentation
• Your company is considering a move to
  Microsoft Azure or Amazon Web Services to host a
  web-based application.
• Prepare an 8- to 10-slide Microsoft PowerPoint p
  resentation (not including any title pages or
  references) that shows the pros and cons your
  business would experience from using such a
  service compared to hosting the application
  internally.  Simply submitting slides is not
  sufficient.
• Choose one of the following delivery options

10
CSS 422 Experience Tradition/newtonhelp.com

• For more course tutorials visit
• www.newtonhelp.com
•  
•  
• CSS 422 Week 5 Team System Modeling
• As a team, finalize the Architectural Design
  Document (ADD) by creating system modeling
  diagrams.
• In the ADD, label this section System Modeling.
  Refer to the list of stakeholders you prepared
  earlier. Prepare a matrix that indicates the
  stakeholders you identified and the types of
  diagrams you would prepare for them. Indicate the
  diagram type, and use the 41 View Model or
  another framework for the classification of your
  diagrams.

11
CSS 422 Experience Tradition/newtonhelp.com