Functional Specification and Testing Management
- Kevin Kuo
This page highlights Vertic’s standard when writing functional specification documents and testing developed solutions.
Functional Specification
Functional specifications are a formal written document during the solution design phase where it forms the blueprint which outlines the solution that Vertic will deliver, what it is going to look like, its specific requirements and functions for the client in the Salesforce ecosystem. This particular document presents the expectations of the completed solution where all stakeholders review and approve before Vertic proceeds to implement and configuration of Salesforce.
We include in the following in our standardised approach:
Overview/Summary - This is an overall look at the solution, where it begins by outlining the solution idea and give as a brief description to introduce the solution and its overall concept. The overview/summary, explains what the final product will look like, what features it will have.
Data model design - Built around business requirements, this illustrate the types of data used and stored within the system, the relationships among these data types, the ways the data can be grouped and organised and its formats and attributes.
Requirements - Describes how you see the appearance and capabilities of the upcoming solution. Outlining how users will interact with it and reference point for the development team as they begin their work
Process diagram - Models the sequence of activities within a process.
Decision log - Used to communicate how a decision was reached, options considered and who approved the decision. Eliminates potential confusion and holds all parties accountable for the decisions made
An example specification can be seen here: https://verticconsulting.atlassian.net/wiki/spaces/LN/pages/1500282887
Examples, use cases and mock-up screens are used in these documents to give readers more context and decrease the chance for misinterpretations. At no point in time should examples include sensitive information or production data.
Sandbox Testing
Before the solution is deployed into production for use, we undergo testing in conditions that closely simulate the client’s production environment but we do this in a sandbox testing environment utilising test data generated via this service for scale or fictional data is applied.
This practice prevent personal and sensitive content from being exposed in the development and testing stages while stress testing the solution ensuring that the solution is robust.
Add fields which are in accordance to the specs
Download large amounts of randomly generated test data to load into test environment
