Difference between revisions of "Functionality Analysis"

Revision as of 15:06, 26 August 2012

What

A description of the functionality in the blocks.

How

The dish

Description of the functionality of each block

Ingredients

• Artefacts from the General Analysis up to this point

Process

Walk through each block in the overall architecture diagram and describe the functionality of each block. Do not think about how the required functionality can be implemented at this point.

All artefacts produced up to this point in time are sources of information for the functionality descriptions.

Customer may possess valuable information that shall be gathered and formalised, hence a high customer involvement is still recommended during this process. The customer may have any mathematics available. The customer is the best source to information about data manipulation in the system-to-be.

Estimate the complexity of each functionality. Use for example the categories: Simple, Medium, Complex and Very Complex. Functionality with a high complexity should be described in more details.

If specific mathematics is needed for the functionality, include the necessary formulas, if available, together with the description.

Why

It is vital to have both an overall description of the system-to-be and as analysis breaks the system down into smaller blocks, the functionality of each block shall likewise be described.

Each time a whole is broken into smaller blocks the details needed to describe the individual block become finer and finer. The developer gains more and more understanding of how the system-to-be shall be implemented.

Example