Hi Community,
I am part of a project leadership team on a large programme that does include a fair amount of SharePoint implementation, some on premise and the in the cloud. Part of my role, as a Solutions Architect is to create various bits of documentation for both client signoff and for the various technology partners. Luckily I will be heavily involved in the build, as otherwise it will be death by a thousand documents 🙁
To ensure the team maintain a good velocity, the idea is that each type of document ( see below) captures the correct amount of information and under the correct document structure. Therefore, excluding the SAD, which covers the “universe”, the other documents can be relevant to SharePoint Farms, portals or even migrations from legacy systems. In the list below I have included my thoughts on what should go in them but I am really keen to hear the opinions from the wider community.
- Software Architecture Documents (SAD) –
- Business Requirements Documents (BRD) –
- High Level Designs (HLD) – short document which covers key stuff for sizing such as number of concurrent users.
- Low Level Designs (LLD) – expansion on the HLD, to capture the details needed to underpin the ( agile) build e.g. Physical Architecture (Server Topology), Information Architecture ( Site Structure, User Interface, Content types etc).
If there are word document templates, samples or other discussions out there, that would be great, as I will compare these with what I am trying to create for the team.
Daniel
