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!

There is always one way that fits for a good relaxation, could be just sitting out in a forest and listen to the wind, running 10km or classical music.

The important thing is to find what works for you and here is some tips to start of with:
1. Breath calm and breath with the stomach (belly move forwards and shoulders do not move upwards)
2. Close your eyes and concentrate on one sense at a time giving input, a scent or sound perhaps
3. Make sure you don't freeze on your special place, it's easier to relax then
4. Be close to water

Good luck!

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!