With the massive increase in interest in BPR, TQM and ISO 9000 has come a tide of texts and evangelical razzamatazz on the philosophy and the hearts and minds issues. But those tasked with making change happen at the coal face must feel short of practical tools to work with when it comes to modelling and analysing the business processes that are to be re-engineered, improved or defined. This book provides an answer. Why worry about processes? People know that organisations have functions and responsibilities but not everyone will see these as part of the process. Each person does their bit, but how do all the pieces fit together? Starting people to think about processes and simply modelling the processes can provide individuals and groups with a perspective which transcends parochial views and results in a more collaborative spirit; "now I know what you want I can ensure you get it reliably". A model that makes the process visible to all concerned brings great value in itself. Business Processes is intended to help people "get out of the functional silos". What is STRIM? STRIM—A Systematic Technique for Role & Interaction Modelling—and its central notation—The Role Activity Diagram— provides a practical method for really getting to grips with what the organisation does and how it does it, in a way which is revealing, communicative, and accessible by everyone around the organisation. The book covers the full method: from organising a modelling project, through the notation, its use at micro and macro levels, patterns of organisational behaviour, through process analysis and on into process support system development.

How to manage quality up, and risk down. This invaluable guide to project planning and strategic decision making for software developers presents practical and realistic planning techniques to increase chances of a project delivering to time and budget. Offering clear explanations and real-world experiences, the key components of technical management are laid out as templates and checklists to assist managers with their project development. With thirty years of experience in software development, Martyn Ould provides:
* Proven strategies for a disciplined approach to project planning
* Steps to take in risks and uncertainties in the project
* Reliable methods for reducing risks to an acceptable level
* A quality planning process that is rooted in the technical requirements of the system
* Insight into monitoring and measuring project progress
* Real-world experience through case studies and examples

The designer of a software system, like the architect of a building, needs to be aware of the construction techniques available and to choose the ones that are the most appropriate. This book provides the implementer of software systems with a guide to 25 different techniques for the complete development processes, from system definition through design and into production. The techniques are described against a common background of the traditional development path, its activities and deliverable items. In addition the concepts of metrics and indicators are introduced as tools for both technical and managerial monitoring and control of progress and quality. The book is intended to widen the mental toolkit of system developers and their managers, and will also introduce students of computer science to the practical side of software development. With its wide-ranging treatment of the techniques available and the practical guidance it offers, it will prove an important and valuable work.