Search My Blog & Website

Wednesday, December 30, 2015

Basic Design Document Components


1.       Systems Context Diagram

This illustrates a high level concept of the WMS system for each release and provides a black box perspective showing interfacing systems, release boundaries and high level view of the system main blocks.
 

2.       Functional Concept

Provides details of the functions of the WMS release and the design details of each function. It includes functional diagrams to show locations of where functions are implemented and an inventory list of details of each function. It includes coding and implementation details for each function.

3.       Entity Relationship Diagram

Offers a detailed view of the relationship across the various SFDC objects including dependencies
 

4.       Operational Concept

Provides details of the operational design of each function of the system, including triggers rules, workflows, and thresholds. It also includes data flow diagrams, process flows, field dependencies, formulas, and report / dashboards designs. The design has details of the all the coding and implementation decisions related to the operational aspect of the system.

5.       Design Constraints

Provides an understanding of any limitations imposed by SFDC environment, business rules, scalability or other non-functional requirements, cost and budgets, operational procedures and development tools.

6.       Interface Details

Includes definitions of interfaces, fields and data details across interfaces, data transmission attributes (frequency, source / destination formats, security, , interface controls and rules.

7.       Integration Design Spec

Includes details about interfacing systems, configuration needs, web services, APIs, XSDs and other integration styles used in the design such as messaging gateways, mappers, dispatchers, control buses and service layer details.

8.       Non-Functional Design Spec

Includes all non-functional design decisions and configurations for security, scalability, accessibility and interoperability.

No comments: