The law of construction classified various components of software engineering and introduced the software engineering system in a horizontal way. And then in each category in the longitudinal and gradual progression,
More completely let us these rookie first knowledge software engineering.
After a semester of study, "Software engineering" with the "construction of the law" to learn, I also have a certain understanding of software engineering. Software = program + Engineering, a
People think that if the program means implementation, then software engineering is more focused on "methods" and "rules". It seems that software engineering is a new discipline, its methodology is a group of rich
Experienced Daniel extracts from their rich programming experience of the essence and lessons learned (my personal imagination), there is no particular perfect (to tell the truth is quite perfect) of the theoretical system,
It's still in the exploratory phase. The software engineering described in the law of construction, in my opinion, focuses more on "application", and all patterns and methods are developed in a specific timeframe.
Good enough software for the premise, so feel to talk about the method to be very free and fit practice, so give people full of freshness. I like this very much. Although the computer industry
Development is fast, but it is a new industry, and it is a feature of rapid change, perhaps in the next few decades, our application of software engineering method is another
The situation (laughter).
Then talk about the law of construction, which is a professional and interesting writing. Read through the book and imagine a person from a novice programmer to a software engineer, and then the team
Together to complete a software development, testing and maintenance of the story. The law of construction is very comprehensive and introduces almost every aspect of software engineering, for both the development process,
Teamwork, as well as demand analysis, design implementation and practical innovation are all explained in great detail.
Let's talk about some of the chapters that I'm very impressed with. Having just experienced team development, I recently read the section "Team and process". Development has been carried out by more than half,
It is also interesting to come up with a reflection.
First of all, we have their own division of labor, and rely on each other to work together to complete the task, so as a team, we are qualified, and then the software team Model,
To reflect on it, we should belong to the amateur theater model (amateur Theater Team). For example, in this team-work project, we started with the topic of the subway,
Then everyone chooses different roles, I participate in the role is "Calculate shortest path", then for various reasons, we changed the topic for the development of online games, in the new project
I changed the role of the participant and was responsible for "client and interface design". Each member of the team plays a different role, responsible for different parts, but we all listen to
Leader's guidance and arrangement. In addition, we would like to talk about two more mature development modes: "Symphony Orchestra mode (Orchestra)" and "Jazz Band".
In my opinion, the former is more stable, the latter more free (but must be a group of Daniel together to achieve ah ...) Not everyone has the ability to improvise. )。 The individual or
Compare to appreciate the symphony orchestra mode (these two kinds of music still like Symphony, hmm), although the innovation ability may not be inferior, but stable long-term. The next step is the development process.
According to the teacher's request, we have done the requirement analysis and the system design before the development of the team project, also completed the relatively brief development document. Although not according to the waterfall model
That's a strict focus on design, write a bunch of development documentation (time, time), but also get rid of the habit of writing code.
The Book of the Construction Law and the group Project