Creating Several Software Architecture Diagrams
Order ID:89JHGSJE83839 Style:APA/MLA/Harvard/Chicago Pages:5-10 Instructions:
Creating Several Software Architecture Diagrams
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.
For this week’s assignment, create several software architecture diagrams for your company’s online sales website. The website is to present a shopping cart system with which users can browse an online catalog and place orders for merchandise. The system also allows users to view previous orders, which is useful for tracking shipping for recent orders and for re-ordering items in the future.
Produce the following three diagrams:
To present a static model of the system, create a diagram for a layered architecture view of the system.
Using the components you identified in your layered view of the system, create an activity diagram that shows how a customer would place an order.
Create a client/server diagram to model the physical view of the system.
Incorporate the three diagrams into a single document in Microsoft® Word. As this document is intended for a technical team, APA formatting is not required.
Creating Several Software Architecture Diagrams
RUBRIC
Excellent Quality
95-100%
Introduction 45-41 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Literature Support
91-84 points
The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned.
Methodology
58-53 points
Content is well-organized with headings for each slide and bulleted lists to group related material as needed. Use of font, color, graphics, effects, etc. to enhance readability and presentation content is excellent. Length requirements of 10 slides/pages or less is met.
Average Score
50-85%
40-38 points
More depth/detail for the background and significance is needed, or the research detail is not clear. No search history information is provided.
83-76 points
Review of relevant theoretical literature is evident, but there is little integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are included. Summary of information presented is included. Conclusion may not contain a biblical integration.
52-49 points
Content is somewhat organized, but no structure is apparent. The use of font, color, graphics, effects, etc. is occasionally detracting to the presentation content. Length requirements may not be met.
Poor Quality
0-45%
37-1 points
The background and/or significance are missing. No search history information is provided.
75-1 points
Review of relevant theoretical literature is evident, but there is no integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are not included in the summary of information presented. Conclusion does not contain a biblical integration.
48-1 points
There is no clear or logical organizational structure. No logical sequence is apparent. The use of font, color, graphics, effects etc. is often detracting to the presentation content. Length requirements may not be met
You Can Also Place the Order at www.collegepaper.us/orders/ordernow or www.crucialessay.com/orders/ordernow Creating Several Software Architecture Diagrams