Lesson: Java Programming Class: 1351
Name: Wang Wei No.: 20135116
Score: Instructor: Lou Jia Peng Experimental Date: 2015.06.03
Experiment level: Preview degree: Experiment time: 14:00~20:00
Instrument Group: Compulsory/Elective: Elective experiment number: 3
Experiment Name: Agile Development and XP practice
Experimental purposes and 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.). The report can refer to Fan Fei's guidance.
3. Plagiarism is strictly forbidden, and the results of the experiment of the perpetrator are zero, and other punitive measures are added.
Experimental instrument:
Name |
Model |
Number |
Pc |
|
1 |
Virtual machines |
Laboratory Building |
1 |
First, the contents of the experiment:
1. XP Basics
2. XP Core Practice
3. Related Tools
Second, the experimental steps:
(i) 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. It is not enough to have ideas of all kinds of processes, and we have a series of tools to ensure that these ideas can operate efficiently in practice. The important point of software development is not to see how many theories you can make, but also how you apply them to related tools, such as the combination of unit tests in Java and JUnit applications, and modeling to be combined with Umbrello or staruml applications. Programming learning is a process that is learned. A common formula is: Software engineering = development process + Tools Xin Zou Two formulas given by the teacher: SW = program + Software engineering and SW Enterprise = Software + business model development process you can refer to the software team and the development process of learning Xin Zou teacher. The common development processes are:
- RUP (Rational Unified Process)
- PSP (Personal software Process)
- TSP (Team software Process)
- Agile Process
- ......
Agile Development (development) is a human-centric, iterative, and progressive approach to development. "Agile Processes" are a collection of values and methodologies. Since 2001, some experts in the software industry have started advocating "agile" values and processes that affirm the value of popular practices, but emphasize that agile practices can bring value.
Among them, extreme programming (EXtreme PROGRAMMING,XP) is a new and fast software development method. The XP team uses on-site customers, special planning methodologies, and ongoing testing to provide rapid feedback and comprehensive communication:
- 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
XP software development is what is expressed through the XP guidelines:
- Communication: XP believes that communication between project members is key to the success of the project and regards communication as the main driver of coordination and cooperation in the project.
- Simple: XP assumes that the future cannot be reliably predicted, and it is economically unwise to consider it now, so you should not think too much about the future but should focus on the urgent needs.
- Feedback: XP considers the system itself and its code to be a reliable basis for reporting on the progress and status of the system development. The feedback of system development status can be used as a means to determine the progress of system development and determine the next development direction of the system.
- Courage: It represents XP's view that people are one of the most important aspects of software development. In the development of a software product human participation throughout its entire life cycle, is the courage to eliminate the dilemma, let the team to the local optimal left behind, to achieve more significant goals. Demonstrates XP's basic trust in "people make projects successful".
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.
(ii) Coding standards
An important understanding of writing code is that "most of the time the program is for people to see", the programming standard makes the code easier to read and understand, and can even guarantee fewer errors. 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.
In the virtual machine, Eclipse enters the following code:
This code cannot see the hierarchy because there is no basic indentation.
Click Source->format in the Eclipse menu or use the shortcut key ctrl+shift+f to indent the specification as specified by Eclipse, with the following effect:
Java experiment four (to be added)