I have been asked to outline the contents of a good Functional Design document and its minimum contents as a deliverable in a SharePoint implementation project and ofcourse we would like to have the best and best practices used in it when handed over by Vendor.
We currently have no Functional Design in this organization to use as a template FD, so I hope you can advise about the contents of a good Functional Design which can then be used as a starting point for the Technical Design.
I found something on the net, and I wanted to have your opinion whether this would be your typical Functional Design Document or not. Please give me your feedback:
============
- OVERVIEW
- Background
- Document Purpose
- INFORMATION ARTEFACTS
- Artefacts overview (the list of information pieces the system operates)
- Data Flow (how data is moving across the system)
- Usage cases (different scenarios of using information artefacts)
- Artefacts Managing (describing how different products sharepoint, SAP, drupal and others) can manage artefacts)
- INFORMATION ARCHITECTURE
- Site Structure
- Site Maps
- User Interface and Branding
- Wireframes
- Navigation
- Branding
- Content Types, Columns and Lists
- Content Types
- Columns
- List
- Site Structure
- LOGICAL ARCHITECTURE
- Feature Mapping (which features of the SharePoint are gonna be used and for which purposes)
- Farm Logical Architecture
- Web Applications
- Zones
- Managed Paths
- Site Collections and Content Databases
- Shared Services
- User Profile and Properties
- Search
- Audiences
- Service Accounts
- CAPACITY PLANNING
- PHYSICAL ARCHITECTURE
- Server Topology
- Network Infrastructure
- Storage Requirements
- Web Front-End Servers
- Application Server
- SQL Server