Journey of a new website: functional specification
When defining functional specification for your project, you need to consider several important aspects:
- User roles
- User scenarios
- Website/Application functionalities
- Call to action
These are sometimes difficult to understand and apprehend, but your digital agency should be able to help you define all those aspects. This document doesn't have to be in any specific form or in any specific technical terms. It can be plain language, so don't be afraid of making a mistake or doing it wrong. There is no wrong way of writing functional specification.
User roles are all different users existing in your website or application. In presentation websites, these are usually admin and visitor. However, modern web applications can have multiple user roles who all have different abilities throughout the system.
User scenarios cover all different scenarios that previously defined user roles can come across while using your new application. These can be described in plain language, not fancy technical language is needed.
App functionalities are all the automated tasks and options that your users can use in their user scenarios. In other words, these will usually be: create new order, edit existing order, delete order etc.
Call to action is probably most important feature of the functional specification, as it describes what is your ultimate goal for this website or application. It can be simple as buying a product on your online store, or giving the call to your sales service, but you need to be aware of what it is from the very beginning. Having clear call to action will define your website or application greatly.