상세정보

Business Process Reengineering (BPR) is the key management trend of the day. Ivar Jacobson's book The Object Advantage presents a blueprint for re-designing a business according to BPR principles. It uses one method to integrate his work of reengineering a business, its processes and its vital infrastructure the information system. It describes all of the details about a business and its processes by viewing customers as users and business processes as cases of how they use the business "use cases". And it manages the risks involved in BPR by using a how-to method based on object technology, offering concrete guidance in the shape of a formal reengineering process. Whilst most books tackle the "soft factors" (motivation, management commitment, leadership), The Object Advantage goes beyond this type of hand-waving and offers practical steps to success that include: * A description that specifies every activity and deliverable involved in the business process * Deliverables, in the form of business models, that focus on the company's architecture and dynamics * A process for the development of an information system that is truly integral to the reengineered company A seamless relationship is created between business model and information system, vastly increasing a company's chances of successfully reenginneering itself - the heart of this relationship is the application of the BPR model and object technology. Ivar Jacobson's book will be essential reading for any manager contemplating reengineering their business or wishing to understand more about BPR and its practical implementation. It will also be invaluable for reenginnering teams re-designing their companies, employees within a reengineered company needing to understand how their new environment will work and what their role will be, and systems analysts and designers wanting to expand their current applications of object technology into business modelling and business reengineering.

정보제공 :

CONTENTS
Foreword / by James Martin = ⅴ
Foreword / by Dan L. Jonson = ⅶ
Preface = ⅸ
1 Business engineering = 1
 1.1 Introduction = 1
 1.2 What is business engineering? = 2
 1.3 Why do we need business engineering? = 7
 1.4 What does the new company look like? = 9
 1.5 Business engineering, business (process) reengineering, and business improvement = 13
 1.6 Risk management = 18
 1.7 The future of business engineering in the corporate world = 22
 1.8 Summary = 25
 1.9 References = 26
2 What is business modelling? = 27
 2.1 Introduction = 27
 2.2 What is a model? = 28
 2.3 What is a business model? = 30
 2.4 What does a business model look like? = 33
 2.5 A few words about the traditional way of modelling = 35
 2.6 Why do we need business modelling? = 36
 2.7 Who should have a business model, and why? = 38
 2.8 Working to develop a business model = 42
 2.9 Summary = 43
 2.10 References = 44
3 What is object orientation? = 45
 3.1 Introduction = 45
 3.2 Object-oriented models = 46
 3.3 What is an lbject? = 48
 3.4 Objects are linked = 52
 3.5 Objects can form aggregates = 59
 3.6 Objects belong to a class = 60
 3.7 One class can inherit other classes = 63
 3.8 A summary = 67
 3.9 Why is object orientation necessary? = 68
 3.10 Object orientation as a platform for the future = 69
 3.11 Object-oriented business modelling = 71
 3.12 Summary = 73
 3.13 References = 74
4 Object-oriented business engineering - an overview = 77
 4.1 Introduction = 77
 4.2 Object-oriented business engineering in context = 77
 4.3 Business reengineering overview = 78
 4.4 The reengineering directive = 82
 4.5 Envisioning = 83
 4.6 The objective specification = 88
 4.7 Reversing the existing business = 89
 4.8 Engineering the new business = 90
 4.9 Installing the new processes = 91
 4.10 Iteration = 92
 4.11 Business improvement = 92
 4.12 Summary = 95
 4.13 References = 96
5 Architecture = 97
 5.1 Introduction = 97
 5.2 What must you be able to express in a business model? = 98
 5.3 Internal and external models of a business = 100
 5.4 The use-case model = 101
 5.5 The object model = 112
 5.6 Use case versus objects = 126
 5.7 Asspcoatopms between use cases = 134
 5.8 More about use cases = 140
 5.9 Subsystems = 142
 5.10 Summary = 146
 5.11 References = 149
6 Reversing the existing business = 151
 6.1 Introduction = 151
 6.2 Why reverse engineering? = 152
 6.3 Overview = 154
 6.4 Building a use-case model = 155
 6.5 Building an object model = 162
 6.6 Analysing the result = 165
 6.7 Summary = 167
 6.8 References = 168
7 Forward business engineering = 169
 7.1 Introduction = 169
 7.2 Building a use-case model = 170
 7.3 Object modelling = 180
 7.4 Interaction diagrams = 191
 7.5 Information system development = 194
 7.6 Verifying the new business = 195
 7.7 Summary = 197
 7.8 References = 198
8 An example = 199
 8.1 Introduction = 199
 8.2 What do we want to change? = 200
 8.3 What kind of organization do we have now? = 202
 8.4 New business processes = 207
 8.5 An object model of the new business = 216
 8.6 Work-flow descriptions = 233
 8.7 Summary = 233
 8.8 References = 235
9 Building the supporting information system = 237
 9.1 Introduction = 237
 9.2 What is software development? = 238
 9.3 The software-development business-system objects = 251
 9.4 System development and business development = 270
 9.5 Procuring the new information-system support = 282
 9.6 Summary = 294
 9.7 References = 296
10 Managing object-oriented business engineering = 297
 10.1 Introduction = 297
 10.2 Tailoring the method = 298
 10.3 Project organization and management = 300
 10.4 Project staffing = 305
 10.5 Organization staffing = 307
 10.6 Reviews = 313
 10.7 Summary = 316
 10.8 References = 317
11 Scaling up to large businesses = 319
 11.1 Introduction = 319
 11.2 Two use-case models at different abstraction levels = 320
 11.3 Business system areas = 324
 11.4 Layered business models = 331
 11.5 Summary = 337
Glossary = 339
Index = 345