Application Planning and storyboarding

Specifications

The first step to creating an application is requirements and specifications.

In software development we have something as an SDD – a Software Description Document. This is what describes what needs to be built, what features to have in it, how it needs to be built etc.

The idea is analysed first –

We identify the one thing the makes the app stand a part from its competitors if any and how we go about doing it. Most of the times it may be the ease of doing things rather than a novel way of doing things that makes a great deal of difference.

What is it supposed to do, Who is going to use it, What they are going to use it for. – this gives us the applications features, the actions and presentations it needs to do. From here we build ‘use cases’ detailing how the app flows. This may be as simple as what’s displayed on each of the screens to triggering more events on app, notifications, or getting permission or approval from another user.

The Applications personality – how it interacts with the users and how users interact with it. – this in turn User Interface and Experience guide, the tone and nature of the app and the look and feel – this is the User Interface. This lists the screens of an app or the pages of a web application, what they show, how they work with the user.

The screens and presentations are to be so created that a typical user needs zero time getting used to.

We identify the most common actions the app will be used for and plan the actions and screens to complete them in as little clicks as possible.

Now that we have who the app is supposed to serve, what is it supposed to do and how, the way it looks and the way it presents any information, we can describe the application’s specifications.

This is by far the most important step in software development.

Tags: