Project Project implementation is arguably the most exciting stage of the project management process. It is during project implementation that project plan

Click here to Order a Custom answer to this Question from our writers. It’s fast and plagiarism-free.

Project 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 and submit 6 deliverables:
(1) 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 2).
You may create your system diagram in Microsoft PowerPoint or a graphics program of your choice.

(2) 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 2 project plan (but may differ based on the research you have conducted since Week 2).
You may create your network diagram in Microsoft PowerPoint or a graphics program of your choice.

(3) 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.
(4) A clearly articulated cybersecurity plan that explains how you plan to secure project data and processes.
(5) Source code (may be partial) for at least one software application.

Your source code may be implemented in HTML/JavaScript, Java, C++, or another programming language. The Source Code component does not need to be written in such a way where it’s a working code. It could be a few lines of the source code to demonstrate that you have some understanding of how to write the source code. 
Download and unzip the HTML/JavaScript/CSS sample code files for an example of a partial software application implementation.

(6) A quality assurance and software test plan.

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 6 deliverables must be portfolio ready, which means as complete and error-free as possible. My preference would be to receive one document that includes all deliverables, which is typically what is created in the real world. For example, please submit your file deliverables as a Microsoft Word, PDF, PowerPoint rather than files with extensions such as, .vsdx, .vsd, .ps1, .odt, zip files. BSA/425 v1.3

Software Test Plan

BSA/425 v1.3

Page 2 of 2

Software Test Plan

Project name:

Purpose of project:

Features To Be Tested/Not To Be Tested

Identify all features and combinations of features that will be tested. Also, describe features that will not be tested and explain why.

Testing Pass/Fail Criteria

Define the pass/fail criteria for each of the tests defined in this test plan.

Testing Approach

Describe the testing processes, testing types, and testing methods that will be used in this testing project. Discuss the testing strategy and how it will be applied to test this application.

Testing Cases

Define 12 to 15 test cases for your project.

Testing Materials (Hardware/Software Requirements)

Identify the resources needed for testing in this project. Include the physical facilities, hardware, software, tools, and any other resources that will be used during testing.

Testing Schedule

Testing Activity

Duration

Resource

Comments

Test Plan Creation

5 days

Test Manager

Test Specification Creation

10 days

Test Leads

Test Specification Team Review

5 days

Project Team

Component Testing

20 days

Component Testers

Integration Testing

20 days

Component and System Testers

System Testing

15 days

System Testers

Performance Testing

5 days

System Testers

Use Case Validation

10 days

System Testers

Alpha Testing

5 days

Product Managers/Analysts

Beta Testing/Pilot Program

20 days

Pilot Program End-Users

Risks and Contingencies Matrix

Risk

Probability

Risk Type

Owner

Contingencies/Mitigation Approach

Do not have enough skilled workers to test components as they are ready for testing.

25%

Project Resources

Testing Manager

Testing schedule will be adjusted based on available resources.

Testing team member turnover

10%

Project Resources

Testing Manager

Adjust testing schedules. Make sure testing team members are cross-trained on testing techniques in case a team member leaves the organization.

Copyright 2020 by University of Phoenix. All rights reserved.

Copyright 2020 by University of Phoenix. All rights reserved.

Place your order now for a similar assignment and have exceptional work written by one of our experts, guaranteeing you an A result.

Need an Essay Written?

This sample is available to anyone. If you want a unique paper order it from one of our professional writers.

Get help with your academic paper right away

Quality & Timely Delivery

Free Editing & Plagiarism Check

Security, Privacy & Confidentiality