The book "Software Engineering" is a more explicit explanation of what is the application (computer programs, procedures, and the related and data that may be required to run a computer system) and the software project (to apply a systematic, standardized, quantifiable approach to the development, operation, and maintenance of the software, which will be applied to the software on an engineering basis. )
The second chapter of software Engineering explains the process, and its basic activities are: 1. Issue 2. Software Requirements Specification 3. Software Design 4. Software implementation 5. Software validation 6. Software Evolution
The model of software process is: Waterfall model, rapid prototyping model, increment model, helix model, formal method model, component-based development model. We describe the process of software development and the method of software development.
Chapter III of software project management ask us about some of the things that need to be considered in software development, such as activities for analysis and management of cost, schedule, quality, personnel, risk, etc. Software project Management is the work we must do to successfully develop software. By reading the third chapter I realize that software development is not just about putting a bunch of programs on the line, it's not just writing code. I learned about the new concepts of Code line technology, feature point technology, etc., which were not previously accessible.
The fourth chapter of the requirements of the project is how to understand the needs of users, first to obtain demand, which is the user's intuitive demand for access, and then is the demand analysis, the demand of the opponent knocked down refining, analysis, careful review, to ensure that all the project stakeholders understand its meaning, and find the errors, Omission or other deficiencies, forming a complete analytical model.
The Book of Software engineering