Titlebook: Software Development with UML; Ken Lunn Textbook 2003Latest edition The Editor(s) (if applicable) and The Author(s) 2003 CASE.design.devel

delegate

Business Modellingerything outlined in this book, the choice of techniques and the rigour with which they are to be used depends very much on the purpose and organization that is undertaking the development. If the development project is for a new business area or a new client, then a comprehensive business analysis

撤退

Requirements Analysisnt of use cases. The notations we have considered so far could have been used by the Ancient Romans to design their administrative systems. There has been a good reason for spending so much time on the context of the system. Use cases fit into business processes, and the best way of finding use case

復(fù)習(xí)

Buy, Build or Adapt. Today the vast majority of business application developments utilize computer packages for part or sometimes all of their computer systems. The policy that most companies adopt today is to buy a package before building one. Only if the software package market cannot produce an adequate solution do

慢跑

Systems Analysise business projects, and the construction of a system is only part of the overall project. It is vital that the groundwork is done well in advance of defining the system. The effect of premature analysis and design can be a great deal of rework later on, or worse the production of a system that is i

CIS

Intrepid

態(tài)學(xué)

小木槌

ovation

Introductionputer system development. However, we shall linger in each of the areas long enough, and give you sufficient pointers, for you to have a real feel of what a computer system development project is about.

heartburn

Case Studies — ICANDO Oilhe transformations that IT can make to the way companies undertake business. For the purpose of providing a realistic background to the examples in this book, we shall look at one major business sector.