IT488_JaySexton_Week5GP

running head DRAFT KEY ASSIGNMENT 1

IT488 IT Capstone II

Phase 5 Group Project

Professor Jimmy Irwin

Author: Jay Sexton

Contributors: Leo Schleicher, Patrick O’Malley, Tyson Weiss

12/22/2014

DRAFT KEY ASSIGNMENT 2

Project Plan......................................................................................................................................3

Detailed Content Plan....................................................................................................................71

Timeline and Milestones................................................................................................................74

The Project will be completed on the set end date, on time and within budget. There were no serious quality assurance issues during this project all rsik were identified and steps were used to repair or replace any hardware, software or operational application issues .................................78

Attachment B SharePoint Administrator Manual (Training guide) Outline (Skeleton)................92

Attachment C SharePoint SharePoint Content Standards (Policies and Procedures) Outline (Skeleton).......................................................................................................................................93

References......................................................................................................................................96

Page 2


Project Plan

Section 1 - Overview of the Project

The company of concern for the Business Document Shell will be J&T Consultants. This is

a civilian contracting firm that provides embedded direct server/client architecture and network

infrastructure management, troubleshooting, administration, and both hardware and software

installation, setup, and configuration instruction. The firm currently employs six personnel,

which are all military veterans, that provide customer service support to the United States

Military. The organization that J&T Consultants supports is the 3rd Infantry Division and all

subordinate units, Brigade and Battalion size elements stationed at Fort Stewart, Georgia. The

firm’s expertise covers numerous career fields, military operations, government service,

information technology, and customer support. J&T Consultants is the selected firm to field,

issues, train, and maintain all commercial off the shelf (COTS) equipment and software service

support through the Department of the Army.

Business Case The business case is all the current hardware and software for 3rd Infantry

division has exceeded it lifecycle and needs to be upgraded. J&T Consulting will deliver, issues,

install, setup, configure and train all newer versions of both hardware and software to 3ID. The

primary goal and objective during this upgrade is to establish a web based interactive data

storage web site using Microsoft SharePoint 2010 as the websites front-end and Microsoft SQL

2008 as the web back-end server to store all data in a SQL database. J&T Consultants is the best

suited firm for this support because all employees are military veterans who know and

Page 3


understand the Army requirements, tactical and strategic operational requirements. This team,

being embedded in the organization, will provide 24 hour daily administration 7 days a week

both at home station and deployed away in foreign lands.

The Application solution that J&T consultants will provide is the fielding of all new up-to-

date hardware equipment, installation, setup, and configuration of newest VMware and

Microsoft software suite applications, built-in a virtual environment, and then replace the current

shared hard drive where important data is being stored and replace it with a new SharePoint web-

based interactive data storage web site that can be accessed across the internet from anywhere in

the world. Finally to provide continue service support and vendor interaction as the Security

managers, system and software administrators, Information assurance, and information managers

for the organization.

Page 4


Section 2 – Requirements

The 3rd Infantry Division is currently using a physical hard drive as a document storage

device. This standard makes it hard to share data and documents to everyone that would need the

information. Outside organizations cannot access this shared storage drive across the internet.

During the requirement elicitation and strategy gathering it was determined that the organization

needs the following objectives met:

• Create a web based interactive database storage web site

• Active Directory linked for DOMAIN user login

• Make it accessible globally

• Administered by trained personnel

• Easily understood web layout

• Search and navigation menu features

• Access permissions

• Web Based document library for viewing, storing, and retrieving tactical information

Page 5


Section 3 – Design

Currently the unit has HP SDL380 Server blades, Winchester Raid storage devices, Net

Link hubs and switches, Cisco T100 routers using Microsoft 2003 operating physical systems. In

order to accomplish these requirements the organization will require a hardware upgrade to Dell

PowerEdge R420xr servers, NetApps 2240 Storage Area Network devices, CISCO 1 Gigabyte

smart switches, 1 Gigabyte 3360 smart Routers, and Universal power supplies. This system is

used in “extreme environments of defense, telecom, emergency response services and industrial

automation. With shock and vibration resistance, optional advanced dust filtration and the ability

to operate in high temperatures and altitudes, the Dell PowerEdge R420xr is built to deliver

virtualization-ready power to demanding deployments constrained by size, weight and power”

(Dell, 2014). All servers will be upgrade to Windows 2008 R2, SQL 2008, SharePoint 2010,

Exchange 2010 all as virtual machines in a VMware virtual environment. VMware is a bare-

metal hypervisor’s management functionality built into the VMkernel, reducing the footprint to

150 MB. This allows for a very small attack surface for malware and over-the-network threats,

improving reliability and security (vmware, 2014).

The specifics the organization wants, is to have a web based data storage capability that can

be accessed across the internet. It will provide the capability to access the data store using any

different type of client operating system. Reduce or eliminate the use of Virtual Private Network

(VPN), or manual mounted shared drives or worry about security breaches to any and all data. If

the organization is upgraded to the newest hardware and Microsoft Business suite applications

then through the use of Windows 2008 R2 Active Directory, DOMAIN Naming System (DNS),

and SharePoint 2010 then the organization can have a web based interactive database storage

web site locally and allow access globally from any user at any location using a classified client

Page 6


with login credentials and site permissions. This will surely meet the organizations requirements,

goals, objectives, wants and needs.

Page 7


Section 4 – System Development Methodology

At this phase of the project the most important issue is determining and

establishing the best system development methodology to use. 3rd Infantry Division is a highly

complex organization and how it functions cannot be controlled by a single system development

methodology. This organization must use a combination of the Dynamic Systems Development

Method (DSDM) integrated with the Feature Driven Development (FDD) methodology. Both are

considered a form of the agile alliance system and bring a multitude of approaches to how 3ID

will accomplish this life cycle upgrade and development of the SharePoint 2010 Web based

interactive data storage database web site.

DSDM is a methodology that requires clear tactical and strategic goals from the unit with

it sight kept of rapid delivery of project needs and wants (DSDM, N.D.). DSDM uses a delivery

framework method which provides direct and quick visible project results. This method

stipulates that the end-user be routinely and actively involved through all stages of the system

development. By ensuring this connection this enforces the thought if they are totally involved

from start to finish then the end-user will embrace and accept the completed project mainly

because they have a direct say in the projects direction. DSDM is big in eliminating business

politics while preventing communication barriers. DSDM makes all early indicators visible to

help determine if the project will work or not and if it will come in on time and within budget. In

using this methodology the project use iterative and incremental development, permits changes

to be reversed, simplifies higher level requirements, uses integrated testing, and lastly DSDM is

collaborative and co-operative approach to system development (Davis, 2004).. DSDM method

will relate to the complete project while the design and development of the SharePoint 2010 Web

Page 8


based interactive data storage database web site will relate to the Feature Driven development

(FDD) methodology.

SharePoint 2010 is a Microsoft web collaboration application that allows users to use

currently design or newly developed web part features to create an interactive web site

customized to the customer desire, wants and needs. Since SharePoint is feature driven if a web

site is designed laid out, verified and validated and then published then the Feature Driven

Development (FDD) methodology has been successfully accomplished. FDD is big on

scalability and repeatability. Once features have been developed for SharePoint they are loaded

into a database and can be used by other users for their specific web site development. FDD

requires that all steps be clear, logical and well worth being seen by all viewers. FDD uses a

model development process, focuses on results by letting well designed processes to be placed

background operations, It uses short, iterative, and feature-driven life cycles, in it plans, design,

and development (AMTP, 2014).

Page 9


Section 5 – Work Breakdown Structure

This section covers the Work Breakdown Structure for the current System Life Cycle

upgrade and SharePoint Web based Interactive Data Storage Database Web Site for 3rd Infantry

Division. The WBS is a major project deliverable for any project. It shows how work is

organized into manageable pieces. The WBS visually identifies the scope of the project and

separates it into controllable phases that are easily understood by the project team (WBS, 2014).

What is a WBS? It is known as a chart that list all the important work task which shows the task

relationships to each other, the start and finish dates of the task, the owners, who it can be deliver

to and the percentage of completion toward the project as a whole (Rouse, 2006). What the WBS

portrays, is the key deliverables and milestones objectives and then identifies the task required to

reach each goal. The following charts list the Work Breakdown Structure by project levels

graphic, Coding scheme and finally the actual Completed work breakdown structure char

Work Breakdown Structure (WBS)The Foundation of Project Planning

A work breakdown structure is an extremely valuable and important project management tool. It sets the foundation for the rest of the project planning. (ProjectSmart, 2014)

Page 10


WBS Project Level Chart Figure 1Project Coding Scheme

1.0 Project :System Life Cycle Upgrade and Web based Interactive Data Storage website1.1 Administrative

1.1.1 Initial Kick off meeting1.1.2 Research 1.1.3 Stakeholder introductions1.1.4 Requirement Gathering1.1.5 End-user interviews1.1.6 Establish time schedule and cost Estimates1.1.7 Develop Prototype Web site1.1.8 Project Start1.1.9 Weekly progress meetings1.1.10 Project review

1.1.10.1 Project review Hardware upgrades1.1.10.2 Project review Server Software upgrades1.1.10.3 Project review Client Setup and configurations1.1.10.4 Project review Data Migration to Hotspot disaster recovery

location1.1.10.5 Project review Web-based Interface

Page 11


1.1.11 Final Implement Changes1.1.12 Distribute Documentation Documents.

1.2 Hardware training build1.2.1 Setup U P S, Server blades, FAS 2240, CISCO Switches1.2.2 Install Cat5 and Fiber Cables to, Server blades, FAS 2240, CISCO Switches1.2.3 Configure RAIDS, LUNS and switch ports for operation

1.3 Software training build1.3.1Installation of VMware Linux shell operating systems1.3.2 Installation of Virtual Machines with Microsoft 2008 R2 Server1.3.3 Setup and configure AD, DNS, Exchange, SQL, and SharePoint servers1.3.4 Setup and configure Active Directory account logins and permissions1.3.5 Data migration from old physical servers to new virtual servers

1.4 Client 1.4.1 Install and setup Windows 7 Operating systems1.4.2 Configure Internet protocol IPv4properties1.4.3 Configure User accounts and connect to the AD DOMAIN server 1.4.4 Configure Web Browser with security, internet options and protection

1.5 Web-based interface1.5.1 Set access permissions with AD DOMAIN accounts1.5.2 Build hierarchy navigation menu and fill in the blank search options1.5.3 Organizational Site graphics and easily usable layout1.5.4 Outlook Calendar interaction1.5.5 Document library for data storage1.5.6 Document review, check-in and check-out user requirements 1.5.7 Internet Explorer and Microsoft office interaction1.5.8 Logout requirements for SharePoint

1.5.8.1 Logout requirements Web Brower and Client laptop1.5.9 Publish Web site

Page 12


Project Work Breakdown Structure Task Relationship and Status Chart.

WBSTRASC Figure 2

Page 13

WBS # Predecessor Task Description Duration Start Date End Date Owner Deliever To % Complete

1.1.4Project :System Life Cycle Upgrade and Web based Interactive Data Storage website

20-Oct 18-NovSexton 100.00%

1.1 Administrative 20-Oct 18-Nov Knudson 100.00%1.1.1 1.1.4 Initial Kick off meeting 20-Oct 22-Oct Knudson 100.00%1.1.2 1.1.1 Research 20-Oct 21-Oct Sexton 100.00%1.1.3 1.1.2 Stakeholder introductions 20-Oct 22-Oct Knudson 100.00%1.1.4 1.1.3 Requirement Gathering 20-Oct 22-Oct Sexton 100.00%1.1.5 1.1.4 End-user interviews 20-Oct 22-Oct Sexton 100.00%1.1.6 1.1.5 Establish time schedule and cost Estimates 22-Oct 22-Oct Sexton 100.00%1.1.7 1.1.6 Develop Prototype Web site 22-Oct 24-Oct Schleicher 100.00%1.1.8 1.1.7 Project Start 25-Oct 18-Nov IT Team 100.00%

1.1.9

1.2 1.3 1.4 Weekly progress meetings

30-Oct, 7-Nov, 11-Nov

30-Oct, 7-Nov, 11-Nov Knudson 100.00%

1.1.10 1.5.8 Project review 14-Nov 14-Nov Knudson 100.00%1.1.11 1.1.10 Implement Changes 14-Nov 15-Nov IT Team 100.00%1.2 1.1.8 Hardware training build 25-Oct 29-Oct Litt 100.00%

1.2.1 1.2Setup U P S, Server blades, FAS 2240, CISCO Switches

25-Oct 26-OctLitt 100.00%

1.2.2 1.2.1 Install Cat5 and Fiber Cables to, Server blades, FAS 2240, CISCO Switches


1.2.3 1.2.2 Configure RAIDS, LUNS and switch ports for operation


1.3 1.1.8 Software training build 25-Oct 29-Oct Weiss 100.00%1.3.1 1.3 Installation of VMware Linux shell operating systems 25-Oct 25-Oct Weiss 100.00%

1.3.2 1.3.1Installation of Virtual Machines with Microsoft 2008 R2 Server

26-Oct 27-OctWeiss 100.00%

1.3.3 1.3.2Setup and configure AD, DNS, Exchange, SQL, and SharePoint servers

27-Oct 29-OctWeiss 100.00%

1.3.4 1.3.3Setup and configure Active Directory account logins and permissions

2-Nov 2-NovWeiss 100.00%

1.3.5 1.1.9

Data migration from old physical servers to new

virtual servers30-Oct 1-Nov

Weiss, Sexton, Litt 100.00%

1.4 1.1.8 Client 25-Oct 29-Oct O'Malley 100.00%1.4.1 1.4 Install and setup Windows 7 Operating systems 25-Oct 26-Oct O'Malley 100.00%1.4.2 1.4.1 Configure Internet protocol IPv4properties 26-Oct 26-Oct O'Malley 100.00%

1.4.3 1.4.2

Configure User accounts and connect to the AD DOMAIN server

26-Oct 28-OctO'Malley 100.00%

1.4.4 1.4.3

Configure Web Browser with security, internet options and protection

29-Oct 29-OctO'Malley 100.00%

1.5 1.4.4 Web-based interface 3-Nov 13-Nov Schleicher 100.00%1.5.1 1.5 Set access permissions with AD DOMAIN accounts 3-Nov 3-Nov Schleicher 100.00%

1.5.2 1.5.1

Build hierarchy navigation menu and fill in the blank search options

3-Nov 5-NovSchleicher 100.00%

1.5.3 1.5.2 Organizational Site graphics and easily usable layout 3-Nov 6-Nov Schleicher 100.00%1.5.4 1.5.3 Outlook Calendar interaction 7-Nov 7-Nov Schleicher 100.00%1.5.5 1.5.4 Document library for data storage 7-Nov 9-Nov Schleicher 100.00%

1.5.6 1.5.5

Document review, check-in and check-out user requirements

9-Nov 10-NovSchleicher 100.00%

1.5.7 1.1.9 Internet Explorer and Microsoft office interaction 11-Nov 12-Nov Schleicher 100.00%1.5.8 1.5.7 Logout requirements 13-Nov 13-Nov Sexton 100.00%1.5.9 1.1.11 Publish Web site 15-Nov 15-Nov Sexton 100.00%

System Life Cycle Upgrade and Web based Interactive Data Storage Web Site Work Breakdown Structure


Section 6 – Communication Plan

PURPOSE

• To document the method of communicating and tracking project information to the stakeholders, Leadership team, project teams, and end-users.

OBJECTIVES• To keep stakeholder informed of progress on the project• To manage end-users expectations and perceptions• To help achieve buy-in from stakeholders and team members• To reduce uncertainty • To reduce levels of misinformation and misunderstanding about the project• To provide multi-layer communication methods of proper feedback among the Leadership

team, end-users and stakeholders

MESSAGES• Project information• Expectations of all team members• Impact of the project on the organization (to include Benefits, Risk Assessment)• How end-users will be affected• How end-user be involved with the project• Successful milestone completed

Project Participants Include:

Name: Role: Phone E-mail_________________________Jay Sexton Project Manager xxx-xxx-xxxx [email protected] Patrick O’Malley Communications xxx-xxx-xxxx [email protected] Schleicher Tech Support xxx-xxx-xxxx [email protected] Weiss Quality Assurance xxx-xxx-xxxx [email protected] Litt Communications xxx-xxx-xxxx [email protected]

Mailing Information:The address for correspondence:J&T ConsultantsCapstone II AvenueCTU, USA, 00000Primary Contact: Mr. Jay Sexton, Project Manager

Page 14

mailto:[email protected]


Communication MatrixWhoStakeholders

HowComm. Media

WhatKey MessagesContent

By WhomResponsibility

WhenTimeline

Leader Team e-mail & SharePoint

• Weekly updates – Status Report

Team LeadsProject Manager

WeeklySubmitted by Monday Afternoon

Office Meeting • Agenda• Project status• Budget tracking• Conversion updates• Recommendations

• Project Topics • Sponsorship and Teamwork• Change Management• Design Phase Kickoff• Change Management

Update• Design Recommendations• Interface Updates• Cut over Plans• Change

Management/Training Update

• Testing/Data Conversion/Interface

• Pre Go Live• Go Live Plan• Go Live Update

• Project Review

Project ManagerTeam Leads

(Send Agenda as e-mail 2 days prior before meeting)

Meet every other week list dates

Project sponsor , Team Leads, Team Members, Project Managers

Status meeting • Review project schedule• Address any issues

Project Managers Tuesdays @8:00am

Page 15


Section 7 – Quality Assurance PlanQuality Assurance Process

Revision History

Date Version Description Author

12/1/2014 1.0 Initial Patrick O’Malley

12/2/2014 1.0 Reviewed by Team Members Schleicher; Sexton; Litt; Weiss

Table of Contents 1.0 Introduction

1.1 Purpose1.2 Scope

2.0 Assumptions3.0 Applicability4.0 Document Terminology and Acronyms5.0 SQA Concepts and Definitions

5.1 Definitions5.2 Background5.3 SQA Standards and Procedures5.3.1 Standards5.3.2 Procedures

6.0 Iterative Development process approach (DSMS).• Iterations:

• Activities:

• Supporting Activities:

• Why Incremental

• Inception Phase

• Elaboration phase

• Construction phase

• Transition phase

6.1 Analysis6.2 Design

Page 16


6.3 Development6.4 Verification & Validation6.5 Testing106.6 Configuration Management6.7 Deployment

7.0 Roles and Responsibilities8.0 Conclusion & Overall Practices for Success

Quality Planning Table

The table below shows a quick reference for associating the project phase to the quality assurance process.

Quality Planning Associated WBS to Quality Assurance TableWBS Quality Assurance Processes

1.1 Administrative All of section 1.0 and QA check list1.2 Hardware All of section 5.0 and QA check list1.3 Software All of section 5.0; 6.0 and QA check list1.4 Client All of section 5.0; 6.0 and QA check list 1.5 Web Site All of section 1.0; 2.0; 3.0; 4.0; 5.0; 6.0 and QA

check list

Quality Assurance Plan

PurposeThe purpose of this Software Quality Assurance Plan (SQAP) is to define standards, processes and procedures that are applicable to all projects at J&T Consultants. It can be used without revisions or can be augmented as needed for specific projects.

A good quality assurance plan or service is a function of the sum of all its parts to include Software Test Plan (STP) and Software Quality Assurance Actives (SQA) that are the most fundamental building blocks that define the project scope, resources, methods, audits and testing activities. This plan will address all of the corresponding phases for the DSDM methodology process that is the foundation for project management for this project. It is our philosophy to attract and retain the best people available.

Quality starts with the individuals. This means that problems or potential issues should be of concern to any and all who are aware of them. Due diligence should be employed to assure that IT services and solutions are always of high quality to migrate any risk and not delivering the project on time.

There are various Quality Assurance (QA) tools and techniques that can help you manage the QA processes. For this project we will use the Tree Diagram which is known as a systematic diagram that with breakdown pecking order such as the WBS, RBS and OBS (organization breakdown). There are many tasks that are associated with the plan and we will use the following checklist for every phase in the WBS.

Page 17


Another goal is to promote the use and adherence to Quality Assurance Process and its best practices at J&T Consultants.

1. ScopeThis plan is the top-level document generated by the J&T consultants Quality Assurance team with the input from various project teams’ members. The use of this plan will help to assure the following:

(1) That software development, evaluation and acceptance standards are developed, documented and followed.

(2) That the results of software quality reviews are communicated to the appropriate management. This provides feedback as to how well the development effort at J&T Consultants is conforming to various Software Development Standards based off IEEE and ISO900.

(3) That test results adhere to acceptance standards.

It is mandated that the document is used by project teams for the Quality Assurance effort guidance.

2. Assumptions

It is assumed that the audience reading this document is familiar with overall J&T Consultants Business Processes. Also they are “involved” in developing and supporting any given system. This includes project managers, developers, business analysts, QA team, dedicated resource people, those people involved in the other creative aspects of the system, and after production support.

Most definitions that describe processes, standards and procedures are used in this document follow the IEEE Standards system

3. Applicability The processes described in this plan are used during the analysis, requirements, design, development, verification and validation, testing and implementation of any given solution/project.

4. Document Terminology and Acronyms

Term Definition

Page 18


5. SQA Concepts and Definitions

5.1 Definitions

Software Quality Assurance (SQA) is defined as a planned and systematic approach to the evaluation of the quality and adherence to any agreed-upon software standards, processes and procedures.

Definition of Quality:(1) The degree to which a system, component or process meets specified requirements(2) The degree to which a system, component, or process meets customer needs or

expectations.

Quality is not tangible and is often considered unimportant in development. However, the odds of success are better if there’s a constructive quality process and testing lifecycle.

5.2 SQA Standards and ProceduresStandards are the established criteria to which the software products are compared. Procedures are the established criteria to which the development and control processes are compared. Standards and procedures establish the prescribed methods for developing software; the SQA role is to ensure their existence and adequacy. Proper documentation of standards and procedures is necessary since the SQA activities of process monitoring and product evaluation rely upon unequivocal definitions to measure project compliance.

5.3 StandardsTypes of standards include:

Documentation Standards will be the control will specify all quality assurance work for planning, control, and product documentation and provide consistency throughout LiveCycle of the project.

Design Standards. Provide rules and methods for translating the software requirements into the software design and for representing it in the design documentation.

Code Standards specify the language in which the code is to be written and define any restrictions on use of language features. They define legal language structures, style conventions, rules for data structures and interfaces, and internal code documentation.

5.4 ProceduresProcedures are explicit steps to be followed in carrying out a process. All processes should have documented procedures. Examples of processes for which procedures are needed are

Page 19


configuration management, problem reporting and corrective action, testing, code reviews, etc.

6.0 Iterative Development process approach (DSDM). At J&T Consultants, we adopted and customized to our needs the Dynamic System Development (DSDM) – a fairly modern, iterative, incremental, object-oriented methodology covering the full Software Development Life Cycle (SDLC).

With appropriate plug-ins, DSDM can be used as a basis for AGILE development processes.

DSDM supports iterative approach that addresses the highest risk items at every stage in the lifecycle, significantly reducing a project’s risk profile.

The development process can be divided into iterations – the periods of task-related work during which the problem-solving activities occur.

Iterations:

Iteration represents one complete pass through the lifecycle, intended to deliver a well-defined subset of system functionality that can deliver value to the end user.

• Inception• Elaboration• Construction• Transition

Activities:

• Analysis• Requirements• Design• Development• Verification and Validation/Testing• Deployment

Supporting Activities:

• Configuration and Change Management• Project Management• Environment

The iterations are not marked by the completion of activities, but by achieving a level of understanding of the problem and the solution.

Page 20


Why Incremental

Software development is sequential in the large, and iterative in the small. Certain steps, such as defining system architecture that must be significantly front loaded, in order to allow for the integration of all desired functionality.

DMSD addresses this necessity through the concept of increments. In incremental development, the team makes several passes through the basic SDLC and shows the iterations.

Figure 1 illustrates the relationship of the phases to the activities

Analysis

Requirements Design

DevelopmentVerification & Validation/Testing

DeploymentConfiguration &

Change ManagementProject Management

Environment

Page 21


Unit Testing Plan

Test ExecutionThe test execution phase for this project will validate all of the software/hardware builds

to ensure that the requirements have been met according to the expected results. Any defects

revealed through the testing environment will be documented and shared with all team members.

After the defect is rectified, the fixed code will be assimilated into the application and regression

testing will begin.

Regression Testing

All regression testing will be required to verify previous releases of the applications or

codes have passed all functional requirements. This is to ensure that the fixes don’t have new

defects that impact the application.

Integration TestingAll components will be tested as individual and modules in a test group to ensure the

combine services work as intended. This testing will be done as each component cleared the

testing phase. The goal is to test different combinations of the applications and interfaces until

the entire system is deployed into production.

Page 22


ID –

Num

ber

1.2.

1

Test Scenario Description #1(Setup U P S, Server blades, FAS 2240, CISCO Switches)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?

ALL STATED REQUIREMENTS EXIST AND FUNCTION

001

Hardware- build to support the Web Interface. Network platform will support the end-users by allowing them to access all applications. The goal is to have this system fully functional with no down time.

002SECURITY

003WBS – 1.4 (Client); WBS 1.4.1(Configure Internet protocols IPv4 properties)

DATA VALIDATION004 TBAENVIRONMENT005 Company’s development platform 006INTERFACES009 WBS 1.5 Web-based Interfaces (All)010

ID –

Num

ber

1.2.

2

Test Scenario Description #2(1.2.2 Install Cat5 and Fiber Cables to, Server blades, FAS 2240,

CISCO Switches) Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?ALL STATED REQUIREMENTS EXIST AND FUNCTION

001


002 Predecessors- WBS 1.2.1SECURITY


DATA VALIDATION004 TBAENVIRONMENT005 Company’s development platform 006INTERFACES

Page 23


ID –

Num

ber

1.2.

2Test Scenario Description #2

(1.2.2 Install Cat5 and Fiber Cables to, Server blades, FAS 2240, CISCO Switches) Te

st S

crip

t Re

fere

nce

Test

ing

Com

plet

e?

007 WBS 1.5 Web-based Interfaces (All)008

ID –

Num

ber

1.2.

3

Test Scenario Description #3(1.2.3 Configure RAIDS, LUNS and switch ports for operation)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001





ID –

Num

ber

1.3.

1

Test Scenario Description #4(1.3.1Installation of VMware Linux shell operating systems)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Hardware- build to support the Web Interface. Network platform will support the end-users by allowing them to access all applications. The goal is to have this system fully functional with no down time


Page 24


ID –

Num

ber

1.3.

1

Test Scenario Description #4(1.3.1Installation of VMware Linux shell operating systems)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?



Page 25


ID –

Num

ber

1.3.

2

Test Scenario Description #5(1.3.2 Installation of Virtual Machines with Microsoft 2008 R2 Server)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Hardware- build to support the Web Interface. Network platform will support the end-users by allowing them to access all applications. The goal is to have this system fully functional with no down time. Also ensure that all connected hardware and software are communicating with each other.




ID –

Num

ber

1.3.

3

Test Scenario Description #6(1.3.3 Setup and configure AD, DNS, Exchange, SQL, and SharePoint

servers) Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Hardware- build to support the Web Interface. Network platform will support the end-users by allowing them to access all applications. The goal is to have this system fully functional with no down time. Also ensure that all connected hardware and software are communicating with each other.



DATA VALIDATION004 TBAENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.5 Web-based Interfaces (All)

Page 26


ID –

Num

ber

1.3.

3Test Scenario Description #6

(1.3.3 Setup and configure AD, DNS, Exchange, SQL, and SharePoint servers) Te

st S

crip

t Re

fere

nce

Test

ing

Com

plet

e?

008

Page 27


ID –

Num

ber

1.3.

4

Test Scenario Description #7(1.3.4 Setup and configure Active Directory account logins and

permissions) Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Software and access functions to allow the end-users to access, edit, and store data. Goal to have a very secured system with using active directory and group policies to accomplish this.


003WBS – 1.4 (Client); WBS 1.4.1(Configure Internet protocols IPv4 properties)WBS-1.5.1


ID –

Num

ber

1.3.

5

Test Scenario Description #8(1.3.5 Data migration from old physical servers to new virtual servers)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001Move all legacy data from the old server over to the new server before going live. Keep a backup copy of data

002 Predecessors- WBS 1.1.9SECURITY003DATA VALIDATION

004• Back up data validate all records have been copied over to new server.• Leave old serve in-services as a backup

ENVIRONMENT

005Company’s development platform New platform

006INTERFACES007

Page 28


ID –

Num

ber

1.3.

5

Test Scenario Description #8(1.3.5 Data migration from old physical servers to new virtual servers)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?

008

Page 29


ID –

Num

ber

1.4.

1

Test Scenario Description #9(1.4.1 Install and setup Windows 7 Operating systems)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001Software install. Install Windows 7 OS. Test all applications that come with this system

002 Predecessors- WBS 1.4SECURITY003DATA VALIDATION004 TBAENVIRONMENT005 Servers and Desktops Computers 006INTERFACES007008

ID –

Num

ber

1.5.

2

Test Scenario Description #10(1.5.2 Build hierarchy navigation menu and fill in the blank search

options) Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001Build hierarchy and navigation menus and search engines. Goal to meet the end-users requirements for how they will interact with the Web site.




Page 30


ID –

Num

ber

1.4.

2

Test Scenario Description #11(Configure Internet Protocol IPv4properties)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001 In the Internet Protocol Version 4 (TCP/IPv4) Properties window, you will need to select "Use the following IP address" and "Use the following DNS server addresses:"

Enter in the corresponding settings per their section. If you don't have the settings, or need help with them, call into tech support so we can provide them to you.

Once the settings have been entered in, click ok on the Internet Protocol Version 4 (TCP/IPv4) Properties window, and then click on close on the Local Area Connections properties window.

At this point the Local Area Connection should say connected. See if you can browse to a web site at this time. If you are able to, your setup is complete. If you are not able to browse, call tech support, so they can verify your settings are correct.

Page 31

Using Static IPs prevents address conflicts between devices and allows you to manage them more easily. Assigning IPs to Windows is essentially the same process, but getting to where you need to be varies between each version.


ID –

Num

ber

1.4.

2

Test Scenario Description #11(Configure Internet Protocol IPv4properties)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

Now you can open the command prompt and do an ipconfig to see the network adapter settings have been successfully changed.

SECURITY

003

DATA VALIDATION

004

ENVIRONMENT

005 Company’s development platform

006

INTERFACES

007 Network and Internet – Local Area Connection

Page 32


ID –

Num

ber

1.4.

3

Test Scenario Description #12(Configure User accounts and connect to the AD DOMAIN server)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001

Mapping your application process to a Windows domain user account requires that you configure the following:

• The Web server.

You must make sure that the Windows domain user account that you specify has sufficient user rights (but no more) to run a Web application.

• Your application.

You must configure the Web.config file for ASP.NET to recognize the domain user account name.

• A connection string.

When you create connection strings for connection objects in your application, you have to specify that the connection strings will use Windows integrated security.

• SQL Server.

You must add the specified domain user account as a SQL Server login user.

SECURITY

003

To use Windows integrated security in a connection string• When you create a connection string for your application, do

not include a user name and password. Instead, for the connection string, set the Integrated Security attribute to SSPI.

The following example shows a connection string that includes the appropriate attributes: data source=myserver;initial catalog=northwind;Integrated Security=SSPI

DATA VALIDATION

004

ENVIRONMENT


Page 33


ID –

Num

ber

1.4.

3

Test Scenario Description #12(Configure User accounts and connect to the AD DOMAIN server)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

006

INTERFACES

007 Server

ID –

Num

ber

1.4.

4

Test Scenario Description #13(Configure Web Browser with security, internet options and protection)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001 Microsoft Internet Explorer 10

Internet-explorer-privacy These settings can be accessed through the “Internet Options” menu.

Configure security settings: Under the “Security” tab, do the following:

Set security zones: IE offers the option to configure different security settings for different “zones,” including the Internet, local intranet, trusted sites, and restricted sites. Set up the zones for Intranet, Trusted Sites, and Restricted sites to your desired security level.

Set Internet zone security to “Medium High” or higher. This blocks certain cookie types, enables ActiveX filtering, and implements several other default settings for increased security.

Disable javaScript: Click “Custom Level,” locate the “Active Scripting” setting, and select “Disable.” It is recommended that users disable JavaScript because of the high amount of vulnerabilities it contains.

Automatically clear history: Select “Delete browsing history on exit” under the “General” tab. Clearing your history at the end of each session helps to limit the amount of information IE saves when you browse.

Configure privacy settings: Under the “Privacy” tab, complete the following steps:

Privacy setting: Set the Internet zone privacy to “Medium High” or higher. This blocks certain cookie types to prevent sites from tracking or contacting you without your consent.

Page 34


ID –

Num

ber

1.4.

4

Test Scenario Description #13(Configure Web Browser with security, internet options and protection)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

Location: Select “Never allow websites to request your physical location.”

Pop-up Blocker: Double check that Pop-up Blocker is enabled.

Configure Advanced Security settings: Scroll down to the “Security” section under the “Advanced” tab and do the following:

Ensure that all default settings are in place. If you aren’t sure, click “Restore advanced settings” before making any other changes.

Select “Do not save encrypted pages to disk.” This will delete files cached from HTTPS pages when the browser is closed.

Select “Empty Temporary Internet Files folder when browser is closed.” This prevents IE from storing your personal info (logins, passwords, activity, etc) beyond your browsing session.

Turn off AutoComplete: The AutoComplete feature should be turned off for forms and usernames/passwords. Keeping AutoComplete turned off ensures that your sensitive information isn’t being stored unnecessarily.

Tracking protection: IE’s Tracking Protection feature keeps your browsing private from specified third-party websites. This feature can be accessed through IE’s “Safety” menu. In order to use Tracking Protection you will need to provide a Tracking Protection List that names all of the sites you don’t want your information being sent to. You can create a list yourself or download lists online.

002Predecessors- WBS 1.4.3 Configure User accounts and connect to the AD DOMAIN server

SECURITY

003 Will be set during the configuration

DATA VALIDATION

004 NA

ENVIRONMENT


INTERFACES

007 Internet Explorer and Microsoft office interaction

Page 35


ID –

Num

ber

1.5.

3

Test Scenario Description #14(Organizational Site graphics and easily Usable layout)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001 1. The screen density is appropriate for the target users and their

tasks.

2. The layout helps focus attention on what to do next.

3. On all pages, the most important information (such as frequently

used topics, features and functions) is presented on the first screenful

of information ("above the fold").

4. The site can be used without scrolling horizontally.

5. Things that are clickable (like buttons) are obviously pressable.

6. Items that aren't clickable do not have characteristics that suggest

that they are.

7. The functionality of buttons and controls is obvious from their labels

or from their design.

8. Clickable images include redundant text labels (i.e. there is no

'mystery meat' navigation).

9. Hypertext links are easy to identify (e.g. underlined) without needing

to 'minesweep'.

10. Fonts are used consistently.

11. The relationship between controls and their actions is obvious.

12. Icons and graphics are standard and/or intuitive (concrete and

familiar).

13. There is a clear visual "starting point" to every page.

Page 36


ID –

Num

ber

1.5.

3


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

14. Each page on the site shares a consistent layout.

15. Pages on the site are formatted for printing, or there is a printer-

friendly version.

16. Buttons and links show that they have been clicked.

17. GUI components (like radio buttons and check boxes) are used

appropriately .

18. Fonts are readable.

19. The site avoids italicised text and uses underlining only for hypertext

links.

20. There is a good balance between information density and use of

white space.

21. The site is pleasant to look at.

22. Pages are free of "scroll stoppers" (headings or page elements that

create the illusion that users have reached the top or bottom of a

page when they have not).

23. The site avoids extensive use of upper case text.

24. The site has a consistent, clearly recognizable look and feel that will

engage users.

25. Saturated blue is avoided for fine detail (e.g. text, thin lines and

symbols).

26. Color is used to structure and group items on the page.

27. Graphics will not be confused with banner ads.

Page 37


ID –

Num

ber

1.5.

3


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

28. Emboldening is used to emphasize important topic categories .

29. On content pages, line lengths are neither too short (<50 characters

per line) nor too long (>100 characters per line) when viewed in a

standard browser width window.

30. Pages have been designed to an underlying grid, with items and

widgets aligned both horizontally and vertically.

31. Meaningful labels, effective background colors and appropriate use

of borders and white space help users identify a set of items as a

discrete functional block.

32. The colors work well together and complicated backgrounds are

avoided.

33. Individual pages are free of clutter and irrelevant information.

34. Standard elements (such as page titles, site navigation, page

navigation, privacy policy etc.) are easy to locate.

35. The organization’s logo is placed in the same location on every

page, and clicking the logo returns the user to the most logical page

(e.g. the home page).

36. Attention-attracting features (such as animation, bold colors and size

differentials) are used sparingly and only where relevant.

37. Icons are visually and conceptually distinct yet still harmonious

(clearly part of the same family).

38. Related information and functions are clustered together, and each

group can be scanned in a single fixation (5-deg, about 4.4cm

diameter circle on screen)

Page 38


ID –

Num

ber

1.5.

3


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

SECURITY

003 NA

DATA VALIDATION

004 TBA

ENVIRONMENT


INTERFACES

007 WBS 1.5 Web-based Interfaces

Page 39


ID –

Num

ber

1.5.

4

Test Scenario Description #15(Outlook Calendar Interaction)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001

Interactions Portlet (requires Client Management module)

Goal: The interactions Portlet lists all interactions with the staff member. Among the interactions may be emails to or from the staff member that are in the designated Outlook public folder.

An email interaction is designated in the list of interactions by an

open envelope icon .

Click on the email interaction to open it in an outlook email window from which you can perform any function on the email that you can in Outlook.

Click on the header of the portlet to view the Interactions screen in Manage Clients (if permitted by security) where you can view all email interactions in the public folder.

SECURITY

003NA

DATA VALIDATION

004 TBA

ENVIRONMENT


INTERFACES

007 Internet Explorer and Microsoft office interaction

008

Page 40


ID –

Num

ber

1.5.

5

Test Scenario Description #16(Document library for data storage)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001 Adding one or more data connection for the document library running on the server using MS Windows and SharePoint Service.

Goal validate the following:

• The location of the SharePoint site and the necessary permissions to access it

• Verification that the site is configured so that your users can get data from the

document library or list

• Verification that you can store the data from the document library or list on your

users' computers for offline use

To allow users to query data from a document library or list on a site that is located on a

server running Microsoft Windows SharePoint Services, you need to do the following in the

form template:

Add a secondary data connection.

2. Configure the form template to use the secondary data connection.

1. On the Tools menu, click Data Connections.

2. In the Data Connections dialog box, click Add.

3. In the Data Connection Wizard, click Create a new connection to,

click Receive data, and then click Next.

4. On the next page of the wizard, click SharePoint library or list, and

then click Next.

Page 41


ID –

Num

ber

1.5.

5


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

5. On the next page of the wizard, type the URL of the SharePoint site

with the document library or list, and then click Next. For example, to use a

document list on a SharePoint site with the

URLhttp://www.adventureworks.com/EmployeeList, you

type http://www.adventureworks.com/EmployeeList.

6. On the next page of the wizard, in the Select a list or library list, click

the list or library that you want to use, and then click Next.

7. On the next page of the wizard, select the check boxes next to the

values that you want to receive. If the form template will be published to the

document library, and you want forms that are based on this form template to get

metadata about the form, select the Include data for the active form

only check box.

8. Click Next.

9. If you want to store the results of the query with the form template,

select the Store a copy of the data in the form template check box. Selecting

this check box stores the query results in the form template. Because the data is

stored in the form template, the data is available in the forms that users fill out,

even if their computers are not connected to a network.

SECURITY Selecting this check box stores the query results in the form

template. Because the data is stored in the form template, it is available in the

forms that users fill out, even if their computers are not connected to a network.

If you are getting sensitive data from this data connection, you may want to

Page 42


ID –

Num

ber

1.5.

5


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

disable this feature to help protect the data in case the computer is lost or stolen.

10. Click Next.

11. On the next page of the wizard, in the Enter a name for this data

connection box, type a descriptive name for this secondary data connection.

This is the name that appears in the Data source list in theData source task

pane. If you want this query to run automatically whenever the form is opened

by a user, select the Automatically retrieve data when form is opened check

box

SECURITY

003 In current setup

DATA VALIDATION

004

ENVIRONMENT

005 Company’s development platform/ Server

INTERFACES

007 SharePoint

Page 43


ID –

Num

ber

1.5.

6

Test Scenario Description #17(Document review, check-in and check-out user requirements)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001 Goal -To enable force check-out:

1. As a Site Owner, navigate to the document library.

2. In the Ribbon Bar, click the Library tab.

3. In the Ribbon Bar in the Settings group, click Library Settings.

4. In the General Settings section, click Versioning settings.

5. The last option is Require Check Out. Ensure Yes is selected.

Page 44


ID –

Num

ber

1.5.

6


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

Users will now be unable to edit documents unless they first check the

document out. While the document is checked out, no one else will be able

to make edits.

Check this Out in Action

So how does this all work?

When a user views a document that is not checked out, SharePoint will

remind them it cannot be edited until it is. This reminder surfaces in different

ways. One way is by a message box like this:

A user has to choose Check Out and Edit and the document is automatically

checked out for them.

Another way users are informed is directly from inside the application, as

shown here:

Page 45


ID –

Num

ber

1.5.

6


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

Just click Check Out and the document is ready for editing.

So now when a user browses to the library, they will see the green-arrow on

the document indicating it is checked out. If they hover the mouse over the

icon, it will display the user who has checked out the item.

Saving

So the user who has checked out the document makes their edits. When

completed, they now need to save the document back to SharePoint and

ensure the document is checked-in so others are able to assist in the search.

This is pretty easy to do. It can be done by first Saving the document as

normal, and then Check-In the document from the client application. In the

Ribbon bar, click File. Click Info.

Page 46


ID –

Num

ber

1.5.

6


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

What’s really helpful is that you’ll be reminded to check the document back

in if you forget. So if you don’t check in the document, when you attempt to

exit Word (in this example), you’ll see a message box like this:

Click Yes and the document is checked in, ready for someone else to edit.

002 Predecessors- WBS 1.3.3

SECURITY

003WBS – 1.4 (Client); WBS 1.4.1(Configure Internet protocols IPv4 properties)WBS-1.5.1

DATA VALIDATION

004 TBA

ENVIRONMENT


006

Page 47


ID –

Num

ber

1.5.

6


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

INTERFACES

007 WBS 1.5 Web-based Interfaces (All)

008

Page 48


ID –

Num

ber

1.5.

7

Test Scenario Description #18(Internet Explorer and Microsoft office interaction)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001 Test add-ons between both platforms and software applications.

Also we need to check ActiveX controls

Generate the CSR

1. Access the IIS Microsoft Management Console (MMC). To do this, right-click My Computer and click Manage. This opens the Computer Management Console. Expand the Services and Application section. Locate Internet Information Services and expand the IIS console.

2. Select the specific Web site on which you want to install a server certificate. Right-click the site and click Properties.

3. Click the Directory Security tab. In the Secure Communications section, click Server Certificate. This starts the Web Server Certificate Wizard. Click Next.

4. Select Create a New Certificate and click Next.

5. Select Prepare the request now, but send it later and click Next.

6. In the Name field, enter a name that you can remember. It will default to the name of the Web site for which you are generating the CSR.NOTE: When you generate the CSR, you need to specify a bit length. The bit length of the encryption key determines the strength of the encrypted certificate which you send to the third-party CA. The higher the bit length, the stronger the encryption. Most third-party CAs prefer a minimum of 1024 bits.

7. In the Organization Information section, enter your organization and organizational unit information. This must be accurate, because you are presenting these credentials to a third-party CA and you must comply with their licensing of the certificate. Click Next to access the Your Site's Common Name section.

8. The Your Site's Common Name section is responsible for binding the certificate to your Web site. For SSL certificates, enter the host computer name with the domain name. For Intranet servers, you may use the NetBIOS name of the computer that is hosting the site. Click Next to access geographical information.

9. Enter your country, state or province, and country or region information. Completely spell out your state or province and country or region; do not use abbreviations. Click Next.

Page 49


ID –

Num

ber

1.5.

7


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

10. Save the file as a .txt file.

11. Confirm your request details. Click Next to finish, and exit the Web Server Certificate Wizard.

002 Predecessors- WBS 1.1.9

SECURITY

003

Grouping Sets of Sites Together

Zone security is a system that enables you to divide online content into categories, or zones.

You can assign specific Web sites to each zone, depending on how much you trust the content

of each site. The Web content can be anything from an HTML or graphics file to a

Microsoft® ActiveX® control, Java applet, or executable file.

Important You should configure the Local intranet zone to correspond to the particular

network and firewall configuration of your organization. The default settings for the Local

intranet zone cannot be guaranteed to match your network configuration, and there is no

method for automatically detecting your firewall and configuring the zone based on your

specific settings. For more information, see "Setting Up Security Zones" later in this chapter.

Internet Explorer includes the following predefined security zones:

• Local intranet zone. The Local intranet zone includes all sites inside an

organization's firewall (for computers connected to a local network).

• Trusted sites zone. The Trusted sites zone can include all Internet sites that you

know are trusted. For example, the Trusted sites zone might contain corporate

subsidiaries' sites or the site of a trusted business partner.

• Internet zone. The Internet zone includes all sites on the Internet that are not in the

Trusted sites or Restricted sites zones.

• Restricted sites zone. The Restricted sites zone can include all sites that you do not

trust.

DATA VALIDATION

004

ENVIRONMENT

005 Desktops; Web Site and Server

INTERFACES

Page 50


ID –

Num

ber

1.5.

7


Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?

007 Desktops; Web Site and Server

Page 51


ID –

Num

ber

1.1.

7

Test Scenario Description #19(Develop Prototype Web site)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001

We will use Solidify. http://www.solidifyapp.com/

Solidify is a very simple and fast way to prototype any interface design and allows you to get user testing feedback on all devices.

Test Concepts Early

Quickly test ideas through free form or heuristic tests without investing any time into development.

Validate InteractionsSee if users are able to accomplish a specific task and ask what they thought about your idea.

Conduct a User TestCollect data on how users interact with your prototype through a remote or in-person user test

Get Unbiased ResultsUse our network of user testers to purchase quality results from a demographically diverse audience

SECURITY

003 NA

DATA VALIDATION

004 NA

ENVIRONMENT

005 http://www.solidifyapp.com/

INTERFACES

Page 52

http://www.solidifyapp.com/

http://www.solidifyapp.com/


ID –

Num

ber

1.5.

9

Test Scenario Description #20(Publish Web Site)

Test

Scr

ipt

Refe

renc

e Test

ing

Com

plet

e?


001

All WBS structures have been tested individually and some with other components.

• In a development environment roll out beta version of the project.

• Identify a test user group

• Run test pilot for 30 days.

• Fix any issues that were found in the test pilot.

• Run test pilot for two weeks

002

SECURITY

003

DATA VALIDATION

004 All

ENVIRONMENT


INTERFACES

007 Project Platform

Page 53


ID –

Num

ber

1.2.

1

Test Scenario Description #1(1..5.8 Logout Requirements for SharePoint)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Software- build to support the Web Interface. Network platform will support the end-users by allowing them to logout of the SharePoint application. The goal is to exit the SharePoint application.

002SECURITY

003WBS – 1.4 (Client); WBS 1.5.6(Document review, check-in and check-out user requirements

DATA VALIDATION004 • Logout of SharePointENVIRONMENT005 Company’s development platform 006INTERFACES009 WBS 1.5 Web-based Interfaces (All)010

ID –

Num

ber

1.2.

2

Test Scenario Description #2(1.5.8.1 Logout requirements Web Brower and Client laptop)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Software- build to support the Web Interface. Network platform will support the end-users by allowing them to logout of all applications and client platform. The goal is to end the web browser use and logout of client operating system.


003WBS – 1.4 (Client); WBS 1.5.8(Logout requirements)

DATA VALIDATION004 • Close web browser and logout of operating systemENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.5 Web-based Interfaces (All)008

Page 54


ID –

Num

ber

1.2.

2

Test Scenario Description #2(1.5.8.1 Logout requirements Web Brower and Client laptop)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


ID –

Num

ber

1.2.

3

Test Scenario Description #3(1.1.10 Project review Introduction, research, requirement gathering,

end-users interviews Weekly progress notes and project changes) Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Review all researched processes, gathered requirements, and end-user interviews to ensure all requested goals and objectives have been meet. The goal is to confirm customers requirements, objectives, scope and goals have been meet with the completion of the project

002 Predecessors- WBS 1.1.2, WBS 1.1.4, WBS 1.1.5SECURITY


DATA VALIDATION

004• Review Introduction notes, all research guidance, gathered requirements,

end-user input, and weekly progress reports and change requestENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.1.1 Initial Kick-off meeting008

ID –

Num

ber

1.3.

1

Test Scenario Description #4(1.1.10.1 Project review Hardware upgrades)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Hardware- build to support all server operating systems and the Web Interface. Network platform will support the end-users by allowing them to access all applications. The goal is to review all hardware device systems and ensure they are fully functional with no down time

002 Predecessors- WBS 1.2.1, WBS 1.2.2, WBS 1.2.3SECURITY

003WBS – 1.2 (hardware); WBS 1.2.1(Setup U P S, Server blades, FAS 2240, CISCO Switches)

DATA VALIDATION

Page 55


ID –

Num

ber

1.3.

1

Test Scenario Description #4(1.1.10.1 Project review Hardware upgrades)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?

ALL STATED REQUIREMENTS EXIST AND FUNCTION004 • Review all hardware upgradesENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.2 Hardware training build 008

ID –

Num

ber

1.3.

2

Test Scenario Description #5(1.1.10.2 Project review Software upgrades)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Software- build to support the units operational requirements. Network platform will support the end-users by allowing them to access Web Browser and SharePoint applications. The goal is to review installation, setup, and configurations of all software operating systems and ensure all is fully functional with no down time. Also ensure that all connected hardware and software are communicating with each other.

002 Predecessors- WBS 1.2SECURITY

003WBS – 1.4 (Client); WBS 1.3(Software training build)

DATA VALIDATION004 • Review all software upgradesENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.3 Software training build 008

ID –

Num

ber

1.3.

3

Test Scenario Description #6(1.1.10.3 Project review Client Setup and configurations)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?

ALL STATED REQUIREMENTS EXIST AND FUNCTION001 Software- build to support the users operations. Client platform will support the

end-users by allowing them to access all applications. The goal is to review the Client system setup and configurations to ensure system is fully functional with no

Page 56


ID –

Num

ber

1.3.

3

Test Scenario Description #6(1.1.10.3 Project review Client Setup and configurations)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?

ALL STATED REQUIREMENTS EXIST AND FUNCTIONdown time. Also ensure that all connected hardware and software are communicating with each other.



DATA VALIDATION004 • Review client operation functionalityENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.4 client setup configurations, 1.5 Web-based Interfaces (All)008

ID –

Num

ber

1.3.

4

Test Scenario Description #7(1.1.10.4 Project review Data Migration to Hotspot disaster recovery

location) Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Software migrations of all operating systems backup, snapshot or replications of data to ensure disaster recovery capabilities of current operating systems. Goal to backed up, snapshot, and replicated data at the hotspot disaster recovery site to ensure recovery capabilities in case of hardware failures or corrupted data files or databases


003WBS – 1.2, 1.3, WBS 1.3.5(Data migration from old physical servers to new virtual servers ) WBS 1.4 (Client), and WBS-1.5.1

DATA VALIDATION004 • Ensure all backups, snapshots and replications are current and accessibleENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.5 Web-based Interfaces (All)008

Page 57


ID –

Num

ber

1.3.

5

Test Scenario Description #8(1.1.10.5 Project review Web-based Interface)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Access SharePoint server through the Internet Explorer, Chrome, or Mozilla Firefox web browsers. Ensure Site access, layout, graphics outlook calendar, document library all meet the customers wants and needs and the finished results meets customers goals and objectives

002 Predecessors- WBS 1.5SECURITY003 WBS 1.3.5 (Data Migration from old physical servers to new virtual servers)DATA VALIDATION

004• Back up data validate all records have been copied over to new server.• Leave old serve in-services as a backup

ENVIRONMENT

005Company’s development platform

006INTERFACES007008

Page 58


ID –

Num

ber

1.4.

1

Test Scenario Description #9(1.1.11 Final Implement Changes)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001Review and make all customer requested changes to all aspects of the current project

002 Predecessors- WBS 1.1.10SECURITY003DATA VALIDATION004 • Make and confirm all customer changes have been meetENVIRONMENT005 Administration, Hardware, Software, Client, and Web-based interfacing 006INTERFACES007 WBS 1.1 Administrative008

ID –

Num

ber

1.5.

2

Test Scenario Description #10(1.1.12 Distribute Documentation Documents.)

Test

Scr

ipt

Refe

renc

e

Test

ing

Com

plet

e?


001

Distribute User Manual, Administration Manual, and Content Standards are given to Stakeholders and end-users to provide help in using, maintaining and setting policies and procedures for the customer. Goal to meet the end-users requirements for how they will interact with all stages of Upgrade support.

002 Predecessors- WBS 1.1.11SECURITY003 WBS – 1.1.4 (Requirement Gathering), WBS 1.1.5 (End-user interviews)DATA VALIDATION004 • Distribute Documentation DocumentsENVIRONMENT005 Company’s development platform 006INTERFACES007 WBS 1.1 Administration008

Page 59


Quality Metrics

QA Check List Level 2 Items (WBS)

ItemNo.

Item Planning Status ¹

Risk Level ²

Comments / Plan to Resolve

1 Does the QA program have documented Quality targets?

2 Is there agreement on the Quality targets?

3 Has staff been assigned specifically to maintain program quality?

4 Is there agreement on how important QA is in this scope of the project?

5 Is there a document and agreed upon change management plan for the QA

6 Is there a process in place to identify and terminate task of low value (e.g. anticipated ROI has declined?)

¹ Enter one of the following: C (Complete), P (Partially Complete), A (Absent); Y (Yes), N (No), NA (Not Applicable)² Enter one of the following: H (High), M (Medium), L (Low); A (Absent),

Page 60


System Defects

During the course of this project our teams will be faced with several challenges and

some of those may include defects. Defects will be measured starting at initial discussions on the

project and will be measured all the way through. Defect measurement is vital to the success of

the project and will be implemented into the quality assurance plan. During this project there are

defects that may happen such as a certain section of the code not working correctly or the

hardware coming in damaged. The process of measuring defects during this project will be

accomplished by all team members involved with the project.

Hardware delivery is an important time to start the process of measuring defects. During

transit hardware can be damaged and this damage can be noticed by a damaged box or may not

be found until further inspection of the package. When the product is first delivered it will be

visually inspected for further damage and will be noted on the delivery ticket. If an employee

notices outer damage to the packaging than they will proceed to open package to ensure no

damage to the internal unit. During the process of installation and damage is found at that time

than the technician who noticed damage will document and tell the project manager. All delivery

defect documents will be scanned and then immediately contact vendor to get replacement

hardware to prevent downtime due to damaged hardware (Mosaic, n.d.).

Page 61


Hardware Damage DocumentDate Serial Number Model

NumberDescription of damage

Risk to Project

Employee Name

12/2/2014 JN167DF HP SDL380 Server blades

Rail connectors damaged preventing installation in rack

Very High Tyson Weiss

Source: Fictitious data, for illustration purposes only

Defects will also be measured on the software and the implementation of the software in

the customer’s infrastructure. As the systems are being set up and software is being activated and

utilized the technicians may face various defects with the software. Each defect will be

documented and relayed to the project manager so they can work on rectifying the defects. The

defects will be rated for severity as it pertains to the progress of the project. These defects will

also come with an option to include quick resolution to rectify the defect (Mosaic, n.d.).

Page 62


Software DefectsDate Product Defect Risk to

Project ProgressLow – Very High

Quick Resolution

Employee Name

12/2/2014 Windows 7 Cannot activate OS

High Enter license key from case

Tyson Weiss


Now not all defects will be noticed during delivery or even during initial install.

Hardware can show defects after being up and running for a while such as faulty hard drive or

faulty memory or even bad power supplies. These defects do not develop until the machine has

been up and running for a while and that is the reason for having warranties on all hardware

components. Software can show defects such as certain data libraries becoming corrupted or

missing which means a repair or reinstall of the software. Another defect could include the

software not working with other programs they run and the printers they may have on site. Since

these defects do not appear until after installation than the company will have active defects and

Page 63


will be documented, relayed to project manager and rectified as quickly as possible (Mosaic,

n.d.).

Active DefectsDate Hardware /

SoftwareDescrip of Product

Descrip of Defect

Risk to company production

Resolution Employee Name

12/2/2014 Hardware HP SDL380 Server blades

Bad stick of memory

Medium RMA stick from vendor

Tyson Weiss


Risk Management Strategy

Page 64


J&T Consultants will utilize a simple risk management strategy plan to ensure that risks

are identified and worked on before the project even begins. All risks will be researched at each

level of the project and will include feedback from all team members involved in the project.

These risks may or may not actually occur during the project but it is always better to be

prepared ahead of time than trying to deal with the risk while under pressure. Fail over plans will

be included into the risk management plan to prevent the whole system coming down and

causing downtime for the company. As risks are identified they will be documented and

delivered to all team members so they are all on the same track. Also to see if any other members

can come up with solutions on how to prevent or rectify the risk. These risks will be prioritized

weekly at the meetings and also discussed to see which ones have been avoided or rectified and

the steps taken to accomplish it.

There are five key steps to the risk management plan that J&T consultants will follow:

• Identify Risk

• Assess the Risk

• Develop Plan

• Implement Plan

• Communication

Each risk will go through the process of these five steps and will be documented until the risk

is resolved. These risks will be monitored weekly with Tyson Weiss as the point of contact. If

new risks appear they will be documented and relayed to Tyson Weiss, who will than add to Risk

Management document and email to all members of the project. Tyson will also take all notes,

Page 65


changes to the existing document and update it and email to all members as well. The

resolutions will be added into a knowledgebase monitored by Tyson Weiss for J&T Consultants

in the vent they face the same risks during the project or even other projects (prince2primer,

2014).

Risk Management DocumentDate Identify Risk Projected

or Actual PriorityLow - High

Resolution Employee Name

12/2/2014

No elevator Actual High Higher more help to carry rack and equip in

Tyson Weiss

12/2/2014

Fire Projected High Offsite backup and hot site ready for deployment

Tyson Weiss


Page 66


Section 8 – Document Plan

Documentation PlanSharePoint Web-based Interactive Data Storage Web Site

Page 67

running head DRAFT KEY ASSIGNMENT 68

Table of ContentsProject Plan......................................................................................................................................3

Detailed Content Plan....................................................................................................................71

Timeline and Milestones................................................................................................................74

The Project will be completed on the set end date, on time and within budget. There were no serious quality assurance issues during this project all rsik were identified and steps were used to repair or replace any hardware, software or operational application issues .................................78

Attachment B SharePoint Administrator Manual (Training guide) Outline (Skeleton)................92

Attachment C SharePoint SharePoint Content Standards (Policies and Procedures) Outline (Skeleton).......................................................................................................................................93

References......................................................................................................................................96

Documentation Overview

Project ScopeThe overall project plan is to conduct a life cycle hardware and software upgrade as well

as design and develop a web-based interactive data storage database web site. This web site will use a document library to store all Intel information in a Structured Query Language (SQL) database management system. This DMS will to replace the old physical Data shared hard drive server.

Project ObjectivesThe project objective will cover the development of three different documents that will be

vital to every user, administrator, and management resource. The documents that will be developed for this project is an SharePoint user manual (instructional guide)l, SharePoint administration manual (training guide) and SharePoint content standards (policy and procedure) documents. These documents will pertain to the web-based interactive data storage database web site document library.

Documentation Scope and ObjectivesThe plan is to provide three SharePoint documentations that cover the user manual which

is the instructional guide that is provided with any developed system, software application or project. This guide gives detail use instructions in both textual and graphic visualization. In layman terms it is a step by step user instruction material with screenshots of the application to ensure the user knows how to use the program. The next one is an administrators manual which is also known as a training guide because it is used to refresh the technicians and maintenance managers maintaining techniques of a program. Lastly the SharePoint content standards (policies and procedures) which delegates how SharePoint must be used dealing with database content management.

Each of these are first created in a draft form at the beginning of the application development stage in the design and implementation phase of the System life cycle development plan. Once the program has been through the quality assurance process and tested to ensure that


each step functions in the described manner then the draft guides are reviewed and formalized for production of the documentation. each of these documentations will routinely go through review until the application development is ready for distribution and just before the application is finished the documents will be review for distribution as well along with the project, but never stop because of application error patching and application revisions. Each will be distributed in a PDF format document that will be titled Software User Manual (SUM), Software Administration Manual (SAM), and SharePoint Content Standards, policies and procedures.

All issued documentation will continue to be reviewed as the software errors, bugs and malfunctions are found and fixed and will be updated to reflect the proper operating steps through all software packet additions, patch changes, security updates, and software revisions. Since these documents are digital format it is vital that all user's store them in a directory on the local user desktop for use and review. As updates and changes are conducted to these three documents the users will be notified by mail, email, and vendor notifications.

All three of these documents will be developed with ease-of-use and user satisfaction in mind. They will all have the capability to achieve change management goals as the organizations goals change. Will be developed and reviewed to validate a thoroughness and logical flow design. Lastly they will comply with usability provision, trademark, intellectual property, and rigid guidelines.

Page 69

Outline of Deliverables

Deliverable Purpose AudienceOutput Media

Writer/Owner

SME Reviewers

Start Date

Pub Date

Notes

User Manual

(Instructional Guide)

Provide conceptual and procedural information on performing actions associated with the quick start and Use of a web site

All users of the software:

PDF

Print

Stakeholder Action Officer

Project Manager

25 Oct 2014

15 Nov 2014

All cautions and front matter to be reviewed by Legal.

Administrator Guide (Training Guide)

Provide conceptual and procedural information on performing actions based on administration and training techniques

Administrators and trainers

PDF

Print


Project Manager

25 Oct 2014

15 Nov 2014

SharePoint Content Standards (Policies and Procedures)

Provide use, administration, and development for organizations using the software.

All users of the software. administrators, and management

PDF

Dynamic HTML


Project Manager

Administrators, site administrators, and users

9 Nov 2014

15 Nov 2014

Business Document Shell 71

Detailed Content Plan

Deliverable 1: User Manual (Instructional guide)

Goals and Objectives

This document will provide both textual and graphical step by step user instructions on how to operate the SharePoint web-based interactive data storage database web site. It will provide instructions how to use the web browser to connect to the web site using either the Internet Protocol (IP) address or the alias site name. Once connected to the site it will provide login access, management console instructions, navigation techniques using the navigation menu and search option window. It will complete user steps in using the application as well as the use of a help function. The User manual will provide guidance, both theoretical and procedural, to assist the user in performing all tasks related with accessing the application, using passwords, navigating the design and layout, using data storage site and saving work to the content management database. user manual (instructional guide) will be created as a PDF file of 50 pages or less.

Audience

DOMAIN SharePoint usersAll SharePoint users who must access to the website to perform work, collaborate data

and access intelligence data routinely performing regular entries of transactions, review and approvals, and month-end reporting are the primary audiences.

Approach

This deliverable will be developed using concrete content procedures and task for setting up the application to suit the individuals workspace needs. User will affect the development of this documentation as errors and bugs during use are discovered. No detailed reference information is expected in this deliverable.

Initial Outline

The content of this document will provide step by step use of functions and features by the SharePoint user. This document will provide an overview of the application, all safety warnings, use of web browser applications to access the web site, then use their individual DOMAIN username and password to gain access and then maneuver around the site using the navigation menu or the search option until they find the interactive data storage site where they will save and check in any data, review existing data and check out and copy all stored data to their local system for use. it will have application window screen shots along with the textual procedures for completing every required task to operate SharePoint web site. The web site application will collate directly with the use of storing of and manipulation of intelligence information into a web based interactive data storage database web site an along with deliverable 1 User manual of the outline of deliverables.

Please see Attachment A as the initial outline of the SharePoint user manual (instructional guide)


Deliverable 2: Administrator Manual (Training guide)


This document will provide textual and graphical administration and management instructions on how to create a SharePoint web-based interactive data storage database web site. It will provide instructions how to create the type of site, design, layout, web part usage, and access permissions for the web site and all sub sites. The administrator will use the management console to setup, configure, link, navigate and workflow techniques used by all users and user administrators. This manual will show how to layout web parts in column format and add specific document libraries, picture, image and video libraries, announcements, user restrictions and permissions, file size use and site properties as well as user preferences. This administrators manual will provide training guidance, both theoretical and procedural, to assist the administrator in performing all tasks related with managing the application and web site environment used in data storage site and saving work to the content management database. The Administrator manual (Training guide) will be created as a PDF file of 50 pages or less.

Audience

SharePoint primary application administrators and site administratorsAll SharePoint administrators that require application management and site specific

administration who must access to the website to perform create user specific web sites, manage web site layouts, functionalities, web part features and the management of the SharePoint Structured Query Language (SQL) content database in order to access intelligence data routinely performing regular entries of transactions, review and approvals, maintain site structures, and conduct routine database snapshots, backups, data migration, and month-end reporting are the primary audiences.

Approach

This deliverable will be developed using concrete content procedures and task for managing the application, setting user and site administrators access permissions, website layouts and design, workflow workspaces to suit the individuals user needs. Administrators and site administrators will affect the development of this documentation as errors and bugs during use are discovered. No detailed reference information is expected in this deliverable.

Initial Outline

The content of this document will be step by step technical functions and features for creating, designing, layout, security, console configuration and content management of the SharePoint server front end application and backend SQL database management system that collate directly with the use of storing of and manipulation of intelligence information into a web based interactive data storage database web site. The administrator will use the SharePoint management console to provide user and site administrators access to connect with the web site, then use permission setting for users and sites so individual DOMAIN username and password to gain access and then maneuver around the site using the navigation menu or the search option until they find the interactive data storage site where they will save and check in any data, review existing data and check out and copy all stored data to their local system for use.

Please see Attachment A as the initial outline of the SharePoint administrator manual (Training guide)


Deliverable 3: SharePoint Content Standards (Policies and procedures)


This document will provide operational administration and management standards that must be upheld when using SharePoint application and managing the contents of the SQL database for the new web based interactive data storage web site. The use of this document will set standards for the use, privacy, copyright, records intention, confidentiality and security of the content. It will stipulate content owners and contributors, application configurations, features, and forums. It mandates document, and homepage standards, site definitions, navigational techniques, site layouts and designs. It provides standards for the use of web parts, pictures, and medias. lastly it covers ratings site standards, social tagging, status updates, user profiles and quality assurance requirements.

Audience

Organization Management, Technical team, SharePoint administrators, site administrators, and all SharePoint users.

Approach

This deliverable will be developed to stipulate regulatory and operational standards for use , administration, management, and oversight of all intelligence content material loaded into the SharePoint web based interactive data storage web site. It provides all standards required in the operation of SharePoint server, SQL server and user web browser interfacing with the content management database. Using these standards will help in managing the application, setting user and site administrators access permissions, website layouts and design, workflow workspaces to suit the individuals user needs. Administrators and site administrators will affect the development of this documentation as errors and bugs during use are discovered. No detailed reference information is expected in this deliverable.

Initial Outline

The content of this document are the content standards for using and operating the SharePoint server, SQL database management system, and accessing the SharePoint web site using the web browser of any local user system. It cover all standards, ownership, security and a multitude of functional requirements, policies and procedures while using SharePoint.

Please see Attachment C as the initial outline of the SharePoint Content Standards (policies and procedures)


Work Breakdown and Expected Review Cycle

When working off the Work breakdown structure each of these documentations will be developed by an outside source that will participate in the overall development of this project. They will use currently designed Microsoft documentations and adjust them to meet the use and requirements of the project customer since this is a governmental organization using commercial off the shelf equipment and techniques convert to meet military tactical and strategic war time needs. Drafts will be created during the complete development, implementation, testing, and evaluation stages of the overall project. This should equal four draft copies prior to the final deliverable of each of the three documents that means there will be four drafts for the user manual, four drafts for the Administrators manual and four drafts of the SharePoint content standards prior to the final three documentations. The reviewers are listed in the deliverable outline and engulf Stakeholders, Action Officer, and Project Manager for both the user and administrator manuals but the SharePoint Content Standards will be reviewed by Stakeholders, Action Officer, Project Manager, Administrators, Site Administrators, and UsersThe following is an example of the proposed work breakdown and Expected Review Cycle1) Content plan

a) Content plan creationb) Content plan review and update

2) Draft 1 – complete outline, Introduction Tasks a), b), and c)a) Written by Leo Schleicherb) Reviewed by Jimmy Irwin and Jay Sexton

3) Draft 2 – revisions of draft 1 and tasks d), e) and f)a) Revised by Patrick O'Malleyb) New content written by Tyson Weissc) Screen captures and graphicsd) New content Reviewed by Jay sexton

4) Beta Testinga) Updated by Leo Schleicherb) Files sent to testers by Jay Sexton

5) Final versiona) Updated by Leo Schleicherb) Final review by Jimmy Irwin and Jay Sextonc) Cleanupd) Release to production

6) Productiona) PDFb) Conversion and upload to CMSc) Publish to customer-facing website

(Giordano, 2013) In-text citation

Timeline and Milestones

The three documentations will be developed at the same time since all cover the same functional aspect of the SharePoint Web based Interactive Data Storage web site. This will occur since this is a web site development of currently structured and documented application.


AssumptionsCompletion of all deliverables outlined in this plan assumes the following:

• Implementation and training on new SharePoint web based interactive data storage web site will be conducted during the design and development of the web site.

• Training of organizational personnel will be conducted during the design and development of the web site .

• Action Officer, Project Team Subject Matter Experts, and Master Administrators have been assigned to provide input and feedback.

ConstraintsThe following constraints have identified that could hinder the completion of the documentation activities for the SharePoint Web based Interactive Data Storage Web Site:

• Changes to project goals and requirements will affect documentation resource availability.

• Completion of Deliverable 1 relies on well-timed approval and accomplishment of objectives as described in the project plan.

ResourcesCompleting all documentation deliverables as outlined requires the following:

• Three full-time content administrators for 1 week.

• One full-time design/UI administrator for 1 week

• One Project performance evaluator for 2 days

• 1 part-time graphics specialist for xx weeks.

• 20 hours per subject matter expert time for initial interviews and draft reviews

We estimate these resource requirements using the following metrics:

• Content development estimated at 12 topics x 3.5 hours of development per topic

• Evaluating requirements estimated at .5 hours per topic.

• Current publishing workflow requires 40 hours to produce web-ready content


TimelineMilestone Start Completion DurationDocumentation Plan 11/3/2014 11/15/2014 12 daysDocumentation Plan Approval 11/14/2014 11/15/2014 2 dayDeliverable 1, 2, and 3 Content Plan Approval 11/09/2014 11/09/2014 1 dayDeliverable 1, 2, and 3 Content Draft 1 11/5/2014 11/09/2014 4 daysDeliverable 1, 2, and 3 Draft 2 Approval 11/09/2014 11/09/2014 1 dayDeliverable 1, 2, and 3 Design completed 11/09/2014 11/10/2014 2 daysDeliverable 1, 2, and 3 Beta Testing Complete 11/10/2014 11/11/2014 2 daysDeliverable 1, 2, and 3 Final version approved 11/11/2014 11/11/2014 1 dayDeliverable 1, 2, and 3 Release to Production 11/11/2014 11/15/2014 3 daysDeliverable 1, 2, and 3 Published 11/15/2014 11/15/2014 1 days


Section 9: Quality Assurance and results of test-case execution

Currently all test cases have been accomplished 100 percent completed to date. Every test case has performed to the highest quality of standards and functionality. During our quality assurance testing several new test cases were discovered and all fell under Project review. The Project Coding Scheme has been updated to reflect the changes but for quick review they were the following:

1.5.8 Logout requirements for SharePoint

1.5.8.1 Logout requirements Web Brower and Client laptop

1.1.10 Project review

1.1.10.1 Project review Hardware upgrades

1.1.10.2 Project review Software upgrades

1.1.10.3 Project review Client Setup and configurations

1.1.10.4 Project review Data Migration to Hotspot disaster recovery

location

1.1.10.5 Project review Web-based Interface

1.1.11 Final Implement Changes

1.1.12 Distribute Documentation Documents.

Unit, Integration, System and Additional Testing

Once the Project reviews were conducted the project team and unit personnel worked hand in hand testing and reviewing all functionalities and processes of the newer hardware and software applications. This testing ensured no faults found and all operating systems and application functioned in the manner they were expected to perform. All backups, snapshots and replications data migration was tested to ensure a good copy of systems were stored in the disaster recovery Hotspot location. At current time both the newer hardware and software will operate along side of the older systems to ensure connectivity, Confidentiality, and usability are still functional. Now that the SharePoint web-based interactive data storage database web site has been completed the Project team, SharePoint master administrator, and several selected SharePoint administrators together accessed the SharePoint web site across the network ensuring access to the organizations web-based interactive data storage web site was good. The following was the testing that was conducted and the percentage of functionability:

Test Type Percent of Completeness

Unit 100%

Integration 1005

System 100%

Network-Readiness 100%

Volume 100%


Recovery 100%

Penetration 100%

Hardware-Certification 100%

Test Type Percent of Completeness

Migration 100%

Regression 100%

Ready-for-use 100%

Status Assessment

The Project will be completed on the set end date, on time and within budget. There were no serious quality assurance issues during this project all rsik were identified and steps were used to repair or replace any hardware, software or operational application issues

Test Execution Results

Purpose:This Web Based Interactive Data Storage Web Site using Microsoft SharePoint 2010 -Test Report provides a summary of the results of the test performed as outline within this section.The tables below summarizes the results of the test cases.

Project Name:

Test Case Results1.4.1

Test Case ID: 1.4.1 Test Designed By:O’Malley

Test Priority(Low/Medium/High):High Test Designed Date:12/5/14Module Name: Install and Setup Windows 7 Operating System Test Executed By:O’MalleyObject of Test Case: Install Windows 7 OS on all computers and ensure all applications are fully functional. Test Execution Date: 12/13/14

Description:

Setup Procedures:Common ways to install Windows 7 & Before you begin installing Windows 7 - http://windows.microsoft.com/en-us/windows/installing-reinstalling-windows#1TC=windows- 7Dependencies – Identify list of clients

http://windows.microsoft.com/en-us/windows/installing-reinstalling-windows#1TC=windows-7

http://windows.microsoft.com/en-us/windows/installing-reinstalling-windows#1TC=windows-7

http://windows.microsoft.com/en-us/windows/installing-reinstalling-windows

http://windows.microsoft.com/en-us/windows/installing-reinstalling-windows


System TestingStep

Procedures For Executing Test Case

Expected Results Result-Pass/Fail

Comments

1 Log on computer Application is installed

Pass

2 Go to Start menu Icon on start menu works

Pass

3 MS Applications Should see all applications (Word, Access, and Excel etc.)

Fail Seems that different not all of the applications are working correctly. – log into regressing testing

4 Open each application Click on application icon

Pass

5 Perform task (open, save, print)

All task work Pass Print worked for all hard copies. User say they need the ability to print to ADOBE (PDF)

Regression TestingStep


Expected Results Result-Pass/Fail

Comments

3 Re-install Windows & OS with appropriate License Codes

All applications are working correctly

Pass

Project Name:


Test Case ID:1.4.2 Test Designed By:O’Malley

Test Priority(Low/Medium/High): High Test Designed Date:12/4/14Module Name: Configure Internet protocol IPv4p properties Test Executed By: O’MalleyObject of Test Case:To use static IPs to prevent addressing conflicts between devices. Test Execution Date: 12/13/14

Description:Setup Procedures:Ensure you have IP address defined for the network.DependenciesAll computers and servers must be installed and OS configured


System TestingStep


Expected Results Pass/Fail

Comments

1 In the Internet Protocol Version 4 (TCP/IPv4) Properties window, you will need to select "Use the following IP address" and "Use the following DNS server addresses:"

Configure and store IP address

Pass Make sure to create tech support guide for what IP addresses we are using.

2 Enter in the corresponding settings per their section. If you don't have the settings, or need help with them, call into tech support so we can provide them to you.

All sub section Subnet and Default gateway are configured

Pass

3 Once the settings have been entered in, click ok on the Internet Protocol Version 4 (TCP/IPv4) Properties window, and then click on close on the Local Area Connections properties window.

At this point the Local Area Connection should say connected. See if you can browse to a web site at this time. If you are able to, your setup is complete. If you are not able to browse, call tech support, so they can verify your settings are correct.

All of the settings hold their information

Connection is live and maintains the configurations

Pass

Pass


4 Now you can open the command prompt and do an ipconfig to see the network adapter settings have been successfully changed.

You should see… Fail Go to Regression testing




Comments

1-3 Follow all of the steps in the system testing

All configurations hold their values

Pass

4 Open the command prompt and do an ipconfig to see the network adapter settings have been successfully changed.

Pass All settings are stored and connected.

Project Name:



Test Priority(Low/Medium/High):High Test Designed Date:12/4/14Module Name:Configure User accounts and connect to the AD DOMAIN server Test Executed By: WeissObject of Test Case: Mapping your application

process to a Windows domain user account requires that you configure the following: The Web server.

Test Execution Date: 12/14/14Setup Procedures:Dependencies1.4.2

Iteration TestingStep



Comments

1 -Web Server- Set up windows domain user account that you specify has sufficient user rights (but no more) to run a Web application.

Make sure the accounts match the user

Pass


2 -Application. You must configure the Web.config file for ASP.NET to recognize the domain user account name.

Pass

3 -Connection string.When you create

connection strings for connection objects in your application, you have to specify that the connection strings will use Windows integrated security strings will use Windows integrated security

Pass

4 SQL Server.You must add the specified domain user account as a SQL Server login user.

Pass

Project Name:

Test Case Results 1.4.4


Test Priority(Low/Medium/High) High Test Designed Date: 12/4/14Module Name:Configure Web Browser with security, internet options and protection Test Executed By:O’MalleyObject of Test Case: Test to ensure all security settings are set according to I.T. Security Policy’s Test Execution Date: 12/14/14Setup Procedures:Dependencies

System TestingStep



Comments

1 Set Internet-explorer-privacy

Set per Enterprise Policy’s

Pass

2 Configure security settings Set per Enterprise Policy’s

Pass

3 Set security zones: Set per Enterprise Policy’s

Pass

4 Set Internet zone security Set per Enterprise Policy’s

Fail Redo didn’t hold for some reason

5 Disable javaScript: Click Set per Enterprise Policy’s

Pass


6 Automatically clear history Set per Enterprise Policy’s

Pass

7 Configure privacy settings Set per Enterprise Policy’s

Pass

8 Privacy setting: Set per Enterprise Policy’s

Pass

9 Location Set per Enterprise Policy’s

Pass

10 Pop-up Blocker: Set per Enterprise Policy’s

Pass

11 Configure Advanced Security settings


Pass

12 Turn off AutoComplete Set per Enterprise Policy’s

Pass

13 Tracking protection Set per Enterprise Policy’s

Pass




Comments

4 Re- Set Internet zone security


Pass

Project Name:


Test Case ID: 1.5.1 Test Designed By:Schleicher

Test Priority(Low/Medium/High): High Test Designed Date:12/4/14Module Name:Set access permissions with AD DOMAIN accounts Test Executed By: SchleicherObject of Test Case:Windows Server 2008 R2 Active Directory explanation of users, groups and assigning permissions to shared folders. The goal is to add Users Accounts to Domain Global Groups, then add them into Domain Local groups which are then used to assign permissions to the shared folders. Test Execution Date: 12/14/14

Description:Setup Procedures:https://www.youtube.com/watch?v=WflcPpnUFk0Dependencies1.5

https://www.youtube.com/watch?v=WflcPpnUFk0


Integration TestingStep



Comments

1 Run LDP.exe from the ADAM install folder c:\windows\adam.

Verify that the ADAM version is selected because this is not the standard Windows LDP client

Pass

2 Open a new connection using the Connection/Connect menu.

The server name must match the CN assigned to the certificate

Pass

3 Enter the LDAPS port and select the SSL checkbox.

The results of a successful connection are some general server information and no errors

Pass

4 Bind(login) to the service. To replicate typical LDAP client connections select the Simple bind option. Enter a valid ADAM user or userProxy distinguished name in the user field and the associated password.

You should see a return message stating ‘Authenticated as:….’ then you have successfully connected using LDAPS.

Pass

Project Name:


Test Case ID:1.5.3 Test Designed By:Schleicher

Test Priority(Low/Medium/High): High Test Designed Date:12/4/14Module Name:Organizational Site graphics and easily Usable layout Test Executed By:Schleicher

Object of Test Case: Test Execution Date: 12/14/14Setup Procedures:


Dependencies

Integration TestingStep



Comments

1 Style sheets A style sheet is a set of statements that specify presentation of a document. Must be cascade.

Pass

2 Tabular information Tablesmust be used to represent logical relationships among data -- text, numbers, images, etc., Check for header information to display correctly.

Pass

3 User Agent Check software to access Web content, including desktop graphical browsers, text browsers, voice browsers, mobile phones, multimedia players, plug-ins, and some software assistive technologies used in conjunction with browsers such as screen readers, screen magnifiers, and voice recognition software

Fail Having some issues with the various types of mobile phones displaying the content correctly.



Expected Results

Pass/Fail

Comments


3 User Agent Research and reload all plug-ins and validate correct browsers

Pass


Project Name:


Test Case ID:1.5.4 Test Designed By:Schleicher

Test Priority(Low/Medium/High):Medium Test Designed Date:12/4/14

Module Name:Outlook Calendar interaction Test Executed By:SchleicherObject of Test Case:Confirm the interaction of the company relationships with the clientsinternal Test Execution Date:12/16/14

Description:Setup Procedures:Windows 7 OS and MS SoftwareDependencies

System TestingStep



Comments

1 Test configuration with automatically “what is happing with you key contacts”

All contacts appear

Pass

2 Test receive alerts when information changes for key contacts

Alerts are received

Pass

3 Test Mutual connections of all people included in an email

All people in email chain are included

Pass

4 Run a briefing report on a contact to quickly get up to speed before a meeting.




Comments

123


Project Name:


Test Case ID: 1.5.7 Test Designed By:Schleicher

Test Priority(Low/Medium/High):High Test Designed Date:12/4/14Module Name:Internet Explorer and Microsoft office interaction Test Executed By:SchleicherObject of Test Case: Ensure Activating ActiveX Controls:Users cannot directly interact with Microsoft ActiveX controls loaded by the APPLET, EMBED, or OBJECT elements. Users can interact with such controls after activating their user interfaces. This topic describes how Internet Explorer handles ActiveX controls, shows how to load ActiveX controls so their interfaces are activated, and describes the impact of this behavior on accessibility tools and applications hosting the WebBrowser Control. Test Execution Date:12/16/14Setup Procedures:Production PlatformDependencies

System TestingStep



Comments

1 http://msdn.microsoft.com/en-us/library/ms537508(v=vs.85).aspx

Pass

23




Comments

12

http://msdn.microsoft.com/en-us/library/ms537508(v=vs.85).aspx



http://msdn.microsoft.com/en-us/library/aa752040(v=vs.85).aspx





Project Name:


Test Case ID: 1.5.8 Test Designed By:Sexton

Test Priority(Low/Medium/High):High Test Designed Date:12/4/14

Module Name:Logout requirements Test Executed By: SextonObject of Test Case: Ensure that end-users are logging out or the system will automatically logout after a certain time period with no activity Test Execution Date:12/16/14Setup Procedures:Production PlatformDependencies

System TestingStep



Comments

1 Have various end-user log on and log off

No issue with logging on or off

Pass

2 Have various end-users leave their session logged on – but they are not actively working in the session

After no activity for 10 mins the system will automatically log the user out

Pass Be sure to document this in the company IT policies

3456




Comments

1

Project Name:


Test Case ID:1.5.9 Test Designed By:Sexton

Test Priority(Low/Medium/High):High Test Designed Date:12/4/14

Module Name: Publish Web site Test Executed By:Sexton


Object of Test Case:Ensure the Web site is fully functional Test Execution Date:12/4/14Setup Procedures:Production PlatformDependenciesAll WBS must be completed and validated

System TestingStep



Comments

1 Internal users test the site All functions of the site must work

Pass

2 External users test the site All functions of the site must work

Pass




Comments

123


Attachment A SharePoint User Manual (Instructional guide) Outline (Skeleton)

Safety Warnings1. Use of Web browser to access SharePoint Site

1.1.1. Use of internet explorer to locate and visit web site2. Login using DOMAIN login and password

2.1.1. Once connected to site viewing is only allowed to gain access user must login system using DOMAIN account or can use same DOMAIN username and password at website

3. Use navigation menu to locate specified site3.1.1. Navigation left side vertical and top horizontal navigation menus can be used to

move between master and sub sites4. Use search option window to locate specific site

4.1.1. Search option window allows specific site name or alias input to locate specific web site

5. Document Library 5.1.1. Viewing a File 5.1.2. Uploading File(s) 5.1.3. Check Document Out 5.1.4. Editing a Document5.1.5. Check Documents In 5.1.6. Viewing Document Version History 5.1.7. Delete a File 5.1.8. Change File Permissions5.1.9. Additional Document Options

6. Team Discussions 6.1.1. Create/Edit a Discussion 6.1.2. Reply to a Discussion 6.1.3. Delete a Discussion

7. Announcements7.1.1. Create/Edit Announcement

8. Calendar Items 8.1.1. Create/Edit Calendar Item8.1.2. Export Calendar Item

9. Links 9.1.1. Links will have the same light blue color for a hyperlink as most Microsoft office

applications9.1.2. Direct links will appear in the left navigation menu or placed in a webpart

throughout a site layout10. Email Alerts 11. Project Tracking

11.1.1. Create New Project Tasks 11.1.2. Update Project Tasks

12. Shared Document Page’s Notable Features

(Microsoft, 2010) In-text citation


Attachment B SharePoint Administrator Manual (Training guide) Outline (Skeleton)

OVERVIEWSafety Warnings1. Using Administration build tools in SharePoint will help in development of web site

1.1. Create Sites or Subsites 1.1.1. Create a Project Site 1.1.2. Create a SubSite1.1.3. Team Site Vs Project Site 1.1.4. Timeline and Project Summary WebPart 1.1.5. Create a Community Site

2. Using administration library tools in SharePoint will help in development of content management2.1. Create Lists and Libraries

2.1.1. Create a Custom List 2.1.2. Create a Custom Document Library 2.1.3. Create a Task List 2.1.4. Create a Discussion Board

3. Using administration page layout a design tools in SharePoint will help in development of customized web designs and layout of web part features3.1. Custom Pages

3.1.1. Create a WebPart Page 3.1.2. Error Pages 3.1.3. Add a Page Option 3.1.4. Changing the default page layout 3.1.5. Set a Welcome Page

4. Using administration Grouping and Permissions tools in SharePoint will help in development of security management of all web sites4.1. Users, Groups & Permissions

4.1.1. Create Groups 4.1.2. Add Users 4.1.3. Create new Permission level 4.1.4. Edit Permission level for default Members group

4.2. Set unique Permissions for a SharePoint List\Library 5. Using administration web content management tools in SharePoint will help in development

of special feature capabilities all web sites5.1. Web Content Management

5.1.1. Drag and Drop multiple documents 5.1.2. Move multiple documents from one library to another 5.1.3. Digital Assert Content Types 5.1.4. Asserts Library and new Video Content Type 5.1.5. IFrames in SharePoint 2013 5.1.6. How to add a YouTube Video in SharePoint 2013 site

(Kapoor, 2013) In-text citation


Attachment C SharePoint SharePoint Content Standards (Policies and Procedures) Outline (Skeleton)

SharePoint Content Standards

1. General Standards1.1. Use, privacy, copyright, records retention, confidentiality and content security

2. Content Contribution and Ownership

2.1. Resources accountable for content, ownership, content modification, site naming and

2.2. copyright violations

3. Content Security

3.1. Product site Security

4. Application Configuration

4.1. Management console preferences and customization

5. Features

5.1. Graphic Design features, site layout, and permission access

6. Discussion Boards and Internal Forums

6.1. Facilitate and categorize readability and response improvement collaboration discussions

7. Document Standards

7.1. Topical and descriptive file names naming standards, file size limits

8. Homepage Standards

8.1. SME and administrator approved designed, usability, and applicability of home site

8.2. standards

9. Site Definitions

9.1. Blog. Workspace, Master and sub-site

10. Navigation

10.1 Horizontal and vertical top navigation 3 level deep

11. Page Design and Layout

11.1 Pages must meet 1024 by 768 resolution requirements, top left region reserved for most


important, use of light fonts on light background and dark on dark

12. WebParts

12.1 Must use only SharePoint designed or approved web parts

13. Pictures and Media

13.1 Alt tags per picture, transcripts per video content, follow consent policies for all pictures

and media inserts

14. Ratings

14.1 Monitor content usage ratings, 5 = important, 0 to 1 = no use

15. Rich Text and Page Content

15.1 Bolding of important text only, no use of underlines except for hyperlinked, all linked

text most be precise, local links never open new window, external links to site always

use new window

16. Site Standards

16.1 Identified sponsor, 12 months review, primary and secondary administrator of site

layout and content, new sites must have person with content and site ownership, security

and growth needs identified, short descriptive names with no spaces or special

characters.

17. Social Tagging

17.1 Security trimmed, add value to content, tag content with phrase or word, no negative

tagging

18. Status Updates

18.1 Beneficial information to share


19. User Profiles

19.1 Individual responsibility for updating and maintaining information, ensure info is

targeted and secure, MySite can contain relevant information of the owner.

20. Quality Assurance

20.1 Routine checks of owner, user and share accounts must be conducted quarterly to

eliminate database over use.

(Rharbridge, N.D.) In-text citation


References

38 Page Layout and Visual Design Usability Guidelines. (n.d.). Retrieved December 7, 2014,

from UserFocus: http://www.userfocus.co.uk/resources/layoutchecklist.html

Association of Modern Technologies Professionals. (2014). Software Development

Methodologies, Retrieved 24 November 2014 from

http://www.itinfo.am/eng/software-development-methodologies/

California Institute of Technollogy. (n.d.). Basic Web Browser Security Settings. Retrieved

December 7, 2014, from http://www.imss.caltech.edu/node/243

Davies, Rachel. (2004). DSDM explained, Retrieved 23 November 2014 from

http://www.agilexp.com/presentations/DSDMexplained.pdf

Dell.com. (2014). Fortify your solution with a powerful 1U, 2-socket server built for rugged

reliability, Retrieved 10 October 2014 from

http://www.dell.com/learn/us/en/555/oem/oem-poweredge-420xr Dell.com. (2014)

Dell OEM 1130, Retrieved 01 November 2014 from

http://www.dell.com/learn/us/en/555/oem/dell-oem-1130-server

Dsdm.org. (N.D.). What is DSDM? Retrieved 23 November 2014 from

http://www.dsdm.org/content/what-dsdm

Dell.com. (2014). Fortify your solution with a powerful 1U, 2-socket server built for rugged

reliability, Retrieved 10 October 2014 from

http://www.dell.com/learn/us/en/555/oem/oem-poweredge-420xr Dell.com. (2014).

http://www.agilexp.com/presentations/DSDMexplained.pdf


Dell OEM 1130, Retrieved 01 November 2014 from

http://www.dell.com/learn/us/en/555/oem/dell-oem-1130-server

Kapoor, Isha. (2013). SharePoint 2010 Site Administration Guide, Retrieved 6 December 2014

from http://www.learningsharepoint.com/wp-content/uploads/downloads/2013/11/

SharePoint-2013-Site-Administration-Guide.pdf

Giordano, Connie. (2013). Documentation Plan Template (Traditional), Retrieved 6 December

2014 from http://techwhirl.com/documentation-plan-template/

McConnell, S. (1996). Rapid development: Taming wild software schedules. Redmond, Wash.:

Microsoft Press.

Microsoft. (2010). Microsoft Office SharePoint 2007 User Guide, Retrieved 6 December 2014

from http://www.fullerton.edu/ittraining/other/sharepoint/user_guides/01_SharePoint

_USER_manual.pdf

Milsark, M. (2012, March 25). SharePoint Tips & Tricks. Retrieved December 7, 2014, from

Check In and Check Out Documents in Microsoft SharePoint:

http://blog.fpweb.net/check-in-and-check-out-documents-in-microsoft-

sharepoint/#.VITmhPnF_EQ

Mosaic. (n.d.). Defect Management. Retrieved from defectmanagement.com:

http://www.defectmanagement.com/defectmanagement/index.htm

Office Online. (n.d.). Add a Data Connection to A SharePoint Document Library or list.

Retrieved December 7, 2014, from Office Online: https://support.office.com/en-


sg/article/Add-a-data-connection-to-a-SharePoint-document-library-or-list-3233d77d-

95af-4245-a124-dca2f6d5d02e

prince2primer. (2014). Risk Management Strategy. Retrieved from PRINCE2 Video Primer:

http://www.prince2primer.com/risk-management-strategy

Project Smart. (2014). Work Breakdown Structure (WBS), The Foundation of Project Planning,

Retrieved 24 November 2014 From http://www.projectsmart.co.uk/work-breakdown-

structure.php

Rharbridge, Richard. (N.D.). SharePoint Content Standards, Retrieved 6 December 2014 from

http://www.rharbridge.com/?page_id=290

Rouse, Margaret. (2006). work breakdown structure (WBS), Retrieved 24 November 2014 From

http://searchsoftwarequality.techtarget.com/definition/work-breakdown-structure

VMware.com. (2014). VMware ESXi, Retrieved 10 October 2014 from

http://www.vmware.com/products/esxi-and-esx/overview

Workbreakdownstructure.com. (2014). Work Breakdown Structure (WBS), Retrieved 24

November 2014 From https://www.workbreakdownstructure.com/

IT488_JaySexton_Week5GP

Documents

quality assurance plan

communication plan

outline of deliverables

detailed content plan

unit testing plan

initial outline work

business case

jt consultants