Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Monica Macedon 1 6/3/2010 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
  2. 2. Monica Macedon 2 6/3/2010 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
  3. 3. Monica Macedon 3 6/3/2010 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
  4. 4. Monica Macedon 4 6/3/2010 Figure 5. Information Architecture Diagram 33 Figure 6. Network Architecture Diagram 35 Conclusion 50 References 51
  5. 5. Monica Macedon 5 6/3/2010 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.
  6. 6. Monica Macedon 6 6/3/2010 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.
  7. 7. Monica Macedon 7 6/3/2010 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.
  8. 8. Monica Macedon 8 6/3/2010 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
  9. 9. Monica Macedon 9 6/3/2010 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.
  10. 10. Monica Macedon 10 6/3/2010  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
  11. 11. Monica Macedon 11 6/3/2010 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.
  12. 12. Monica Macedon 12 6/3/2010 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
  13. 13. Monica Macedon 13 6/3/2010 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.
  14. 14. Monica Macedon 14 6/3/2010 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
  15. 15. Monica Macedon 15 6/3/2010 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.
  16. 16. Monica Macedon 16 6/3/2010 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, 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
  17. 17. Monica Macedon 17 6/3/2010 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 Project Manager Monica Macedon ECVC, Project Manager Team Member John Salisbury ECVC, Human Resource Manager
  18. 18. Monica Macedon 18 6/3/2010 Team Member Beth Davis ECVC, Chief Financial Officer Business Department Team Member Charles Buck ECVC, System Designer IT Department Team Member Ellen Jackson ECVC, Database Administrator Team Member Doug Bonds ECVC, Quality Manager Team Member Crystal Talmadge ECVC, Systems Analyst Team Member Tina Wainwright ECVC, Payroll Department Sign-off: Dan LeRoux John Salisbury Charles Buck Doug Bonds Crystal Talmadge Monica Macedon Beth Davis Ellen Jackson Tina Wainwright
  19. 19. Monica Macedon 19 6/3/2010 Appendix C - Scope Statement Project Title: Project Management HRMS Project Date: October 10, 2005 Prepared by: Monica Macedon, Project Manager, (252) 341-7763 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 .
  20. 20. Monica Macedon 20 6/3/2010 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.
  21. 21. Monica Macedon 21 6/3/2010 Appendix D HRMS Work Breakdown Structure TBD 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. Name Human Resource Management System Sponsor - Daneel LeRoux Start Date 10/10/2005 End Date 12/18/05 Strategic Design and Development Plan Actual Start Item No Task Completion Date Activities Resources Date 1. Project Initiation 10/10/05 10/12/05 1.1 Define project scope 10/10/05 10/10/05  * Analyze current and future state Monica, mentor Charles statement of the benefit process. * Identify business long-term objectives 1.2 Prepare project charter 10/11/05 10/11/05  *Create letter of agreement of Dan, Monica, Beth, John, initiated project and project Charles, Jeanette, Tina, objectives. Doug, Ellen, Joe, Crystal *Clarify roles, expectations and signatures for the project. 1.3 Team contract 10/11/05 10/12/2005  *Review signed project charter. Dan, Monica, Beth, John, * Each member to contribute ideas Charles, Jeanette, Tina, and input for the contract. Doug, Ellen, Joe, Crystal Project Planning 10/13/05 12/2/05 2.1 Develop project plan  *Systems Requirement Analysis Monica, Charles *Prepare systems design/application *Prepare schedule & cost baseline *Prepare WBS *Prepare tasks & assign resources *Direct team effort *Monitor & control process *Communicate project progress/issues 3. Executing Project 10/17/2005 12/02/2005 3.1 Evaluate current system  *Analyze problem Monica, Crystal *Analyze business process *Interview users *List business functional/nonfunctional features *List business rules & guidelines *Present findings and recommendations
  22. 22. Monica Macedon 22 6/3/2010 3.7 Implement system 11/28/05 12/02/05  *Conduct final iteration testing Monica, Joe, Jeanette, *Place new system into operation Tina *Install populated database with existing data from old system *Prepare conversion plan *Train end-users and provide them with user manuals *User feedback *Ongoing technical support *Program maintenance for software bugs 4. Project Controlling 10/13/2005 12/02/2005 4.1 Monitoring project  *Define risks and risk management Monica, Charles, Doug approach *Project quality management *Status reports *Corrective actions *Lessons learned 5. Submit project draft 12/4/05 5.1 *Review, feedback and  Monica comments 6. Project Closing 12/18/05 12/18/05 6.1 Submit final project  *Formal acceptance of project Monica from stakeholders and team members * Business solution deliver to the user community, Instructor Sharon, and classmates Baseline End Date Appendix E Stakeholder Communication Analysis
  23. 23. Monica Macedon 23 6/3/2010 Stakeholders Document Name/ Document Objectives Frequency Permissio Access Accountability Delivery Format n Sponsor System (Repository) To review expectations Bi-Monthly read, PM, HRM, Improvement Database for the new system. write, BM, IT, DBA, Report Directory make QM, SA, ADV changes Sponsor Team Progress E-mail To express support and Bi-Monthly PM, HRM, Report appreciation of the BM, IT, DBA, project team’s QM, SA, ADV accomplishments. Project Project Status (Repository) To review successes, Bi-weekly read, SP, HRM, Manager Report Database constraints and write, BM, IT, DBA, Directory progresses. make QM, SA, ADV changes Project Project Charter (Repository) To review work being As needed read, SP, HRM, Manager Database performed during the write, BM, IT, DBA, Directory final project make QM, SA, ADV development. changes Project Project Schedule (Repository) To review outlined Monthly read, SP, HRM, Manager Database activities and tasks for write, BM, IT, DBA, Directory the planned project. make QM, SA, ADV changes Project System Proposal Hard copy Evaluate recommended As needed SP, HRM, Manager Report system solution and BM, IT, DBA, feasibility assessment. QM, SA, ADV Project Risk Management (Repository) To evaluate and control As needed read, SP, HRM, Manager Plan Database what might go wrong in write, BM, IT, DBA, Directory the final project before make QM, SA, ADV it becomes a threat. changes Project Change Control (Repository) To review and managed As needed read, SP, HRM, Manager Log Database appropriate changes write, BM, IT, DBA, Directory throughout the final make QM, SA, ADV project. changes Project Implementation (Repository) To review and ensure As needed read, SP, HRM, Manager Plan Database that the installed system write, BM, IT, DBA, Directory software meets user make QM, SA, ADV requirements and changes expectation. Project Conversion Plan (Repository) To review the strategy As needed read, SP, HRM, Manager Database and smooth transition write, BM, IT, DBA, Directory of converting from the make QM, SA, ADV old system to the new changes system. Project Team Meeting E-mail To provide the Bi-weekly SP, HRM, Manager opportunity to develop BM, IT, DBA, ideas and collaborate on QM, SA, ADV the final project. HR Manager Staff Acquisition (Repository) View the needs of each As needed SP, PM, BM, Plan Database team members’ tasks IT, DBA, QM, Directory and work hours. SA, ADV HR Manager Team Development (Repository) To review team As needed read, SP, PM, BM,
  24. 24. Monica Macedon 24 6/3/2010 Plan Database members’ productivity write, IT, DBA, QM, Directory and create an make SA, ADV environment for growth changes and prosperity. Business Communication Email Provide appropriate and Weekly read, SP, PM, Manager Plan consistent levels of write, HRM, IT, information to all make DBA, QM, SA, ADV stakeholders changes IT Design Statement (Repository) Serves as a blueprint As needed read, SP, PM, Database for the detailed design write, HRM, CFO, Directory system. make DBA, QM, SA, ADV changes IT Process/Logical (Repository) To review system As needed read, SP, PM, Models Database models and business write, HRM, CFO, Directory processing make DBA, QM, SA, ADV requirements. changes Database Database prototype (Repository) To review design As needed read, SP, PM, Administrator Database specifications and write, HRM, CFO, Directory requirements. make IT, QM, SA, ADV changes Database Application (Repository) To review internal and As needed read, SP, PM, Administrator Architecture Database external design of each write, HRM, CFO, Directory system components. make DBA, QM, SA, ADV changes Quality Quality Plan ISO Manual To evaluate and Periodically read, SP, PM, Manager monitor the deliverables write, HRM, CFO, and overall project make IT, DBA, SA, ADV performance. changes Quality Audit Test Plan (Repository) To certify that the Periodically read, SP, PM, Manager Database system is free of errors write, HRM, CFO, Directory and is ready to be make IT, DBA, SA, ADV placed into operation. changes Systems Requirements (Repository) To review specified As needed read, SP, PM, Analyst Statement Database system requirements. write, HRM, CFO, Directory make IT, DBA, QM, ADV changes Systems Use Cases (Repository) To review system As needed read, SP, PM, Analyst Database functions and graphical write, HRM, CFO, Directory requirements of the make IT, DBA, QM, ADV business. changes Quality Test Plan (Repository) To review appropriate Periodically Read, SP, PM, Manager Database system testing and write, HRM, CFO, Directory verify all requirements make IT, DBA, QM, SA changes Advisor Training Plan Manual To provide group As needed SP, PM, training and properly HRM, CFO, guide 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
  25. 25. Monica Macedon 25 6/3/2010 Project Name: Project Management HRMS project Team Member Name: Monica Macedon, Date: November 1, 2005 Work 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 Cost estimating, Measure, monitor, Management cost budgeting and control overall cost performance. Documentation of any constraints. Quality Control Quality Quality assurance, Determine Management Plan Quality checklists correctness of Quality Metrics deliverables. Recommended corrective actions. Documentation of lesson learned. Risk Monitoring Project Risk Risk Identification Documentation and Control Management Qualitative Risk reviews. List of Analysis identified risks and Risk response root causes. Update planning risk register. Schedule Control Project Time Schedule Identifying and Management development. documenting logical Activity definition relationships among and activity schedule activities. sequencing. Periodic Progress reporting. Table 1. Control Change Plan Appendix G HMRS Cost Estimates
  26. 26. Monica Macedon 26 6/3/2010 HRMS Project Estimated Cost for a Proposed System Solution and supporting details Estimated Costs for Proposed Systems Solution DEVELOPMENT COSTS: Personnel: (418 hours/ea 1 Project Manager $65.00/hr) $ 27,170.00 (198 hours/ea 1 Sponsor $50.00/hr) $ 9,900.00 (110 hours/ea 1 Quality Manager $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 (252 hours/ea 1 IT Tech $40.00/hr) $ 10,080.00 (322 hours/ea 1 Systems Analyst $50.00/hr) $ 16,100.00 (218 hours/ea 1 DB Administrator $40.00/hr) $ 8,720.00 (156 hours/ea 1 Payroll Advisor $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: (125 hours/ea 2 Programmer/Analyst $35.00/hr) $ 8,750.00 1 Database administrator (30 hours/ea $20.00/hr) $ 600.00 Total $ 9,350.00
  27. 27. Monica Macedon 27 6/3/2010 Expenses: Program/System Maintenance 1 Fee $ 995.00 Maintenance Agreement for 1 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 Risk Identification Severity Probability Mitigation Strategies
  28. 28. Monica Macedon 28 6/3/2010 Area/Category Project Initiation Schedule Commitment - need High Medium Produce a more detailed plan to to identify adequate resources identify stakeholders at the start to allocate to the scheduled and establish the procedures that tasks at the scheduled time. will be used by the project stakeholders. Project Planning Business Strategic Objectives – High Medium Conduct an analysis study and Scope cannot start project planning develop a plan to address risk to until a business plan is develop. stakeholders and the project team. Project Cost Budge and Costs – cost overrun High Low Monitor project approved Management of project funding likely to expenditures and report status of occur. budget on a monthly basis. Actual or potential problems need to be communicated to Executive Steering Committee for immediate resolution. Project Risk Project Management Ability High Medium Adequate risk assessment practice. Management and Expertise – cannot Develop a procedure document on implement risk plan without Risk Identification, Qualitative appropriate management and Risk Analysis, Risk Response technical risk assessment. Planning, and Security Planning. Project Scope Change Organizational High Medium Establish a preliminary or baseline Management Structure and Focus – scope during the initial project misalignment of work, policies, plan. Educate stakeholders about and procedures will affect the effects of changes. Adopt a formal business strategy and goal. change management plan. Develop a contingency plan. Project Quality Product Performance High Medium Develop explicit rules that must Management Requirements – failure or non- address the business requirements. conformance is likely to result Prioritize requirements in design problems/functions. Cost Estimation Economic Conditions – Moderate Low Develop an economic analysis and new software technology. forecasting plan. Process Management Development Process/Tools – High Low Integrate agile methodologies and poor quality software will tools that will support in-house exceed schedule and budget. software solution. Project Management Technical Approach – High Low Follow a system philosophy to functionality of the system understand how the final project must be optimized to fit the relates to the business. business Continuously reevaluate feasibility and risks through out the final project. Project Stakeholders Needs – High Medium Create a communication plan Communication misinformation, stress tension, Establish a community portal Management and lack of accountability can (Intranet) to open lines of create low performance level communication. Interpersonal, and time wasted. effective communication, and listening skills. Table 2. Risk Management Plan Matrix Appendix I Business Requirement Use Case {Employee Self Services System}
  29. 29. Monica Macedon 29 6/3/2010 Author (s): Monica Macedon_ Date: October 28, 2004 Version:1.0__________ USE CASE NAME: Select Benefits USE CASE TYPE USE CASE ID: BEP BUC00-1.0 Business Requirements:  PRIORITY: High SOURCE: Requirement – BPE-R1.00 PRIMARY Employee BUSINESS ACTOR: OTHER • Human Resources PARTICIPATING • Payroll Department ACTORS: • Insurance Carriers OTHER • Business/Financial Management – Interested in enrollment activity in INTERESTED order to manage the company’s financial resources. STAKEHOLDERS: • 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 Response OF EVENTS: Step 1: The employee Step 2: The system responds by validating all provides his or her network required information that has been provided credentials (username and by the user against the employee record in password). 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 Alt-Step 2: If an employee does not enroll within the allotted time, the default COURSES: 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,
  30. 30. Monica Macedon 30 6/3/2010 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 • Web-based interface to be provided for Eastern Carolina Vocational CONTRAINTS AND Center’s users, and web screen to be provided for employees. SPECIFICATIONS 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 TYPE USE CASE ID: BPE BUC00 -1.0 Systems Analysis:  PRIORITY: High SOURCE: Requirement – BPE-R1.00 PRIMARY BUSINESS Human Resources ACTOR: OTHER • Employees PARTICIPATING • Payroll Department ACTORS: • Insurance Carriers OTHER INTERESTED • Business/Financial Management – Interested in enrollment activity in order to STAKEHOLDERS: 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.
  31. 31. Monica Macedon 31 6/3/2010 TYPICAL COURSE Actor Action System Response OF EVENTS: Step 1: HR associate extracts Step 2: The system responds by returning employee demographic data from the electronic data into HRIS. the Benefits Enrollment database. Step 3: The HR associate imports Step 3: The system displays the employee’s the data into a spreadsheet benefits and costs summary. report. Step 4: The HR associate views Step 5: The system retrieves and process the benefits package. If no the data, then uploads the information into changes are made, the associate the Payroll database. approves and saves the data. 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 • Provide the logic, calculations and data to define a business’ benefits CONTRAINTS AND offerings in order to verify eligibility and premiums. SPECIFICATIONS • 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
  32. 32. Monica Macedon 32 6/3/2010 Figure 3. Benefits Use Case Diagram Appendix J Activity Diagram
  33. 33. Monica Macedon 33 6/3/2010 Figure 4. Activity Diagram Appendix K Organizational Structure Web Site
  34. 34. Monica Macedon 34 6/3/2010 Eastern Carolina Vocational Center, Inc. Secure Access Gate Keeper Successful Invalid Login Area 1 Login Login Company ECVC Information Homepage Support Thank You Desk Form Confirmation Information Center Sign Out Personal Data Update Management Personal Data Management Form Enrollment Update Enrollment Process Process Form Enrollment Menu Medical/Dental/ Vision Plan Open Life/Health/Accidental Enrollment Death Plan Long Term Disability Plan Terms Of Use Short Term Disability Plan Privacy Statement Figure 5. Information Architecture Appendix L Network Architecture
  35. 35. Monica Macedon 35 Web Browser 6/3/2010 Web Server Internet Explorer and Netscape HTML/JAVA Web scripts HTML: Page Content executed here and Enrollment XML: Data Content Client PC Authentication Employee Protected Login Area Web Pages User Communication Web Server Employee Data Exchange ECVC Data Exchange Simple Mail Carrier Data Exchange Transfer Protocol (SMTP) Mail Files File Transfer Read requested Protocol (FTP) Benefits Selection Utility enables file and eligibility transfer to and from the server ESS Database stored here Benefits Benefits Information Information and and Automatically Service Requests Service Response Upload Files Enroll Access Application logic executed here Application Server Updated Retrieve Benefits Information Request Benefits Windows/Access Request to create, read, update, or delete 2000 Import Files records SQL/Server executed here Database Figure 6. Network Computing System: Intranet/Internet Linking an internal database to the Web.
  36. 36. Monica Macedon 36 6/3/2010 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.
  37. 37. Monica Macedon 37 6/3/2010 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.
  38. 38. Monica Macedon 38 6/3/2010 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 Responsibilities Test 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 testing Test Web interfaces, input/output control modules Test Designer - Crystal Evaluates effectiveness of test efforts Project Manager - Monica Tester - John Documents test results and problems Data Logger - Tina Observes and logs data metrics Test System Administrator - Charles Set-up and maintain software environment Test Moderator- Monica Performs usability/accessibility test Database Administrator - Ellen Ensure test data (database) are managed and maintained Security Testing - Monica Test logon security and apply security roles QA Management - Doug Quality assurance testing validating individual components of software Technical/Security Setup - Charles Provides technical support for testing tools Acceptance 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:
  39. 39. Monica Macedon 39 6/3/2010  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.
  40. 40. Monica Macedon 40 6/3/2010 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 properly All 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.
  41. 41. Monica Macedon 41 6/3/2010 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 MX Web Design HTML Validator Completion Criteria: Each Web page has been validated for HTML conformance. Table 5. Web Page Testing
  42. 42. Monica Macedon 42 6/3/2010 4.1 Security and Access Control Testing This 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 only those functions or data for which their user type is provided permissions. System-level Security: Verify that only those users with access to 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 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
  43. 43. Monica Macedon 43 6/3/2010 User Testing Preparation Worksheet User Testing Project __HRMS Project_____________________________________________ Scheduled Dates and Times _____________________________________________________ Location: On-site testing Testers _____________________________________________________________________ Observers ___________________________________________________________________ Required demographic _________________________________________________________ Number of test users 4__________________________________________________________ Computer configuration(s): Hardware ___________________________________________________________________ OS and version ______________________________________________________________ Browser and version __________________________________________________________ Other software ______________________________________________________________ Other equipment: Stopwatch Task list To 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 Task Starting State Successful Completion Criteria Benchmark Script Task 2 Description Task Starting State Successful Completion Criteria Benchmark Script Task 3 Description Task Starting State Successful Completion Criteria Benchmark Script
  44. 44. Monica Macedon 44 6/3/2010 Usability/Accessibility Evaluation Form Tester’s User’s name_________________________ name__________________________ Task tested_____________________ 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
  45. 45. Monica Macedon 45 6/3/2010 Web Usability and Accessibility Guide 1. Technical Features: Description Compliance Yes No Partial 1.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 page 1.4 Appropriate use of KEYWORDS and DESCRIPTION meta tags 1.5 Compatibility with current Netscape and Microsoft IE browsers Results st 1.6 Site Speed (seconds) 1 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 Partial 2.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 person 2.4 Human Resource contact information available from home page 2.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;