SPA2005 session: What To Do Before OO | |||
| One-line description: | How to use Soft Systems Methodology to sort out what software to build. | ||
| Session format: | Working group [read about the different session types] | ||
| Abstract: | This session is about Soft Systems Methodology: why. when and how to use it to prepare for UML/OO program design. Sometimes systems are designed without enough attention, before requirements definition, to factors in the social context. Things (or people) that are ignored or insufficently understood show up in the middle of a development as requirement changes or worse. (These are called \\\'messy situations\\\' in SSM parlance.) SSM is a good way of checking that all relevant matters are considered. SSM has the added advantage of producing analysis artifacts that lend themselves to UML/OO design! Participants will learn what Soft Systems Methodology is, and get experience in doing it. | ||
| Audience background: | Participants may be people who are interested in working with customers to decide what systems need to be built. We hope to use one or more \\\'messy situations\\\' contributed by participants for the group exercises. We would want to limit the size of the working group to 15 participants. | ||
| Benefits of participating: | * An opportunity to work with the area of system development that is crucial to \\\'getting it right\\\'. * An introductory knowledge of Soft Systems Methodology. * A fun afternoon! | ||
| Materials provided: | Handouts, Introduction to Soft Systems Methodology, and How to do SSM (updated from OT2004). \\\'Messy situation\\\' examples to use in the exercises if participants are not able to provide them. | ||
| Process: | 00:00 - 00:15 General introduction - why this session? the timetable, etc. 00:15 - 01:00 Introduction to Soft Systems Methodology - where it came from, ideas involved, how it\\\'s been used 01:00 - 01:10 Break 01:10 - 01:25 Defining a \\\'messy situation\\\' to use with SSM methods 01:25 - 01:55 Doing it: rich pictures, CATWOE, PQR, levels, activity diagrams 01:55 - 02:05 Break 02:05 - 03:00 Continuation of exercise 03:00 - 03:10 Break 03:10 - ??? Concluding discussion | ||
| Outputs: | Some interesting drawings for a poster. A design for a system?! We\\\'d be prepared to follow-up by email if participants desired this. | ||
| History: | Rob used SSM with Debbie and her Port of Dover ICT colleagues, when exploring requirements for an invoicing system. Debbie has explored the usefulness of SSM when thinking with customers about what information support they need. They ran this workshop at OT2004, and are delighted to be doing it at SPA2005. | ||
| Presenters | |||
| 1. Deborah Lawther Dover Harbour Board |
2. Rob Day RDA Limited |
3. | |