SharePoint Requirement Types

Category: SharePoint

As of a part of SharePoint Business Analyst series (which is a part of my book, The SharePoint Business Analyst Guide), I wanted to review many of the different types of requirement documents I use on my projects. Each project will require a different set of documents depending on the complexity, people involved, budget, stakeholders, etc.

Remember, you may not use all of these SharePoint requirement, pick and choose which are needed for your project.

Type Reason for Use Examples    
Business Requirements Business requirements are high-level requirements that management and a board of directors would typically understand. The emphasis is on what is required, rather than on how to achieve it.
States the ‘why’ for a project.
“The system will allow users to enter data on each customer call and notate the current status to track inbound calls.”
“Creating an employee asset deployment tracking system that allows configuration and support teams to document their work and management to monitor it.”
Functional Requirements Functional requirements are very detailed and outline exactly what needs to be delivered and would typically be read by business analysts, developers, project manager and testers.
Outlines the ‘what’ for a project.
For example, if the business requirement is to create an asset deployment system as listed above, the functional requirements may outline how each support team will interact with the system, who has access to the system, how the managers will view the data, who will have ownership of the data and which time, what type of SharePoint site (list or library) would be used, etc.
Technical Requirements (non-functional) A technical requirement pertains to the technical aspects that your system must fulfill, such as performance-related issues, reliability issues, and availability issues and/or how the system will be built.

What is needed to support the project during implementation, development and ongoing delivery.

Any emergency outages will be responded to in less than 2 hours.
The system will ensure a 99.9% uptime with non-emergency planned outages being given one week notice.
Managing server logs to see if workflows produce errors.
Monitor the performance of the SQL Server database storage.
Provide server and network response times of lower than ___ seconds to save a form over an average period of time.
Data Type Diagrams Clearly defines the data types of each field This field will be of type multi-line rich text field.
Flow Diagrams When your project requirements become more complex (Visio) Defines the process of how things will flow before you build a workflow.
Prototypes / Mockups / Wireframes Screenshots, hierarchical site structure mapping State the structure of a site, assists with UI/UX
Testing Requirements Should always come back to verify the deliverables Having a user perform a specific set of tasks to validate a specific requirement works as agreed upon.
Technical Specifications Example of a proposed architecture, how a system would be built or architected. Example on how I would build an app and the restrictions in place that might prevent this so that I might obtain approval to deploy it.
Use Cases or User Stories  To determine a specific person’s functional need. Examples might be something like step-by-step instructions, 1. Go to website 2. Click on login 3. Enter username and password 4. You are redirected to the start page.
Data Type Diagrams Clearly defines the data types of each field This field will be of type multi-line rich text field.
Flow Diagrams When your project requirements become more complex (Visio) Defines the process of how things will flow before you build a workflow.
Prototypes / Mockups / Wireframes Screenshots, hierarchical site structure mapping State the structure of a site, assists with UI/UX
Testing Requirements Should always come back to verify the deliverables Having a user perform a specific set of tasks to validate a specific requirement works as agreed upon.
Technical Specifications Example of a proposed architecture, how a system would be built or architected. Example on how I would build an app and the restrictions in place that might prevent this so that I might obtain approval to deploy it.
Use Cases or User Stories  The specific need or case a user has. Examples might be something like step-by-step instructions, 1. Go to website 2. Click on login 3. Enter username and password 4. You are redirected to the start page.

 

(Visited 1 times, 1 visits today)
5/5 (2)

Please rate this blog post!

  •  
  •  
  •  
  •  
  •  
  •  
  •  

Leave a Reply

Your email address will not be published.