Project implementation is arguably the most exciting stage of the project management process. It is during project implementation that project plans begin to come to life and assumptions are able to be tested and measured in real-life scenarios.
One of the outcomes of project implementation is a set of deliverables that typically includes a system diagram; a network diagram; a database design document, including an entity-relationship diagram, a data dictionary, and table definitions; a clearly articulated cybersecurity plan; and source code.
To complete this assignment, you will create:
- A system diagram that shows, in graphic form, the components of your project.
- Your system diagram should follow the system description you submitted in your Week 2 project plan (but may differ based on the research you have conducted since Week 3). The week 3 project plan is in the upload files
- You may create your system diagram in Microsoft PowerPoint or a graphics program of your choice.
- A network diagram that shows, in graphic form, the flow of data within your project.
- Your network diagram should follow the network description you defined in the Week 3 project plan (but may differ based on the research you have conducted since Week 2). The week 3 project plan is in the upload files
- You may create your network diagram in Microsoft PowerPoint or a graphics program of your choice.
- A database design document, including an entity-relationship diagram, a data dictionary, and table definitions, representing all of the data that must be stored and maintained within the context of your project and how that data is organized.
- A clearly articulated cybersecurity plan that explains how you plan to secure project data and processes.
- Source code (may be partial) for at least one software application.
- ^ web address: https://myresource.phoenix.edu/secure/resource/BSA425r1/BSA425r1.3_wk4_sample_code.zip
- A quality assurance and software test plan. See plan in uploaded files
- Download the Software Test Plan for an example of what information is typically included and how it is typically organized in a software test plan.
Note: All deliverables must be portfolio ready, which means as complete and error-free as possible.