Quantcast
Channel: SharePoint 2013 - General Discussions and Questions forum
Viewing all articles
Browse latest Browse all 26374

Purpose and content of a good Functional Design

$
0
0

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:

============

  1. OVERVIEW
    1. Background      
    2. Document       Purpose

 

  1. INFORMATION ARTEFACTS
    1. Artefacts       overview (the list of information pieces the system operates)
    2. Data Flow       (how data is moving across the system)
    3. Usage       cases (different scenarios of using information artefacts)
    4. Artefacts       Managing (describing how different products – sharepoint, SAP, drupal and       others) can manage artefacts)

 

  1. INFORMATION ARCHITECTURE
    1. Site       Structure
          
      1. Site        Maps
    2. User       Interface and Branding
          
      1. Wireframes         
      2. Navigation         
      3. Branding       
    3. Content       Types, Columns and Lists
          
      1. Content        Types  
      2. Columns  
      3. List
  2. LOGICAL      ARCHITECTURE
    1. Feature       Mapping (which features of the SharePoint  are gonna be used and for       which purposes)
    2. Farm       Logical Architecture
    3. Web       Applications
          
      1. Zones  
      2. Managed        Paths
    4. Site       Collections and Content Databases
    5. Shared       Services
    6. User       Profile and Properties
    7. Search
    8. Audiences      
    9. Service       Accounts
  3. CAPACITY      PLANNING
  4. PHYSICAL      ARCHITECTURE
    1. Server       Topology
    2. Network       Infrastructure
    3. Storage       Requirements
          
      1. Web        Front-End Servers  
      2. Application  Server  
      3. SQL        Server

I am a SharePoint Infrastructure Engineer, focussed on Administration and Installation of SharePoint Server environments.MCITP SP2010 Administration



Viewing all articles
Browse latest Browse all 26374

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>