Required Artifacts

Artifacts required during the presentation

  1. SOAI (Systems, Objects, Actors/licenses, Integration) Artifact
  2. Role Hierarchy Artifact
  3. Data Model Artifact
  4. System Landscape Artifact
  5. Release Artifact
  6. SSO/OAuth Flow and Artifact
  7. Governance

SOAI Diagram

Objects            |       Systems             |    Actors/Licenses
                  |                           |                                     
                  |                           |                                     
                  |                           |                                     
                  |                           |                                     
                  |                           |  ___________________
                  |                           |                                     
                  |                           |    Integrations
                  |                           |                                     
                  |                           |                                     
                  |                           |                                     

Role Hierarchy Diagram

Block Diagram of Actor hierarchy (Internal and External)

 _____________________
|                     |
|     Actor           |
|                     |
|________________INT__|
                 |
__|___________
|              |
|     Actor   |
|              |
|_________EXT _|

Data Model Diagram

___________________
| OWD    Data Vol |
|                  |
|   Object Name    |
|                  |
|_Owner____________|
  • Black = Standard Object
  • Green = Custom Object
  • Red Line is Master-Detail
  • Blue line is Lookup

Notes: Use high-level ERD showing standard and custom objects, indicate master-detail vs. lookup, highlight EXTERNAL systems (data), Mark in ERD Box (Object Name, OWD, Data Volume, and Owner)

System Landscape Diagram

Key

  • Black = Users/Client
  • Green = Secure (Behind Firewall)
  • Red Line = On Prem Systems
  • Blue line = Salesforce and Cloud-based Apps

Note: Provide all the Key Components (Systems, applications and Browser/Devices). Show Existing, New, and Removed (With X through the component). Identify Key SF Licenses and Actors. State and show Single or Multi SF Org. Identify key 3rd Party Applications and systems (Behind the firewall and in the cloud). Consider data migration (both ETL and ESB or Integration)

Release Diagram

Consider:

  • 1) Plan, 2) Development, 3) Testing, 4) Build Release, 5) Test Release, 6) Release
  • If possible, include CLI and Scratch Org using VCS
  • CI with Test Automation — CD with Build Automation — Developer to VCS with Feature Branches

Show Sandbox type (limits included) for steps

Dev –> VCS (feature) –> Integration (Pro 1g) –> QA (Partial 5g) –> UAT (Full) –> Pre Prod (Full) –> Prod

Note: The release plan needs to provide the Key Release Environment (Dev, SIT, UAT, Prod, etc.), the Sandbox types. It should show the release process (plan) using CI/CD (automation), VCS, Testing process and Tools and applications used.

SSO/OAuth Flows

Use this format:

  • OAuth/SSO Flow used – Why?
  • Swimlane
  • Flow Diagram
  • Identify IDP and SP clearly

Note: Identify each Flow and why you selected it. Present the section with both Swimlane diagram and flow diagram. Describe what happens at each step. Mark it on diagram. Consider and show each of the following 1) Connected Applications, 2) MyDomain, 3)Auth Providers, 4) configurations

Governance

Identify each governance requirement using bullets, approvals, etc. Bullet format is acceptable

Leave a Reply

Close Menu