download

Monica Macedon 1 4/12/2023

DEVELOPMENT PROCESS AND PROJECT INTEGRATION MANAGEMENT

Human Resources Management System Project

Master of Science in Information Technology

TS5990 – Integrative Project

Capella University

Prepared by

Monica Macedon

Presented to

Instructor - Professor Sharon Gagnon

November 26, 2005


Contents

Page

Abstract 3

Purpose 4

PROJECT MANAGEMENT 6

Project Scope 6

Project Plan 7

PROJECT COMMUNICATION MANAGEMENT 8

Human Resource Communication 8

PROJECT CONTROLLING 8

Integrated Change Control 8

PROJECT COST MANAGEMENT 9

Costs and Benefits 9

PROJECT QUALITY MANAGEMENT 10

Quality Control 10

PROJECT RISK MANAGEMENT 10

Project Risk Plan 10

PROJECT EXECUTION 10

Executing Processes 10

SYSTEM IMPLEMENTATION 48

Integration Plan 48

Conversion Plan 48


APPENDICES

Appendix A: Eastern Carolina Vocational Center Business Statement 14

Appendix B: Project Charter 16

Appendix C: Scope Statement 19

Appendix D: HRMS Work Breakdown Structure 21

Appendix E: Stakeholder Communication Analysis 23

Appendix F: Status Report 25

Appendix G: HRMS Cost Estimates 26

Appendix H: Risk Management Plan 28

Appendix I: Business Requirement Use Case 29

Systems Analysis Use Case 30

Appendix J: Benefits Use Case 32

Business Activity Use Case 33

Appendix K: Organizational Structured Web Site 34

Appendix L: Network Architecture 35

Appendix M: Test Plan 36

Illustrations

Table 1. Control Change Plan … ………………………………… ………………….. 21

Table 2. Table 2. Risk Management Plan Matrix ………………………………………26

Figure 1 “Select Benefits” Use Case ……………………………………………………27

Figure 2 “Maintain Benefits” Use Case …………………………………………………27

Figure 3. Benefits Use Case Diagram …………………………………………………...31

Figure 4. Business Activity Diagram ..…………………………………………………..32


Figure 5. Information Architecture Diagram 33

Figure 6. Network Architecture Diagram 35

Conclusion 50

References 51


Abstract

This report outlines an integrative management process for the Human Resource

Management System Project. Managing this information technology project will provide an

automated benefits enrollment process with immediate information; conducting Human

Resource Management process through decision-making; coordinating the project plan; and

guiding the project execution and project control. Including several types of testing

documentations and testing strategies are introduced in order to understand process issues and

careful project planning.

The purpose of my project is utilizing my learning skills and knowledge; incorporating

tools, techniques and software engineering; demonstrating the ability to apply the concepts of

project management practices, including my capabilities in successfully creating and managing

this project. Fulfilling the highest quality Human Resource Management Information System

and services to Eastern Carolina Vocational Center will enable benefits personnel and the

business community to spend time on serving the employees versus data entry in a cost-effective

manner.


Project Management

Project Scope

In the initiation phase, a kick-off meeting is held to establish the project team, assign a

project manager, identify key stakeholders, view the scope statement, and develop a project

charter. According to Paula K. Martin (2001), “…project management technology is based on

team participation and control, empowerment and a focus on deliverables instead of activities”

(Usability, par.1).

The main results (deliverables) will keep the team focused on what are important – the

outputs. The team members are very interested in the starting point of planning and identifying

the business’ long-term objectives, resources, and policies. Their interest of better service, better

performance, more information, stronger controls, and reduced costs are important factors when

it comes to the level of complexity and risks. This is where experienced technology and

technical expertise are carefully managed by the team members, and we knew exactly what we

wanted and what the system will do. See appendix A for the deliverable business statement.

The scope of the HRMS project is to analyze current and future state of the benefit process that

will bring out any process change requirements and impact to the system design, and

development.

Once all key stakeholders and the project manager agree to the project scope, a Project

Charter is created. This document recognizes the existence of a project and provides duration on

the project’s objectives and management. The project deliverable is a project charter that is

reviewed and signed by the project team members. See Appendix B for the HRMS Project

Charter.


Project Plan

The development of the team’s project plan documents all coordinating project activities,

resources, project execution, and project control. According to Tom Mochal (2003), “The work

plan is a vital tool for ensuring that the project manager and project team know what they need to

do to complete the project” (Usability, par. 2). Common mistakes of failed projects result from

poor management practices and not updating the project plan on a regular basis. This realistic

and useful project plan establishes the initial scope in this second-key process phase, which

includes inputs from all team members. The project deliverable is an agreed-on Scope

Statement. See Appendix C for the HRMS Scope Statement.

Once the project team establishes the scope plan, a project schedule is created and further

work is broken down into manageable pieces called a definition scope. This process improves

accuracy of time, cost, and resource estimates, base-lined for performance measurement, and

project control. Use of Microsoft Project 2003 ensures timely completion of the project, which

involves specific activities, activity sequencing, activity duration, schedule development, and

schedule control, which improves the project’s performance. This useful tool defines the total

scope of the project, organizes and divides the work into logical parts based on how each work

will be performed.

Total involvement and commitment from all project team members can keep the schedule

on time and using the Gantt Chart for the actual scheduled progress lists the project activities and

their corresponded start and finished dates can produce a successful project. The project high-

level deliverable is a Work Breakdown Structure (WBS) Document. See Appendix D for the

total scope of the project’s HRMS WBS.


PROJECT COMMUNICATION MANAGEMENT

Human Resource Communication

In order to understand politics of the business and know how to use them in the project,

people resources are identified for each task in the form of roles. This process is concerned with

making effective use of the team members involved in the project that includes organizational

planning, staff acquisition, and team development. Communication is the lifeblood for a

business, and effective communication improves a business’ productivity, image, and

responsiveness.

It is important for the project manager to understand each team member’s preference for

communications and that listening is an important aspect of communications. Communication

needs should include “Sensitivity and Culture; Trust and Respect; and Accurate and Clear” when

building a strong relationship among project team members. The HRMS project team develops a

communication plan that includes communication planning, information distribution,

performance reporting, and administrative closure to coordinate the work flow. This plan will

guide the project team’s communication, which includes methods for obtaining information. The

deliverable is a Stakeholder Analysis. See Appendix E for the Stakeholder Communication

Analysis.

Project Controlling

Integrated Change Control

Continuous monitoring and reporting the project’s progress through emails, meetings,

and status reports that are honest, and accurate, create consistency with the business project

planning strategy. The project change control plan includes – cost control, quality control, risk


monitoring and control, and schedule control to review necessary changes in the project

development.

A best-practice document is created that will assist the project team in implementing a

successful configuration management plan. See Appendix F, example of Status Report for

performance reporting of how the resources are used, and the Control Change Plan table.

PROJECT COST MANAGEMENT

Costs and Benefits

The project will be completed within the approved budget. Sunil Sharma (2002) states,

“…considering all aspects of the business touched by the IT system…conduct an analysis to

reveal all hidden costs and put a price tag on all intangible and strategic benefits” (Usability,

par.1). Utilizing a computerized tool, Microsoft Excel helps to reduce and control cost in order

to complete the project within the budget and constraints. The project deliverable is the

estimated costs and benefits analysis. See Appendix G for the HRMS Cost Estimate proposed

system solution and supporting details. Below is a list of tangible and intangible benefits the

system will provide:

Tangible Benefits

Automated processing – Internet-based electronic enrollment and benefit

management system, and reduced paper-based process

Reduced administrative costs and improved information access

Efficient transaction processed with fewer errors and lowered employee benefits rate

Respond quickly to changes by establishing new business rules.


Intangible Benefits

Improved employee morale and efficient employee self-service functionality.

Flexible security and management reporting, better decision-making & easy to learn

and use.

PROJECT QUALITY MANAGEMENT

Quality Control

The project manager and project team begin with a culture that recognizes everyone in

the business is responsible for quality and each is committed to continuous process improvement.

The HRMS project quality plan includes identifying quality standards that are relevant to the

project; incorporating quality standards into the project design; and periodically evaluating

overall project performance (Schwalbe, Kathy 2004).

PROJECT RISK MANAGEMENT

Project Risk Plan

The project team will decide how to approach and plan the risk management activities for

the project by reviewing the project charter, WBS, roles and responsibilities, and the business’

risk management policies. The project team will ensure that the risk awareness will be an

ongoing activity throughout the project life cycle. See Appendix H for the Project Risk

Management Plan.

PROJECT EXECUTION

Executing Processes

With a supportive and organizational culture, strong leadership skills, useful guidelines and

templates, the project team’s expertise skills can incorporate a good relationship in order to


execute the project successfully. The desired work plan will help the project team to monitor

and measure the project’s performance efficiently.

Below are the steps and deliverable output processes to execute the project plan:

1. Analyze problems, users/business’ needs and tasks – the Project Manager and

Systems Analyst will create use cases that will describe the system functions in terms

of inputs, outputs, processes, and stored data that are acceptable to the stakeholders.

Including characteristics and constraints that are defined and may restrict the

development project. See Appendix I for the Business Requirements Use Case and

Systems Analysis Use Case.

2. Identify in-house solution for the new system – a system proposal is produced that

will fulfill business requirements identified in the Business Statement (Appendix A).

From the Project Manager, Systems Analyst, and the Chief Financial Officer’

analysis, technically, the solution will be practical; operationally, the solution will

fulfill the users’ requirements; economically, the solution is cost-effective; and can

be designed and implemented within the acceptable time period.

3. Design the system – the approach is to facilitate usage-centered development in

modeling the system requirements. The Systems Analyst and IT team will create a

use case and activity diagrams using Poseidon UML and Visual Paradigm tools to

determine what the system is required to do from the user and stakeholder

perspective. This Tool will capture functional requirements, provide functional

specifications for designing user and system interfaces, and provide a baseline for

test plans and test cases. See Appendix J for the Benefits Use Case and Activity Use

Case diagrams.


4. Design Application Architecture – the Systems Analyst and System Designer will

design the information architecture in a site outline that will be used to guide the

development of the site. The design work will be based on the site requirements,

content, and user testing. See Appendix K for the Organizational Structured Web

Site.

5. Design Database – the System Designer, Database Administrator, and Systems

Analyst will develop the database design specifications for the in-house software. A

Data Flow Diagram (DFD) will be created and used as a system design tool and

serves as a blueprint for system construction and implementation. See Appendix L

for the physical data flow of the Network Architecture Diagram.

6. Web Interface – the System Designer and Database Administrator will create input

designs of Web pages using Macromedia Dreamweaver MX. Usability and

accessibility will be incorporated to establish a well-structured site, as well as

performing user testing. The live site will be presented in the next step of the testing

process.

7. Testing – the testing team will create a test plan that will record the business

transactions in terms of data entry and program documentation created for testing

data. See Appendix M for a detailed description of the Test Plan. The test cycle will

provide business requirements to be implemented by the programs and the project

team will assume overall responsibilities for the program design strategy, standards,

and construction:

Unit test – identify system outputs and review logical requirements. Output

designs (web pages) that are simple to read and easy to interpret. Ensure


input controls are entered accurately and protected against intentional errors

and abuse. Input designs (web pages) with effective navigation controls for

user review and testing. This test will be driven by the human engineering

concerns that will support the ways in which the system users work. For

security considerations, system users will be authenticated and established to

perform certain actions and access privileges.

Integration testing – Integrate output and input designs that will establish the

dialogue between the user and the computer. Web-based user interfaces

(forms) will blend well into the user’s workplace environment where the user

can test these forms to see if they work or not.

System testing – The integrated set of programs will run through tests to

make sure one program is properly accepted as inputs and outputs of other

programs. Ensuring that the application programs written and tested work

properly when they are integrated into the total system.

User acceptance testing – System users will experiment and test the interface

design before extensive programming and actual implementation begins.

Providing the opportunity to perform testing in accepting or rejecting the

system.


Appendix A Eastern Carolina Vocational Center Business Statement

Redesigning of the benefits process will increase employee self-service

functionality and efficient employee enrollment process. Immediate confirmations and

processing of information increase greater accuracy with fewer problems. Greater

integration with the company’s HR System and the Business Information System will

allow for real time processing and consolidation into one database. Simplifies audits and

reconciliation processes, which enhances timeliness.

Summary and discussion of facts and details

The system must be designed to comply with business’ entities, process

requirements, and policy rules. Integrating a comprehensive business solution will allow

the business to use current technology to significantly expand system functionality and

dramatically increase in value. Eastern Carolina Vocational Center’s current business

processes:

1. Employee completes paper form for multiple benefit plans;

2. Submits applications to HR;

3. HR reviews forms, then photo copies forms for employee file;

4. Sends paperwork to payroll for premium deductions;

5. Payroll reviews forms and calculates deductions amount;

6. Reconciles and mails payment to insurance carrier; and

7. Distributions of deduction reports, edit reports, and mismatch statement.

ECVC’s current systems have a series of fragmented HR/Payroll business

processes that either don’t interact with one another or that require extensive manual

effort to connect. The current process is frustrating and problematic when employees


with families have to file manual paperwork for family/dependent/beneficiary data.

There is also resulting lag time in submitting the information to the carrier. Notification

of employee/retiree status changes are not adjusted or updated on a timely basis.

Methods Standards and Procedures:

Incorporate Project Management best practices

Software Technology (development environment- HTML, ASP JavaScript, ASP

VBScript & CGI Script)

Interface Technology (Macromedia Dreamweaver MX 2004)

Manage requirements

Use component-based architecture (database engine-VLESQL Server, platform-

Windows XP, Open Database Connection with Microsoft Access)

Visually model software and verify software quality

Monitor and control progress/changes to software

Progress reporting – every week, consistent with business project planning

strategy

Scope analysis – documentation changes

Schedule analysis – create project timeline processes and activities

Final conclusion

The benefits process redesign should be accomplished in a way that enhances a

smooth transaction for the employees and minimizes any negative results for the end-

users of this system.


Appendix B Project Charter

Project Title: Project Management HRMS Project

Project Start Date: October 11, 2005

Projected Finish Date: December 18, 2005

Project Manager: Monica Macedon, 252-341-7763, [email protected]

Budget Information:

Project Justification: Dan LeRoux, President of Eastern Carolina Vocational

Center Inc. requested this project to support the business strategic goals. Redesigning of

the Human Resource Management System will give employees self-service access via

Web for enrollment, company information, and links to third-party Websites with

benefits-related information. It will also perform accurate data transaction and electronic

transmission to insurance carriers, while improving overall processes and results in better

service to the employees, as well as increase web-based self-service usage by 50%.

The budget for this project is $144,575. An additional $11,255 will be required

for operational expenses after the project is completed. Estimated benefits are $200,000

each year. It is important to focus on the system paying for itself within one year.

Project Objectives:

Develop a web-based self-service as the primary method for employees to

transact their benefit updates and allow an alternative method, such as gatekeeper

authority to reduce internal processes, and overcome management information issues.

The HRMS project will provide an online enrollment site that will add the ability to track

dates/actions used to manage benefit enrollments. Examples, an electronic notification

via one-way workflow, a 31 day window for new hire to enroll in benefit plans, and

mailto:[email protected]


automate price and premium deductions. Provide a communication and connectivity

platform that will supply benefit choices and information to employees. Example, an

employer-branded Website that educates employees about their benefit options, view

plan information, selects and makes changes to benefits.

Approach:

Analysis approach to collect information on processing requirements (interviews).

Identification of sensitive information and an outline of steps to take for data

protection.

Analyze software for in house-development that both fulfill requirements and will

be user friendly to its end users. Prepare technical design specifications for a

database such as inputs, outputs, and interface dialogues that are adaptable for

future requirements and expansion.

Provide direct connectivity with carriers, as well as with HR/Payroll system that

allows the end-users to manage enrollment.

Lower employee benefits rate to be more cost effective.

Design the system to comply with business entities, process requirements, and

policy rules.

Provide online training and administrative support.

Roles and Responsibilities

Role Name Organization/Position Contact Information

Sponsor Dan LeRoux ECVC, President [email protected]

Project Manager Monica Macedon ECVC, Project Manager [email protected]

Team Member John Salisbury ECVC, Human Resource Manager [email protected]


Team Member Beth Davis ECVC, Chief Financial Officer Business Department

[email protected]

Team Member Charles Buck ECVC, System Designer IT Department

[email protected]

Team Member Ellen Jackson ECVC, Database Administrator [email protected]

Team Member Doug Bonds ECVC, Quality Manager [email protected]

Team Member Crystal Talmadge ECVC, Systems Analyst [email protected]

Team Member Tina Wainwright ECVC, Payroll Department [email protected]

Sign-off:Dan LeRoux John Salisbury Charles Buck Doug Bonds Crystal TalmadgeMonica Macedon Beth Davis Ellen Jackson Tina Wainwright


Appendix C - Scope Statement

Project Title: Project Management HRMS Project

Date: October 10, 2005

Prepared by: Monica Macedon, Project Manager, (252) 341-7763 [email protected]

Project Justification: Dan LeRoux, CEO of Eastern Carolina Vocational Center Inc., requested

this project to support the business strategic goals. Some of the business’ current HR/Payroll

business practices are the outcome of seven years of modifications put in place to satisfy related

business processes and particular needs. Redesigning of the HRMS will give employees self-

service access via Web for enrollment, company information, and links to third-party Websites with

benefits-related information. The system will stream-line the current business processes, improves

efficiency, reduce costs, and maximize returns with the use of project management knowledge,

templates, tools, and techniques to the company’s work force.

Product-related deliverables:

1. Business use case – will identify and describe the necessary system processes from the

users’ perspective.

2. Application design – prepares a technical design specification for a database that will be

adaptable for future requirements and expansion.

3. User interface design – develops inputs, outputs, and dialogue specifications that is easy to

learn and easy to use for the new system.

4. System modeling – develops an Intranet-based computing architecture that will integrate the

business processes and HR/Payroll databases into a single cohesive framework.

5. Scope statement – defines the boundaries of the project, work to be performed and

agreed-on between, stakeholders, project manager, and project team.

6. System improvement objectives – identify, analyze, and recommend a candidate solution

for in-house software

7. Business requirements statement – defines and prioritizes business and users’ requirements.

8. System proposal – analyzes candidate solutions for software

9. Application architecture – defines the system’s design process.

10. Database structure – designs and constructs database schema and database program


11.Operational System – prepares conversion plan .

Assumptions:

Operational feasibility – the system will require training for users.

Technical feasibility – the system will be able to handle projected growth of the business in

the future.

Economic feasibility – stream-lining the current business processes will improve efficiency

and reduce costs.

Constraints:

Budget Constraints

The system cannot cost more than $160,000.

The system must be able to attain a 50% improvement level.

Technology Constraints

The system must provide employee self-services

The system must coordinate HR/Payroll implementation with insurance carriers’ system.

The system must automatically update changes and calculate deductions based on

insurance carriers criteria.

The system must enable HR/Payroll administrators to track past, current, and pending

employee benefit file.


Appendix D HRMS Work Breakdown StructureTBD Below is a generic WBS in Excel Spreadsheet form. The original WBS will be created in Microsoft Project 2003 and be implemented in the Final Draft.


Appendix E Stakeholder Communication Analysis


StakeholdersAccountability

Document Name/Delivery

DocumentFormat

Objectives Frequency Permission

Access

Sponsor System Improvement Report

(Repository)DatabaseDirectory

To review expectations for the new system.

Bi-Monthly read, write, make changes

PM, HRM, BM, IT, DBA, QM, SA, ADV

Sponsor Team Progress Report

E-mail To express support and appreciation of the project team’s accomplishments.

Bi-Monthly PM, HRM, BM, IT, DBA, QM, SA, ADV

Project Manager

Project Status Report


To review successes, constraints and progresses.

Bi-weekly read, write, make changes

SP, HRM, BM, IT, DBA, QM, SA, ADV

Project Manager

Project Charter (Repository)DatabaseDirectory

To review work being performed during the final project development.

As needed read, write, make changes


Project Manager

Project Schedule (Repository)DatabaseDirectory

To review outlined activities and tasks for the planned project.

Monthly read, write, make changes


Project Manager

System ProposalReport

Hard copy Evaluate recommended system solution and feasibility assessment.

As needed SP, HRM, BM, IT, DBA, QM, SA, ADV

Project Manager

Risk Management Plan


To evaluate and control what might go wrong in the final project before it becomes a threat.



Project Manager

Change Control Log


To review and managed appropriate changes throughout the final project.



Project Manager

Implementation Plan


To review and ensure that the installed system software meets user requirements and expectation.



Project Manager

Conversion Plan (Repository)DatabaseDirectory

To review the strategy and smooth transition of converting from the old system to the new system.



Project Manager

Team Meeting E-mail To provide the opportunity to develop ideas and collaborate on the final project.

Bi-weekly SP, HRM, BM, IT, DBA, QM, SA, ADV

HR Manager Staff Acquisition Plan


View the needs of each team members’ tasks and work hours.

As needed SP, PM, BM, IT, DBA, QM, SA, ADV


HR Manager Team DevelopmentPlan


To review team members’ productivity and create an environment for growth and prosperity.


SP, PM, BM, IT, DBA, QM, SA, ADV

Business Manager

CommunicationPlan

Email Provide appropriate and consistent levels of information to all stakeholders

Weekly read, write, make changes

SP, PM, HRM, IT, DBA, QM, SA, ADV

IT Design Statement (Repository)DatabaseDirectory

Serves as a blueprint for the detailed design system.


SP, PM, HRM, CFO, DBA, QM, SA, ADV

IT Process/Logical Models


To review system models and business processing requirements.



Database Administrator

Database prototype (Repository)DatabaseDirectory

To review design specifications and requirements.


SP, PM, HRM, CFO, IT, QM, SA, ADV

Database Administrator

Application Architecture


To review internal and external design of each system components.



Quality Manager

Quality Plan ISO Manual To evaluate and monitor the deliverables and overall project performance.

Periodically read, write, make changes

SP, PM, HRM, CFO, IT, DBA, SA, ADV

Quality Manager

Audit Test Plan (Repository)DatabaseDirectory

To certify that the system is free of errors and is ready to be placed into operation.

Periodically read, write, make changes

SP, PM, HRM, CFO, IT, DBA, SA, ADV

Systems Analyst

RequirementsStatement


To review specified system requirements.


SP, PM, HRM, CFO, IT, DBA, QM, ADV

Systems Analyst

Use Cases (Repository)DatabaseDirectory

To review system functions and graphical requirements of the business.


SP, PM, HRM, CFO, IT, DBA, QM, ADV

Quality Manager

Test Plan (Repository)DatabaseDirectory

To review appropriate system testing and verify all requirements

Periodically Read, write, make changes

SP, PM, HRM, CFO, IT, DBA, QM, SA

Advisor Training Plan Manual To provide group training and properly guide

As needed SP, PM, HRM, CFO, IT, DBA, QM, SA

Key Access Role: SP – Sponsor PM – Project Manager HRM – HR Manager SA – Systems Analyst QM – Quality Manager CFO – Chief Financial Officer IT- Information Tech DBA – Database Administrator


Appendix F Status Report

Project Name: Project Management HRMS projectTeam Member Name: Monica Macedon, [email protected]: November 1, 2005Work completed this week:Work to complete next week:What’s going well and why:What’s not going well and why:Suggestions/Issues:Project changes

Appendix F Control Change Plan

Process Topic Item Manage

Cost Control Project Cost Management

Cost estimating, cost budgeting

Measure, monitor, and control overall cost performance. Documentation of any constraints.

Quality Control Quality Management Plan

Quality assurance, Quality checklistsQuality Metrics

Determine correctness of deliverables. Recommended corrective actions. Documentation of lesson learned.

Risk Monitoring and Control

Project Risk Management

Risk IdentificationQualitative Risk AnalysisRisk response planning

Documentation reviews. List of identified risks and root causes. Update risk register.

Schedule Control Project Time Management

Schedule development. Activity definition and activity sequencing.

Identifying and documenting logical relationships among schedule activities. Periodic Progress reporting.

Table 1. Control Change Plan

mailto:[email protected]


Appendix G HMRS Cost Estimates

HRMS Project Estimated Cost for a Proposed System Solution and supporting detailsEstimated Costs for Proposed Systems Solution

DEVELOPMENT COSTS:

Personnel:

1 Project Manager(418 hours/ea $65.00/hr) $ 27,170.00

1 Sponsor(198 hours/ea $50.00/hr) $ 9,900.00

1 Quality Manager(110 hours/ea $50.00/hr) $ 5,500.00

1 Business Manager (98 hours/ea $50.00/hr) $ 4,900.00 1 HR Manager (84 hours/ea $50.00/hr) $ 4,200.00

1 IT Tech(252 hours/ea $40.00/hr) $ 10,080.00

1 Systems Analyst(322 hours/ea $50.00/hr) $ 16,100.00

1 DB Administrator(218 hours/ea $40.00/hr) $ 8,720.00

1 Payroll Advisor (156 hours/ea $30.00/hr) $ 4,680.00

Total $ 91,250.00

Expenses:6 Group training for system users ($995.00/student) $ 5,970.00

Total $ 5,970.00

New software & hardware:1 MS SQL Server DBMS $ 3,000.00 1 HRMS software application $ 4,000.00 1 Intranet/Intranet Client/Server $ 19,000.00 1 DBMS server software $ 4,500.00 7 DBMS client software ($800.00 per client) $ 5,600.00

Total $ 36,100.00

Total Development Costs: $ 133,320.00

Projected Annual Operating Costs

Personnel:


2 Programmer/Analyst(125 hours/ea $35.00/hr) $ 8,750.00

1 Database administrator (30 hours/ea $20.00/hr) $ 600.00 Total $ 9,350.00

Expenses:

1Program/System Maintenance Fee $ 995.00

1Maintenance Agreement for Server DBMS server $ 385.00

1 Software license payments $ 525.00 $ 1,905.00

Total Projected Annual Costs: $ 11,255.00


Appendix H Risk Management Plan

Knowledge Area/Category

Risk Identification Severity Probability Mitigation Strategies

Project Initiation Schedule Commitment - needto identify adequate resources to allocate to the scheduled tasks at the scheduled time.

High Medium Produce a more detailed plan to identify stakeholders at the start and establish the procedures that will be used by the project stakeholders.

Project Planning Scope

Business Strategic Objectives – cannot start project planning until a business plan is develop.

High Medium Conduct an analysis study and develop a plan to address risk to stakeholders and the project team.

Project Cost Management

Budge and Costs – cost overrun of project funding likely to occur.

High Low Monitor project approved expenditures and report status of budget on a monthly basis.Actual or potential problems need to be communicated to Executive Steering Committee for immediate resolution.

Project Risk Management

Project Management Ability and Expertise – cannot implement risk plan without appropriate management and technical risk assessment.

High Medium Adequate risk assessment practice. Develop a procedure document on Risk Identification, Qualitative Risk Analysis, Risk Response Planning, and Security Planning.

Project Scope Management

Change Organizational Structure and Focus – misalignment of work, policies, and procedures will affect the business strategy and goal.

High Medium Establish a preliminary or baseline scope during the initial project plan. Educate stakeholders about effects of changes. Adopt a formal change management plan.Develop a contingency plan.

Project Quality Management

Product Performance Requirements – failure or non-conformance is likely to result in design problems/functions.

High Medium Develop explicit rules that must address the business requirements. Prioritize requirements

Cost Estimation Economic Conditions – new software technology.

Moderate Low Develop an economic analysis and forecasting plan.

Process Management Development Process/Tools – poor quality software will exceed schedule and budget.

High Low Integrate agile methodologies and tools that will support in-house software solution.

Project Management Technical Approach – functionality of the system must be optimized to fit the business

High Low Follow a system philosophy to understand how the final project relates to the business.Continuously reevaluate feasibility and risks through out the final project.

Project CommunicationManagement

Stakeholders Needs – misinformation, stress tension, and lack of accountability can create low performance level and time wasted.

High Medium Create a communication plan Establish a community portal (Intranet) to open lines of communication. Interpersonal, effective communication, and


listening skills. Table 2. Risk Management Plan MatrixAppendix I Business Requirement Use Case

{Employee Self Services System}

Author (s): Monica Macedon_ Date: October 28, 2004 Version:1.0__________

USE CASE NAME: Select Benefits USE CASE TYPEUSE CASE ID: BEP BUC00-1.0 Business Requirements:

PRIORITY: HighSOURCE: Requirement – BPE-R1.00PRIMARY BUSINESS ACTOR:

Employee

OTHER PARTICIPATING ACTORS:

Human Resources Payroll Department Insurance Carriers

OTHER INTERESTED STAKEHOLDERS:

Business/Financial Management – Interested in enrollment activity in order to manage the company’s financial resources.

Insurance Carriers – Interested in enrollment activity in order to collect premiums.

Board of Directors – Interested in benefits activity in order to evaluate company performance and employee satisfaction

DESCRIPTION: This use case describes the event of the employee making online benefits enrollment selections and receiving confirmation directly from Eastern Carolina Vocational Center’s web-based, self-service site. The employee’s enrollment data is a validated accordingly to the business rules and imported to HR database. On completion, the employee will be sent a confirmation statement.

PRE-CONDITION: The employee submitting the benefits selection is subject to final employer authorization.

TRIGGER: This use case is initiated when benefits selection is submitted.TYPICAL COURSE Actor Action System ResponseOF EVENTS: Step 1: The employee

provides his or her network credentials (username and password).

Step 2: The system responds by validating all required information that has been provided by the user against the employee record in HR database.

. Step 3: Once authorized, the system asks the user to view, browse, and make selections. Step 4: If employee views current status, the system displays benefits package. Step 5: If the employee browses for choices, the system presents available benefits plans according to the user’s preferences.Step 6: If employee decides to make a selection that is finalized, the system presents a summary of the employee’s choices and costs.Step 7: Once the employee saves the choices, the system generates a confirmation


statement and sends it to the employee by email.

ALTERNATE COURSES:

Alt-Step 2: If an employee does not enroll within the allotted time, the default level of coverage will be applied. Notifications to the employee will be generated.Alt-Sep 3: If changes are required due to major life events (birth, injury, etc.), the employee can review their benefits selection and make changes as required, throughout the year.

Alt-Step4: If missing or incorrect information, or requirements of rules that are overlooked, the system will automatically inform the employee to edit the information correctly.

Alt-Step 5: If the member requests additional assistance, the system answers simple employee questions regarding their benefits and helps the employee research physicians, access and completes forms, and contact agents and insurers.

CONCLUSION: This use case concludes when the employee receives a confirmation statement.

POST-CONDITION: The benefits selection has been transmitted to the HR database.BUSINESS RULES Confidentiality of employee benefits information, authentication,

authorization, access and data integrity are secured.IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS

Web-based interface to be provided for Eastern Carolina Vocational Center’s users, and web screen to be provided for employees.

ASSUMPTIONS: The system should send e-mail reminders to those who haven't enrolled.

OPEN ISSUES: None

Figure 1 “Select Benefits” Use Case

Systems Analysis Use Case

{Employee Self Services System}

Author (s): Monica Macedon_ Date: October 28, 2004 Version: 1.0__________

USE CASE NAME: Maintain Benefits USE CASE TYPEUSE CASE ID: BPE BUC00 -1.0 Systems Analysis: PRIORITY: HighSOURCE: Requirement – BPE-R1.00PRIMARY BUSINESS ACTOR:

Human Resources

OTHER PARTICIPATING ACTORS:

Employees Payroll Department Insurance Carriers

OTHER INTERESTED STAKEHOLDERS:

Business/Financial Management – Interested in enrollment activity in order to manage the company’s financial resources.

Board of Directors – Interested in benefits activity in order to evaluate company performance and employee satisfaction

Insurance Carriers – Interested in enrollment activity in order to collect premiums.


DESCRIPTION: This use case describes the event of Human Resources processing a benefits package for the employee. The employee’s benefits information is extracted from HR database and views the validated employee’s benefits statement. Once the benefits package is approved, a report is created and transmitted to the Payroll database.

PRE-CONDITION: The HR associate must be provided with a complete list of required administrative tasks.

TRIGGER: This use case is initiated when the benefits package is processed.TYPICAL COURSE Actor Action System ResponseOF EVENTS: Step 1: HR associate extracts

employee demographic data from the Benefits Enrollment database.

Step 2: The system responds by returning the electronic data into HRIS.

Step 3: The HR associate imports the data into a spreadsheet report.

Step 3: The system displays the employee’s benefits and costs summary.

Step 4: The HR associate views the benefits package. If no changes are made, the associate approves and saves the data.

Step 5: The system retrieves and process the data, then uploads the information into the Payroll database.

ALTERNATE COURSES: Alt-Step 6: If the benefits package requires changes, the HR associate can place the benefits package on hold (the associate contacts the employee, either by a valid e-mail or in person). The system place the information in pending status. Once the employee is contacted and changes are made, the system reprocesses the package (go to step 5). Alt-Sep 3: If the HR associate needs assistance, the system’s authoring tools provide guidance through a series of questions to gather and manage data and policy changes.

CONCLUSION: This use case concludes when HR completes and/or updates the benefits package.

POST-CONDITION: The benefits package has been uploaded to the Payroll database.BUSINESS RULES Data is defined by the business’ benefits offering of eligibility and premiums.

Event code-driven that corresponds to data requirements are generated when a given event code is used.

IMPLEMENTATION CONTRAINTS AND SPECIFICATIONS

Provide the logic, calculations and data to define a business’ benefits offerings in order to verify eligibility and premiums.

Provide employees self-service access to their benefits. Provide data connectivity and synchronization to insurance providers, HR,

information systems, and payroll. Transmits data to HRIS and payroll system (for payroll deduction and data

synchronization), then to benefit providers via an EDI interface.ASSUMPTIONS: HR must be trained to update application, for example, change benefits level

(separate use case). Employees have online, year-around access to their own benefits, HR and

managers will become less involved in administering the employment lifecycle.

OPEN ISSUES: Need to determine how insurance carriers are communicated. The new application and process must be integrated with HR and payroll databases (Change Management Process). Integrates with this vendor’s systems for COBRA administration, HIPAA compliance, and retiree premium billing.

Figure 2 “Maintain Benefits” Use Case


Appendix J Benefits Use Case

Figure 3. Benefits Use Case Diagram


Appendix J Activity Diagram


Figure 4. Activity DiagramAppendix K Organizational Structure Web Site


Figure 5. Information ArchitectureAppendix L Network Architecture

ECVCHomepage

Personal DataManagement

Life/Health/Accidental Death Plan

Long TermDisability Plan

Medical/Dental/ Vision Plan

EnrollmentProcess

InformationCenter

CompanyInformation

SupportDesk Form

Gate Keeper

EnrollmentMenu

PrivacyStatement

Successful Login

InvalidLogin

Sign Out

Terms Of Use

OpenEnrollment

Short TermDisability Plan

Login Area 1

Thank You Confirmation

Update Personal Data Management Form

Update Enrollment Process Form

Eastern Carolina Vocational Center,

Inc.Secure Access


Benefits InformationandService Response

Automatically Upload Files

Read requestedBenefits Selection

and eligibility

MailFiles

Communication Employee Data Exchange ECVC Data Exchange Carrier Data Exchange

Windows/Access2000

SQL/Serverexecuted here

Database

Retrieve Benefits Information Request

Request to create, read, update, or delete records Import Files

UpdatedBenefits

User

Web Browser

Web ServerHTML/JAVAWeb scripts

executed here

Client PCEnrollment

Internet Explorer and Netscape

HTML: Page Content andXML: Data Content

Benefits Information and Service Requests

Authentication

Employee Protected Login Area

Web Server

Simple Mail Transfer Protocol (SMTP)

File Transfer Protocol (FTP)Utility enables file transfer to and from the server

Enroll Access

Application logic executed here

Application Server

ESS Database stored here

WebPages

Figure 6. Network Computing System: Intranet/InternetLinking an internal database to the Web.


Appendix M Test Plan

Purpose

This test plan is designed to describe the HRMS Project’s scope, approach, resources, and

schedule of all activities. The plan identifies the items to be tested, the features to be

tested, the types of testing to be performed, the personnel responsible for testing, the

resources and schedule required to complete the testing, security, and the risks associated

with the plan. This document will be used to test and validate functional and technical

requirements, which supports the following objectives:

Analyze users, needs, and tasks/determine test user groups:

Find problems with the information structure in order to improve it

Ensure integrity and availability of the database environment

Incorporate software engineering/AQ Assurance practices/standards

Determine usability/accessibility task goals

Measure qualitative and quantitative data

Schedule key dates for testing

Develop test cases/create scenarios

Prepare test documents/test environment software

Scope Definition

This document provides instruction and strategy for incorporating software testing

practices and procedures into the project. The scope of the project team’s work is

presented in a Work Breakdown Structure. Requirements specification (Business Use

Case), Design Specifications (Business Activity Diagram and Application Architecture

Structure) will be use to create test cases.


Test Goals

Test all modifications, interfaces and data delivery developed for the

implementation

Test design specification and requirement specification

Validate all set up, Web pages (HTML), and security login

Determine errors, report errors for resolution prior to implementation

Features (availability, response time)

Validate Quality Conformance Report

Features Not To Be Tested

Entity Relationship Diagram/Data Integrity Rules – they will be addressed by the

existing Business Case and Activity processes.

Assumptions

The tools, resources, technical support, and infrastructure essential for testing will be

available through a successful implementation. Necessary project team members

(includes key departments) will assist in or resolve any problems discovered during

testing.

Risks

Shortage of testing personnel due to illness or understaffed. The contingency plan

is to train other team members to use testing tools and testing methodologies.

Not enough time to adequately test all processes before the implementation date.

The contingency plan is to prioritize testing efforts, testing critical and major

processes early in the schedule as soon as possible.


Software Test Strategy

This approach describes in details the major testing tasks and identifies the types of

testing to be performed along with the methods, criteria, procedures, and software

environment requirements to be used in performing test activities.

Testing Roles and Responsibilities

This table presents the recommended resources for the HRMS Project, their main

responsibilities, and their knowledge or skill set.

Role/Worker Specific ResponsibilitiesTest Project Manager – Monica Provides technical direction, acquire

appropriate resources, and provide management reporting

Test Manager – Beth Provides management oversight and monitor testing process.

Test Designer(s) – Crystal, Monica Generates and document test case for functional and performance testingTest Web interfaces, input/output control modules

Test Designer - Crystal Evaluates effectiveness of test effortsProject Manager - MonicaTester - John Documents test results and problemsData Logger - Tina Observes and logs data metricsTest System Administrator - Charles Set-up and maintain software environmentTest Moderator- Monica Performs usability/accessibility testDatabase Administrator - Ellen Ensure test data (database) are managed and

maintainedSecurity Testing - Monica Test logon security and apply security rolesQA Management - Doug Quality assurance testing validating

individual components of softwareTechnical/Security Setup - Charles Provides technical support for testing toolsAcceptance testing - All workers Ensure user requirements and objectives are

met. Table 1. Roles and Responsibilities

Software Test Environment

Environmental requirements are described below to specify both the necessary

and desired properties for the test environment:


Software items – Windows XP, Microsoft Navision Server, HTML, ASP

JavaScript, ASP VBScript & CGI Script, ESS Database, Open Database

Connection with Microsoft Access 2000

Interface item - Macromedia Dreamweaver MX 2004

Hardware items – Intel Pentium III Processor with 1GB of RAM and redundant

disk storage

Network - Three-tiered client/server

Communications – Web (Intranet/Internet), Employee Data Exchange, Business

Data Exchange, Carrier Data Exchange

Equipment items – one computer workstation with the full software, softer

lighting, and three seats: one for the participant, one for the test monitor, and one

for the observer (data logger)

Assistive Technology – if needed, can provide screen readers,

voice input, alternative keyboard or pointing device

Test lab set-up – located in business testing room

Other materials – test scripts and final testing report

Tools – Web guideline checklist, HTML authoring tool, SQL

Scripting tool, Web Design HTML Validator, W3C Validation

tool, data collection instruments

Staffing and training needs – training on the software, training for

any test tools to be used, provide onsite usability expert for users

with accessibility issues or problems.


Schedule

The schedule is based on realistic and validated estimates, which ties all test dates

directly to their related development activity dates. This will help in identifying and

tracking potential slippage in the schedule caused by the test process. See Appendix A of

the developed timeline for the Execute Test development.

Testing Types

Each type of test provides a description and technique of the test and why it is being

implemented and executed.

Function Testing

The target of this test focuses on the requirements that are traced directly to the Business

use case and business rules. See Table 2, below for this testing.

Test Objective: Ensure proper test functionality of site navigation, data entry, form processing, and retrieval

Technique: Execute an input form using valid and invalid data to verify the following:

The expected results occurred when valid data is used (input form processed successfully) The appropriate error or warning messages are displayed when invalid data is used.Navigation provides a logical architecture to the information in the site. Consistent primary navigation (links to home page and other key content areas) on all pages.

Completion Criteria: All planned test executed and each business rules applied properlyAll identified defects been addressed (description of one target page inaccurate) Applied appropriate link description

Table 2. Function Testing

Data and Database Integrity Testing The target of this test focuses on the subsystem of the HRMS Project. See Table 3 on the

next page for this testing.


Test Objective: Ensure database access methods and processes function properly and without data corruption.

Technique: Invoke SQL scripting for proper loading of all tables in the database through DSN connection to the database to check the following: Database has been populated as intended, including events of updating. Data validated properly. Correct data was retrieved for the correct reason

Completion Criteria: All database access methods and processes function as designed and without any data corruption. No defects addressed

Table 3. Data/Database Integrity Testing

User Interface Testing

The target of this test verifies a user’s interaction with the system. See Table 4, below for

this testing.

Test Objective: Verify the following:User Interface provides the user with the appropriate access methods (tab keys, mouse movements) and navigation Window objects and characteristics, such as menus, size, position, and focus conform to standards

Technique: Create or modify each window to verify proper navigation and object for each application window

Completion Criteria: Each window successfully verified to remain consistent within acceptable standards.

Table 4. User Interface Testing

Web Page Testing

The target of this test verifies each Web page document for HTML conformance. See

Table 5 below, for this testing.

Test Objective: Verify the following:test internal controls such as authorization to login, functional testing of command action buttons validate each Web page for syntax errors and undefined document type definitions

Technique: Tools used to test for valid HTML:

HTML authoring tool in Macromedia Dreamweaver MXWeb Design HTML Validator

Completion Criteria: Each Web page has been validated for HTML conformance.Table 5. Web Page Testing


4.1 Security and Access Control TestingThis testing focuses on two key areas – Application-Level security and System-

Level Security. See Table 6 below, for this testing.

Test Objective: Application-level Security: Verify that a user can access onlythose functions or data for which their user type is providedpermissions.System-level Security: Verify that only those users with accessto the system and applications are permitted to access them.

Technique: Application-Level - Identify and list each user type and the functions or data each type has permissions for.System Access Level – see consideration below

Completion Criteria: Transaction permission for each data typed is verified correctly as available or denied access rights.

Consideration: Access to the system must be reviewed with the appropriate network or systems administrator. This testing may not be required as it may be a function of network or systems administration.

Table 6. Security and Access Control Testing

Usability/Accessibility Testing

Now that all functional testing has been completed, this testing focuses on the system

performance to measure the success rate for participants using the site to perform specific

tasks. See below for the Usability/Accessibility Testing Plan

Introduction

This document describes the usability/accessibility testing plan for

http://www.lc.capellauniversity.edu/~143714/SecureAccess.html. The purpose of a

usability evaluation is to predict the expected performance of the actual user using the

current product and materials, as well as detect any serious problems prior to the release

of the product. This plan includes the following sections:

User Testing Preparation Worksheet Task lists Testing scripts Design of the usability evaluation

http://www.lc.capellauniversity.edu/~143714/SecureAccess.html


User Testing Preparation Worksheet

User Testing Project __ HRMS Project_________ ____________________________________ Scheduled Dates and Times _____________________________________________________Location: On-site testingTesters _____________________________________________________________________Observers ___________________________________________________________________Required demographic _________________________________________________________Number of test users 4__________________________________________________________Computer configuration(s): Hardware ___________________________________________________________________OS and version ______________________________________________________________Browser and version __________________________________________________________Other software ______________________________________________________________Other equipment: Stopwatch

Task listTo clarify the goals of this test, the testing script provides the exact wording for each of these:

Task 1. Speed, Design Structure Task 2. Main navigational elements (links, navbars) Task 3. Is site useful for disabled users?

Task 1 Description

TaskStarting StateSuccessful Completion CriteriaBenchmarkScript

Task 2 Description


Task 3 Description


Usability/Accessibility Evaluation Form


Tester’s name_________________________

Task tested_____________________

User’s name__________________________

Design of the Usability/Accessibility Form

This evaluation is to ensure that the web site is on track to satisfy the goals of the design and the user.

Observe the user:

1. User preference setting.2. Does the user get frustrated/confused

while completing the task or a specific step?

3. Did the user complete the task successfully?

Accessibility of web site.Interview the user and analyze the data based on your observations and interview:

1. What is the biggest problem with the site?

2. Navigating the web.

3. Did the visual design and style help the user, or did they create problems? What problems? How can they be solved?

4. Download time and system performance time.

5. Error tolerant.

Make recommendations based on your analysis:

1.2.3.4.5.

Form 1. Usability/Accessibility Evaluation Form


Web Usability and Accessibility Guide

1. Technical Features:Description Compliance

Yes No Partial1.1 Appropriate DOCTYPE tag at the top of each page, e.g. <!

DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>Appropriate use of KEYWORDS and DESCRIPTION meta tags.Compatibility with current Netscape and Microsoft IE browsers

1.2 Compatibility with current Netscape and Microsoft IE browsers

1.3 Appropriate html TITLE (in head section) for each page1.4 Appropriate use of KEYWORDS and DESCRIPTION meta tags1.5 Compatibility with current Netscape and Microsoft IE browsers

Results

1.6 Site Speed (seconds) 1st 2nd average

Home page download time with 56 kbps modem (two attempts)

1.7 Broken Links Total Broken % links links broken

1.8 Broken links on site

2. Essential Information:Description Compliance

Yes No Partial2.1 Clear identification of business on home page

2.2 Privacy and Terms Of Use easily available from all relevant pages

2.3 Feedback facility and/or email link to an appropriate person2.4 Human Resource contact information available from home

page2.5 Date of Last Update of information on pages

Usability Scoring Information

The N/A – the item described in the statement is not available at all;

1. Strongly Disagree – the statement DOES NOT apply to almost the entire site and/or

any pages of the site;

2. Disagree - The statement DOES NOT apply to most of the site and/or any pages of the

site (about 70%);

3. Neither Agree Nor Disagree – with the statement;


4. Agree – The statement DOES apply to most of the site and/or any pages of the site

(about more than 70%);

5. Strongly Agree – The statement DOES apply to almost the entire site and/or any

pages of the site.

3. NavigationDescription N/A Strongly Disagree/

Strongly Agree1 2 3 4 5

3.1 The navigation features of the site are clear and easy to use.

3.2 The link labels and link names were clear and directed me to the correct information.

3.3 There is clear and consistent primary navigation (finding links to the home page and other key content are) on all pages.

3.4 The text used for links is descriptive, appropriate and useful.

4. Content:Description N/A Strongly Disagree/


4.1 All information is accurate and requirements met.

4.2 The content is suitable and relevant to the purpose of the site.

4.3 The headings and subheadings are meaningful to the users of the site.

4.4 Key content is presented in languages appropriate to the users of the site.

5. Page layout and presentation:Description N/A Strongly Disagree/


5.1 The site clearly identified the services and information available.

5.2 No errors in spelling, punctuation or grammar.

5.3 All images have an ALT tag describing the image and where it links.

5.4 Forms on the site contain sufficient information about their purpose and the form fields are easy to identify and fill in.

5.5 The page layout is uncluttered, clear and easy to follow.

5.6 Each page has appropriate heading or identifier that is consistent with the link label.

5.7 All content in tables are contained within the display screen area with a setting of 800x600 pixels.

6. Accessibility:


Description N/A Strongly Disagree/Strongly Agree1 2 3 4 5

6.1 Alternative text provided for all image type buttons in forms.

6.2 No errors in spelling, punctuation or grammar.

6.3 All images have an ALT tag describing the image and where it links.

6.4 Forms on the site contain sufficient information about their purpose and the form fields are easy to identify and fill in.

6.5 The page layout is uncluttered, clear and easy to follow.

6.6 Each page has appropriate heading or identifier that is consistent with the link label.

6.7 Use of high contrast and highly legible fonts

Test Results TBD


SYSTEM IMPLEMENTATION

Integration Plan

The purpose of the implementation is:

To define the organization of the code, in terms of implementation subsystems organized

in layers

To implement classes and objects in terms of components (source files, binaries, and

executables).

To test and develop components as units

To integrate the results produced by individual implementers (or teams), into an

executable system.

Workflow will be managed through the document approval and information copy process.

Integrated imaging must support the storage and retrieval of both systems generated and

manually prepared documents. Appropriate business and technical resources will be available

during the project’s duration.

Conversion Plan

Conversions to a new system will require mapping old data elements to new elements in the

new data structure (SQL Server). Extraction of the flat files in its raw form will enable the web

based technology to access the data via an import program. Then business rules must be applied

to determine which system has the best data quality. Always extract the data from the legacy

system in its raw legacy stored form to a delimited flat file format. This serves two purposes.

First, a delimited flat file enables every technology to access the data via an import. Steps of the

conversion plan include:

Plan or revision of an existing one

Yes


Document data flow and actions

Develop functional and technical models

Assess IT and user issues for flexibility

Identify relationships between the data

For each repository document, the actions performed on and controlled by data

Develop a logical data architecture

Schema and Meta Data sources

Develop a physical data architecture

Identify non-relational and relational

constraints

Develop, extract, transform and load processes

for each database

Develop cleaning process

Determine data loading process - ODBC/JDBC

Determine the appropriate tools to execute

conversion

Develop audit trail and track business metrics


CONCLUSION

TBDQuality Conformance ReportUser AcceptanceRelease of software


References

Skilled Team Members:

Monica Macedon – Project Manager (managing project)

Daneel LeRoux – President (sponsor)

Charles Buck – business analyst/IT expert (mentor)

Beth Davis – Chief Financial Officer

John Salisbury – Human Resource

Crystal Talmadge – Systems Analyst

Ellen Jackson – Database Administrator

Doug Bonds – Quality Manager

Tina Wainwright – Payroll Supervisor

Configuration Management: Best Practices White Paper (2005). Figure 1. High-level

process flow for Configuration Management Plan.

http://www.cisco.com/warp/public/126/configmgmt.html

Do It Yourself Assessment 2001. Retrieved on 11-01-2005, from Web site:

http://www.dartmouth.edu/~webteach/articles/assessment.html

Gomik, Davor (2001). IBM Rational Unified Process: Best Practices for Software

Development Teams.

http://www-306.ibm.com/software/rational/offerings/lifecycle.html

http://www-306.ibm.com/software/rational/offerings/lifecycle.html

http://www.dartmouth.edu/~webteach/articles/assessment.html

http://www.cisco.com/warp/public/126/configmgmt.html


Green, Garo & Lynda Weinman (2004). Macromedia Dreamweaver MX 2004. Hands-on

training. Published by Peachpit Press. Indianapolis, IN>

Martin, Paula K. (2001). The new role of the Project Manager. Retrieved on 10/08/05,

from Web site: www.gantthead.com/article.cfm?ID=15744&authenticated=1

Mochal, Tom (2003). Project mangers must manage their work plans to be successful.

Retrieved on 10/08/05, from Web site: http://techrepublic.com.com/5100-6315-

5034543.html

Noyes, Brian (2002). Define a flexible process with Rational Unified Process.

Retrieved from Web site:

http://www.fawcette.com/resources/managingdev/methodologies/rup/

Project Management Body of Knowledge (2004). 3rd Edition. Published by Project

Management Institute, Inc. Newtown Square, Pennsylvania.

Project Management Framework (2004). Retrieved on 10/12/05, from Web site:

www.dis.wa.gov/pmframework/planning/communications.htm

Raynor, Darrel (1998). Communicating Risk to Management. Retrieved on 10/12/05,

from Web site: www.projectmanager.com/dataanalysis/RaynorColumns.htm

http://www.projectmanager.com/dataanalysis/RaynorColumns.htm

http://www.dis.wa.gov/pmframework/planning/communications.htm

http://www.fawcette.com/resources/managingdev/methodologies/rup/

http://techrepublic.com.com/5100-6315-5034543.html

http://techrepublic.com.com/5100-6315-5034543.html

http://www.gantthead.com/article.cfm?ID=15744&authenticated=1


Schwalbe, Kathy (2004). Information Technology Project Management. 3rd Edition.

Published by Course Technology. Boston, Massachusetts.

Sharma, Sunil (2002). Determining ROI of IT Projects: But how do you quantify all

benefits? Retrieved on 10/13/05, from Web site:

www.gantthead.com/article.cfm?ID=145956&authenticated=1

Software Test Plan (STP) Template (n.d.). Retrieved on November 10, 2005, from

Web site:

http://www.industrex.com/dynamic/reference/software_test_plan_template.doc.

Test Plan Recruitment (2005). Retrieved on October 19, 2005, from Web site:

http://stars.sas.cornell.edu/testing/recruittestplan.pdf

http://stars.sas.cornell.edu/testing/recruittestplan.pdf

http://www.industrex.com/dynamic/reference/software_test_plan_template.doc

http://www.gantthead.com/article.cfm?ID=145956&authenticated=1

download

Business

project deliverable

project controlling

project execution10

project activities

managingthis project

project usability

project quality management

project management technology