Wording For Welcoming Destination Wedding Guests

A picture - EBC on the web (part 1)

Some time ago I have begun the EBC paradigm in use to refer to my work. Meanwhile, a few examples emerged and many contributions in the discussion groups. But all that is incurred up there, you can see more under the light of the proof of concept.
To EBC technology continues to push forward, they need examples. Before all that, you can understand. Now that sounds logical, but as usual the devil is in the details.

• What kind of application? How realistic they should
• be implemented?
• How do you deal with change?
• And, as it is generally closer to the implementation of such an example?

These are all questions I have asked myself in recent days over again until I came to the conclusion that implementing the entire step by step and not everything in advance to plan by.
I begin simply with the ideas, then I invent meaningful performance requirements, find the domain and data objects, formulate the processes in the system and finally I try to implement the concept also in code.
That should be doable.

What an idea ... In today's

Time it is almost an insult if you do not offer web application as an example and to me this ... submit to, do I have decided what a miracle to develop a web application, which is located in the data-driven application. To mark the occasion I select a project from my immediate environment.
I would like to implement a payment system that is embedded in a web application to provide enhanced content to a user available to you.

The Story

"Customers want to use enhanced content to a standard web application. The enhanced content are subject to charges. To provide the customers of that content available to he has to put to his already well-known profile data, payment information and specify the nature of the payment product. "
That sounds not heavy. Especially since the entire payment process is provided by a service provider. Reaching him a couple of data from a customer and then he takes over the account and credit check, credit check, etc., etc. So I concentrate on a few processes related to data validation, and status messages from the payment service provider.
is thus formulated the idea of the example. Now I "invent" the benefits of the system and attack again in the box to me already known specifications.

The story as concept

Since I like to to communicate images and also the UML'm not averse I formulate the required performances of the system in a Use Case Diagram. To ensure that the chart is properly understood, I would like to once describe the contents of the chart in addition to words.

performance of the system
The user is the actor of the system, they expect benefits from the system, fulfilling his desire to make premium content available. The following services are provided by the system.

• The user can make a booking, the booking
• consists of the following steps: Select a Product
  
  • ,
  • enter billing address and payment method
  • choose
• A booking is confirmed with an email and
• The data of the payment will be verified during the booking process.

This is the framework for the application in the form of a summary management reports. The next step will be to describe the domain and the associated data.
So far so good, so the post office not too long, I would like to publish a description of the domain and the data in a next post.

January