05 - Application Profiler Flashcards
Describe the Application Profile
- 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
Where can the Application Profiler be run from?
- PRPC Designer Studio
- PRPC Business Architect Studio
When does Direct Capture of Objectives Begin?
With creation of the Application Profile via the Application Profiler
Who determines the profile options for the Application Profile (Framework? Implementation?)
The Lead Business Architetc or Lead System Architect
What is a Framework?
An application that provides generic functionality to be accessed from other applications, i.e. Personal Lines Insurance
What is an Implementation?
An application that provides specific functionality usually for just one purpose, i.e Auto Insurance
What profile options exist when creating the Application Profile?
- New Framework & Implementation
- New Framework (only)
- New Implementation (only)
What happens when you UPDATE an Existing Application for the Application Profile?
- A new Application Profile is created for the existing PRPC Application Rule
- Does not modify the existing Appliation Profile
What happens when you MODIFY an existing Application Profile
- Updates are made to the exsting AP
What happens if you switch from NEW to UPDATE Application?
You will lose all work. Consults with the LBA/LSA before doing this.
What does “Built on Framework” do?
Allows you to select an existing (framework) application to serve as a starting point
What High Level information is captured on the Application Profile?
- Business Objectives - A measurable Business reasoning for doing the project that brings significant value (business or technical)
- Project Description
What does the Actions menu provide in the AP?
Access to other actions such as:
- Adding Actors
- Saving the AP
- Sizing the AP
- Documenting the AP
- etc.
What are Actors and how is this information used?
- 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
What is a Work Type?
A case
Describe the Discovery Map
- 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
What types of Paths are defined in the Discovery Map?
Primary and Alternate Paths
How is complexity handled in the Discovery Map?
Through the use of Sub-Processes
What is the color legend for objects on the Discovery Map?
- Blue: Sub-Processes
- Green: Human based step
- Yellow: Automated Step
- Red: Integration Step
What may each shape in the Discovery Map represent?
A specification
Describe a Specification
A specification is defined as a “Set of steps that describe exactly “How” the requirements will be met by the application”.
Describe the Levels in Specifications
- 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
Do all steps shapes need to be referenced in a specification?
No, however they should be accounted for in a specificaiton.
How should attachments in specifiations be used
To capture artifacts that are requlated to the Requirements and Specifications
Helps with reuse avoid creating new artifacts