| | | Copyright |
| | | Foreword |
| | | Preface |
| | | | The Inspiration for This Book: Object-Oriented Analysis |
| | | | About the Book |
| | | | The Important Stuff |
| | | | Acknowledgments |
| |
| | | Introduction |
| | | | About Requirements Analysis |
| | | | From Analysis to Design |
| | | | About This Book |
| |
| | | Chapter 1. A Framework for Architecture |
| | | | The Zachman Framework |
| | | | The Architecture Framework |
| | | | The Analysis Process |
| | | | Implications |
| |
| | | Chapter 2. Managing Projects |
| | | | Introduction |
| | | | Summary of Development Phases |
| | | | About Strategy |
| | | | About Requirements Analysis |
| | | | Process One: Define Scope |
| | | | Process Two: Plan the Process |
| | | | Process Three: Gather Information |
| | | | Process Four: Describe the Enterprise |
| | | | Process Five: Define What Is Required of a New System |
| | | | Process Six: Determine the Existing Systems Environment |
| | | | Process Seven: Plan for Transition |
| | | | Summary |
| |
| | | Chapter 3. Column One: Data |
| | | | Views of Data |
| | | | A Brief History of Data Architecture |
| | | | Advanced Data ManagementMeta-data |
| | | | GraphicsData Modeling |
| | | | Using Entity/Relationship and Object Models |
| | | | Normalization |
| | | | Data Modeling Conventions |
| | | | Entity/Relationship Model Validation |
| | | | The Requirements Analysis DeliverableColumn One |
| | | | Data and the Other Columns |
| | | | Conclusion |
| |
| | | Chapter 4. Column Two: Activities |
| | | | From the Business Owners' View to the Architect's View |
| | | | Approach |
| | | | Function Hierarchies |
| | | | Dependency Diagrams |
| | | | Data Flow Diagrams |
| | | | IDEF0 |
| | | | The UML Activity Diagram |
| | | | Interaction Diagrams |
| | | | Use Cases |
| | | | A Word About Business Process Re-engineering |
| | | | Detailed Function and Process Documentation |
| | | | Implications of Analyzing Activities |
| | | | The Requirements Analysis DeliverableColumn Two |
| | | | Activities and the Other Columns |
| |
| | | Chapter 5. Column Four: People and Organizations |
| | | | How to Organize the Enterprise (Row One) |
| | | | Row Two: The Business Owner's View |
| | | | Row Three: The Nature of a (Human) System |
| | | | Implications of This Model |
| | | | System Use |
| | | | Requirements Analysis DeliverableColumn Four |
| | | | People, Organizations, and the Other Columns |
| |
| | | Chapter 6. Column Three: Locations |
| | | | Row TwoGeography |
| | | | Row ThreeNetwork (and the Other Columns) |
| | | | The Requirements Analysis DeliverableColumn Three |
| |
| | | Chapter 7. Column Five: Timing |
| | | | Introduction |
| | | | Row One: Scope |
| | | | Row Two: The Business Owner's View |
| | | | Row Three: The Architect's View |
| | | | The Requirements Analysis DeliverableColumn Five |
| | | | Timing and the Other Columns |
| | | | Conclusion |
| |
| | | Chapter 8. Column Six: Motivation |
| | | | Introduction |
| | | | Row One: Scope |
| | | | Row Two: Business Owners' Views |
| | | | Row Three: Architect's View |
| | | | Requirements Analysis DeliverableColumn Six |
| | | | Motivation and the Other Columns |
| | | | Conclusion |
| |
| | | Appendix A. The Zachman Framework |
| | | Appendix B. A Comparison of Data Modeling Techniques (Syntactic Conventions) |
| | | | Peter Chen |
| | | | Information Engineering |
| | | | Richard Barker's Notation (as Used by Oracle Corporation) |
| | | | IDEF1X |
| | | | Object-Role Modeling (ORM) |
| | | | The Unified Modeling Language (UML) |
| | | | Extensible Markup Language (XML) |
| | | | Recommendations |
| |
| | | Appendix C. The Business Rules Group Motivation Model |
| | | Appendix D. The Business Rules Group and David C. Hay Modified Motivation Model |
| | | Glossary |
| | | Bibliography |
| | | Index |