Info
- Utilizzare la checkbox di selezione a fianco di ciascun documento per attivare le funzionalità di stampa, invio email, download nei formati disponibili del (i) record.
Agile processes in software engineering and extreme programming : 23rd International Conference on Agile Software Development, XP 2022, Copenhagen, Denmark, June 13-17, 2022, Proceedings / / editors, Viktoria Stray[et al.]
| Agile processes in software engineering and extreme programming : 23rd International Conference on Agile Software Development, XP 2022, Copenhagen, Denmark, June 13-17, 2022, Proceedings / / editors, Viktoria Stray[et al.] |
| Autore | Stray Viktoria |
| Pubbl/distr/stampa | Cham, : Springer Nature, 2022 |
| Descrizione fisica | 1 online resource (x, 237 pages) : illustrations (some color) |
| Altri autori (Persone) |
StrayViktoria
StolKlaas-Jan PaasivaaraMaria KruchtenPhilippe |
| Collana | Lecture notes in business information processing |
| Soggetto topico |
Agile software development
eXtreme programming |
| Soggetto non controllato |
agile software development
software creation and management Scrum lean software development process management test-driven development project and people management software development techniques risk management empirical software engineering software measurement |
| ISBN | 3-031-08169-2 |
| Formato | Materiale a stampa  |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto | Agile Practices From Collaboration to Solitude and Back: Experiences with Remote Pair Programming during COVID-19 UX Work in Software Start-ups: Challenges from the Current State of Practice How to Write Ethical User Stories? Impacts of the ECCOLA Method Process Assessment Setting the Scope for a New Agile Assessment Model: Results of an Empirical Study Towards a Standardized Questionnaire for Measuring Agility at Team Level The Impact of Agile Transformations on Organizational Performance: A Survey of Teams, Programs and Portfolios Measuring Software Delivery Performance using the Four Key Metrics of DevOps Large-scale Agile Evolution of the Agile Scaling Frameworks Coordination Strategies: Managing Inter-team Coordination Challenges in Large-scale Agile Challenges of Adopting SAFe in the Banking Industry - A Study Two Years after its Introduction Benefits and Challenges of Adopting SAFe - An Empirical Survey.-Short Contributions Using a Low Code Development Environment to Teach the Agile Methodology Comparing Participants' Brainwaves during Solo, Pair, and Mob Programming |
| Record Nr. | UNINA-9910574858903321 |
Stray Viktoria
|
||
| Cham, : Springer Nature, 2022 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Agile processes in software engineering and extreme programming : 23rd International Conference on Agile Software Development, XP 2022, Copenhagen, Denmark, June 13-17, 2022, Proceedings / / editors, Viktoria Stray[et al.]
| Agile processes in software engineering and extreme programming : 23rd International Conference on Agile Software Development, XP 2022, Copenhagen, Denmark, June 13-17, 2022, Proceedings / / editors, Viktoria Stray[et al.] |
| Autore | Stray Viktoria |
| Pubbl/distr/stampa | Cham, : Springer Nature, 2022 |
| Descrizione fisica | 1 online resource (x, 237 pages) : illustrations (some color) |
| Altri autori (Persone) |
StrayViktoria
StolKlaas-Jan PaasivaaraMaria KruchtenPhilippe |
| Collana | Lecture notes in business information processing |
| Soggetto topico |
Agile software development
eXtreme programming |
| Soggetto non controllato |
agile software development
software creation and management Scrum lean software development process management test-driven development project and people management software development techniques risk management empirical software engineering software measurement |
| ISBN | 3-031-08169-2 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto | Agile Practices From Collaboration to Solitude and Back: Experiences with Remote Pair Programming during COVID-19 UX Work in Software Start-ups: Challenges from the Current State of Practice How to Write Ethical User Stories? Impacts of the ECCOLA Method Process Assessment Setting the Scope for a New Agile Assessment Model: Results of an Empirical Study Towards a Standardized Questionnaire for Measuring Agility at Team Level The Impact of Agile Transformations on Organizational Performance: A Survey of Teams, Programs and Portfolios Measuring Software Delivery Performance using the Four Key Metrics of DevOps Large-scale Agile Evolution of the Agile Scaling Frameworks Coordination Strategies: Managing Inter-team Coordination Challenges in Large-scale Agile Challenges of Adopting SAFe in the Banking Industry - A Study Two Years after its Introduction Benefits and Challenges of Adopting SAFe - An Empirical Survey.-Short Contributions Using a Low Code Development Environment to Teach the Agile Methodology Comparing Participants' Brainwaves during Solo, Pair, and Mob Programming |
| Record Nr. | UNISA-996478861103316 |
|
Stray Viktoria
|
||
| Cham, : Springer Nature, 2022 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. di Salerno | ||
| ||
Professional Java tools for extreme programming [[electronic resource] ] : Ant, Xdoclet, JUnit, Cactus, and Maven / / Richard Hightower ... [et al.]
| Professional Java tools for extreme programming [[electronic resource] ] : Ant, Xdoclet, JUnit, Cactus, and Maven / / Richard Hightower ... [et al.] |
| Pubbl/distr/stampa | Indianapolis, IN, : Wiley, c2004 |
| Descrizione fisica | 1 online resource (769 p.) |
| Disciplina | 005.13/3 |
| Altri autori (Persone) | HightowerRichard |
| Soggetto topico |
Java (Computer program language)
eXtreme programming Open source software |
| Soggetto genere / forma | Electronic books. |
| ISBN |
1-280-35014-8
9786610350148 0-7645-7274-1 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Professional Java Tools for Extreme Programming; Credits; About the Authors; Contents; Introduction; Why Spend So Much Time on the Tools?; Who Should Read this Book; Why Open Source?; Automated Testing: A Summary; Continuous Integration: A Summary; How This Book Is Organized; What's on the Web Site; Chapter 1: Introduction to Extreme Programming; XP Overview; Adopting XP?; Summary; Chapter 2: J2EE Deployment Concepts; The JAR File; Web Applications and the WAR File; Enterprise Beans and the EJB JAR File; Enterprise Applications and the EAR File; Conclusion
Chapter 3: Storing and Managing Code with CVSThe Benefits of Versioning; About CVS; CVS Foundations; Setting Up CVS on the Server; CVS Pitfalls and Solutions; Chapter 4: Ant Primer; Standard Targets; Chapter 5: Building Java Applications with Ant; Hello World Recap; Conclusion; Chapter 6: Building J2EE Applications with Ant; The Pet Store Case Study; Summary; Chapter 7: XDoclet Primer; What Is XDoclet?; Code Generation Templating; Installing XDoclet; Configure Ant; A Simple Example; XDoclet Tasks, Subtasks, and Templates; XDoclet Merging; Summary Chapter 8: Building J2EE Web Components with Ant and XDocletServlet Example; Webdoclet Tags; Using Ant for the Configuration; Using Ant Properties, Init-Params, and Filtering; Creating Taglibs; Using Eclipse with Webdoclet; Summary; Chapter 9: Building EJBs with Ant and XDoclet; Generating XDoclet EJBs; Summary; Chapter 10: Building Struts Apps with Ant and XDoclet; Brief Introduction to Struts; Installing Struts; A Sample Application; Struts and XDoclet; Summary; Chapter 11: Creating Custom Ant Tasks; How Ant Works; An Example Task; A Skeleton Task Example; Building a New Task Using the New TaskSummary; Chapter 12: Creating XDoclet Custom Tags and Templates; XDoclet Architecture; A Simple Template; Building an XDoclet Template; Summary; Chapter 13: Unit Testing with JUnit; Case Study: Adding an Entity Bean to the Pet Store; Summary; Chapter 14: Load Testing with JUnitPerf; JUnitPerf Concepts; TimedTest Example; LoadTest Example; Summary; Chapter 15: Defect Tracking with Bugzilla; Enter Bugzilla; Bugzilla Setup; Bugs in Bugzilla; Security; Summary; Chapter 16: Functional Testing with HttpUnit; Why Functional Testing?; Why HttpUnit?; HttpUnit Basics Advanced Topics in HttpUnitSpider Example; Summary; Chapter 17: Performance Testing with JMeter; Overview of JMeter; JMeter Concepts; Using JMeter to Test a Web Application Navigation; Using JMeter to Test the Web Application's Form Entry; Using JMeter to Test Performance of Our RDBMS; Case Study: The Pet Store; Summary; Chapter 18: Cactus Primer; Why In-Container Testing?; Why Cactus?; Installing Cactus; Cactus Architecture; Cactus with Ant; Summary; Chapter 19: Testing Servlets and Filters with Cactus; Testing Servlets; Testing Filters; Summary Chapter 20: JspTestCases and Testing Custom Tags with Cactus |
| Record Nr. | UNINA-9910456416703321 |
| Indianapolis, IN, : Wiley, c2004 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Professional Java tools for extreme programming [[electronic resource] ] : Ant, Xdoclet, JUnit, Cactus, and Maven / / Richard Hightower ... [et al.]
| Professional Java tools for extreme programming [[electronic resource] ] : Ant, Xdoclet, JUnit, Cactus, and Maven / / Richard Hightower ... [et al.] |
| Pubbl/distr/stampa | Indianapolis, IN, : Wiley, c2004 |
| Descrizione fisica | 1 online resource (769 p.) |
| Disciplina | 005.13/3 |
| Altri autori (Persone) | HightowerRichard |
| Soggetto topico |
Java (Computer program language)
eXtreme programming Open source software |
| ISBN |
1-280-35014-8
9786610350148 0-7645-7274-1 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Professional Java Tools for Extreme Programming; Credits; About the Authors; Contents; Introduction; Why Spend So Much Time on the Tools?; Who Should Read this Book; Why Open Source?; Automated Testing: A Summary; Continuous Integration: A Summary; How This Book Is Organized; What's on the Web Site; Chapter 1: Introduction to Extreme Programming; XP Overview; Adopting XP?; Summary; Chapter 2: J2EE Deployment Concepts; The JAR File; Web Applications and the WAR File; Enterprise Beans and the EJB JAR File; Enterprise Applications and the EAR File; Conclusion
Chapter 3: Storing and Managing Code with CVSThe Benefits of Versioning; About CVS; CVS Foundations; Setting Up CVS on the Server; CVS Pitfalls and Solutions; Chapter 4: Ant Primer; Standard Targets; Chapter 5: Building Java Applications with Ant; Hello World Recap; Conclusion; Chapter 6: Building J2EE Applications with Ant; The Pet Store Case Study; Summary; Chapter 7: XDoclet Primer; What Is XDoclet?; Code Generation Templating; Installing XDoclet; Configure Ant; A Simple Example; XDoclet Tasks, Subtasks, and Templates; XDoclet Merging; Summary Chapter 8: Building J2EE Web Components with Ant and XDocletServlet Example; Webdoclet Tags; Using Ant for the Configuration; Using Ant Properties, Init-Params, and Filtering; Creating Taglibs; Using Eclipse with Webdoclet; Summary; Chapter 9: Building EJBs with Ant and XDoclet; Generating XDoclet EJBs; Summary; Chapter 10: Building Struts Apps with Ant and XDoclet; Brief Introduction to Struts; Installing Struts; A Sample Application; Struts and XDoclet; Summary; Chapter 11: Creating Custom Ant Tasks; How Ant Works; An Example Task; A Skeleton Task Example; Building a New Task Using the New TaskSummary; Chapter 12: Creating XDoclet Custom Tags and Templates; XDoclet Architecture; A Simple Template; Building an XDoclet Template; Summary; Chapter 13: Unit Testing with JUnit; Case Study: Adding an Entity Bean to the Pet Store; Summary; Chapter 14: Load Testing with JUnitPerf; JUnitPerf Concepts; TimedTest Example; LoadTest Example; Summary; Chapter 15: Defect Tracking with Bugzilla; Enter Bugzilla; Bugzilla Setup; Bugs in Bugzilla; Security; Summary; Chapter 16: Functional Testing with HttpUnit; Why Functional Testing?; Why HttpUnit?; HttpUnit Basics Advanced Topics in HttpUnitSpider Example; Summary; Chapter 17: Performance Testing with JMeter; Overview of JMeter; JMeter Concepts; Using JMeter to Test a Web Application Navigation; Using JMeter to Test the Web Application's Form Entry; Using JMeter to Test Performance of Our RDBMS; Case Study: The Pet Store; Summary; Chapter 18: Cactus Primer; Why In-Container Testing?; Why Cactus?; Installing Cactus; Cactus Architecture; Cactus with Ant; Summary; Chapter 19: Testing Servlets and Filters with Cactus; Testing Servlets; Testing Filters; Summary Chapter 20: JspTestCases and Testing Custom Tags with Cactus |
| Record Nr. | UNINA-9910780457503321 |
| Indianapolis, IN, : Wiley, c2004 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Professional Java tools for extreme programming [[electronic resource] ] : Ant, Xdoclet, JUnit, Cactus, and Maven / / Richard Hightower ... [et al.]
| Professional Java tools for extreme programming [[electronic resource] ] : Ant, Xdoclet, JUnit, Cactus, and Maven / / Richard Hightower ... [et al.] |
| Edizione | [1st ed.] |
| Pubbl/distr/stampa | Indianapolis, IN, : Wiley, c2004 |
| Descrizione fisica | 1 online resource (769 p.) |
| Disciplina | 005.13/3 |
| Altri autori (Persone) | HightowerRichard |
| Soggetto topico |
Java (Computer program language)
eXtreme programming Open source software |
| ISBN |
1-280-35014-8
9786610350148 0-7645-7274-1 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Professional Java Tools for Extreme Programming; Credits; About the Authors; Contents; Introduction; Why Spend So Much Time on the Tools?; Who Should Read this Book; Why Open Source?; Automated Testing: A Summary; Continuous Integration: A Summary; How This Book Is Organized; What's on the Web Site; Chapter 1: Introduction to Extreme Programming; XP Overview; Adopting XP?; Summary; Chapter 2: J2EE Deployment Concepts; The JAR File; Web Applications and the WAR File; Enterprise Beans and the EJB JAR File; Enterprise Applications and the EAR File; Conclusion
Chapter 3: Storing and Managing Code with CVSThe Benefits of Versioning; About CVS; CVS Foundations; Setting Up CVS on the Server; CVS Pitfalls and Solutions; Chapter 4: Ant Primer; Standard Targets; Chapter 5: Building Java Applications with Ant; Hello World Recap; Conclusion; Chapter 6: Building J2EE Applications with Ant; The Pet Store Case Study; Summary; Chapter 7: XDoclet Primer; What Is XDoclet?; Code Generation Templating; Installing XDoclet; Configure Ant; A Simple Example; XDoclet Tasks, Subtasks, and Templates; XDoclet Merging; Summary Chapter 8: Building J2EE Web Components with Ant and XDocletServlet Example; Webdoclet Tags; Using Ant for the Configuration; Using Ant Properties, Init-Params, and Filtering; Creating Taglibs; Using Eclipse with Webdoclet; Summary; Chapter 9: Building EJBs with Ant and XDoclet; Generating XDoclet EJBs; Summary; Chapter 10: Building Struts Apps with Ant and XDoclet; Brief Introduction to Struts; Installing Struts; A Sample Application; Struts and XDoclet; Summary; Chapter 11: Creating Custom Ant Tasks; How Ant Works; An Example Task; A Skeleton Task Example; Building a New Task Using the New TaskSummary; Chapter 12: Creating XDoclet Custom Tags and Templates; XDoclet Architecture; A Simple Template; Building an XDoclet Template; Summary; Chapter 13: Unit Testing with JUnit; Case Study: Adding an Entity Bean to the Pet Store; Summary; Chapter 14: Load Testing with JUnitPerf; JUnitPerf Concepts; TimedTest Example; LoadTest Example; Summary; Chapter 15: Defect Tracking with Bugzilla; Enter Bugzilla; Bugzilla Setup; Bugs in Bugzilla; Security; Summary; Chapter 16: Functional Testing with HttpUnit; Why Functional Testing?; Why HttpUnit?; HttpUnit Basics Advanced Topics in HttpUnitSpider Example; Summary; Chapter 17: Performance Testing with JMeter; Overview of JMeter; JMeter Concepts; Using JMeter to Test a Web Application Navigation; Using JMeter to Test the Web Application's Form Entry; Using JMeter to Test Performance of Our RDBMS; Case Study: The Pet Store; Summary; Chapter 18: Cactus Primer; Why In-Container Testing?; Why Cactus?; Installing Cactus; Cactus Architecture; Cactus with Ant; Summary; Chapter 19: Testing Servlets and Filters with Cactus; Testing Servlets; Testing Filters; Summary Chapter 20: JspTestCases and Testing Custom Tags with Cactus |
| Record Nr. | UNINA-9910828240103321 |
| Indianapolis, IN, : Wiley, c2004 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Running an agile software development project [[electronic resource] /] / Mike Holcombe
| Running an agile software development project [[electronic resource] /] / Mike Holcombe |
| Autore | Holcombe W. M. L (William Michael Lloyd), <1944-> |
| Pubbl/distr/stampa | Hoboken, N.J., : Wiley, c2008 |
| Descrizione fisica | 1 online resource (328 p.) |
| Disciplina |
005.1/1
005.11 |
| Soggetto topico |
Computer software - Development
Agile software development eXtreme programming |
| ISBN |
1-282-13692-5
9786612136924 0-470-38588-X 0-470-38587-1 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Running an Agile Software Development Project; Contents; Preface; 1. What Is an Agile Methodology?; 1.1 Rapid Business Change: The Ultimate Driver; 1.2 What Must Agile Methodologies be Able to Do?; 1.3 Agility: What Is It and How Do We Achieve It?; 1.4 Evolving Software: Obstacles and Possibilities; 1.5 The Quality Agenda; 1.6 Do We Really Need All This Mountain of Documentation?; 1.7 The Human Factor; 1.8 Some Agile Methodologies; 1.8.1 Dynamic Systems Development Method; 1.8.2 Feature-Driven Design; 1.8.3 Crystal; 1.8.4 Agile Modeling; 1.8.5 SCRUM; 1.8.6 Summary Table; 1.9 Review; Exercise
ConundrumReferences; 2. Extreme Programming Outlined; 2.1 Some Guiding Principles; 2.2 The Five Values; 2.2.1 Communication; 2.2.2 Feedback; 2.2.3 Simplicity; 2.2.4 Courage; 2.2.5 Respect; 2.3 The 12 Basic Practices of XP; 2.3.1 Test-First Programming; 2.3.2 Pair Programming; 2.3.3 On-Site Customer; 2.3.4 The Planning Game; 2.3.5 System Metaphor; 2.3.6 Small, Frequent Releases; 2.3.7 Always Use the Simplest Solution That Adds Business Value; 2.3.8 Continuous Integration; 2.3.9 Coding Standards; 2.3.10 Collective Code Ownership; 2.3.11 Refactoring; 2.3.12 Forty-Hour Week; 2.4 Can XP Work? 2.5 The Evidence for XP2.5.1 Evidence for Test First; 2.5.2 Evidence for Pair Programming; 2.5.3 Evidence for XP; 2.6 Preparing to XP; Exercise; Conundrum; References; 3. Foundations: People and Teams Working Together; 3.1 Software Engineering in Teams; 3.2 Personalities and Team Success; 3.3 Observations of Team Behavior in XP Projects; 3.4 Setting Up a Team; 3.5 Developing Team Skills; 3.6 Training Together; 3.7 Finding and Keeping a Client for a University-Based Project or a Small Business Start-Up; 3.8 The Organizational Framework; 3.9 Planning 3.9.1 PERT (Program Evaluation and Review Technique)3.9.2 Gantt Charts; 3.10 Dealing with Problems; 3.10.1 Basic Strategies; 3.10.2 When Things Go Really Wrong; 3.11 Risk Analysis; 3.12 Review; Exercises; Conundrum; References; 4. Starting an XP Project; 4.1 Project Beginnings; 4.1.1 Researching the Business Background; 4.1.2 Exploring the Outline System Description; 4.2 The First Meetings with the Client; 4.3 Business Analysis and Problem Discovery; 4.4 The Initial Stages of Building a Requirements Document; 4.5 Techniques for Requirements Elicitation; 4.6 Putting Your Knowledge Together 4.7 Getting Technical4.8 Developing the Requirements Documents; 4.9 Specifying and Measuring the Quality Attributes of the System; 4.9.1 Identifying Attributes; 4.9.2 Specifying the Acceptable Level of an Attribute; 4.9.3 User Characteristics and User Interface Characteristics; 4.10 The Formal Requirements Document and System Metaphor; 4.10.1 Commentary; 4.11 Contract Negotiation; 4.12 Case Study: The Impact of Organizational Politics; 4.13 Review; Conundrum; References; 5. Identifying Stories and Preparing to Build; 5.1 Looking at the User Stories; 5.2 Collections of Stories 5.2.1 Pharmacovigilance |
| Record Nr. | UNINA-9910144432303321 |
|
Holcombe W. M. L (William Michael Lloyd), <1944->
|
||
| Hoboken, N.J., : Wiley, c2008 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Running an agile software development project [[electronic resource] /] / Mike Holcombe
| Running an agile software development project [[electronic resource] /] / Mike Holcombe |
| Autore | Holcombe W. M. L (William Michael Lloyd), <1944-> |
| Pubbl/distr/stampa | Hoboken, N.J., : Wiley, c2008 |
| Descrizione fisica | 1 online resource (328 p.) |
| Disciplina |
005.1/1
005.11 |
| Soggetto topico |
Computer software - Development
Agile software development eXtreme programming |
| ISBN |
1-282-13692-5
9786612136924 0-470-38588-X 0-470-38587-1 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Running an Agile Software Development Project; Contents; Preface; 1. What Is an Agile Methodology?; 1.1 Rapid Business Change: The Ultimate Driver; 1.2 What Must Agile Methodologies be Able to Do?; 1.3 Agility: What Is It and How Do We Achieve It?; 1.4 Evolving Software: Obstacles and Possibilities; 1.5 The Quality Agenda; 1.6 Do We Really Need All This Mountain of Documentation?; 1.7 The Human Factor; 1.8 Some Agile Methodologies; 1.8.1 Dynamic Systems Development Method; 1.8.2 Feature-Driven Design; 1.8.3 Crystal; 1.8.4 Agile Modeling; 1.8.5 SCRUM; 1.8.6 Summary Table; 1.9 Review; Exercise
ConundrumReferences; 2. Extreme Programming Outlined; 2.1 Some Guiding Principles; 2.2 The Five Values; 2.2.1 Communication; 2.2.2 Feedback; 2.2.3 Simplicity; 2.2.4 Courage; 2.2.5 Respect; 2.3 The 12 Basic Practices of XP; 2.3.1 Test-First Programming; 2.3.2 Pair Programming; 2.3.3 On-Site Customer; 2.3.4 The Planning Game; 2.3.5 System Metaphor; 2.3.6 Small, Frequent Releases; 2.3.7 Always Use the Simplest Solution That Adds Business Value; 2.3.8 Continuous Integration; 2.3.9 Coding Standards; 2.3.10 Collective Code Ownership; 2.3.11 Refactoring; 2.3.12 Forty-Hour Week; 2.4 Can XP Work? 2.5 The Evidence for XP2.5.1 Evidence for Test First; 2.5.2 Evidence for Pair Programming; 2.5.3 Evidence for XP; 2.6 Preparing to XP; Exercise; Conundrum; References; 3. Foundations: People and Teams Working Together; 3.1 Software Engineering in Teams; 3.2 Personalities and Team Success; 3.3 Observations of Team Behavior in XP Projects; 3.4 Setting Up a Team; 3.5 Developing Team Skills; 3.6 Training Together; 3.7 Finding and Keeping a Client for a University-Based Project or a Small Business Start-Up; 3.8 The Organizational Framework; 3.9 Planning 3.9.1 PERT (Program Evaluation and Review Technique)3.9.2 Gantt Charts; 3.10 Dealing with Problems; 3.10.1 Basic Strategies; 3.10.2 When Things Go Really Wrong; 3.11 Risk Analysis; 3.12 Review; Exercises; Conundrum; References; 4. Starting an XP Project; 4.1 Project Beginnings; 4.1.1 Researching the Business Background; 4.1.2 Exploring the Outline System Description; 4.2 The First Meetings with the Client; 4.3 Business Analysis and Problem Discovery; 4.4 The Initial Stages of Building a Requirements Document; 4.5 Techniques for Requirements Elicitation; 4.6 Putting Your Knowledge Together 4.7 Getting Technical4.8 Developing the Requirements Documents; 4.9 Specifying and Measuring the Quality Attributes of the System; 4.9.1 Identifying Attributes; 4.9.2 Specifying the Acceptable Level of an Attribute; 4.9.3 User Characteristics and User Interface Characteristics; 4.10 The Formal Requirements Document and System Metaphor; 4.10.1 Commentary; 4.11 Contract Negotiation; 4.12 Case Study: The Impact of Organizational Politics; 4.13 Review; Conundrum; References; 5. Identifying Stories and Preparing to Build; 5.1 Looking at the User Stories; 5.2 Collections of Stories 5.2.1 Pharmacovigilance |
| Record Nr. | UNINA-9910818861003321 |
|
Holcombe W. M. L (William Michael Lloyd), <1944->
|
||
| Hoboken, N.J., : Wiley, c2008 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Swing extreme testing [[electronic resource] ] : the extreme approach to complete Java application testing / / Tim Lavers, Lindsay Peters
| Swing extreme testing [[electronic resource] ] : the extreme approach to complete Java application testing / / Tim Lavers, Lindsay Peters |
| Autore | Lavers Tim |
| Edizione | [1st edition] |
| Pubbl/distr/stampa | Birmingham, U.K., : Packt Publishing Ltd., 2008 |
| Descrizione fisica | 1 online resource (328 p.) |
| Disciplina | 005.1/4 |
| Altri autori (Persone) | PetersLindsay |
| Collana | From technologies to solutions |
| Soggetto topico |
Computer software - Testing
eXtreme programming Java (Computer program language) |
| Soggetto genere / forma | Electronic books. |
| ISBN | 1-84719-483-4 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Cover; Table of Contents; Preface; Chapter 1: What Needs Testing?; An Example; What Classes Do We Test?; Test First-Always!; What Classes Don't We Test?; What Methods Need Testing?; What Methods Don't We Test?; Invoking Hidden Methods and Constructors; Unit Test Coverage; Who Should Implement the Unit Tests?; What About Legacy Code?; Where Does Integration Testing Fit In?; Documentation of Unit Tests; Testing at the Application Level; Who Should Implement the Function Tests?; Automated Test Execution; A Hierarchy of Tests; What Language Should Our Tests Be In?; Is it Really Possible?; Summary
Chapter 2: Basics of Unit TestingA Simple Example; The Default Implementation; Test Cases; Design by Contract and Non-Defensive Programming; Test Code Example; Bootstrapping Our Implementation; Load Testing; Summary; Chapter 3: Infrastructure for Testing; Where Should the Unit Tests Go?; Where Should the Function and Load Tests Go?; Management of Test Data; What Do We Require of a Test Data Management System?; Temporary Files; Summary; Chapter 4: Cyborg-a Better Robot; The Design of Cyborg; Using the Keyboard; Mousing Around; Checking the Screen; Summary Chapter 5: Managing and Testing User MessagesSome Problems with Resource Bundles; A Solution; The UserStrings Class; ResourcesTester; How ResourcesTester Works; Getting More from UserStrings; Summary; Chapter 6: Making Classes Testable with Interfaces; The LabWizard Comment Editor; The Wizard; A Test for Wizard; A Test for Step; Handlers in LabWizard; Summary; Chapter 7: Exercising UI Components in Tests; The LabWizard Login Screen; The Design of LoginScreen; UI Wrappers; The Correct Implementation of UILoginScreen; A Handler Implementation for Unit Testing; Setting Up our Tests Our First TestFurther Tests; Some Implicit Tests; Other User Interfaces; Summary; Chapter 8: Showing, Finding, and Reading Swing Components; Setting Up User Interface Components in a Thread-Safe Manner; Finding a Component; Testing Whether a Message is Showing; Searching for Components by Name; Reading the State of a Component; Case Study: Testing Whether an Action Can Be Cancelled; The Official Word on Swing Threading; Summary; Chapter 9: Case Study: Testing a 'Save as' Dialog; The Ikon Do It 'Save as' Dialog; Outline of the Unit Test; UI Helper Methods; Dialogs Getting the Text of a Text FieldFrame Disposal; Unit Test Infrastructure; The UISaveAsDialog Class; The ShowerThread Class; The init() Method; The cleanup() Method; The Unit Tests; The Constructor Test; The wasCancelled() Test; The name() Test; The show() Test; The Data Validation Test; The Usability Test; Summary; Chapter 10: More Techniques for Testing Swing Components; Testing with JColorChooser; Using JFileChooser; Checking that a JFileChooser has been Set Up Correctly; Testing the Appearance of a JComponent; Testing with Frames; Frame Location; Frame Size; Testing with Lists List Selection Methods |
| Record Nr. | UNINA-9910456617703321 |
|
Lavers Tim
|
||
| Birmingham, U.K., : Packt Publishing Ltd., 2008 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
