Functional Specification
Account Planning & Field Contact Report
Document ID:See EDMS
Version:0.1
Effective Date:Date of last signature
PMM Template Version:4.0 [December 2012]
Group Informatics / Functional Specification /
Account Planning & Field Contact Report
APFCR-FS.doc / Effective Date: Date of last signature
Document Information
Project Name / Account Planning & Field Contact ReportDocument Name / Functional Specification
Document Owner / Tracy Wiseman
Document Location /
Associated Documents / APFCR-Charter.doc
APFCR-URS.doc
Authors
Role / Name / Dept. / Signature / DateBusiness Systems Analyst / Tracy Wiseman / Genentech IT / Electronically signed
Reviewer
Role / Name / Dept. / Signature / DateProgram Manager / Martha Johnson / Genentech IT / Electronically signed
Project Manager / Linda Luoma / Genentech IT
Tech Lead / Lukasz Hryckiewicz / ADMD
QA Lead / Shane Berreen / Genentech IT
Approver
Role / Name / Dept. / Signature / DatePortfolio Operations / Bob Wyrsch / Genentech Sales / Electronically signed
Director Sales Operations / Sean Jackson / Genentech Sales
Document History
Version / Changes / Who / Date0.1 / Initial draft / TW / 5/31/13
.
Contents
1.Introduction
1.1Dependencies/Constraints
2.User Requirements Specification Document Reference
3.Use Case Specification
3.1Use Case Actors
3.2Use Case Summary
3.3Business Rules Summary
3.4Use Case Diagrams
3.4.1Use Case Context Diagram
3.4.2Account Plan iPad Workflow
3.4.3Field Contact Report iPad Workflow
3.4.4AP/FCR SFDC Workflow
3.4.5AP/FCR Attach/Update/Delete Attached File
3.5UC01: Create Account Plan
3.5.1Use Case Details
3.5.2Path of Events
3.5.3System Enforced Business Rules
3.6UC02: View/Update Account Plan
3.6.1Use Case Details
3.6.2Path of Events
3.6.3System Enforced Business Rules
3.7UC03: Save/Version Account Plan
3.7.1Use Case Details
3.7.2Path of Events
3.7.3System Enforced Business Rules
3.8UC04: Submit Account Plan
3.8.1Use Case Model
3.8.2Use Case Details
3.8.3Path of Events
3.8.4System Enforced Business Rules
3.9UC05: Publish Account Plan
3.9.1Use Case Details
3.9.2Path of Events
3.9.3System Enforced Business Rules
3.10UC06: Create Field Contact Report
3.10.1Use Case Details
3.10.2Path of Events
3.10.3System Enforced Business Rules
3.11UC07: View/Update Field Contact Report
3.11.1Use Case Details
3.11.2Path of Events
3.11.3System Enforced Business Rules
3.12UC08: Save/Version Field Contact Report
3.12.1Use Case Details
3.12.2Path of Events
3.12.3System Enforced Business Rules
3.13UC09: Submit Field Contact Report
3.13.1Use Case Details
3.13.2Path of Events
3.13.3System Enforced Business Rules
3.14UC10: Publish Field Contact Report
3.14.1Use Case Details
3.14.2Path of Events
3.14.3System Enforced Business Rules
3.15UC11: Print / Report / Export AP/FCR
3.15.1Use Case Details
3.15.2Path of Events
3.15.3System Enforced Business Rules
3.16UC12: Attach File to AP/FCR
3.16.1Use Case Details
3.16.2Path of Events
3.16.3System Enforced Business Rules
3.17UC13: Update/Delete AP/FCR Attached File
3.17.1Use Case Details
3.17.2Path of Events
3.17.3System Enforced Business Rules
3.18UC14: View AP/FCR Status
3.18.1Use Case Details
3.18.2Path of Events
3.18.3System Enforced Business Rules
3.19UC15: Prefill / Configure AP/FCR
3.19.1Use Case Details
3.19.2Path of Events
3.19.3System Enforced Business Rules
3.Information specification
4.User Interface (UI) Specification
4.1Screen Relationship: Account Planning
4.2Screen Relationship: Field Contact Report
4.3Menu Items
4.4Screen Details
4.4.1<Parent Page/Page Name1>
4.4.2<Parent Page/Page Name2>
4.5Error Messages
4.5.1<Error Message 1>
4.6Notification Details
4.6.1<Notification 1>
4.6.2<Notification 2>
5.Report Specification
6.Data Specification
6.1System Context diagram (SCD)
6.1.1System Context Diagram
6.1.2System Interface Details
6.2Data Flow Diagram (DFD)
6.3Conceptual Data Model (CDM)
7.Data Conversion
8.ERES and Audit Trail
9.Compliance
10.Security
10.1User Setup and Profile Options
10.2User Authentication
10.3User Management
10.4Data Encryption
10.5Application Logging
10.6Input Validation
10.7Error Handling
11.Supplementary Specifications
Introduction
This document describes high-level solutions for implementing the requirements specified in the Genentech Sales Operations Account Planning & Field Contact Report URS. This functional specification extends the requirements listed in this URS to enable the Account Planning and Field Contact Report applications to be designed, developed, and validated for release and deployment.
Dependencies/Constraints
There are no additional dependencies or constraints beyond those listed in the Charter.
User Requirements Specification Document Reference
Requirements Specification document name: APFCR-URS.doc / Version: 1.0Use Case Specification
This section details the user actions, system response, and specific detailed requirements for each use case. Each use case provides one or more scenarios that convey how the system should interact with the end user or with another system, to achieve a specific business goal or task.
Use Case Actors
The following table lists the use case actors and their descriptions:
# / Actor / Actor Description1 / Clinical Specialist (CS) / GNE Sales Rep who uses the Account Planning (AP) tool to create, submit and collaborate on Account Plans, and uses the Field Contact Report (FCR) tool to create and submit Field Contact Reports.
2 / Division Manager (DM) / GNE Sales Supervisor who uses the AP tool to create, submit and collaborate on Account Plans, and uses the Field Contact Report tool to review, update, and approve Field Contact Reports.
3 / Business Admin / GNE Sales Supervisor who
Configures and prefills information in the AP/FCR apps.
Works with SFDC administration to ensure only designated GNE Sales Staff have access to AP/FCR, products, business units and franchises in SFDC.
4 / Compliance Specialist / GNE Compliance Specialist in the Healthcare Compliance Office (HCO) who tracks and audits compliance aspects of AP/FCR usage.
Use Case Summary
The following use cases are included in this document, with traceability to actor/roles and UI screen names (if any):
# / Use Case Name / Actors/Roles / UI Screen Name(s)UC01 / Create Account Plan / CS, DM / TBD
UC02 / View/Update Account Plan / CS, DM / TBD
UC03 / Save/Version Account Plan / CS, DM / TBD
UC04 / Submit Account Plan / CS, DM / TBD
UC05 / Publish Account Plan / CS, DM / TBD
UC06 / Create Field Contact Report / CS, DM / TBD
UC07 / View/Update Field Contact Report / CS, DM / TBD
UC08 / Save/Version Field Contact Report / CS, DM / TBD
UC09 / Submit Field Contact Report / CS, DM / TBD
UC10 / Publish Field Contact Report / CS, DM / TBD
UC11 / Print / Report / Export AP/FCR / CS, DM,
Compliance Specialist / TBD
UC12 / Attach File to AP/FCR / CS, DM / TBD
UC13 / Update/Delete AP/FCR Attached File / CS, DM / TBD
UC14 / View AP/FCR Status / CS, DM / TBD
UC15 / Prefill / Configure AP/FCR / Business Admin / TBD
Business Rules Summary
The following table contains a summary of system-enforced business rules, which are found throughout the use cases:
# / Business Rule / UC No#BR01 / Field Visits and associated FCRs occur four times per year per CS. / All
BR02 / Account Plans are created and published twice per year per Territory. / All
FR03 / Account Plans are saved only when the End User (CS or DM) explicitly indicates Save, Submit, Publish. / UC01, UC02, UC03, UC04, UC05, UC12, UC13, UC14
BR04 / Account Plans that are saved but not submitted are accessible only to the CS for view/update. / UC02, UC03, UC04, UC05, UC11, UC12, UC13, UC14
BR05 / Account Plans cannot be deleted. Account Plans can be versioned.
Only the current Account Plan is visible on the iPad.
Account Plan versions are only visible on the SFDC Server. / UC02, UC03, UC04, UC05, UC11, UC12, UC13, UC14
BR06 / Account Plans that are submitted from CS to DM, or from DM to CS are accessible only to the CS and DM for view/update. / UC04, UC14
BR07 / Account Plans that are created and saved, but not submitted or published are visible only to the CS, and can be found via the Archive screen. / UC01, UC02, UC03, UC14
BR08 / CSs can view a list of all Account Plans they’ve created in any state (saved, submitted, published) on their Archive screen. / UC14
BR09 / DMs can view a list of all Account Plans that have been submitted to them, or published by them, on their Archive screen. / UC14
BR10 / When Account Plans are archived, only the associated CS and DM can view them.
TBD: defined Archive = Save, Submit, Publish? / TBD
BR11 / Only a CS can create an Account Plan. / UC01
BR12 / Only a DM can submit an Account Plan. / UC05
BR13 / Account Plan submit can only be done by the CS or DM associated with the Account Plan. A CS and DM may submit an Account Plan back and forth between each other as many times as necessary until they agree the Account Plan is ready for publish. / UC04
BR14 / Only a DM can publish an Account Plan. / UC05
Use Case Diagrams
Use Case Context Diagram
Account Plan iPad Workflow
Field Contact Report iPad Workflow
j
AP/FCR SFDC Workflow
AP/FCR Attach/Update/Delete Attached File
UC01: Create Account Plan
Use Case Details
Use Case Name: / Create Account PlanDescription: / Users are able to navigate to the Account Planning tool and create an Account Plan, by interacting with any of the Account Planning create/edit screens, in any order, then explicitly saving.
Actors: / CS
Trigger(s): / Account Plan is due, per CS, per Territory.
Pre-conditions: / User has logged into Account Planning.
User has sufficient rights to access Account Planning.
Post-conditions: / Only User (CS) can view/access newly created Account Plan.
Successful end state: / A new Account Plan is created and visible to CS author only, until CS submits to DM.
Failure end state: / User is unable to create Account Plan.
Preceding Use Cases: / None.
Subsequent Use Cases: / UC02, UC03, UC04, UC05, UC11, UC12, UC13, UC14
Path of Events
Basic path:
# / User Action / System Response1 / User navigates to any AP screen and enters information in any order/sequence to populate the Account Plan. Screens visited and information entered include:
Territory Plan
Current Status
Opportunity
Obstacles
Incremental Resource Requests
Territory Data
Account Plan
Objective
Tactic
Resource
Team Member
Timeline
Details/Comments
Team Plan
Account
Timeline
Objective
Tactic
Resources / System records user entered information, enables user to view/modify any AP information entered. System indicates there are unsaved changes.
2 / User can optionally view the Franchise Goal, then dismiss the Franchise Goal, while working with the Territory Plan / screen. / System displays/dismisses Franchise Goal, as user indicates.
3 / User Saves Account Plan. / System Saves Account Plan.
System makes saved Account Plan visible to CS Account Plan author only, via the Archive screen, until the AP is Submitted or Published.
System unflags unsaved changes.
Alternate path:
# / User Action / System ResponseError or Exception path:
# / User Action / System Response1 / User is unable to access Account Plan. / System displays error: Account Plan TBD inaccessible or unavailable.
2 / User is unable to save Account Plan. / System displays error: TBD Account Plan cannot be saved
System Enforced Business Rules
# / Business RuleBR03 / Account Plans are saved only when the End User (CS or DM) explicitly indicates Save, Submit, Publish, Attach File or Update/Delete Attached File.
BR04 / Account Plans that are saved but not submitted are accessible only to the CS or DM for view/update.
BR05 / Account Plans cannot be deleted. Account Plans can be versioned.
Only the current Account Plan is visible on the iPad.
Account Plan versions are only visible on the SFDC Server.
TBD
UC02: View/Update Account Plan
Use Case Details
Use Case Name: / View/Update Account PlanDescription: / Users are able to navigate to the Account Planning tool, find an Account Plan they wish to view/update, select an Account Plan to view details, then view or update the Account Plan.
Actors: / CS, DM
Trigger(s): / Account Plan is due, per CS, per Territory.
CS has created an Account Plan, saved it, then returned to view/update it.
CS has submitted Account Plan to DM.
DM has submitted Account Plan to CS.
Account Plan is published by DM.
Pre-conditions: / User has logged into Account Planning.
User has sufficient rights to access Account Planning.
User can find the Account Plan they wish to view/update.
User has sufficient rights to view/update the Account Plan.
Post-conditions: / The Account Plan has been viewed &/or modified.
Successful end state: / User has located Account Plan they wish to view or update, and has viewed &/or updated the Account Plan
Failure end state: / User is unable to locate Account Plan to view/update.
User is able to find Account Plan, but is unable to view/update it.
Preceding Use Cases: / UC01
Subsequent Use Cases: / UC03, UC04, UC05, UC11, UC12, UC13, UC14
Path of Events
Basic path:
# / User Action / System Response1 / User opens the account plan they wish to view/update / System displays selected Account Plan details, for user to view or update.
2 / User optionally modifies Account Plan details. / System enables view/edit of Account Plan details. System flags unsaved changes.
3 / User optionally saves Account Plan. / System saves changes to Account Plan. System unflags unsaved changes.
Alternate path:
# / User Action / System Response1 / User opens the account plan they wish to view. / System displays selected Account Plan details, for user to view or update.
2 / User views Account Plan, then dismisses Account Plan without making any changes, by selecting another Account Plan or logging out. / System waits for user command.
Error or Exception path:
# / User Action / System Response1 / User is unable to access Account Plan. / System displays error: Account Plan TBD inaccessible or unavailable.
2 / User is unable to save Account Plan. / System displays error: TBD Account Plan cannot be saved
3 / User is unable to view or modify Account Plan. / System displays error: TBD Account Plan cannot be displayed or modified.
System Enforced Business Rules
# / Business RuleBR03 / Account Plans are saved only when the End User (CS or DM) explicitly indicates Save, Submit, Publish, Attach File or Update/Delete Attached File.
BR04 / Account Plans that are saved but not submitted are accessible only to the CS or DM for view/update.
BR05 / Account Plans cannot be deleted. Account Plans can be versioned.
Only the current Account Plan is visible on the iPad.
Account Plan versions are only visible on the SFDC Server.
TBD
UC03: Save/Version Account Plan
Use Case Details
Use Case Name: / Save/Version Account PlanDescription: / Users are able to save an Account Plan upon Create or Modify, and optionally create a new version. Both old and new versions are visible on the SFDC Server. Only the current version is visible on the iPad client.
Actors: / CS, DM
Trigger(s): / Account Plan is due, per CS, per Territory.
Pre-conditions: / User has logged into Account Planning.
User has sufficient rights to access Account Planning.
User can find the Account Plan they wish to save/version.
User has opened the Account Plan they wish to save/version, and modified it.
Post-conditions: / The Account Plan has been Saved & optionally Versioned.
Successful end state: / User has located Account Plan they wish to view or update, and has modified, saved and optionally versioned the Account Plan
Failure end state: / User is unable to locate Account Plan to view/update.
User is able to find Account Plan, but is unable to view/update it.
User has modified Account Plan, but cannot Save it or Version it.
Preceding Use Cases: / UC01, UC02
Subsequent Use Cases: / UC04, UC05, UC11, UC12, UC13, UC14
Path of Events
Basic path:
# / User Action / System Response1 / User modifies an Account Plan. / System displays user updates to Account Plan, and flags unsaved changes.
2 / User indicates Save Account Plan. / System saves Account Plan, and unflags unsaved changes.
Alternate path:
# / User Action / System Response1 / User modifies an Account Plan. / System displays user updates to Account Plan, together with the status that there are unsaved changes.
2 / User indicates Save AND Version Account Plan. / System saves Account Plan, and indicates to user that Account Plan is saved into new version #.
System indicates that there are no unsaved changes.
TBD: should users be able to version an AP if there are no changes, so there’d be 2 versions of an AP that are exactly the same?
Error or Exception path:
# / User Action / System ResponseSystem Enforced Business Rules
# / Business RuleUC04: Submit Account Plan
Use Case Model
Use Case Details
Use Case Name: / Submit Account PlanDescription: / Users (CS or DM) can submit an Account Plan to each other. Only the CS associated with an Account Plan can submit to the DM associated with an account plan. And only the DM associated with an account plan can submit to the CS associated with an account plan.
Actors: / CS, DM
Trigger(s): / User needs feedback or action on an Account Plan from another User.
Pre-conditions: / User has logged into Account Planning.
User has sufficient rights to access Account Planning.
User can find the Account Plan they wish to submit.
User has opened the Account Plan they wish to submit.
Post-conditions: / The Account Plan has been Submitted to the other user associated with the Account Plan.
Successful end state: / Both users (CS or DM) can see that the Account Plan submit has occurred.
TBD should AP status include the history of submits?
The user receiving the submit has received a notification of submit.
Failure end state: / User is unable to locate Account Plan to submit.
User is able to find Account Plan, but is unable to submit it.
Preceding Use Cases: / TBD
Subsequent Use Cases: / TBD
Path of Events
Basic path:
# / User Action / System Response1 / User (CS or DM) opens an Account Plan. / System displays Account Plan details.
2 / User submits Account Plan to the other User (CS or DM) associated with the Account Plan. / System confirms submit.
System notifies recipient that an Account Plan has been submitted.
Both users can see that the Account Plan has been submitted.
Alternate path:
# / User Action / System ResponseError or Exception path:
# / User Action / System Response1 / User is unable to access Account Plan. / System displays error: Account Plan TBD inaccessible or unavailable.
2 / User is unable to submit Account Plan. / System displays error: TBD Account Plan cannot be submitted.
System Enforced Business Rules
# / Business RuleTBD
UC05: Publish Account Plan
Use Case Details
Use Case Name: / Publish Account PlanDescription: / User (DM) publishes Account Plan, which changes state to final/published.
Actors: / DM
Trigger(s): / CS and DM agree that Account Plan is final and should be published.
Pre-conditions: / User has logged into Account Planning.
User has sufficient rights to access Account Planning.
User can find the Account Plan they wish to publish.
User has opened the Account Plan they wish to publish.
Post-conditions: / The Account Plan has been published and state has been changed to final.
Successful end state: / Both users (CS or DM) can see that the Account Plan publish has occurred.
TBD should AP status include the history of publish?
Both Users (CS and DM) have received notification of publish.
Failure end state: / User is unable to locate Account Plan to publish.
User is able to find Account Plan, but is unable to publish it.
Preceding Use Cases: / TBD
Subsequent Use Cases: / TBD
Path of Events