tailieunhanh - Chapter08: Extreme programming - Programming practices - Nguyen Thi Thanh Thuy

At its core, XP is: Very Short Cycles Intense Feedback Networked Communication User Stories Release Planning Iteration Planning On Site Customer Pair Programming Test-first Design Refactoring Continuous Integration Collective Ownership Coding Standard 40 hour week. | Extreme Programming Programming Practices Object Mentor, Inc. Portions of this material are Copyright © 2000, by Addison Wesley Longman,Inc. and have been reproduced here with permission. Extreme Programming (XP) At its core, XP is: Very Short Cycles Intense Feedback Networked Communication The XP Planning Practices User Stories Release Planning Iteration Planning On Site Customer XP Programming Practices Pair Programming Test-first Design Refactoring Continuous Integration Collective Ownership Coding Standard 40 hour week XP Programming Practices Pair Programming Test-first Design Refactoring Continuous Integration Collective Ownership Coding Standard 40 hour week Pair Programming Two Programmers sit at one workstation They take turns “driving” Pairs are short lived Pairing transmits knowledge to the team Pairing train newbies Pairing keeps the pace When programming alone, you sometimes find yourself working at super speed. After awhile, you lose focus and . | Extreme Programming Programming Practices Object Mentor, Inc. Portions of this material are Copyright © 2000, by Addison Wesley Longman,Inc. and have been reproduced here with permission. Extreme Programming (XP) At its core, XP is: Very Short Cycles Intense Feedback Networked Communication The XP Planning Practices User Stories Release Planning Iteration Planning On Site Customer XP Programming Practices Pair Programming Test-first Design Refactoring Continuous Integration Collective Ownership Coding Standard 40 hour week XP Programming Practices Pair Programming Test-first Design Refactoring Continuous Integration Collective Ownership Coding Standard 40 hour week Pair Programming Two Programmers sit at one workstation They take turns “driving” Pairs are short lived Pairing transmits knowledge to the team Pairing train newbies Pairing keeps the pace When programming alone, you sometimes find yourself working at super speed. After awhile, you lose focus and drift away in the afterglow. Your partner keeps both from happening. Pair Programming Research Laurie Williams, Findings: Pairs use no more manhours than singles. Pairs create fewer defects. Pairs create fewer lines of code. Pairs enjoy their work more. XP Programming Practices Pair Programming Test-first Design Refactoring Continuous Integration Collective Ownership Coding Standard 40 hour week Test First Design In Tiny (5 min) cycles Write a test case. Write the code that passes it. Repeat until program does what you want. Test First Example import .*; public class TestAutoMileageLog extends TestCase { public TestAutoMileageLog(String name) { super(name); } public void testCreateFuelingStationVisit() { FuelingStationVisit v = new FuelingStationVisit(); } } Test First Example import .*; public class TestAutoMileageLog extends TestCase { public TestAutoMileageLog(String name) { super(name); } public void .

• Cơ sở dữ liệu
• Software Process Models
• Software Process Models
• Dependent on software
• Software engineering
• Extreme programming
• Programming practices
• Công nghệ phần mềm
• Công nghệ thông tin
• Deployment Process
• Process lab
• Analysis Process
• Design Process
• Requirement Process
• Development Process
• Testing Process
• Rational Unified Process Made Easy
• Practitioner’s Guide to RUP
• Lecture Software engineering
• Software process
• Process models
• Process patterns
• Software Processes
• Process activities
• Process iteration
• Bài giảng Kỹ thuật phần mềm
• Process improvement
• Lecture Software process improvement
• Bài giảng Cải tiến quy trình phần mềm
• Software process improvement
• Process standardization
• Kỹ thuật phần mềm
• Problem statement
• Basic requirements
• Software process descriptions
• The waterfall model
• Waterfall model phases
• Lecture Software design
• Software design
• Bài giảng Thiết kế phần mềm
• Agile process models
• Nhập môn Công nghệ phần mềm
• Copingwith change
• Objected oriented
• Classical software engineering
• The scope of software engineering
• Software life cycle models
• The software process
• The tools of the trade
• Planning and estimating
• System models
• Context models
• Logical system models
• Business process models
• State transition diagrams
• Company’s centralized database
• Reliable component base system
• Component software
• Component based development process
• Component models
• Component composition