Book description
The complete guide to requirements analysis for every system analyst and project team member.
Thousands of software projects are doomed from the start because they're based on a faulty understanding of the business problem that must be solved. The solution is effective requirements analysis. In Requirements Analysis: From Business Views to Architecture, David C. Hay gives you a comprehensive overview of the world's best requirements analysis practices, organized coherently to help you choose and execute the best approach for every project. In addition, he guides you through the process of defining an architecture—from gaining a full understanding of what business people need to the creation of a complete enterprise architecture.
Practical solutions will help you:
Focus more clearly on the goals of requirements analysis
Represent the fundamental structures and systems environment of any enterprise more accurately
Identify key information processing gaps and discover which information technologies can best address them
Clarify the goals of your new system and reflect them more accurately in your models
Understand crucial people-related issues that impact requirements
Plan smooth transitions to new systems
Requirements Analysis: From Business Views to Architecture provides the complete process of defining an architecture—so that you can build a rock-solid foundation for your next software project.
Table of contents
- Copyright
- Foreword
- Preface
- Introduction
- 1. A Framework for Architecture
-
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
- Step 1: Define Data Models (See Chapter 3)
- Step 2: Define Activity Models (See Chapter 4)
- Step 3: Define Location Models (See Chapter 6)
- Step 4: Define People and Organization Models (See Chapter 5)
- Step 5: Define Event and Timing Models (See Chapter 7)
- Step 6: Define Motivation Models (See Chapter 8)
- Step 7: Present Models
- Step 8: Deliverables: Model Descriptions
-
Process Five: Define What Is Required of a New System
- Step 1: Restate Project Purpose
- Step 2: Identify Key Players
- Step 3: Identify Required Capabilities
- Step 4: Identify Requirement Constraints
- Step 5: Identify Non-functional Requirements
- Step 6: Determine Level of Technology
- Step 7: Identify Capacity Requirements
- Step 8: Decide Whether to Make or Buy
- Step 9: Deliverable: Requirements Statement
- Process Six: Determine the Existing Systems Environment
- Process Seven: Plan for Transition
- Summary
-
3. Column One: Data
- Views of Data
- A Brief History of Data Architecture
- Advanced Data Management—Meta-data
- Graphics—Data Modeling
- Using Entity/Relationship and Object Models
- Normalization
- Data Modeling Conventions
- Entity/Relationship Model Validation
- The Requirements Analysis Deliverable—Column One
- Data and the Other Columns
- Conclusion
-
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 Deliverable—Column Two
- Activities and the Other Columns
- 5. Column Four: People and Organizations
- 6. Column Three: Locations
- 7. Column Five: Timing
-
8. Column Six: Motivation
- Introduction
- Row One: Scope
- Row Two: Business Owners' Views
-
Row Three: Architect's View
- Classes of Rules
- Quality Criteria
-
Rule Descriptions
- Natural Language
- Object Constraint Language
- Ronald Ross Notation
-
Object-Role Modeling (ORM)
- Entity Types, Attributes, and Relationships
- About Constraints
- Mandatory Roles
- Uniqueness
- Objectified Relationships
- Occurrence Frequency
- Derivations
- Value Constraints
- Set Constraints—Subsets
- Set Constraints—Join Subset Constraint
- Set Constraints—Equality
- Set Constraints—Exclusion
- Ring Constraints
- Other Constraints
- Rule Patterns
- Business Rule Patterns—CASEtech, Inc.
- Requirements Analysis Deliverable—Column Six
- Motivation and the Other Columns
- Conclusion
- A. The Zachman Framework
- B. A Comparison of Data Modeling Techniques(Syntactic Conventions)
- C. The Business Rules Group Motivation Model
- D. The Business Rules Group and David C. Hay Modified Motivation Model
- Glossary
- Bibliography
Product information
- Title: Requirements Analysis: From Business Views to Architecture
- Author(s):
- Release date: August 2002
- Publisher(s): Pearson
- ISBN: 9780130282286
You might also like
book
Software Requirements Essentials: Core Practices for Successful Business Analysis
20 Best Practices for Developing and Managing Requirements on Any Project Software Requirements Essentials presents 20 …
book
Patterns of Enterprise Application Architecture
The practice of enterprise application development has benefited from the emergence of many new enabling technologies. …
book
Data Management at Scale, 2nd Edition
As data management continues to evolve rapidly, managing all of your data in a central place, …
book
Data Quality Fundamentals
Do your product dashboards look funky? Are your quarterly reports stale? Is the data set you're …