Assignment Task
Executive Summary
The executive summary should cover all the main points in your assignment. Note that an executive summary is not an introduction, and it is not just a summary. The executive summary is to be read on its own and should stand by itself as a succinct version of your complete assignment. A good way to think about the executive summary is that it is a cover letter or cliff notes version of your assignment – containing the main and important details of your full assignment.
The executive summary should be a maximum of one (1) page in length. Given the requirement for an executive summary to be readable by itself, I strongly advise that you use all this available length.
The executive summary is not marked separately from the remainder of the assignment and is primarily used as a marking aid so that markers know what to expect in the remainder of your assignment. The overall quality of the executive summary will be considered in the formatting and style marks
For this assignment, a good way of writing your executive summary may be to list and briefly describe how your implementation in Pega meets the criteria set out in the assignment.
Process implementation in Pega
Build a Pega implementation of your process, satisfying the following requirements:
1. Examples of appropriate requirements, specifications, and business objectives recorded and linked in Pega – note that this does not have to be exhaustive: demonstrating one appropriate example of each with appropriate links and references is sufficient for full marks for this requirement.
2. Appropriately name the case type, stages, and steps in your process’s primary or expected path.
3. Appropriate organisation of the stages and steps in your process’s primary or expected path.
4. Appropriate stage and step transitions in your process’s primary or expected path.
5. Appropriate use of alternate stages, including configuration of steps and behaviour in these alternate stages.
6. Appropriate data model, including data types.
7. Appropriate assignment to different operators to represent different responsibilities – as the existing operators will be used for assignment routing (see the instructions in the previous section), also describe what roles these existing operators will play in your process (as the names of the operators in Pega will probably not match the roles needed for your process!)
8. Appropriate SLAs for at least one assignment, including explanation and justification for why the SLA has been configured in this manner.
9. Appropriate SLAs for the entire case, including explanation and justification for why the SLA has been configured in this manner.
10. Appropriate correspondence details for at least one instance of correspondence in the case, including an explanation and justification for why the correspondence has been configured in this manner
