Software methods for business reengineering
著者
書誌事項
Software methods for business reengineering
Springer, c1996
大学図書館所蔵 件 / 全8件
-
該当する所蔵館はありません
- すべての絞り込み条件を解除する
注記
Includes bibliographical references (p. [260]-268) and index
内容説明・目次
内容説明
An approach to reorganising businesses using software engineering as a guiding paradigm. The author argues that software engineering provides both the necessary analytical expertise as well as the tools to transform process descriptions to support systems. He begins by introducing the necessary concepts, principles and practice before demonstrating how a business can define and construct the information base required. As a result, any manager or technically-minded person will learn here how to implement the reengineering of a business.
目次
I. What is Business Reengineering.- 1. The Established and the Reengineered.- 2. Business Reengineering is Not New.- 3. The Purpose of Reengineering.- 4. Steps in the Reengineering Effort.- 5. Making the Most of Human Resources.- 6. The Nature of a Process.- II. What is Software Engineering.- 7. Engineering Principles in Software Development.- 8. Classifications of Software.- 9. Modularization and Requirements Engineering.- 10. Software Quality Attributes.- 11. The Software Development Process.- 12. Software Cost and Risk Estimation.- III. Business Analysis.- 13. Analysis of Business Activities.- 14. Individual Interviews.- 15. Group Sessions.- 16. Business Process Prototyping.- IV. The Reengineering Blueprint.- 17. From Natural Language to Entities and Relationships.- 18. State Transitions and Control Flows.- 19. Control Flows in Terms of Petri Nets.- 20. From ER Diagrams to Information Modules.- 21. From Flow Diagrams to Process Modules.- 22. Validation of the Blueprint.- V. Information-Control Systems.- 23. Specification of Business Processes.- 24. The Specification Language SF.- 25. An SF Specification: An Editorial Office.- 26. A Case Study: Order Processing.- VI. Implementation of Reengineering.- 27. The Reengineering Process.- 28. Determination of Priorities.- 29. Legacy Software.- 30. The Communication Infrastructure.- 31. User Interfaces.- 32. Maintainability and Reusability.- Appendices.- A. Basic Mathematical Notations.- B. A Reading Guide.- References.
「Nielsen BookData」 より