Average Joe’s Membership System must determine the hardware and software they will need as prerequisites for the implementation of their system. We must decide what hardware is appropriate for our intent of the system. It is important to begin with a model encapsulating the network and hardware required and then refine further down to a hardware and software specification form with the relevant nonfunctional requirements. Let’s begin by determining what exactly we will need. The key to remember moving forward is that this is a company spanning different locations across the Midwest.
1. What is the deliverable from the physical architecture layer design?
2. What two architectural components absolutely necessary for a physical architecture?
3. What is the difference between server-based architectures, client-based architectures, and client-server based architectures?
a. Create a table showing the differences between each 3.
4. Should Average Joe’s go with cloud computing or keep their on-site physical architecture?
5. Why is it effective for Average Joe’s to use virtualization technology for their physical hardware?
6. How could Average Joe’s incorporate the IoT into their organization? What benefits could come of it? What disadvantages?
7. What efforts can we do for Average Joe’s to incorporate Green IT?
The physical architecture must be modeled for next steps. The architecture can be informed by the developing the hardware deployment diagram. Once we have the model built, we can create a hardware and software specification form.
1. Design a hardware deployment diagram for Average Joes using a modeling tool.
2. Based on your diagram, develop a software and hardware specification form for Average Joes.
