| This work belongs courses |
< Links courses > |
| Where the job requires |
|
| Team Name |
"You too beautiful machine" Team |
| The target job |
Learning modern software engineering, software teams and individuals the ability to understand, develop good programming habits |
The first job blog links: links .
Questions:
One problem: 2.4 Practice - Design meaningful engineering work - the book say that the software work from the actual software very much worse, except that these jobs require students to master the basic knowledge of programming, but also what should be required?
Answer: Before this course, most of the courses work is programmed exercises, it is to let us master the basic knowledge of programming and some programming specifications. In the later course, I think the opportunity to work is not only a practiced hand, but also allow us to develop an idea of when software programming, software is not just programming, it also includes a number of methods, for example before we complete a project deal with this project to make analysis and judgment, we do not need to program the blind, also have to complete a software program.
Question two: 6.1 agile processes - the book lists 12 principles of agile processes, for so much more suitable in principle when choosing this agile process?
Answer: To be honest, agile processes, I think at the right time is not necessarily fully meet the 12 principles of agile processes, so you can use agile processes while substantially satisfy the principles required.
Question three: 13.2 various test methods - In this section, made many kinds of test methods, then these test methods in addition to the test program bug, whether more testing performance of the program?
Answer: Through this course of study, and the completion of the project team found that not necessarily need to find a program bug during testing, of course, there must be a procedure is robust bug, the test can test the software, reliability etc., you can also test the efficiency of software running these.
Question 4: 15.1 to release from the code - in this section referred to the consultation team concept, but in the programming process has a code review process, whether such consultation team will work extra hours?
Answer: group consultation is not only a review of the code, the summary report can also be the case for the team to be arranged on the back of the process, so the group is different from the code review consultation process, the Panel consultation in a complete software development process is need to exist, it will not delay the work time.
Question 5: 16.1 innovation myth - in the IT industry, when a team is dealing with innovation, how to properly grasp the direction of innovation?
Answer: the need to comply with the development direction of the grasp of the times when the direction of innovation, such as the current big data, information sharing and so on.
to sum up:
This semester, through this course makes me think of software engineering is a certain understanding, development of software engineering is a process, not a meal holding a keyboard operation. In complete software project development process, we need to do to locate our project, analysis, every aspect of each step is we need to try the dedication. In addition, software projects are usually completed by a team of cooperation, so often a team is able to facilitate problem solving. In the team, the team needs to make the division of tasks, everyone has everyone's role and mandate, a person's problems can be solved together in teams. This time through the course benefited me.