Implementation Methodology and Charter Overview - SIS

HRMS/SIS Project
HRMS/SIS
Page 1 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
PeopleSoft Implementation Methodology Overview
Table of Contents
Overview of the Methodology................................................................................................................................... 1
Charter Document (not Scope Doc)......................................................................................................................... 1
Project Management................................................................................................................................................ 2
Business Process Analysis...................................................................................................................................... 3
Requirements........................................................................................................................................................... 4
Design...................................................................................................................................................................... 5
Development & Unit Testing..................................................................................................................................... 6
User Acceptance Testing.......................................................................................................................................... 8
Documentation and Training.................................................................................................................................... 8
Overview of the Methodology
Charter Document (not Scope Doc)

Goal: To document and define the project's key goals, objectives, and deliverables. In addition, SIS has decided
to document key decisions or changes to decisions in the scope document. Scope document includes:
Goals and Objectives

Scope
Critical Success Factors
Key Decisions
/var/www/apps/conversion/tmp/scratch_7/273925506.doc
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 2 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
Project Management
Goal: To track the progress of the system implementation. Provide the project manager and the project team
members with an accurate and descriptive picture.
1. Project Milestones
Goal: To identify the key events and deliverables in a project lifecycle. This allows the project managers
to track the progress of the project. A milestone may also identify a point in time when executive approval
is required.
Responsibility: Project Manager
Tool: Milestone Gantt Chart
2. Deliverables and Tasks
Goal: To identify and track team tasks and deliverables required to complete the project. A task is a
specific activity that must be completed. A deliverable is a specific product or artifact (e.g., document,
data conversion) required to complete the project, and is usually subject to approval from stakeholders or
management. Leads will measure progress based on completion of tasks and deliverables.
Description: One project plan per module and service area that includes both technical and functional
tasks.
Responsibility: Functional and Technical Lead
Tool: Deliverables and Tasks (MS Excel)
3. Glossary
Goal: To help project team members and stakeholders communicate. Allows people to have a common
understanding of commonly used terms (technical or functional) to be used on the project. The terms
may be kept in any format (e.g., MS Word document, Exchange Public Folder, Access Database, or MS
Excel spreadsheet), but must be maintained in only one location.
Tool: Glossary Document
4. Issue Tracking
Goal: To help project team members, stakeholders, and managers track issues related to the system
implementation.
Responsibility: Leads Identify, describe and track issues.
Project Manager Follow up and manage issue resolution
Tool: Issue Document (MS Excel) with an Index to documents.
5. Meeting Minutes
Goal: To maintain a record of key topics, discussions, decisions, issues, and action items for meetings
held with project team members and stakeholders. Team members should identify the following
information: Date of Meeting, Topic, Attendees, Discussion Items, Decisions, Issues, and Action Items.
Project team should reference meeting minute documents (and not embed them) in approach papers,
campus community papers, or other documents.
Tool: Meeting Minutes Template
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 3 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
Business Process Analysis

Goal: To document IU Business Practices and compare to delivered functionality. This analysis will serve as the
basis for defining the fit/gap of the new system.
1. Context Diagrams
Goal: To provide a high level of overview of actors (systems, persons, and rules) that provide information
to the new system, use the new system, or depend on data from the new system. This should provide
stakeholders with an initial understanding of users, automated interfaces, and manual interfaces.
Deliverable: Context Diagrams
Responsibility: Functional
2. Scenarios
Goal: To create some key scenarios that describe how the users will interact with the new system and
how the system will behave, at a high level.
Description: The draft version should outline: What are the business processes? What are the variations
across campuses? The final version should refine above and then include: How do we accomplish the
business process using PeopleSoft?
Deliverable: Scenarios
3. Use Cases
Goal: To describe the "use of the system". Defines specific interactions between an end user and the
system. Used to communicate user/system interaction to stakeholders, end users, and project team
members.
Description: Document As-Is process flow as well as document what functionality is delivered in
PeopleSoft and define the final implementation approach.
Deliverables: Use Cases, Preliminary Specification Documents and Approach Papers.
(Use Cases may have 1 to Many approach papers that document the options for implementation.)
4. Fit/Gap Analysis
Goal: To walk-thru the vended product with a consultant looking at each Scenario and Use Case for the
purpose of discovering any missing pieces of functionality or features that dont line up with the process
flow of a use case.
Description: The findings from the fit/gap sessions are documented in the Use Case. This should include
the % of fit, list of gaps and overall recommendation for satisfying the gaps.
Deliverables: Use Cases, Approach Papers and Preliminary Specification Documents
Responsibility: Functional with some technical support for Approach Paper options
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 4 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
5. Prototype
Goals: To exercise and analyze the software to enable operations, begin a Fit/Gap Analysis, Identify
issues and establish and refine scenarios, use cases and preliminary specifications.
Deliverables: Demonstrate product functionality, Systems Inventory and preliminary control table
specifications.
6. Scenario / Use Case Review with Stakeholders
Goal: To walkthrough functionality and verify needs with end users using scenarios and use cases. Elicit
feedback from end users, identify potential changes to the potential changes to existing data entries,
identify any possible customizations, and describe possible workflow requirements.
Deliverable: Meeting with end users scheduled, held, and documented
Requirements
Goal: To develop a set of requirements for the new implementation. This set of requirements is used as the
basis for defining the scope of the system and how it is expected to behave.
1. User and Security Profile
Goal: To identify the various types of users (e.g., by role, by function, or by some other characterization)
to identify user specific needs for the application (e.g., security, navigation, functionality, access rights).
Deliverable: User and Security Profile Document
2. Systems Inventory
Goal: To provide an index of all objects by functionality and sub-functionality.
3. Table Inventory and Load Sequence
Goal: To manage the data requirements for the PeopleSoft Control and XLAT Tables.
Deliverable: Table Inventory/Load Sequence Document(Excel Spreadsheet)
4. XLAT Table Inventory
Goal:
5. Approach Papers
Goal:
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 5 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
6. Preliminary Specification
Goal:
Potential conversion areas include:
Customizations
Mappings
Field-to-field
Ddd table/file
Conversion and logic
Known technical issues/software needs
Responsibility: Technical
7. Batch/Interface Inventory
Goal: To describe the design for a newly defined interface or batch program. This should provide
enough information to describe the requirements, inputs, results, and other outputs. This should also
include enough information to provide information for run-to-run controls.
Deliverable: Batch/Interface Specification Document, Batch Job Inventory and Scheduling Information
Document
Responsibility:
Design
Goal: To develop detailed specifications and develop a training inventory.
1. Control and XLAT Table Specifications
Goal: Document table coding strategies, business processes affected by control tables, owners/experts
of control tables, and navigation instructions. Review and adjust delivered control table values, identify
IU values and load data into the PeopleSoft Control Tables.
Deliverable: Control Table Specification Document and XLAT Master List of Changes (Excel
Spreadsheet)
2. Customization and Extension Technical Specifications
Goal: Finalize specifications and describe the customizations for the implementation. Specifications can
include PeopleSoft customizations, IU extensions to PS, IU developed applications and third party
applications. (After the customization has been documented, the customization must be reviewed and
approved by the project team and the DIRT team before being implemented.)
Deliverable: Customization Specification Document, Customization Inventory and DIRT documents
3. Conversion Specification
Goal: To describe how existing IU data will be converted into the PeopleSoft application. The conversion
specification should be reviewed by the functional staff. The specification includes the following:
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 6 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
Scope of Conversion (timeframe, sources)

Assumptions made about the legacy data
Unresolved Issues
Data Mapping (Target and Source)
Legacy Data Extraction and Final Conversion Schedule
Validation and Reconciliation strategies
References to Approaches for complex conversions
Deliverable: Conversion Specification Document, Data Mapping Document

4. Batch Specification
Goal: To describe the design for a newly defined batch program. Describe the requirements, inputs,
results, PS run controls, QA controls and other outputs.
Deliverable: Batch Specification Document, Batch Job Inventory and Scheduling Information and
Dependencies Document
5. Interface Specification
Goal: To describe the design for a newly defined real time and/or batch interface program. Describe the
requirements, inputs, results, and other outputs.
Deliverable: Interface Specification Document, Batch Job or Program Inventory and Scheduling
Information and Dependencies Document.
6. Training Inventory
Goal: Outline the major functionality for end user training.
Deliverable: Course Inventory which includes preliminary topic outlines
Development & Unit Testing

Goal: To develop the software and components and data required to implement a system that meets business
requirements.
1. Source Code
Goal: To develop necessary software components to support business processes. (e.g. write programs
for PS customizations, conversions, batch processes and interfaces)
Deliverables: Programs, Job Streams, and Scripts
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 7 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
2. Transaction Data
Goal: To convert and load transaction data to SIS.
Deliverables: Populated transaction tables
Responsibility: Technical and Functional
3. Developer Unit Test
Goal: To define and execute the test cases for the initial functional test. Unit Tests are more appropriate
for newly developed software components (e.g., panels, SQRs, interface programs). These test cases
are validated by technical team leads.. The unit test plan should cover the following:
All successful execution paths

All errors generated by the application logic within the component
Verify the generated output, results, and/or reports
Deliverable: Unit Test Plans; Unit Test Plan Results

4. Functional Test
Goal: To verify control table value accuracy and the functionality of delivered PS panels. The test plan
should cover the following:
All panels in scope

All control table values, row counts
All delivered processes
Business Process Flow
Deliverable: Unit Test Plans; Unit Test Plan Results

5. User and Security Profile development
Goal: To establish end user security operator classes, roles and permissions.
Responsibility: IPS
6. Conversion Test
Goal: To define and execute the test cases for verifying the conversion results. Validate and reconcile
legacy data with converted data.
Deliverable: Conversion Test Scripts; Conversion Test Script Results, Reconciliation Procedures
7. Developer Integration Test
Goal: To define and execute the test cases for verifying the proper configuration and navigation of
software. Integration testing covers multiple software components (e.g. panels, SQRs, interface
programs).
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 8 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
8. User Acceptance Testing Preparation: To confirm that SIS functionality has been properly implemented,
the core module and service area leads must submit the following documents to the core management
team for review.
User and Security Profile
System Inventory
Master Table Inventory
Customization Inventory
Batch Job Inventory
Functional Test Plans and Results
Developer Integration Test Plans and Results
Scheduling Information Documents
User Acceptance Testing

Goal: To test the complete system
1. LIT System Testing
Goal: To define and execute the test cases for verifying the implementation of software against the
original requirements and scope document. System test focuses on executing and verifying business
processes from end to end. System test scripts are usually mapped back to requirements to ensure that
the system test scripts and cases have covered all requirements of the new system.
Deliverable: System Test Scripts; System Test Script Results
2. Performance Test
Goal: To define and execute the test cases for verifying system processing time and online response
times. The performance test focuses more on the technical configuration and implementation of the
software. The project identifies potential test scripts based on known high-volume transaction processing
or expected online load. At the completion of the performance test, the application must be tuned and
configured to meet the performance expectations originally defined in the scope document or
requirements.
Deliverable: Performance Test Scripts; Application Tuning Tasks
3. Stakeholders Acceptance Test
Goal: Conduct testing to determine the operational readiness of the system.
Deliverable: Acceptance Test Scripts; Acceptance Test Script Results
20 October, 2010
Draft
HRMS/SIS Project
HRMS/SIS
Page 9 of 9
Last Updated: 10/20/2010 07:14:00
AM
Project Management
Memo
Documentation and Training

Goal: tbd
Deliverables include:
20 October, 2010
Draft

Implementation Methodology and Charter Overview - SIS

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Implementation Methodology and Charter Overview - SIS

Hochgeladen von

Copyright:

Verfügbare Formate

HRMS/SIS Project

PeopleSoft Implementation Methodology Overview

Overview of the Methodology

Charter Document (not Scope Doc)

Goals and Objectives

PeopleSoft Implementation Methodology Overview

PeopleSoft Implementation Methodology Overview

Business Process Analysis

PeopleSoft Implementation Methodology Overview

PeopleSoft Implementation Methodology Overview

PeopleSoft Implementation Methodology Overview

Scope of Conversion (timeframe, sources)

Deliverable: Conversion Specification Document, Data Mapping Document

Development & Unit Testing

PeopleSoft Implementation Methodology Overview

All successful execution paths

Deliverable: Unit Test Plans; Unit Test Plan Results

All panels in scope

Deliverable: Unit Test Plans; Unit Test Plan Results

PeopleSoft Implementation Methodology Overview

User Acceptance Testing

PeopleSoft Implementation Methodology Overview

Documentation and Training

Das könnte Ihnen auch gefallen