business modelling — UML, use cases, IT strategy, …

whitepapers, resources, and information

business modelling study — the library
excerpt"Actually, you don’t reserve a Book: you reserve a Title. A Book is a particular copy of a literary work; a Title is our name for that work. A reservation goes through a couple of states: when it is made, it is waiting for a Book to be found for it. Once a Book is found, it is waiting for the Member to come and collect it. The library records how long a reservation has been in the latter state, and drops the reservation if the book is not collected within a few days. A book that is being held for a reservation is neither available nor borrowed; this extends the ‘xor’ to encompass available, borrowed, and held for a reservation. When a book is held for a.reservation, it has to be a book that is available inthe library to which the member belongs."

UML modelling examples and exercises
excerpt "The states you associate with a Phone don't have to be information recorded within the Phone itself: for example, you might have a 'suspended' state for phones whose bills are unpaid. As analysts, we haven't yet decided where this information might be kept, but it's more likely to be in the Billing Agency than the Phone itself. Nevertheless, your statechart can include it because the information is associated with the phone somewhere in the world we're dealing with – and it certainly has an effect on the phone's behaviour. We'll decide at a later design stage, where to put the information. Consider whether it might be more useful to draw a statechart for a Phone Service – that is, the service provided to a customer by various organisations through a phone. A Phone Service has similar states to a Phone; but a Phone Service may continue through the replacement of a broken Phone. · For each state, write its definition (1) in natural language; (2) as a boolean function of other attributes and associations of Phone (or PhoneService) in your model. You may need to add new associations to the model for this purpose. If there are new use-cases you have found, add these to the model and draft pre/postconditions for them. "

complete solutions for process adoption
(consultancy, courses, workshops, mentoring, seminars, development)

process adoption | requirements engineering and project management | process definition | business modelling
email us  or  telephone   UK: 01625 850 839    International: +44 1625 850 839