Monday, 12 October 2009

3 Tier Architecture

System Base Service Registration

Due to the last discussion in later session we should change our diagram to system base service registration.
In the customer base Service registration we encounter some problem which one of them will occur when the related customer is removed from the department .
Because of there are services that should be completed in any condition ,
we need to register our services based on related system.

Saturday, 3 October 2009

Modify Of Person, Admin, Tech, Supervisor and Customer's class diagram

Incomplete form of diagarm A with some correction

For precise comparison between Diagram A and B I place UML form of diagram A .certainly this is not perfect one and need to be discussed in detail.


I removed the relation between customer and system classes and associated new relations from case and device classes and to customer class.

Friday, 2 October 2009

How to identify service process?

Let suppose that we identify each requested service based on related customer(the owner of the service)
one exception is that, if a customer was removed from the list , what happen to services which requested by this customer(employee) .
we can handle this exception in two different way :
1.we can remove requested service(s) created by this customer from the list of services.
2.flag these services as completed and close them.
but one problem exists :
there are services that should be completed unrelated of which one has requested them-the unconditional services- which should be completed under any situation.(should be discussed).

The question is:

how can we determine the customer independent services ?