Adjust the attachment with the feedback provided. FEEDBACK For the peer review I will break down the review by the different sections in the Individual Project. Overall- The paper isnt consistent with Font and Font Size. The preferred font and font size for the paper is 12pt Times New Roman. Also, there are many paragraphs throughout the paper are not indented. Overview-Some confusing sentences that are highlighted in the peer review. About the company- Capitalize the word Company in the section heading. System Overview- What king of emergency would require the employees to be notified? What is the process that would over in which an emergency is received and sent to the employees? Network Requirements- You mention a fail-safe system in which if one internet connection were to fail, the system would still be accessible to the users. Budget-You mentioned that the 600,000 is an overestimation to leave room for any additional expenses (including monthly charges). I would recommend to remove the cents from 600,000.00 System Architecture- What architecture are you going to pick for the enterprise system? It isnt very clear. Also, did you cover cloud architecture? You mentioned that the software will be local with a cloud based link in case of failure. Embedded Architecture- A few errors in continuity that are highlighted in the peer review. Centralized Architecture- Some confusing sentences highlighted in the peer review. Decentralized Architecture- Some corrections highlighted in the peer review. Distributed System Project Plan- I think that it is a little unclear which system you are implementing. Client/Server or Peer-to-Peer? What is the is the plan of implementing it? Budget-Do you have a breakdown of the individual hardware and software components? Implementation of Tasks-A few possible errors highlighted in the peer review. Resources needed- What is the other software needed to run the system? Do you need any kind of database or custom built application? References- The references need to begin on a separate page. Strengths- I think that you have a good idea for an emergency response system for Ritel. The breakdown of individual personnel does a good job of showing what their responsibilities are what resources they need. Weaknesses- Some of the ideas in the paper are unclear. For example, what type of distributed system are you going to implement within the system? Is it Client/Server or Peer-to-Peer? Also, how are these systems configured? I also did not see cloud architecture being covered in the System Architecture section. Areas for Improvement- I included some minor corrections in the peer review.

Adjust the attachment with the feedback provided. FEEDBACK For the peer review I will break down the review by the different sections in the Individual Project. Overall- The paper isnt consistent with Font and Font Size. The preferred font and font size for the paper is 12pt Times New Roman. Also, there are many paragraphs throughout the paper are not indented. Overview-Some confusing sentences that are highlighted in the peer review. About the company- Capitalize the word Company in the section heading. System Overview- What king of emergency would require the employees to be notified? What is the process that would over in which an emergency is received and sent to the employees? Network Requirements- You mention a fail-safe system in which if one internet connection were to fail, the system would still be accessible to the users. Budget-You mentioned that the 600,000 is an overestimation to leave room for any additional expenses (including monthly charges). I would recommend to remove the cents from 600,000.00 System Architecture- What architecture are you going to pick for the enterprise system? It isnt very clear. Also, did you cover cloud architecture? You mentioned that the software will be local with a cloud based link in case of failure. Embedded Architecture- A few errors in continuity that are highlighted in the peer review. Centralized Architecture- Some confusing sentences highlighted in the peer review. Decentralized Architecture- Some corrections highlighted in the peer review. Distributed System Project Plan- I think that it is a little unclear which system you are implementing. Client/Server or Peer-to-Peer? What is the is the plan of implementing it? Budget-Do you have a breakdown of the individual hardware and software components? Implementation of Tasks-A few possible errors highlighted in the peer review. Resources needed- What is the other software needed to run the system? Do you need any kind of database or custom built application? References- The references need to begin on a separate page. Strengths- I think that you have a good idea for an emergency response system for Ritel. The breakdown of individual personnel does a good job of showing what their responsibilities are what resources they need. Weaknesses- Some of the ideas in the paper are unclear. For example, what type of distributed system are you going to implement within the system? Is it Client/Server or Peer-to-Peer? Also, how are these systems configured? I also did not see cloud architecture being covered in the System Architecture section. Areas for Improvement- I included some minor corrections in the peer review.