Software Engineering-Construction of the law semester summary

First, translation
1, the software engineer is to lead the project team to do software requirements analysis, software manuals, software design, development, testing and software operation and maintenance of high-paid and respected occupations. According to the commitment to health, safety and public interest, software engineers should observe some of the professional ethics:
(1) Public---Software engineers should be consistent with public interests.
(2) Customers and employers---software engineers should maximize the benefits of their clients and ensure that employers are in the public interest.
(3) Product---Software engineers should ensure that their products and related modifications meet the highest professional standards as far as possible.
(4) Judge---Software engineer should maintain its integrity and independence in professional judgment.
(5) Management---Software engineering managers and leaders should develop and propose an ethical approach to managing the development and maintenance of the system.
(6) Professional---Software engineers should maintain the integrity and reputation of the industry in advance in the public interest.
(7) Colleagues---software engineers should be fair and supportive of their colleagues.
(8) Self-taught---software engineers should participate in lifelong learning, and professional practice, and promote professional ethics.


second, the current study situation raises some questions ,

Now that we have finished the software engineering course, can everyone answer these questions, please answer them in this homework.

my first piece of knowledge of software engineering: http://www.cnblogs.com/chengxs/p/5248956.html

for awareness and questions:
1, indeed in the Software engineering class you are not a person to fight, is a team in the fight.
2, has been using ADT, enough to want to replace as, the computer tried to change 2 times or went in, the output HelloWorld, on the wrong tips, on the internet to find someone else technical blog or can not solve, so I still use ADT to compile Android.
3, we to a development of the software, its front desk and back-end development and maintenance, I think if it is our own each person to build and maintain. The implementation of this front desk is still easy to implement, the local test can pass and run, run on the server has a problem, now learning how to build a server environment, and put their own writing to the server, as well as daily maintenance. Build the virtual server, the database part of the error, the reason for their own, in the study.


Third, personal summary
First of all thank you let us try to the Software engineering curriculum reform, I have always thought that software engineering will be like before the modern enterprise management, the curriculum mainly by the teacher to the basic concept of knowledge point, and then the teacher began to talk about the case, and then ended the course, Finally, I feel that the modern enterprise management in their own mind left only a familiar pattern of administration.
but in the course of software engineering, I know that this is the entire development process of a management software. Listen to the former seniors said, they learn software engineering This course, the teacher in the above from the requirements analysis, then is the software design, coding implementation, software testing, software delivery, software maintenance ... , and then after the course there are exams, the teacher gave us a range before the exam, and then the students go back to review the key knowledge, the test is relatively easy to pass, but after the test, or the software project in the specific how to implement or just stay in said, and will not do, how to do, what to do.
the first day of our class, the teacher said this year our school software engineering This course reform, I still want a test course can change, not to the final exam results to determine their final results, but know the whole reform blueprint know this software engineering become the subject of the curriculum, Then began to write their own blog, I feel that this oneself in the university a good habit, write technical blog, write technology to share, feel very good, do not limit your use of the language to complete the needs, use your own familiar language to complete the project, but also in their own familiar language to the next level. Summarize your thoughts on software engineering-the method of building this semester:

first, the software engineering lesson is actually very interesting
individuals in the university class is always such a rule, a new course, the first time to feel good interest in class, tell yourself to study hard, and then in the course of their own slowly do not want to listen to the teacher lectures, and then quickly to review the time, they will become Superman like, their own reading textbooks, their own summary review materials, Oneself from the basic concept to the calculation analysis understanding, the question as long as in the past normal scope to feel oneself generally can test the good. If the topic style changes, it may be worse. Every homework, every project, I always want to think about what language to write, how to implement the logical function, and then find themselves in the writing of the bug in the place himself will also look at the library of relevant programming code, once you find their own code to write some redundancy, You can think of a better data structure and the amount of code is down. And time complexity is also a lot smaller, their own in the process of their own slowly learned the lack of programming, their own learning new knowledge, constantly summed up their learning to write a blog, finally the software written out to find software development is actually very interesting.

second, software engineering is not a class that just knocks the code
Software Engineering, a project does not rely on a person to complete independently, but a team of mutual cooperation and mutual collocation, complete software development and maintenance. Software engineering is the process management of the whole process, not only the code is finished, the personal feel more important is the software design phase, the software design phase is to specify the requirements, how to achieve, the use of what the development model, the team adopted what mode, test when the use of what test cases, software programming language selection, Complete the Software design documents, Draw good e-r diagram, draw a good flowchart, design a good database part. In the next part of the code implementation, not to write the code is OK, there are writing development documents, encountered errors, wrong solution, while there are engineering module follow-up speed, project completion ratio, daily code volume. The next software test requires us to determine the code implementation part of the syntax, lexical, semantic errors. Software testing is a good test case, and the way to test it, using black box testing and white box testing.

third, software engineering training Team collaboration Ability
before oneself has been a personal project small homework, oneself can always decide in what language to use, how to develop, but the last project job will have a variety of problems, such as the requirements analysis phase, the team members sometimes want reasonable demand, but he did not consider how to implement the logic, For example, the game platform can be developed into an instant communication platform, plus web search function, plus positioning function ... And then a good project after everyone said, feel this is a project, the need to become more complex, unclear, unclear. As a team leader, it is necessary to deny the unrelated parts, and to grasp the core of the project, do not deviate from the specific project too much. At the same time you have to identify the project division, who is good at what, let him do the corresponding work, rather than a part of everyone to do together, this will cause this part or a few do, other people in the rest, not fully use the characteristics of personnel, will cause a project dragged long, the division of labor important, once you are responsible for the problem You can pick up the root of the problem, find the wrong place, and quickly try to solve the mistake. This is not a problem, everyone is to do this part, we are each other, said I just wrote a little code, I do not know other people wrote that part, find the wrong will take a long time, and then feel the whole project once out of point problems, internal contradictions will become larger, and not implemented to specific to people, easy to misunderstand others, Blame others.

Software Engineering-Construction of the law semester summary