PQS 2.0

Project Offshore - Centre Management Workstream

Mid Year Catch Up

Michael Vlcek

PQS 2.0 04/06/20133

PQS 2.0 – Infrastructure & Environments

• Liaise with Dan and the London infrastructure team to develop/use/implement theright approach for the common functionalities, such as notifications, searches, nonSQL queries and workflows;

• We need to deploy to the UAT environment on a regular basis – after the end of eachSprint, and this will include real live data migration from the source systems;

• We also need a CI available environment, so that the London teams can see/use theDEV version of a current Sprint;

PQS 2.0 04/06/20134

PQS 2.0 – Workflow - BLL

PQS 2.0 04/06/20135

PQS 2.0 – Documentation

“To document or not to document, that is the question!”

• User Stories well documented (Utopia?);

• We need something, that makes it comprehensive to anybody understand what the system does…

• Just Enough – The bear minimum which is needed to explain what the system does and how it works;

• Screen shots with brief description;

• Flow diagrams showing processes and logic flow;

• Domain Models to pinpoint the entities and relationships;

PQS 2.0 04/06/20136

PQS 2.0 – User Stories well documented - Utopia?

PQS 2.0 04/06/20137

PQS 2.0 – Just Enough, but comprehensive

Allocated Traditional Marking – display the list of Traditional Marking orders alreadyallocated. This screen gives the possibility to Reallocate AA and Send notifications. Hovering anitem in the grid will show a tool-tip.

PQS 2.0 04/06/20138

PQS 2.0 – Just Enough, but comprehensive, cont.

PQS 2.0 04/06/20139

PQS 2.0 – Documentation! Why do we need it?

• Share knowledge – “the system functionality shouldn’t be in one person’s

head”;

• Explain to the business what the systems does, and how it works;

• Extremely helpful to manage the scope and the development

process;

• Helps the developer to ask questions, allowing to spot and

anticipate issues;

• Documentation should be created during the whole process, since

the very beginning of the story discussion, till the end of the

testing, and mainly by the developer himself;

PQS 2.0 04/06/201310

PQS 2.0 – Migration Strategy for BTEC/NG (1.5) • Database renaming – ODS schemas for Centre Management

Persons - common

• Addresses - Common

• TelephoneNumbers - Common

• EmailAddresses – Common

Organisations - customer

• OrganisationGroups - customer

• OrganisationGroupMembers - customer

• OrganisationIdentities - customer

• OrganisationContacts - customer

• OrganisationAddresses - customer

• OrganisationAddressTelephoneNumbers - customer

• OrganisationEmailAddresses - customer

• OrganisationAchievables - customer

• LookupOrganisationAchievableStatuses - customer

• LookupOrganisationAccessLevels - customer

• LookupOrganisationFundings - customer

• LookupAddressTypes - customer

• LookupCentreTypes - customer

• OrganisationChangeRequests - customer

• OrganisationPropertyChanges - customer

• Documentation: https://docs.google.com/a/pearson.com/viewer?a=v&pid=gmail&attid=0.1&thid=13f134b181bf91f7&mt=application/vnd.openxmlformats-

officedocument.wordprocessingml.document&url=https://mail.google.com/mail/u/0/?ui%3D2%26ik%3Dc9be56b728%26view%3Datt%26th%3D13f134b181bf91f7%26a

ttid%3D0.1%26disp%3Dsafe%26realattid%3Df_hhk7cfox0%26zw&sig=AHIEtbRkZ_4UFWCNJ_B8tTneL3V49VdFUg

• BTEC/NG and FS/ICT integration into one system

• Estimate refactoring of all 1.5 apps into PQS 2.0;

• Brainstorming session to identify the challenges and work needed;

• Refactor AR3 Venue Centre Addresses

PQS 2.0 04/06/201311

PQS 2.0 – QA & Testing Strategy

Ian Betts – QA Manager

• Testers will report to him

• Code Reviews Policy

• Acceptance Criteria Format

• DoD for MRF’s and Stories

• Can we add for UAT applications, a drop-down list with all different users in the context, so that

the UAT user don’t have to login and out with different users to test the application?

PQS 2.0

Thank you!

Questions & Answers