000			02889nam a22001937a 4500
999			_c4580 _d4580
005			20230118160238.0
008			230118b ||||| |||| 00| 0 eng d
020			_a9780367766849
082			_a005.1 _bCOX
100			_aCox, Karl _910607
245			_aBusiness analysis, requirements, and project management: _ba guide for computing students
260			_bCRC Press _aLondon _c2022
300			_axviii, 200 p.
365			_aGBP _b44.99
504			_aTable of Contents 1. Business Concept Models 2. Business Process Modelling 3. Problem Frames 4. Requirements and Specification 5. Use Cases 6. A Brief Discussion of Software Project Management 7. Product Breakdown Structures 8. Gantt Charts 9. Kanban Boards 10. Summary A. Solutions B. Fizzit Case Study
520			_aIT 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.
650			_aAgile software development _97252
942			_2ddc _cBK