05 - Application Profiler Flashcards

1
Q

Describe the Application Profile

A
  • Tool for describing the scope of an application.
  • Can be used to describe an application at the Program Level for budgetary planning or at a Project Level.
  • Program Level AP has bigger Scope where as Project is a sliver of a Program)
  • Program Level AP is very rarely if ever accelerated
  • The Plus/Minus factor associated with the effort estimates should be larger for a Program given the level details known
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Where can the Application Profiler be run from?

A
  • PRPC Designer Studio
  • PRPC Business Architect Studio
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

When does Direct Capture of Objectives Begin?

A

With creation of the Application Profile via the Application Profiler

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Who determines the profile options for the Application Profile (Framework? Implementation?)

A

The Lead Business Architetc or Lead System Architect

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is a Framework?

A

An application that provides generic functionality to be accessed from other applications, i.e. Personal Lines Insurance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is an Implementation?

A

An application that provides specific functionality usually for just one purpose, i.e Auto Insurance

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What profile options exist when creating the Application Profile?

A
  • New Framework & Implementation
  • New Framework (only)
  • New Implementation (only)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What happens when you UPDATE an Existing Application for the Application Profile?

A
  • A new Application Profile is created for the existing PRPC Application Rule
  • Does not modify the existing Appliation Profile
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What happens when you MODIFY an existing Application Profile

A
  • Updates are made to the exsting AP
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What happens if you switch from NEW to UPDATE Application?

A

You will lose all work. Consults with the LBA/LSA before doing this.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What does “Built on Framework” do?

A

Allows you to select an existing (framework) application to serve as a starting point

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What High Level information is captured on the Application Profile?

A
  • Business Objectives - A measurable Business reasoning for doing the project that brings significant value (business or technical)
  • Project Description
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What does the Actions menu provide in the AP?

A

Access to other actions such as:

  • Adding Actors
  • Saving the AP
  • Sizing the AP
  • Documenting the AP
  • etc.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are Actors and how is this information used?

A
  • Actors are entities which take action on a work type at a specific business process point
  • Information will be accessed when creating specifications in discovery maps
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is a Work Type?

A

A case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Describe the Discovery Map

A
  • Facilitates capturing manual and/or automated steps in a process
  • Business participates significantly in drafting out the Discovery Map processes
  • Provides an at-a-glance view of all specifications in a process
  • Uses color coded shapes to distinguish automated, manual, or system steps
  • Sub process shapes used to handle complexity
  • Not meant to replace flow modeling which encompasses decisions, looping, routing or other details that come out of subsequent process refinement sessions
  • By capturing the main steps in a process, teams can get to a sufficient level of detail necessary for project sizing without overanalyzing the entire solution
  • Should be high level depiction of the flows, don’t go too far. Organize & Design for reuse
17
Q

What types of Paths are defined in the Discovery Map?

A

Primary and Alternate Paths

18
Q

How is complexity handled in the Discovery Map?

A

Through the use of Sub-Processes

19
Q

What is the color legend for objects on the Discovery Map?

A
  • Blue: Sub-Processes
  • Green: Human based step
  • Yellow: Automated Step
  • Red: Integration Step
20
Q

What may each shape in the Discovery Map represent?

A

A specification

21
Q

Describe a Specification

A

A specification is defined as a “Set of steps that describe exactly “How” the requirements will be met by the application”.

22
Q

Describe the Levels in Specifications

A
  • Level-1 is captured during the Inception phase of a project using Pega BPM and is a high level description of the process. It does not have all the details spelled out.
  • Level-2 is captured during the DCO Elaboration Session process and is full detail of the specification
23
Q

Do all steps shapes need to be referenced in a specification?

A

No, however they should be accounted for in a specificaiton.

24
Q

How should attachments in specifiations be used

A

To capture artifacts that are requlated to the Requirements and Specifications

Helps with reuse avoid creating new artifacts

25
Q

What information is typically captured in the Specification with the Discovery map?

A
  • Name
  • Shape Type (sub-process, human based, etc.)
  • Status
  • Actors
  • Trigger - access method used when an actor encounters this specification
  • Complexity - used in project sizing estimates
  • Related Business Objectives
  • Subject Matter Experts
  • Pre & Post Conditions
  • Description
26
Q

What is a Best Practice Related to creating Requirements?

A

Create them in advance as they may then be selected from a drop-down during creation of the Discovery Map

27
Q

Describe Specifications versus Requirements

A

Requirements:

  • Describe “What” the business need is
  • Always have clear descriptions
  • Have a strong naming convention
  • Be linked to Specifications

Specifications:

  • Describe “How” the requirements will be met
  • Always have clear descriptions
  • Have strong naming convention
  • Be linked to Discovery Map Shapes
  • Should utilize a standard template to ensure consistency
28
Q

What information is gathered when defining Integrations in the Discovery Map?

A
  • Name
  • Does the source currently exist
  • Protocol to be used to connect
  • Number of distinct calls made
  • Complexity used to drive estimates
29
Q

How is the “Level of Detail” used when defining reports and correspondance?

A
  • Low Level of Detail - enter summary information about the objects and an estimated count
  • High Level of Detail - enter detailed (line item) information about each object
30
Q

How are assumptions used?

A

Provide a mechanism to capture project related information that pertains to many different areas (added to AP document only)

31
Q

How are Project Participants used in the AP?

A

Allow for resource planning (added to AP document only)

32
Q

Describe (High-Level) the process for Delegating work in the Application Profile

A
  • Work can be divided and assigned to indviduals
  • Appears in their worklist
  • When delegated tasks are completed must be merged back with the primary profile
  • Operators responsible for merge must be in the Access List for the AP
  • Operator assigned clicks on MERGE
33
Q

Describe some Application Profile Best Practices

A
  • Use the Save action (click Actions > Save) to save work on individual steps of the AP.
  • If multiple resources will be collaborating on one Application Profile (AP), solidify your delegation strategy before starting to capture objectives
  • As you accomplish your operational walkthrough, model your AP processes
  • Create as many iterations of the AP as required before submitting it for approval
  • Document your AP and have it approved by the business
  • Consider the final AP as “locked” once the Application Accelerator has been run
  • If you no longer need a profile and want to remove it, use the Withdraw action (Actions > Withdraw) to resolve and withdraw the profile. A withdrawn profile cannot be used to populate data in the Application Accelerator.
  • If updating an existing application that did not use DCO, you can use the “Discover Work Types” button on the application rule to enable DCO features
34
Q

What aspects of the Application Profile can be imported from Excel and what are the advantages?

A

Requirements and specifications may be imported from Excel.

Allows you to enter them all at once.

35
Q

Can the Applicatio Profile be moved to another system?

A

Yes, it can be packaged into a Zip file from the Actions menu and then imported into the other system via PRPCs Import Wizard