Prakash / Rolland / Pernici Information System Development Process

Proceedings of the IFIP WG8.1 Working Conference on Information System Development Process, Como, Italy, 1-3 September, 1993
1. Auflage 2014
ISBN: 978-1-4832-9848-1
Verlag: Elsevier Science & Techn.
Format: PDF
Kopierschutz: 1 - PDF Watermark

E-Book, Englisch, Band Volume 30, 351 Seiten, Web PDF

Reihe: IFIP Transactions A: Computer Science and Technology

This volume aims to pave the way to a greater understanding of the information system development process. Traditionally, information systems have been perceived as a slice of real world history. This has led to a strong emphasis on the development of conceptual models, the requirements specifications of which can readily be expressed. However, the route to such an expression, or the process of development, has not received any substantial attention.It is now agreed that a study of the development process affords notable benefits. Firstly, it helps to create an understanding of what a realistic development process is and how it proceeds from an initial specification to its acceptable representation. Secondly, the nature of guidance that can be provided by the next generation of CASE tools can be substantially improved. It can be expected that these tools will cease to be mere drafting aids and consistency checking programs. Instead it is likely that they will provide a procreative environment in which the development engineer will play an important role. This tool/user symbiosis should have a beneficial impact on both the productivity of the developer and on the quality of the product.In bringing together researchers and practitioners from such diverse areas as AI, Software Engineering, Decision Support and Information Systems, it is hoped this publication will take the quest to comprehend information system development processes a significant step forwards.

Autoren/Hrsg.

Prakash, N.

Rolland, C.

Pernici, B.

Inhaltsverzeichnis

1;Front Cover;1
2;Information System Development Process;4
3;Copyright Page;5
4;Table of Contents;10
5;PREFACE;6
6;PROGRAM COMMITTEE;8
7;LIST OF REFEREES;9
8;PART 1: INTRODUCTION;12
8.1;Chapter 1. Vision Driven System Engineering;14
8.1.1;1. INTRODUCTION;14
8.1.2;2. WHERE DO THE GOALS COME FROM ?;15
8.1.3;3 . HOW ARE THE GOALS USED ?;19
8.1.4;4. HOW ARE THE GOALS MANAGED ?;27
8.1.5;5. CONCLUSIONS;30
8.1.6;REFERENCES;30
9;PART 2: PROCESS/PRODUCT MODELING I;32
9.1;Chapter 2. Customization and Evolution of Process Models in EPOS;34
9.1.1;1. Introduction;34
9.1.2;2. Background;35
9.1.3;3. EPOS Survey: SPELL and Subdatabases;38
9.1.4;4. Process Models, Consistency and Variability;42
9.1.5;5. Proposals for Control of PM Changes;46
9.1.6;6. Conclusions and Further Work;47
9.1.7;References;48
9.2;Chapter 3. The Evolutionary Object Model (EOM);52
9.2.1;1. INTRODUCTION;52
9.2.2;2. MODELING EVOLUTION OF PRODUCT OBJECTS;54
9.2.3;3. F3 TRACING MODEL;58
9.2.4;4. CONCLUSION;67
9.2.5;REFERENCES;68
10;PART 3. REUSE I;70
10.1;Chapter 4. Mechanisms of Standardized Reusability of Objects (MCO methodology);72
10.1.1;1. INTRODUCTION;72
10.1.2;2. REMINDER OF THE PRINCIPAL CONCEPTS OF THE MCO MODEL;74
10.1.3;3. MAIN CONCEPTS OF OBJECT REUSABILITY;75
10.1.4;4. THE STANDARDIZED REUSABILITY OF OBJECTS;76
10.1.5;5. EXAMPLE OF RESULTS OF THE STANDARDIZED REUSABILITY OF OBJECTS;83
10.1.6;6. USE AND IMPLEMENTATION OF THE ALGORITHM OF STANDARDIZED REUSABILITY OF THE OBJECTS;83
10.1.7;7. USE OF MECHANISMS OF STANDARDIZED REUSABILITY DURING THE INTEGRATION OF NEW INSTANCES;85
10.1.8;8. STEPS WHERE THE OBJECT REUSABILITY IS STUDIED;86
10.1.9;9. CONCLUSION;86
10.1.10;REFERENCES;88
10.2;Chapter 5. Reuse of Specifications and Designs in a Development Information System;90
10.2.1;1. Introduction;91
10.2.2;2. Development Information System;92
10.2.3;3. Reuse model;97
10.2.4;4. Application Specification Session;103
10.2.5;5. Concluding remarks and future work;105
10.2.6;Acknowledgments;106
10.2.7;References;106
11;PART 4: REQUIREMENTS ENGINEERING;108
11.1;Chapter 6. Use of Domain Knowledge for Requirements Validation;110
11.1.1;1. INTRODUCTION;110
11.1.2;2. A PRELIMINARY THEORY OF DOMAIN KNOWLEDGE;111
11.1.3;3. VALIDATION AND THE DOMAIN THEORY;118
11.1.4;4. FUTURE WORK ON VALIDATION;122
11.1.5;5. CONCLUSIONS;124
11.1.6;ACKNOWLEDEGEMENTS;124
11.1.7;REFERENCES;125
11.2;Chapter 7. Utilizing Scenarios in the Software Development Process;128
11.2.1;Abstract;128
11.2.2;1. Introduction;128
11.2.3;2. An Example Application;129
11.2.4;3. A Scenario is;130
11.2.5;4. Three Example Systems;132
11.2.6;5. Roles of scenarios;134
11.2.7;6. Computer-Based Support for Scenarios;141
11.2.8;7. Summary;144
11.2.9;References;144
11.3;Chapter 8. Assessment and control of the requirements elicitation process in a CASE environment;146
11.3.1;Abstract;146
11.3.2;1. INTRODUCTION;146
11.3.3;2. AN UPGRADED CASE ENVIRONMENT;147
11.3.4;3. CALCULATION OF SPECIFIC RISKS;152
11.3.5;4. CONCLUSIONS;156
11.3.6;REFERENCES;157
12;PART 5: METAMODELING;158
12.1;Chapter 9. A Meta-Model for Representing Software Specification & Design Methods;160
12.1.1;1. INTRODUCTION;160
12.1.2;2. REQUIREMENTS TO META MODEL;161
12.1.3;3. META MODEL;162
12.1.4;4. REPRESENTING METHODS BY USING META MODEL;164
12.1.5;5. RELATED WORKS;168
12.1.6;6. METHOD BASE SYSTEMS;171
12.1.7;7. Conclusion;175
12.1.8;REFERENCES;175
12.2;Chapter 10. A Method Engineering Approach to Information Systems Development;178
12.2.1;Abstract;178
12.2.2;1. Introduction;178
12.2.3;2. The Framework;181
12.2.4;3. The Decomposition Process;184
12.2.5;4. Aspects of the Framework;190
12.2.6;5. Instantiating the Framework, an Example;193
12.2.7;6. Conclusions and further research;195
12.2.8;References;196
13;PART 6: COOPERATIVE APPROACHES;198
13.1;Chapter 11. The Role of Interaction Analysis in Requirements Engineering;200
13.1.1;Abstract;200
13.1.2;1. INTRODUCTION;200
13.1.3;2.0. INTERACTION ANALYSIS;203
13.1.4;3.0. CASE STUDY;207
13.1.5;4.0. FURTHER DEVELOPMENTS;213
13.1.6;5.0. SUMMARY;214
13.1.7;REFERENCES;215
13.1.8;ACKNOWLEDGEMENTS;216
13.2;Chapter 12. Conflict Management in Systems Development Groups;218
13.2.1;Abstract;218
13.2.2;1. INTRODUCTION;218
13.2.3;2. A WAY OF WORKING;221
13.2.4;3. DEVELOPMENT TRANSACTIONS;224
13.2.5;4. FUTURE WORK;235
13.2.6;REFERENCES;237
14;PART 7: PROCESS/PRODUCT MODELING II;240
14.1;Chapter 13. Product Modeling for Requirements Engineering Process Modeling;242
14.1.1;1. INTRODUCTION;242
14.1.2;2. THE NATURE PROCESS MODELING APPROACH;243
14.1.3;3. PRODUCT MODELING;247
14.1.4;4. SITUATION BUILDING UPON THE PRODUCT;252
14.1.5;5. CONCLUSION;255
14.1.6;REFERENCES;255
14.2;Chapter 14. A Development Model: Application to Z Specifications;258
14.2.1;1. Introduction;258
14.2.2;2. A Model for Developing Specifications;259
14.2.3;3. Phone Network Case Study;264
14.2.4;4. Conclusion;273
14.2.5;References;274
15;PART 8: REUSE II;276
15.1;Chapter 15. Reusing Process Specifications;278
15.1.1;ABSTRACT;278
15.1.2;1. INTRODUCTION;278
15.1.3;2. CONCEPTUAL MODELING;279
15.1.4;3. REUSE OF CONCEPTUAL SPECIFICATIONS;282
15.1.5;4. CONCLUDING REMARKS;292
15.1.6;REFERENCES;293
15.2;Chapter 16. Repositories for Software Reuse: The Software Information Base;296
15.2.1;Abstract;296
15.2.2;1. INTRODUCTION;296
15.2.3;2. DESCRIPTION OF SOFTWARE;298
15.2.4;3. FUNCTIONALITY AND ARCHITECTURE OF THE SIB;301
15.2.5;4. USAGE EXAMPLE;306
15.2.6;5. IMPLEMENTATION;313
15.2.7;6. CONCLUSION;315
15.2.8;REFERENCES;316
16;PART 9: INFORMATION SYSTEM ENGINEERING;320
16.1;Chapter 17. Concurrent engineering of information systems;322
16.1.1;1. INTRODUCTION;322
16.1.2;2. A GENERIC SOFTWARE PROCESS;323
16.1.3;3. PARTITIONING OF AN INFORMATION SYSTEM;325
16.1.4;4. CONCURRENCY IN THE SOFTWARE PROCESS;327
16.1.5;5. SF SPECIFICATION OF A CONCURRENT SOFTWARE PROCESS;329
16.1.6;6. CONCLUSIONS AND RECOMMENDATIONS;333
16.1.7;REFERENCES;334
16.2;Chapter 18. Business Process Redesign and Information Systems Design: A Happy Couple?;336
16.2.1;ABSTRACT;336
16.2.2;SETTING THE SCOPE;337
16.2.3;WHY REDESIGN BUSINESS PROCESSES?;337
16.2.4;DEFINITIONS;338
16.2.5;WHY BUSINESS PROCESSES IN INFORMATION PRODUCTION ARE NOT REDESIGNED;339
16.2.6;BUSINESS PROCESS REDESIGN VERSUS INFORMATION SYSTEM DESIGN;340
16.2.7;COUPLING BUSINESS PROCESS REDESIGN AND INFORMATION SYSTEM DESIGN;344
16.2.8;CONCLUSION;346
16.2.9;REFERENCES;347
17;AUTHOR INDEX;348
18;IFIP;350