Overview of a Simple Development Method

Background Before discussing some specific methods we will consider a simple method that doesn’t have a name but is a bit like the USDP This is the method followed by former colleague Ken Lunn in his book Ken now works for the NHS where he is paid a lot of money to try to apply his method to some terrifyingly complex software development projects He is happy to co-supervise MSc projects

The Vision – a reminder Business Models Use Cases Activity Models Interaction Diagrams Object Models Programs Databases Business Computing

One possible lifecycle

Let’s wander through this lifecycle with a Case Study The Huddersfield Playhouse

A Word from our Sponsor

Aims of the Case Study To see the different UML models in action To see how the models fit together

The Vision Activity Diagrams Use Cases Sequence Diagrams Class Diagrams Programs Databases Business Computing Entity Models

Let’s have a look at this first

Company background The Huddersfield Playhouse, a newly formed repertory theatre, wishes to have a new system for selling tickets and managing their various venues. They currently use an old-style system that is slow and cumbersome, and does not meet all their needs. They already have a modern computer and a printer that prints tickets.

Your role You are the business systems analyst assigned to the task by HudSoft, the new state-of-the-art software house. The project manager needs a clear picture of the system scope so that he can put a formal bid together. Not all the things that the theatre wants to do are possible, and some of them will be too expensive. You are there to determine in the first instance what is possible.

Huddersfield Playhouse We have been supplied with some basic information. The company needs to be able to: Make telephone bookings Make desk bookings on the night of the performance Transfer sales information to the accounts system Handle two venues, a main theatre and a studio Produce and maintain a mailing list Take bookings via their Web site

Stakeholders Customers Booking clerk Theatre manager

Map out Business Processes

Review with Stakeholders Added by theatre manager

Review with Stakeholders Discuss with Theatre manager and Booking Clerk They are happy with your ideas so far Now we look at how the new system will function First some activity diagrams are produced for the activities

Counter booking process Select venue on system Select performance on system Choose seats Take customer name and contact details Print reservation stub for customer Advise them to pay for and collect tickets 30 mins before performance

Counter booking process Select venue on system Select performance on system Choose seats Print reservation stub for customer Take customer name and contact details Advise them to pay for and collect tickets 30 mins before performance Take details on paper and enter later Wait until performance details are on system

Counter booking process Select venue on system Select performance on system Choose seats Print reservation stub for customer Take customer name and contact details Advise them to pay for and collect tickets 30 mins before performance Take details on paper and enter later Wait until performance details are on system Long Queue Customer declines

Counter booking process Select venue on system Select performance on system Choose seats Print reservation stub for customer Take customer name and contact details Advise them to pay for and collect tickets 30 mins before performance Take details on paper and enter later Take Payment Wait until performance details are on system Long Queue Customer declines Customer offers to pay

Counter booking process Select venue on system Select performance on system Choose seats Print reservation stub for customer Take customer name and contact details Advise them to pay for and collect tickets 30 mins before performance Handwrite reservation details Take details on paper and enter later Take Payment Wait until performance details are on system Printer not working Long Queue Customer declines Customer offers to pay

Produce next activity diagram The Take Payment activity

Take payment activity diagram Advise customers of tickets price Request payment method Print tickets and hand to customer Thank customer Take payment by cheque Cheque offered

Take payment activity diagram Advise customers of tickets price Request payment method Print tickets and hand to customer Take payment by cheque Thank customer Take Cash Payment Cheque offered Cash offered

Take payment activity diagram Advise customers of tickets price Request payment method Print tickets and hand to customer Take payment by cheque Thank customer Take payment by credit card Take Cash Payment Cheque offered Credit card offered Cash offered Credit card refused

Take payment activity diagram Advise customers of tickets price Request payment method Print tickets and hand to customer Take payment by cheque Thank customer Take payment by credit card Hand write tickets Take Cash Payment Cheque offered Credit card offered Cash offered Can’t print Credit card refused

Produce diagram for Take payment by credit card

Take payment by credit card Swipe credit card Enter amount Check signature Return credit card, voucher and till receipt to customer Enter amount on till and print receipt Wait for acceptance Obtain signature

Take payment by credit card Swipe credit card Enter amount Check signature Obtain signature Return credit card, voucher and till receipt to customer Credit Card refused Enter amount on till and print receipt Wait for acceptance

Take payment by credit card Swipe credit card Enter amount Check signature Obtain signature Return credit card, voucher and till receipt to customer Credit Card refused Enter amount on till and print receipt Wait for acceptance Signature does not match

Take payment by credit card Swipe credit card Enter amount Check signature Obtain signature Return credit card, voucher and till receipt to customer Credit Card refused Enter amount on till and print receipt Wait for acceptance Signature does not match Refer to manager Second attempt does not match Manager approves Manager refuses

Let’s have a look at this

Now Consider Use Cases Booking Clerk Use Case Diagram Book tickets Print tickets

Now Consider Use Cases Booking Clerk Use Case Diagram Book tickets Print tickets Add to mailing list > Print reservation stub > Take payment >

Book ticket use case (1)

Book ticket use case (2)

So what have we got An overview of the business A detailed breakdown of some processes A set of use cases A detailed description of use cases Consulted stakeholders

The flow of work in requirements capture Print Tickets Booking Clerk Take Payment > Add to mailing list Book tickets > Print reservation stub >

What next? Class Diagrams Design using sequence diagrams

We now need to look at this

Getting Started

Moving on

Implying the need for this class diagram

That gets us to here

Research Topic

‘Best practice’ in contemporary business systems design splits an application into four principal layers Presentation Application, Process, Task or Controller Domain object model Persistence

But “The Naked Objects Pattern” eliminates the controller layer by encapsulating all business functionality on the entity objects Presentation Application, Process or Use-case controller Domain object model Persistence

And has a generic presentation layer that automatically reflects the domain object model as an object-oriented user interface And has a generic presentation layer that automatically reflects the domain object model as an object-oriented user interface Presentation Application, Process or Use-case controller Domain object model Persistence

CarServ: A tale of two business applications

Good Idea? One of the research topics for the coursework element of this module Final project???