Assignment nine: A summary of the software engineering course

First, the answer to the questions raised earlier

1. How to learn software engineering in the case of weak foundation courses?

In the study of software engineering, the code and the first course are not the most important. Because in the process of developing the software, the amount of code is less than 30% of the total amount of work, the management and maintenance of the latter account for more than 60% to 80%. Software Engineering course is to learn the idea and process of development, as for the first curriculum Foundation is weak or not good at code this problem, we can learn the accumulation of little bit, slowly make up. Code is just a small process of developing software for this vast project.

2. The main learning style of our course is " doing high school ", emphasizing the importance of practice, but we all know that before this course is reformed, We learn the final assessment of the Software engineering course is a theoretical written examination, and some test centers are relatively lagging behind and we do not use in the actual operation, then these theories in our study still need to master it?

Theory can guide practice, practice can test the theory, the combination of theory and practice is the best way to learn. Although this semester's soft-work class learning method is "doing high school", emphasis on practice. But in practice, a strong theoretical support is also needed.

3. Users and developers look at the software angle is different, then the book written in the " good enough " software more focused on who the eyes of the " good enough "?

I think, "Good enough" is "good enough" in both eyes. First of all, developers believe that this software has been more mature, more perfect function, maintainability is strong ... In the eyes of developers, it has been "good enough" after the release of the promotion. Second is the user after use, think it "good enough". After agreeing on both, they thought it was "good enough" and the software was really "good enough".

4. which pair mode is better in pair programming? is the combination of equal strength a strong one (one person with one person)?

I think that each combination of the pros and cons of the key is to see the individual learning attitude. The biggest difficulty we encounter when programming is coding problem, if the learning attitude is not positive, the coding ability of a strong one weak combination will be slack, the end result is a combination of only by coded strongman. The equal combination of strength is likely to slack both sides. So, if we want to learn from the subjective, no matter which combination we will have a harvest.

5. not very understanding of waterfall processes and agile processes.

Waterfall model is a traditional software cycle model that strictly follows the fixed order of each phase of the software lifecycle: Planning, analysis, design, programming, testing, and maintenance, before the last stage can be entered into the next stage, the whole model is like a waterfall straight down.

The agile development takes the user's demand evolution as the core, uses the iterative, the gradual step method carries on the software development. In agile development, software projects are cut into multiple sub-projects in the early stages of construction, and the results of each sub-project are tested for visual, integrated, and operational use features. In other words, a large project is divided into several interconnected, but also can be run independently of small projects, and completed, in the process of software has been in a state of use.

Second, summing up the experience of the course this semester

This semester of software engineering class is nearing the end, review this semester's study has many gains.

The feeling of "doing the middle school": Before this class, I heard that the soft work class is a very dull and tedious theory course, and this semester's software engineering class has carried on the reform, obeys "does the middle school" the study way. I think this kind of learning method is more suitable for our study improvement. Before the study of our theory class was to fool the past, two weeks before the exam began the crazy "genius" mode, these two weeks to master all the theoretical knowledge to deal with the exam, this way to learn nothing. Now this way of learning, weekly Update blog work, check the way the work is open and transparent, learning attitude has to straighten up, and this way let everyone move up, can not say how good effect, but I think do better than not do.

The "Pair programming" feeling: In the previous course, we are mainly personal programming, basically no contact with the project, this pair of programming for me is a new experience. In the process of pairing programming, I think that two people cooperation is the process of mutual learning, in the face of problems, two people to discuss, put forward their own solution to the problem, not only the promotion of their own personal ability to provide partners with understanding of the idea of mutual learning and improve efficiency.

The feeling of "team Programming": Team programming is dominated by team collaboration and communication skills in team programming, after pairing programming. Team programming more people, how fair and reasonable allocation of tasks is very important, this time to test our team tacit understanding and communication skills, teamwork, the better the quality of the software to complete the higher.

The above is my experience of the most profound part of this course. Finally to thank the teachers and classmates in this semester to help me!

Iii. Recommendations for the course

I think we can finally use the class as a unit of brainstorming, in the case of force, the class team produced a "good enough" software.

Assignment nine: A summary of the software engineering course