Analysis Phase.docx

7/28/2019 Analysis Phase.docx

1/6

Project Standards

Standards

Documentation Standards Documentation should have elements like coverpage, table of contents, headers, footers andother useful information.

The cover page shall include the followinginformation: Organization Name, Project Title andDocument Title.

A header shall be on all pages from the secondpage to the last page of the document indicatingProject Title and Document Title.

A footer shall be included on all pages from thesecond page to the last page of the documentindicating Confidential if needed and pagenumber.

Coding Standards Indentation should be used to emphasize thebody of a control statement such as a loop or aselect statement.

Three to four spaces shall be used to indent andtabs shall not be used for indentation purposes.

Generally, every program must include one line ofcomment for every five lines of code.

Procedural Standards Alterations to requirements document must be

permitted by the project manager.Specification RequirementStandards

Designed programs name

Special mathematical operations

Timer


2/6

Timer

Risk Assessment

RISK #1: The project manager fails to plan and manage resources required for

achieving goals because of some inevitable circumstance.

Likelihood of risk: Medium probability of risk

Potential impact on the project: This risk may lead to budget overruns, time overruns

or both, or at most, to the failure of completing the project.

Ways to address this risk: It is dire to have a full understanding of the systems that

will be used to improve the project, and the project manager needs to certify the

weaknesses of the development environment. Likewise, an effective project controlling

and monitoring should be formed to enrich project performance thru the project life

cycle. In cases of inevitable situations, proper site investigation should be done to

ensure that all site conditions are noted in the design and apply value management that

could be used to find the best cost effective options in addressing such situations.

RISK #2: The team members are not so familiar with the technology and may not have

the appropriate skills and knowledge about the system.

Likelihood of risk: Medium probability of risk

Potential impact on the project: The time to complete the tasks will be delayed.

Ways to address this risk: Additional training through mentoring and hands-on

instruction with a company trainer can be conducted. Aside from that, providing a


3/6


4/6

2. Performance

2.1. The system will show data screens with no noticeable pauses.

2.2. Data requests will be loaded within 3 seconds.

3. Security

3.1. The system will protect all confidential data by transmitting it on a network

using an encrypted connection.

3.2. No employee can access any customers personal account.

3.3. Only the owner and customer can approve changes in customer accounts.

4. Cultural and Political

4.1. Customers private information is protected in accordance with the Data

Privacy Act of 2012.

Staffing Plan

Role Description Assigned To

Project Manager Allocates resources, shapes priorities,coordinates interactions with customersand users, and generally keeps theproject team focused on the right goal

Gleir


5/6


6/6

3 Implementation 37 3/7 4/16 Open

3.1 Code programs andTest

28 3/7 4/3 Open

3.1.1 Unit test plans Precyl 5 3/7 3/11 2.2.1.3 Open

3.1.2 Module test plans Precyl 5 3/7 3/11 2.2.1.3 Open3.1.3 Code programs Precyl 19 3/12 3/30 3.3.1.3.1.1

3.3.1.3.1.2Open

3.1.4 Unit test plan results Precyl 5 3/12 3/16 3.3.1.3.1.1 Open3.1.5 Individually test

modulesKathleen 4 3/31 4/3 3.3.1.3.1.3 Open

3.2 Install system 5 4/4 4/8 3.3.1.3.1.5 Open

3.2.1 Integration tests andresults

Kathleen 5 4/4 4/8 Open

3.2.2 Help/tutorial Precyl 5 4/4 4/8 Open

3.2.3 Deployment Guides 4 4/9 4/12 3.3.2.3.2.13.3.2.3.2.2

Open

3.2.3.1 System administrator Precyl 4 4/9 4/12 Open

3.2.3.2 User Precyl 4 4/9 4/12 Open3.2.3.3 Standalone Installation Precyl 4 4/9 4/12 Open

3.3 Post-implementation 4 4/13 4/16 3.3.2.3.2.3 Open

3.3.1 System Documentation Gleir 4 4/13 4/16 Open

3.3.2 User Manuals Gleir 1 4/13 4/13 Open3.3.3 ID sheet and

installation CDGleir 1 4/13 4/13 Open

Documents

Analysis Phase.docx