• Fri frakt över 249 kr
  • •
  • Snabba leveranser
  • •
  • Billiga böcker
Kundservice

Du är på sajten för privatpersoner.

Företag, bibliotek eller offentlig verksamhet?

Du handlar på classic.bokus.com, där alla dina funktioner finns intakta.
Till classic.bokus.com
Bokus logotyp. Gå till startsidan.
  • Erbjudanden
  • Nyheter
  • Student
  • Topplistor
  • Barn & ungdom
  • Bokus Play
  • E-böcker
  • Pocketböcker
  • Spel & pussel

10% rabatt på allt med kod: NYSTART10 →

Sidfot

Mina sidor

    Hjälp

    • Kundservice
    • Vanliga frågor och svar
    • Frakt och leverans
    • Retur vid ångerrätt
    • Reklamera vara
    • Betalning
    • Köpvillkor
    • Allmänna villkor
    • Information om webbplatsens tillgänglighet

    Om Bokus

    • Om oss
    • Pressrum
    • För studenter
    • För företag
    • För bibliotek och offentlig verksamhet
    • För leverantörer
    • Hållbarhet

    Populärt

    • Aktuella erbjudanden
    • Presentkort
    • Studentlitteratur
    • Nya böcker
    • Topplistor
    • Signerade böcker
    • Engelska böcker

    Inspiration

    • Boktips
    • BookTok
    • Populära bokserier
    • Barnbokskaraktärer
    • Populära författare
    Logotyp för Bokus
    Följ oss på Facebook (extern länk)Följ oss på Instagram (extern länk)Följ oss på YouTube (extern länk)Följ oss på TikTok (extern länk)
    bokus @ CookiesAnpassa cookiesIntegritetspolicyKöpvillkor
    Till Citymail hemsida (extern länk)Till Budbee hemsida (extern länk)Till Postnord hemsida (extern länk)Till Schenker hemsida (extern länk)Till Early Bird hemsida (extern länk)Till Walleys hemsida (extern länk)
    1. Data och IT
    2. Programmeringsböcker

    Running an Agile Software Development Project

    AvMike Holcombe

    Inbunden, Engelska, 2008

    1 331 kr

    Beställningsvara. Skickas inom 5-8 vardagar. Fri frakt över 249 kr.

    Fler format och utgåvor

    E-bok

    1 483 kr

    Beskrivning

    A Practical Approach To Building Small To Medium Software Systems For Real Business Clients Based on more than 100 actual commercial projects, this book clearly explains how to run an agile software development project that delivers high-quality, high-value solutions to business clients. It concentrates on the practical, social, business, and management aspects as well as the technical issues involved.Professor Holcombe successfully connects readers with the wave of "Agile 2.0" concepts that take the techniques of agile development and place them in the service of business goals. Since it is widely believed that the use of Windows XP will become much more common in coming years, readers should be armed with cutting-edge knowledge of the latest practices in the field. Further features of the book include: Case studies provide real-world examples and describe how XP was introduced into the environment Analysis is provided to help readers determine which elements of XP are suitable for the unique challenges and environments for different projects Problems of a failing agile project and how they can be fixed are covered, including insight into which managerial techniques can be employed An Instructor's Guide provides practical advice on how to motivate students, organize real group projects, and deal, in a simple and effective way, with many of the problems that arise A sample syllabus, sample tests, and additional case study information are available on an instructor's password-protected ftp site Running an Agile Software Development Project is an indispensable guide for professional software developers, engineers, and project managers interested in learning how to use agile processes. It is also a valuable textbook for advanced undergraduate- and graduate-level students in computer engineering and software engineering courses.

    Produktinformation

    • Utgivningsdatum:2008-11-28
    • Mått:163 x 243 x 22 mm
    • Vikt:585 g
    • Format:Inbunden
    • Språk:Engelska
    • Antal sidor:336
    • Förlag:John Wiley & Sons Inc
    • ISBN:9780470136690

    Utforska kategorier

    • Programmeringsböcker inom Data och IT

    Mer om författaren

    Mike Holcombe, BSC, MSC, PHD, is Professor of Computer Science at the University of Sheffield, UK. He is also founder of Genesys Solutions, which is a student-run commercial software house that is strongly supported by IBM (winning the IBM International Eclipse Innovation Award in 2004 and 2005) and is also designated as a Microsoft Innovation Center. The University of Sheffield has recently "spun out" this company as epiGenesys Ltd. Dr. Holcombe's research interests include software and systems biology. A former dean of the faculty of engineering at the University of Sheffield, he is a Fellow of the British Computer Society and a Fellow of the Institute of Mathematics and Its Applications. He is on the editorial board of the journal BioSystems and Software Testing, Verification and Reliability (Wiley). He is also on the editorial board of the International Journal of Agile and Extreme Software Development and has been appointed to the Academic Advisory Board of Microsoft.

    Innehållsförteckning

    • Preface xi1. What Is an Agile Methodology? 11.1 Rapid Business Change: The Ultimate Driver 11.2 What Must Agile Methodologies be Able to Do? 21.3 Agility: What Is It and How Do We Achieve It? 21.4 Evolving Software: Obstacles and Possibilities 51.5 The Quality Agenda 61.6 Do We Really Need All This Mountain of Documentation? 91.7 The Human Factor 101.8 Some Agile Methodologies 111.8.1 Dynamic Systems Development Method 121.8.2 Feature-Driven Design 131.8.3 Crystal 141.8.4 Agile Modeling 141.8.5 Scrum 151.8.6 Summary Table 151.9 Review 16Exercise 17Conundrum 17References 182. Extreme Programming Outlined 192.1 Some Guiding Principles 192.2 The Five Values 202.2.1 Communication 202.2.2 Feedback 222.2.3 Simplicity 242.2.4 Courage 242.2.5 Respect 252.3 The 12 Basic Practices of XP 252.3.1 Test-First Programming 252.3.2 Pair Programming 262.3.3 On-Site Customer 272.3.4 The Planning Game 282.3.5 System Metaphor 292.3.6 Small, Frequent Releases 302.3.7 Always Use the Simplest Solution That Adds Business Value 302.3.8 Continuous Integration 312.3.9 Coding Standards 322.3.10 Collective Code Ownership 322.3.11 Refactoring 332.3.12 Forty-Hour Week 332.4 Can XP Work? 342.5 The Evidence for XP 352.5.1 Evidence for Test First 352.5.2 Evidence for Pair Programming 362.5.3 Evidence for XP 362.6 Preparing to XP 37Exercise 37Conundrum 38References 393. Foundations: People and Teams Working Together 413.1 Software Engineering in Teams 413.2 Personalities and Team Success 423.3 Observations of Team Behavior in XP Projects 463.4 Setting Up a Team 503.5 Developing Team Skills 523.6 Training Together 543.7 Finding and Keeping a Client for a University-Based Project or a Small Business Start-Up 543.8 The Organizational Framework 563.9 Planning 603.9.1 PERT (Program Evaluation and Review Technique) 613.9.2 Gantt Charts 623.10 Dealing with Problems 653.10.1 Basic Strategies 653.10.2 When Things Go Really Wrong 663.11 Risk Analysis 683.12 Review 69Exercises 69Conundrum 70References 704. Starting an XP Project 734.1 Project Beginnings 734.1.1 Researching the Business Background 744.1.2 Exploring the Outline System Description 764.2 The First Meetings with the Client 794.3 Business Analysis and Problem Discovery 804.4 The Initial Stages of Building a Requirements Document 824.5 Techniques for Requirements Elicitation 844.6 Putting Your Knowledge Together 854.7 Getting Technical 854.8 Developing the Requirements Documents 884.9 Specifying and Measuring the Quality Attributes of the System 914.9.1 Identifying Attributes 924.9.2 Specifying the Acceptable Level of an Attribute 944.9.3 User Characteristics and User Interface Characteristics 954.10 The Formal Requirements Document and System Metaphor 964.10.1 Commentary 1064.11 Contract Negotiation 1084.12 Case Study: The Impact of Organizational Politics 1144.13 Review 116Conundrum 116References 1175. Identifying Stories and Preparing to Build 1195.1 Looking at the User Stories 1195.2 Collections of Stories 1285.2.1 Pharmacovigilance 1295.2.2 Stamps System 1315.2.3 DELTAH (Developing European Leadership Through Action-Learning in Healthcare) 1315.3 User Interfaces 1395.4 Communicating Clearly with the Customer and Building Confidence 1415.5 Demonstrating the Non-Functional Requirements 1435.5.1 Non-Functional Requirements 1435.6 Estimating Resources 1445.6.1 Software Cost Estimation 1455.6.2 Object Point Analysis 1465.6.3 Cosmic Ffp 1475.7 Review 149Exercises 149Conundrum 150References 1516. Bringing the System Together as a Coherent Concept 1536.1 What is the Problem? 1536.2 A Simple Common Metaphor 1566.3 Architectures and Patterns 1596.4 Finite State Machines 1606.5 Extreme Modeling (XM) 1636.6 Multiple Stories and XXMs 1666.7 Building the Architecture to Suit the Application: A Dynamic System Metaphor 1716.8 Another Look at Estimation 1776.9 Review 179Exercise 180Conundrum 180References 1807. Designing the System Tests 1817.1 Preparing to Build Functional Test Sets 1817.1.1 Tests and Testing 1817.1.2 Testing from a Model 1837.1.3 Developing the Model 1877.2 Testing with the Data in Mind 1917.3 The Full Functional System Testing Strategy 1927.4 The Thinking Behind the System Test Process 1937.4.1 An Algorithm for Determining the Transition Cover 1987.5 Design for Test 2017.5.1 Design for Test Principle 1: Controllability 2027.5.2 Design for Test Principle 2: Observability 2027.6 Test Documentation 2037.7 Non-Functional Testing 2057.7.1 Reliability 2067.7.2 Usability 2067.7.3 Efficiency 2077.7.4 Portability 2077.8 Testing Internet Applications and Web Sites 2077.9 Review 209Exercise 210Conundrum 213References 2138. Units and Their Tests 2158.1 Basic Considerations 2158.2 Identifying the Units 2168.3 Unit Testing 2198.4 More Complex Units 2228.4.1 Case Example: The AddElement Function in JHotDraw 2238.5 Automating Unit Tests 2328.5.1 Writing Unit Tests in JUniti 2338.5.2 Managing Tests 2358.6 Documenting Unit Test Results 2358.7 Review 237Exercises 237Conundrum 237References 2389. Evolving the System 2399.1 Requirements Change 2399.2 Changes to Basic Business Model and Functionality 2409.3 Dealing with Change: Refining Stories 2419.3.1 Changes to the Underlying Data Model 2419.3.2 Changes to the Structure of the Interface, Perhaps the Introduction of a New Screen 2429.3.3 Adding a New Function 2429.3.4 Changing the Functionality of a Function 2429.4 Changing the Model 2429.4.1 Changing a Process 2429.4.2 Removing States 2449.4.3 Adding States 2459.4.4 Adding a Complete Machine 2469.4.5 Adding Processes 2469.5 Testing for Changed Requirements 2479.6 Refactoring the Code 2489.7 Estimating the Cost of Change 2499.8 Review 249Exercises 250Conundrum 250Reference 25010. Documenting and Delivering the System 25110.1 What is Documentation for and Who Is Going to Use It? 25110.2 Coding Standards and Documents for Programmers 25210.3 Coding Standards for Java 25310.3.1 Genesys Coding Standard for Java 25310.3.2 Blank Lines 25510.4 Maintenance Documentation 26210.5 User Manuals 26310.6 Version Control 26410.6.1 The Project Archive 26510.6.2 Naming Conventions 26510.7 Delivery and Finalization 26610.8 Review 267Exercises 267Conundrum 267Reference 26711. Reflecting on the Process 26911.1 Skills and Lessons Learned 26911.2 The XP Experience 27011.3 Personal and Team Assessment 27011.4 Review 271Exercises 27111.5 Conundrums: Discussion 27111.6 A Final Word 27712. Lifestyle Matters 28112.1 Keeping Fit 28212.1.1 Correct Sitting Position 28312.1.2 Combating RSI 28412.2 General Well-Being 28512.3 Mental Preparation 28512.4 Diet 28612.4.1 Diet and Brain Function 28612.4.2 Summary of Dietary Information 28712.5 Music and Work 28812.6 Review 289References 290Appendix 291Bibliography 305Index 309