تحلیل کسب‌وکار، الزامات و مدیریت پروژه: راهنمایی برای دانشجویان کامپیوتر

IT projects emerge from a business need. In practice, software developers must accomplish two big things before an IT project can begin: find out what you need to do (i.e., analyse business requirements) and plan out how to do it (i.e., project management). The biggest problem in IT projects is delivering the wrong product because IT people do not understand what business people require. This practical textbook teaches computer science students how to manage and deliver IT projects by linking business and IT requirements with project management in an incremental and straightforward approach. Business Analysis, Requirements, and Project Management: A Guide for Computing Students presents an approach to analysis management that scales the business perspective. It takes a business process view of a business proposal as a model and explains how to structure a technical problem into a recognisable pattern with problem frames. It shows how to identify core transactions and model them as use cases to create a requirements table useful to designers and coders. Linked to the analysis are three management tools: the product breakdown structure (PBS), the Gantt chart, and the Kanban board. The PBS is derived in part from the problem frame. The Gantt chart emerges from the PBS and ensures the key requirements are addressed by reference to use cases. The Kanban board is especially useful in Task Driven Development, which the text covers. This textbook consists of two interleaving parts and features a single case study. Part one addresses the business and requirements perspective. The second integrates core project management approaches and explains how both requirements and management are connected. The remainder of the book is appendices, the first of which provides solutions to the exercises presented in each chapter. The second appendix puts together much of the documentation for the case study into one place. The case study presents a real-word business scenario to expose students to professional practice. This textbook links business and IT requirements with project management. Designed for computing students, it presents a step-by-step approach, examples, explanations, exercises, and answers. The text gives students what they need to get through requirements and management courses and prepares them for professional practice. Cover 1 Half Title 2 Title Page 4 Copyright Page 5 Table of Contents 6 Introduction 10 Chapter 1: Business Concept Models 20 Why Start Here? 21 The Basics of Business Concept Models 22 Why Bother with Business Concept Models? 22 Business Data or Database Data? 23 Introducing the Case Study 24 Definition of Terms 33 Notes 36 Chapter 2: Business Process Modelling 38 BPMN: A Very Useful Subset for Whilst at University 39 Activities and Pools/Swimlanes – What Happens Where 40 Sending Messages 44 Data and Databases 46 Errors and Cancellations 48 From Concept to Process 52 Case Study: Fizzit in BPMN 52 Notes 58 Chapter 3: Problem Frames 60 Elements of the Problem Frame 60 Making Use of Problem Frames When We Can 63 Multiframe Problem for Google Translate 66 Progression of Problems 70 Deriving Problem Frames from Business Processes 74 Notes 75 Chapter 4: Requirements and Specification 76 More about Requirements 78 Types of Requirements 79 Ways to Gather Requirements 83 Specification of Requirements 87 How to ‘Specify’ a Requirement in 10 Easy Steps 88 Notes 94 Chapter 5: Use Cases 96 Use Case Diagram 97 Elements of the Use Case Diagram 97 The Slight Problem with < > 102 Use Case Descriptions 104 Clerk closes the account 107 Use Case Description Writing Rules 110 Seven Style Rules 110 Two Structure Rules 111 Note 114 Chapter 6: A Brief Discussion of Software Project Management 116 Management and Requirements 118 The Idea 120 What’s the Official Record of Software Projects? 121 What’s the Point of Project Management? 123 Project Management Tools of You 124 But...before We Move On 124 Why Not Just Propose Scrum? 128 Notes 128 Chapter 7: Product Breakdown Structure 130 Basic Process and How to Get It Wrong 130 Example Product Breakdown Structure (PBS) 133 Work or Product? Breakdown Structure 137 A Note on Risk Management 139 Notes 141 Chapter 8: Gantt Chart 142 Feature-Driven Development (FDD) 148 Task-Driven Development? 149 Creating the Gantt Chart 150 Notes 154 Chapter 9: Kanban Boards 156 What the Columns Mean 162 Why Do We Need So Many Columns? 164 Notes 165 Chapter 10: Summary 166 Appendix 1: Solutions 170 Chapter 1. Business Concept Models 170 Chapter 2. BPMN 172 Chapter 3. Problem Frames 175 Chapter 4. Requirements 178 Chapter 5. Use Cases 179 Chapter 7. Product Breakdown Structure 181 Chapter 8. Gantt Chart 182 Chapter 9. Kanban 183 Appendix 2: Fizzit.com Case Study 186 Business Rules 186 Concept Model Diagram 189 Fizzit Definition of Terms 190 Fizzit Business Process Models 192 Drop-Off Location Process 192 Fizzit QA and Payment 193 Problem Frames 194 Drop-Off Location (Workpiece) 195 QA Check (Workpiece) 195 Requirements 196 Requirements Specification Tables 197 Use Cases 202 Use Case Descriptions 203 UC1. Get Price Offer 203 UC2. Conduct Trade 204 UC3. Log Drop-Off 205 UC4. Price Updates 205 UC5. Check Item Quality 206 UC6. Pay Customer 207 UC7. Email Customer 208 UC8. Collect Package 208 UC9: Access Customer Account < > 209 Product Breakdown Structure 210 Gantt Chart 211 Kanban Board 213 Index 216 business,analysis;,business,concept,models;,business,process,modelling;,case,descriptions;,case,descriptions,writing,rules;,case,diagram;,feature-driven,development;,Gantt,chart;,Google,translate;,Kanban,boards;,multiframe,problem;,project,management,tools;,product,breakdown,structure;,pools/swimlanes;,seven,style,rules;,risk,management;,software,project,management;,task-driven,development;,two,structure,styles business analysis,business concept models,business process modelling,case descriptions,case descriptions writing rules,case diagram,feature-driven development,Gantt chart,Google translate,Kanban boards,multiframe problem,project management tools,product breakdown structure,pools/swimlanes,seven style rules,risk management,software project management,task-driven development,two structure styles