module 03 course project design documentation
- Understand the design documentation phase
- Document several cloud services needed for this project
- Create a flow chart of the course lab application
- Implement a historical change grid at the top of the document
- Submit the module use-case document to the course Dropbox for grading
The project design phase begins with opening the discussions into more details about the project requirements. The details can cover the user interface look and feel to how each of the controls will be used and what type of permissions are applied to each user control. During this phase, it is critical for the system/network administrators and database admins to step in and contribute to these discussions. The design of these system components are important and they will have a direct effect on the performance of the product or service.
- In this objective imagine that you are a system/network engineer and document some of the common cloud services to implement a software application product built in-house as an enterprise product that must supports 100 simultaneous users. Make sure to document why you need the cloud service for this type of enterprise solution and then document the benefits of using the cloud service for each component that you recommended.
- In this step design and build a new flow-chart of current course lab application. You will be far enough into the course lab that you will be able to build a flow-chart from it. Use whatever tools are at your disposal from Microsoft Paint to Visio or hand draw a design and take a picture of it with your phone. Flow charts give the reader a visual understanding of the project design and the user responds to different scenarios while using the product.
- At the top of this document, implement historical changes grid so all readers know when a section in the use case was changed, and by whom. The historical change section should be easy to understand why a change to the document occurred, with informative details such as name, change description, date of change, and version. In a way, this is used for document control, there are other ways to manage document changes but they do not keep track of the history of each change, sometimes this is a manual process.