Case Study 2: Software System Architecture

  Case Study 2: Software System Architecture   Due Week 8 and worth 100 points       Read the case study titled “A Patient Information System for Mental Health Care”, located in Chapter 1 of your textbook. Develop an overall architecture for the system described in the assigned reading. Your architecture should be based on any one of the common architectural patterns (e.g., Pipe and Filter architecture pattern). Your architecture should be documented in text and in UML diagrams (at minimum a class diagram and a sequence diagram).       Write a two to four (2-4) page paper in which you:   Describe your chosen architecture pattern. Explain why you selected the architecture of this case study. Explain how your chosen pattern could be applied to this case study. Describe any shortcomings associated with your chosen architecture pattern for the case study. Describe how your architecture could be implemented in hardware and software. Develop a UML diagram to document the architecture of the system through the use of Microsoft Visio or its open source alternative, Dia. Note: The graphically depicted solution is not included in the required page length.       Your assignment must follow these formatting requirements:   Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions. Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length. Include charts or diagrams created in Visio or an equivalent such as Dia. The completed diagrams / charts must be imported into the Word document before the paper is submitted.       The specific course learning outcomes associated with this assignment are:   Explain how service-oriented software can be used to build distributed applications using Web services. List the characteristics of embedded real-time systems. Use technology and information resources to research issues in software engineering. Write clearly and concisely about software engineering using proper writing mechanics and technical style convention   Grading for this assignment will be based on answer quality, logic / organization of the paper, and language and writing skills, using the following rubric.       Points: 100 Case Study 2: Software System Architecture Criteria   Unacceptable Below 60% F Meets Minimum Expectations 60-69% D   Fair 70-79% C   Proficient 80-89% B   Exemplary 90-100% A 1. Describe your chosen architecture pattern. Weight: 15% Did not submit or incompletely described your chosen architecture pattern. Insufficiently described your chosen architecture pattern. Partially described your chosen architecture pattern. Satisfactorily described your chosen architecture pattern. Thoroughly described your chosen architecture pattern. 2. Explain why you selected the architecture of this case study. Weight: 15% Did not submit or incompletely explained why you selected the architecture of this case study. Insufficiently explained why you selected the architecture of this case study. Partially explained why you selected the architecture of this case study. Satisfactorily explained why you selected the architecture of this case study. Thoroughly explained why you selected the architecture of this case study. 3. Explain how your chosen pattern could be applied to this case study. Weight: 15% Did not submit or incompletely explained how your chosen pattern could be applied to this case study. Insufficiently explained how your chosen pattern could be applied to this case study. Partially explained how your chosen pattern could be applied to this case study. Satisfactorily explained how your chosen pattern could be applied to this case study. Thoroughly explained how your chosen pattern could be applied to this case study. 4. Describe any shortcomings associated with your chosen architecture pattern for the case study. Weight: 15% Did not submit or incompletely described any shortcomings associated with your chosen architecture pattern for the case study. Insufficiently described any shortcomings associated with your chosen architecture pattern for the case study. Partially described any shortcomings associated with your chosen architecture pattern for the case study. Satisfactorily described any shortcomings associated with your chosen architecture pattern for the case study. Thoroughly described any shortcomings associated with your chosen architecture pattern for the case study. 5. Describe how your architecture could be implemented in hardware and software. Weight: 15% Did not submit or incompletely described how your architecture could be implemented in hardware and software. Insufficiently described how your architecture could be implemented in hardware and software. Partially described how your architecture could be implemented in hardware and software. Satisfactorily described how your architecture could be implemented in hardware and software. Thoroughly described how your architecture could be implemented in hardware and software. 6. Develop a UML diagram to document the architecture of the system through the use of Microsoft Visio or its open source alternative, Dia. Weight: 15% Did not submit or incompletely developed a UML diagram to document the architecture of the system through the use of Microsoft Visio or its open source alternative, Dia. Insufficiently developed a UML diagram to document the architecture of the system through the use of Microsoft Visio or its open source alternative, Dia. Partially developed a UML diagram to document the architecture of the system through the use of Microsoft Visio or its open source alternative, Dia. Satisfactorily developed a UML diagram to document the architecture of the system through the use of Microsoft Visio or its open source alternative, Dia. Thoroughly developed a UML diagram to document the architecture of the system through the use of Microsoft Visio or its open source alternative, Dia. 7. Clarity, writing mechanics, and formatting requirements Weight: 10% More than 8 errors present 7-8 errors present 5-6 errors present 3-4 errors present 0-2 errors present