CSS 422

Learning Team: Use Cases, User Stories, Components and Connectors

1st half

develop the next three sections of the Architectural Design Document (ADD)

1. ADD Developmental Methodology on the attach paper.
2. In the ADD, label this section "Functional Requirements." Identify architecturally significant functional requirements and quality requirements for the system. Prepare an executive summary on each, and explain how you will solve them through architecture. You should specifically compare and contrast architectural patterns and design patterns in your solution. Most important, identify why you chose your solution to the problems identified. These are your design decisions.
3. Summarize your design decisions by creating a matrix that shows the problem and how you solved it through software architecture techniques you have learned from this course. For example, if you decided on using a client/server pattern for this system, what problem did this solve?2nd PARTAs a team, finalize the Architectural Design Document (ADD) by creating system modeling diagrams.
4. 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 4+1 View Model or another framework for the classification of your diagrams.
5. Create at the following architectural diagrams in 1 to 2 pages for your CRM system:

• Architectural pattern (pipes and filters, layers, SOA, etc.)
• Logical modeling (you may choose an object diagram, class diagram, etc.)
• Dynamic modeling (you may show a data flow diagram, activity diagram, sequence diagram, etc.)
• Physical view -- Cloud, P2P, Client Server, etc. diagram of the system
• Data model -- ERD or XML template for a portion of data represented within the system

 

CSS 422

Learning Team: Use Cases, User Stories, Components and Connectors

1st half

develop the next three sections of the Architectural Design Document (ADD)

1. ADD Developmental Methodology on the attach paper.
2. In the ADD, label this section "Functional Requirements." Identify architecturally significant functional requirements and quality requirements for the system. Prepare an executive summary on each, and explain how you will solve them through architecture. You should specifically compare and contrast architectural patterns and design patterns in your solution. Most important, identify why you chose your solution to the problems identified. These are your design decisions.
3. Summarize your design decisions by creating a matrix that shows the problem and how you solved it through software architecture techniques you have learned from this course. For example, if you decided on using a client/server pattern for this system, what problem did this solve?2nd PARTAs a team, finalize the Architectural Design Document (ADD) by creating system modeling diagrams.
4. 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 4+1 View Model or another framework for the classification of your diagrams.
5. Create at the following architectural diagrams in 1 to 2 pages for your CRM system:

• Architectural pattern (pipes and filters, layers, SOA, etc.)
• Logical modeling (you may choose an object diagram, class diagram, etc.)
• Dynamic modeling (you may show a data flow diagram, activity diagram, sequence diagram, etc.)
• Physical view -- Cloud, P2P, Client Server, etc. diagram of the system
• Data model -- ERD or XML template for a portion of data represented within the system

 

 

CUSTOMER RELATIONSHIP ARCHITECTURE SYSTEMLEARNING TEAM B

• 1494048389-CRM.docx

ComputerScienceExpert

(11)

Status NEW Posted 06 May 2017 05:05 AM My Price 11.00

-----------

Attachments

file 1494048388-Solutions file 2.docx preview (51 words )

H-----------ell-----------o S-----------ir/-----------Mad-----------am ----------- Th-----------ank----------- yo-----------u f-----------or -----------you-----------r i-----------nte-----------res-----------t a-----------nd -----------buy-----------ing----------- my----------- po-----------ste-----------d s-----------olu-----------tio-----------n. -----------Ple-----------ase----------- pi-----------ng -----------me -----------on -----------cha-----------t I----------- am----------- on-----------lin-----------e o-----------r i-----------nbo-----------x m-----------e a----------- me-----------ssa-----------ge -----------I w-----------ill----------- be----------- qu-----------ick-----------ly -----------onl-----------ine----------- an-----------d g-----------ive----------- yo-----------u e-----------xac-----------t f-----------ile----------- an-----------d t-----------he -----------sam-----------e f-----------ile----------- is----------- al-----------so -----------sen-----------t t-----------o y-----------our----------- em-----------ail----------- th-----------at -----------is -----------reg-----------ist-----------ere-----------d o-----------n -----------THI-----------S W-----------EBS-----------ITE-----------. ----------- Th-----------ank----------- yo-----------u -----------

Not Rated(0)

• Buy Answer