Even though its tempting to dive into functions and details its better to first get a grip of the process and big picture first.

This way you build up a good knowledge of impact of the parts in the chain and which functions to focus on and save resources at a later stage when implementing.

At a first glance it's easy to direct focus the wrong direction when starting on functional levels

If you enjoyed this post, make sure you subscribe to my RSS feed!

Focus on big picture business flows that is easy to overview commercially and break it down to detailed processes that is easier to develop and technically. Its easier to adopt in an organization if all levels understand the ideas.

Just as well as raising turnover figures with high margins the win with a system could be that it release resources that can produce more important services

If you enjoyed this post, make sure you subscribe to my RSS feed!

Use case documentation is a way to describe interaction in a system, function or sub function with input, outputs, validations et cetera.

To build good test scenarios use cases is a good base for this.

A use case should be a description both with a flow diagram and described in text of the different interactions and they can be broken down to sub use cases in many levels depending for whom they are written.

The use cases should describe scenarios covering all requirements in variants both for end users and developers

If you enjoyed this post, make sure you subscribe to my RSS feed!