How 2 Make Some One Fall Asleep

creates an image - EBC on the Web (Part 3)

It goes on ...

After the system and the idea have described domain, here is now developing the core of planning, the process description. EBC design process, the individual activities and processes are described in layers from a high to a low level of abstraction. This form of description reflects the infrastructure of the application. It corresponds to the formulation of the White Box diagrams for components. I use the graphic forms of activity diagrams, what is the nature of the thing, if you want to describe processes, activities and actions.

processes in project

The payment process is the simplest view of the system and describes that after the permission of booking is issued for the advanced content.

An overview level down is' book product ", the entire process. Each activity listed here is again viewed as a process and can be implemented with straightforward effort as a single story. A small exception here takes 'choose payment method' is the one activity. As I still do not know exactly how I put these shoes, I have it for the time being excluded from the planning stage.

the way out

In this post I do not want to represent all the diagrams for each process step, because I believe am that is sufficient is an exemplary representation to understand the principle.

deviation 1: 'Product Book' In the first diagram and process level, I have omitted the typical for the EBC pins to show that the pins are important to describe the process.

deviation 2: Even though I've entered in the next diagram the pins already, still missing a very important detail, the error handling. It would be modeled by Pin's Out and Activity.

Back on the road

an example, I present here 'to enter your billing address, "Now the process is step (without error handling).

What is shown? If "Enter Billing Address', the user enters the process / trigger / start, he can decide what is typed first. 'Enter first name' intermediate to 'enter email' every combination in it. After a finished entering the value or value combination is validated by logic. At the end of the process (represented here are not optimal), all inputs are validated and the process can 'choose payment method' start.

Well, I think I could represent the principle. The next step is to go even to code. Code shows an example of as the processes, activities and actions are put together.

January