20145307 Third Java Learning Experiment Report

20145307 Java Programming Third Experimental report Beijing Institute of Electronic Technology (BESTI) Experimental report

Course: Java Programming Class: 1453 Instructor: Lou Jia Peng Experimental Date: 2016.04.22 Experiment Name: Agile Development and XP practice

First, the contents of the experiment

XP基础XP核心实践相关工具

Second, the experimental requirements

1. Students who do not have a Linux base are advised to start with the Linux basics (new version) Vim Editor course

2. Complete the experiment, write the experiment Report, the experiment report is published in the blog site blog, note that the experimental report is focused on the results of the operation, problems encountered (tool search, installation, use, program editing, commissioning, operation, etc.), solutions (empty methods such as "Check Network", "Ask classmates", "reading" 0 points) as well as analysis (what can be learned from it, what gains, lessons, etc.).

Third, the experimental steps

Agile Development and XP

Software engineering is the process of applying the systematic, orderly and quantifiable methods to the development, operation and maintenance of the softwares. Software engineering covers the following areas: Software requirements analysis, software design, software construction, software testing and software maintenance. People have many technologies, practices, habits and ideologies in the process of developing, operating, and maintaining software. Software engineering unifies these related technologies and processes into one system, called the "development process". The purpose of the software development process is to improve the efficiency of software development, operation and maintenance, and improve the quality of software, customer satisfaction, reliability and maintainability of software.

A common formula is: Software engineering = development process + tools.

Agile Process Development includes many modes:

Extreme Programming (EXtreme PROGRAMMING,XP)

XP is a methodology developed to target software that meets customer needs

XP is a practice-based software engineering process and thought

XP believes that code quality is more important than people generally think.

XP is ideal for small, responsible, self-motivated teams to develop software that requires uncertainty or rapid change

A testing-centric development process

The basis for successful use of a practice in an XP environment is presented through the rules of XP, including: Quick feedback, hypothesis simplicity, incremental changes, advocating for change, and quality of work.

XP software development is the cornerstone of XP activities, including: coding, testing, listening, design.

The technology for project member users to successfully execute XP activities is presented through XP practices, including 12 practices related to programming, teamwork, and process.

Second, the coding standard

Programming standards include: Descriptive names, clear expressions, straightforward control flow, readable code and annotations, and the importance of consistently using certain rules and idioms when pursuing these content.

Three, pair programming

There are two roles in pairing programming:

The driver (Driver) is the person who controls the keyboard input. The Navigator (Navigator) plays the role of pilotage and reminding.

How to pair programming, why to pair programming, we refer to pair programming and two people cooperation, the focus is:

Drivers: Write design documents, conduct coding and unit tests, and other XP development processes.

Navigator: Review the driver's documentation, the driver's implementation of the development process such as coding, consider the coverage of unit tests, think about the need for and how to refactor, and help drivers solve specific technical problems.

Drivers and pilots constantly rotate their roles and do not work for more than an hour, and take 15 minutes off each hour of work. The navigator has to control the time.

Active participation. Any task is the responsibility of the two people, and the responsibility of all. There is no "My Code", "Your Code" or "his/her code", only "our code".

There are only horizontal gaps, and there is no level difference. They are pairs, and although they may have different levels of seniority, both sides have equal decision-making rights in terms of analysis, design, or coding.

Iv. Division of Labor

Member: 20145335 http://www.cnblogs.com/20145335hh/

Division of Labor: I download the modified and then upload, reflecting the refactoring of at least five features.

Five, reconstruction

Refactoring (refactor) is to change the structure within the software without changing the external behavior of the software, making it easier to read, easy to maintain, and easy to change.

A complete refactoring process consists of:

Check out code from the version control system library

Read code (including test code)

Find Bad smell

Refactoring

Run all the unit Tests

Check in code to codebase

20145307 Third Java Learning Experiment report