A Patient Information System for Mental Health Care DQ

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 conventions.

You must proofread your paper. But do not strictly rely on your computer’s spell-checker and grammar-checker; failure to do so indicates a lack of effort on your part and you can expect your grade to suffer accordingly. Papers with numerous misspelled words and grammatical mistakes will be penalized. Read over your paper – in silence and then aloud – before handing it in and make corrections as necessary. Often it is advantageous to have a friend proofread your paper for obvious errors. Handwritten corrections are preferable to uncorrected mistakes.

Use a standard 10 to 12 point (10 to 12 characters per inch) typeface. Smaller or compressed type and papers with small margins or single-spacing are hard to read. It is better to let your essay run over the recommended number of pages than to try to compress it into fewer pages.

Likewise, large type, large margins, large indentations, triple-spacing, increased leading (space between lines), increased kerning (space between letters), and any other such attempts at “padding” to increase the length of a paper are unacceptable, wasteful of trees, and will not fool your professor.

The paper must be neatly formatted, double-spaced with a one-inch margin on the top, bottom, and sides of each page. When submitting hard copy, be sure to use white paper and print out using dark ink. If it is hard to read your essay, it will also be hard to follow your argument.