Determining Project RequirementsOrganizations waste millions of dollars every year on failed projects. Failure is practically guaranteed by poor or incomplete requirements that do not properly define projects in their initial stages.Business analysis is the critical process ensuring projects start on the path toward success. To accurately determine project requirements, busines |
Lietotāju komentāri - Rakstīt atsauksmi
Ierastajās vietās neesam atraduši nevienu atsauksmi.
Saturs
Chapter 1 Introduction | 1 |
Chapter 2 Laying the Foundation | 13 |
Chapter 3 Enterprise Analysis | 31 |
Chapter 4 Creating a Plan for the Requirements Phase | 61 |
Chapter 5 Development Methodologies and Requirements Impact | 89 |
Chapter 6 Categorizing Requirements | 105 |
Chapter 7 Ways to Gather Requirements | 121 |
Chapter 8 Requirements Modeling and Documentation | 179 |
Chapter 11 SwedeMart Case Study | 243 |
Chapter 12 Activity Solutions for SwedeMart Case Study | 249 |
Acronyms | 265 |
Business Requirements Document Templates | 267 |
United Nations Organizational Chart | 287 |
289 | |
291 | |
Back cover | 303 |
Chapter 9 Effective Requirements Communication | 215 |
Chapter 10 Making Sure the Requirements are Implemented | 225 |
Citi izdevumi - Skatīt visu
Bieži izmantoti vārdi un frāzes
activity diagrams analysis phase approach approval Best Practices brainstorming business analyst business process Business Requirements Document business rules buy-in C.V. Green captured Chapter communication constraints cost create customers cycle Data Flow Diagram data model decision defined deliverables detail discussed distribution center drug interaction DSDM effort Enter content enterprise analysis entity environment evaluate example facilitator Figure focus focused functionality gathering requirements goals ideas identify IIBA impact implemented important initial interface interview inventory involved iteration JAD session look ments organization organizational package participants person pharmacist pharmacy PMBOK Prescription Interaction Project prioritization problem project manager prototype questions Rapid Application Development requirements gathering Requirements Plan responsibilities risk role scenarios scope Section skills Software Engineering Institute solution sponsor stakeholder analysis standards storyboard Swede-Mart SWOT analysis template tion Track understand