You are required to develop an architecture for a system that helps customers in a department store. The store is part of a chain. It does this via specialized store-owned cell phones used only within the store. The system has the following characteristics.
- The cell phones can be used to talk—but only to a store representative using Voice-Over-IP.
- Customers may be transferred to a remote employee if specialized expertise is required.
- The cell phones are loaded with a single application (“the app”).
- The app allows taking and transmission of photographs of items in the store.
- The app allows customers to pay for an item at any time (and thus avoid checking it out).
The following is a key use case.
- Select the entity classes (“business” classes) and design classes sufficient to cover this use case. Draw a class model. Introduce inheritance if it adds value. You should have about 8-14 classes. You may use the following Visio template.
- Design and draw a physical data flow diagram. Explain the parts of your physical data flow diagram that are not obvious. Your diagram should have about 5-10 processing elements. You may use the following Visio template.
- Select and describe an appropriate system architecture, and your reason for selecting it. Describe other architectures you considered, and why you chose not to select them
- Draw a networking data flow diagram, as illustrated in the textbook. Your figure should contain about 5-10 processing elements. Greater level of detail than 20 elements is not required. We are not expecting you to be a networking expert: you may copy aspects from the book for appropriate rates and standards. (On Visio, the best I could find to draft this is General../Basic Flowchart with “control transfer” arrows, reduced in size, annotated.) You may use the following Visio template.
- Explain how your architecture fulfills applicable common design goals – or how it should be enhanced to do so. It will clarify your presentation if you indicate where the architecture allows (but does not actually require) a desired property.
Hints
Miscellaneous
- Augment UML diagrams and your architecture with appropriate notation and comments to make your architecture clear. A separate narrative may serve this purpose as well.
Physical Data Flow Diagram
- Explain how you selected your data flow diagram elements.
System Architecture
In selecting your architecture, demonstrate your understanding: explain what alternative architectures you have considered and why other alternatives are inferior to your choice. Explicitly specify criteria that you use to compare alternatives. Keep in mind that in real life, the choice of architecture affects maintenance for years.
Networking Data Flow Diagram
An example of a networking data flow diagram can be found below.
0 comments