PR Word Edit 3386

7/29/2019 PR Word Edit 3386

http://slidepdf.com/reader/full/pr-word-edit-3386 1/12

APPLICATION PROFILE

RcrtmntSystem

Recruitment System for TSS division in ABCD

Definition for ABCD

Presented onTuesday, February 19, 2013

Created using: pxAP-10-LVNTW031W282BS

The contents of this proposal are Proprietary and Confidential. We retain the right to change any aspect of this proposal without prior notice.

7/29/2019 PR Word Edit 3386


© Copyright 2013Pegasystems Inc., Cambridge, MA

All rights reserved.

This document may contain trade secrets and proprietary information. The document and product

are protected by copyright and distributed under licenses restricting their use, copying

distribution, or transmittal in any form without prior written authorization of Pegasystems Inc.

This document is current as of the date of publication only. Changes in the document may be

made from time to time at the discretion of Pegasystems. This document remains the property of

Pegasystems and must be returned to it upon request. This document does not imply any

commitment to offer or deliver the products or services described.

This document may include references to Pegasystems product features that have not been

licensed by your company. If you have questions about whether a particular capability is included

in your installation, please consult your Pegasystems service consultant.

For Pegasystems trademarks and registered trademarks, all rights reserved. Other brand or

product names are trademarks of their respective holders.

Although Pegasystems Inc. strives for accuracy in its publications, any publication may contain

inaccuracies or typographical errors. This document or Help System could contain technical

inaccuracies or typographical errors. Changes are periodically added to the information herein.

Pegasystems Inc. may make improvements and/or changes in the information described herein

at any time.

This document is the property of:Pegasystems Inc.101 Main StreetCambridge, MA 02142-1590

Phone: (617) 374-9600Fax: (617) 374-9620www.pega.com

Document Name: Application Profile

Template: SelfLedAP 06-01-20, saved on 09/15/2010

Updated: December 30, 2011


7/29/2019 PR Word Edit 3386


Contents

Executive Summary................................................................1Actors....................................................................................2Work Types, Processes, and Use Cases....................................3

Interfaces...............................................................................4Reports and Correspondence...................................................4Timeline.................................................................................5Prerequisites..........................................................................5Project Participants and Roles.................................................5Functional and Performance Testing........................................6Enablement/Training...............................................................7Governance and Communications............................................7Assumptions...........................................................................7Appendix A – Unassociated Requirements................................9


7/29/2019 PR Word Edit 3386


Executive Summary

ABCD enabled resources will build a dynamic solution and build success in BPM implementations.

The team understands the business and technology and can provide the greatest value at the lowestrisk to this implementation.

1.1 Business Context

ABCD is a financial company,with world wide presence they are loking for fresh poeople to join their technology team across Treasury services team in India.This will for the new Pega competency set-upin india so that they can have some savings in terms of the extra cost involved in getting theapplications developed by people from vendors.

1.2 Initial Solution TargetThe proposed system will target the following business objectives. These objectives will be used as ameasure of success:

(No business objectives were selected.)

1.3 Implementation ApproachThis project initiative will be lead by ABCD’s Project Management team. Pegasystems’ Project

Management team will be supporting the client team throughout the entire project implementationlifecycle.

Based upon our experience with hundreds of successful PegaRULES Process Commander Implementation it has been a best practice to look at the current client implementation methodologyand integrate into to it many of Pegasystems industry leading best practices including but not limited toour Direct Capture capabilities.

While most organizations have been trained to create voluminous requirements documents in order tobuild software applications, Pegasystems Direct Capture of Objectives (DCO) product suite isintegrated into the system to facilitate build for change development regardless of IT or businessorientation.


P a g e | 1

7/29/2019 PR Word Edit 3386


Pegasystems approach is to directly capture executable requirements within the system and its Buildfor Change™ directive addresses the problems with the traditional SDLC approach. Pega’s DCOCapabilities work with all Implementation Methodologies and greatly increase their efficiencies byautomating many different work products.

Pegasystems also has an iterative, agile and adaptable methodology that is supported by its awardwinning SmartBPM platform which can be deployed as ABCD methodology of choice for this initiative.

SmartBPM provides wizards, constructs, and easy to use forms to directly capture and executerequirements. Each phase of the methodology depends upon the SmartBPM platform, and therequirements are automatically documented – always matching your requirements to developmentefforts.

Using Pegasystems SmartBPM™ Implementation methodology and/or DCO Capabilities will help ABCD achieve their objectives in a much timelier manner with a higher degree of quality. It will alsoassist ABCD in realizing their return on investment (ROI) much earlier than other waterfall or big-bangapproaches to development and delivery.

1.4 Stepping to the FutureThe Pegasystems approach begins with a defined implementation that rapidly achieves businessvalue – allowing you to expand that value through additional projects.

The Build For Change™ philosophy embraced by ABCD in this project is based on a commitment tocontinuous improvement and self-sufficiency. This project represents an initial step towards anevolution of ongoing efficiency and service gains. Business benefits beyond this project will bedesigned and achieved through follow-on implementations.

Actors

Actors are the individuals or systems that will interact with the RcrtmntSystem System. Their names,type, access method and volumes are listed in the following table:

Actor Type Count Access Method

Technical Lead Operator Browser

The Standard user portals will be used for the above with the following modifications:


P a g e | 2

7/29/2019 PR Word Edit 3386


• Add ABCD Custom Logo

• Removal of unnecessary PRPC Gadgets

Work Types, Processes, and Use Cases

Work Types describe the high level business functions that will make up this application. Each WorkType lists the specific Use Cases (scenarios) and the specific Interfaces that are invoked. Anyfunctionality not specified below may be addressed in follow-on projects. The names of the WorkTypes, Use Cases, and Interfaces should be chosen with care, as they will be used extensively insubsequent documentation and governance functions.

1.5 RcrtmntSystemEdit the Description for this work type here

1.5.1 StartRcrtmntSystem

1.5.1.1 Primary Path for StartRcrtmntSystem (Page 3)

1.5.1.1.1 Step NameNo details specified

1.5.2 Work Type RcrtmntSystem includes the followingunreferenced Use Cases:

1.5.2.1 Resource requirement requestResource requirement request

Shape: N/A Triggers:

Status: New Complexity: Low

Actors:Technical Lead

Description

Technical lead raises request for resource specific to a technology to his HR team member

1.6 CommonUse cases shared by multiple work types

1.7 SecurityUse cases dealing with authentication, authorization

1.8 NavigationUse cases specific to getting between work types and general application processing


P a g e | 3

7/29/2019 PR Word Edit 3386


1.9 DataManagementUse cases specific to managing lists of products, reference data tables, broadcast messages

1.10 SysAdmin

Use cases specific to managing operator profiles, calendars, skills, rule migration/promotion

Interfaces

The Pegasystems solution will interchange with the systems described in this section using theprotocol specified.Overview: Once candidate is selected,Onboarding team will send mail to candidate confirming his/her

joining details.For this,integration with Mail server is required

Name Protocol Data Source

Exists

# of

Interchanges

Description

E-Mailintegration

Service-Email

Yes Send e-mail to candidate if he isselected

Reports and Correspondence

Decisions about reporting are typically best made after some experience with the system.Therefore, reporting activity typically occurs as a separate initiative and may require that ABCD

export data from the system to a data warehouse. These data warehouse initiatives cantypically overlap with user acceptance testing.

Reports - We expect that the standard reports will be supplemented by 2 custom reports.Show cicular chart for no of positions open against each technology

Name Category Complexity Description

Technology WiseOpenPositions

WorkMonitoring Low Show details about Open positions againsteach Technology

Candidates applied for eachopen positions

WorkMonitoring Medium Create a Bar-Graph showing no of candidates applied for each position

Correspondence - The Pegasystems solution is expected to generate approximately 1 pieces of

Correspondence (email, letter, PDF).

Name Complexity Description

Send Joining Mail to candidate Low Send mail to candidate confirming his/her joining details


P a g e | 4

7/29/2019 PR Word Edit 3386


Timeline

The timeframes presented below represents an estimate based upon the information know at thistime. It is further based upon an allocation of resources and assumptions about the skill levels of

these resources from ABCD. As more information becomes available and upon further due diligenceregarding this project, these estimates and staffing assumptions may need to be adjusted.

Estimated Timeline

0 2 4 6 8 10 12

Weeks

Inception Elaboration Construction Transition

The phases of the project are estimated to take:

Inception 2 weeks

Elaboration 3 weeks

Construction 5 weeks

Transition 2 weeks

Prerequisites

Prior to project start, the following prerequisites must be met:

• Customer to name team members by role

• Customer to send each team member to appropriate role based training

• Joint agreement on an iterative implementation methodology, Pegasystems recommendsconducting a Method Adoption Workshop

• Joint agreement on a formal governance structure and process

Project Participants and Roles

ABCDRole Alloc. Responsibility /

WorkEnablement

Plan

ProjectManager

1.0FTE

Project Plan, Overall Project Success Business ArchitectEssentials

Business 1.0 Create/Validate Use Cases, Create Customized Reports Business Architect


P a g e | 5

7/29/2019 PR Word Edit 3386


7/29/2019 PR Word Edit 3386


Enablement/Training

Training is a key success factor in helping to ensure a successful PRPC Go-Live. Customers who traintheir project team members realize significant business benefits through increased self-sufficiency and

productivity. The benefits include:• Realization of the “Build for Change” value proposition, as PRPC-trained business analysts

respond directly to expected changes and evolving project requirements

• Faster response to new business demand due to lower reliance on external resources

• Trained delivery project team members design and build solutions faster and project risks areminimized

• Career development opportunities for business and IT staff as they acquire new businessprocess management skills

• Lower total cost of ownership by utilizing in-house skilled resources

At a minimum Pegasystems does require a single resource be trained as a Pegasystems ProcessCommander administrator by taking the “PegaRULES System Administration” course. This role iscritical for all projects during both implementation and post production support. Client resources that

will be performing the project roles defined in section 6.4 are also required to take Fast Track to PRPCand PRPC Bootcamp training to help facilitate project implementation.

The timing of training is critical; we recommend 2- 6 weeks in advance of a project start. Trainingpositively increases the effectiveness of team member’s ability to lead projects, and ultimately, thequality of the final deliverable. Individuals who take training at the right time retain the knowledgeneeded to keep projects on track and contribute productively to the project.

The above courses can be taken at a Pegasystems public training site, virtually or can be deliveredonsite to the customer. Information about additional training courses and pricing can be found on our web site at:

http://www.pega.com/Services/EducationalServices

Governance and Communications

Effective communications and active governance are two critical components of successful projectdelivery. Bi weekly stakeholder governance meetings shall be held along with weekly project statusmeetings.

Assumptions

The following assumptions are critical elements of the functional, schedule, and staff aspects of thisproposal. Should these not occur in accordance with the agreed to project schedule then projectdelays and overruns are deemed the responsibility of the customer. Many of these assumptionsembody an iterative implementation philosophy, where the initial implementation is often continuouslyimproved at a frequent pace, based on changes in actual experience.


P a g e | 7



7/29/2019 PR Word Edit 3386


• PRPC authentication will be the security mechanism

• Project Sponsor will provide external connectivity to development and test environment for thePegasystems team members on project commencement

• Project Sponsor will be responsible for procurement, installation and provisioning of allhardware and non-PRPC-related (third party) software

• Project Sponsor will provide working facilities, desktops and required software licenses for all

resources to work on this project at the requested location.• Project Sponsor has a test region with access to data that accurately represents test and

production information.

• Project Sponsor will independently build and configure interfaces for external applications aspart of the proposed work.

• Implementation of the application, including the UI, is expected to be handled through out-of-the-box (OOB) rules provided in PRPC with minimum customizations.

• Standard Harnesses based on standard UI framework and HTML rules (minor modifications toa couple of HTML properties is acceptable)

• Standard Work Items, Covers (and Folders if needed)

• Standard Routing and Assignments.

• Word correspondence based on HTML generation, with standard PDF Generation asindicated in the Use Cases.

• Standard SLA handling and Notifications.• Standard Input Validation.

• Standard Interfaces to External Systems (including error handling).

• PRPC authentication will be the security mechanism for this project unless there is an explicitalternative specified in the Interfaces.

• Production roll-out and training is out of the scope of this proposal.

• Project Sponsor will be responsible for exporting data into a customer-defined data warehouseor developing ad hoc reports from SQL Output.


P a g e | 8

7/29/2019 PR Word Edit 3386


Appendix A – Unassociated Requirements

The following is a list of the Business Requirements that must be met to ensure Business acceptance.These requirements are not referenced in any of the use cases above.

No Requirements Specified.


P | 9

PR Word Edit 3386

Documents