How to specify in UML

[ssharish2005]

Hello all,

I'm in a process of building an uml diagram for room booking system scenario. And I’m a bit stuck at the following paragraph.

"Some bookings will take priority over others: long series of lectures are harder to fit in than one-off events, so sometimes the latter kind of booking is merely provisional until the former kind have all been settled; and anyway, the Head of Department has absolute power, and can (ask a secretary to) 1overrule any existing booking in favour of a later one that he deems more important."

As you see, there is a priority involved over when you book room for lectures in contrast to one-off event. But really the booking lectures have the priority.

I have a Booking class and members class and the relation between them is quite easy. But i cant really think of on how to represent the priority thing in any uml diagram. Any thoughts on how to?

Thanks very much guys!

ssharish

[phantomotap]

O_o

UML class diagrams are... well, they are class diagrams.

UML activity diagram are, for the purposes of this discussion, domain logic.

Even though these function loosely as clients of each other, they are distinct components.

A reservation has a priority. That's easy; the booking system (thus the class diagram) has an action that accesses and transforms the priority for reservation for each member. The booking system (class diagram) may reference a limited number of available placements so must also have an action that accesses and transforms the available number of reservations and placements. For a reservation to place the precondition states that a placement must be available at that priority level or higher.

The rule that says how a reservation may be cancelled if a different reservation gets priority is domain logic (thus the activity diagram). The facility that supports this behavior is natural to the booking system (class diagram), but the threshold, venue, placements, and reserved blocks are domain logic (activity diagram). The booking system (class diagram) must clearly provide actions that manipulate those components.

The rule that says how an unrelated component may adjust reservation priority is domain logic (thus the activity diagram). The booking system must provide support for this mechanism (class diagram). This can be accomplished through standard "OOP" patterns like visitor or observer (class diagram).

The "HoD" having approval then is referenced by claiming that he may adjust priority (thus the activity diagram) by referencing facilities of the booking system (class diagram).

Soma

[ssharish2005]

I have one more question, just wanted to verify if my model is correct. Following is the equipment

The primary use of the system will be for room bookings—for seminar and meeting rooms, laboratories, a video-conferencing suite, 
social spaces, and so on.  The various rooms have different characteristics—capacity, whiteboard space, different kinds of 
computer, video cameras and fixed projectors, water heaters, etc.

The portfolio of rooms changes rarely, but the portable resources change frequently."

So I had an original design with the class Room which was further extended to seminar, laboratories, a video-conferencing suite and etc.



But after I second requirement change it to the second design. But you see with the latter design, it clearly states, when you create a new room, there is always a portfolio attached to it, so that i could be anyone of room which is states above. Whereas if the former design lacks this sort of information. Please validate and do let me know what you think of it?



Thanks guys

ssharish

[ssharish2005]

anyone? any thoughts :-/

ssharish