how detailed is TicketMaster in sequence diagram

[Saha Kumar]

Hello All,

How many details of the HTTPs protocol should be put into the sequence diagram when paying by credit card? I know to use HttpsConnection, but there are other concerns. How many details should be shown?

Thanks in advance.

-Saha

[Ricardo Ferreira]

Originally posted by Saha Kumar:
Hello All,

How many details of the HTTPs protocol should be put into the sequence diagram when paying by credit card? I know to use HttpsConnection, but there are other concerns. How many details should be shown?

Thanks in advance.

-Saha

Hi Saha,

My Advice for you is for do not put any technology details in your sequence diagrams. The idea behind this scenario is only show an legacy access.

So, a good design for this scenario is one service component, let�s call it 'PaymentDAO' for instance. This PaymentDAO component access an subsystem component that represents the TransMaster system.

One key information that must be embodied in the diagram, is the method call type (synchronous or asynchronous).

The technology details must be described in yours assumptions section. There, you can explain what protocols to use, SSL implementation, versions, etc.

In the architecture discipline, there are two main concerns that must be ensured:

- HOW THE SYSTEM WORKS ?
- HOW THE SYSTEM MUST BE IMPLEMENTED

Usually, this two concerns generates a lot of doubts for the system designers, but, a good architecture must emphatize the 'HOW THE SYSTEM WORKS', much more than 'HOW THE SYSTEM MUST BE IMPLEMENTED'.

Good Luck!

[Saha Kumar]

Thanks Ricardo, that was a very good solution. I had planned to use something similar with mileage account...but why not credit card also!

Very cool.

-Saha