1. The first chapter layman 's terms of finishing
Professional terms in bold:
Software architecture (Software Architecture), software design and implementation (Software Design, Implementation and Debug), source code management (Source Code Control), Configuration Management (Software Configuration Management), quality assurance (Quality Assurance), Software Test (Test), demand analysis (Requirement analysis), program understanding (program comprehension), software maintenance (software maintenance), service operation (service operation), the software life cycle (software life cycle, SLC), user experience (user experience), international and localization (Globalization & Localizatiion)
Generalized inferences software engineering: software = + Software Engineering program . And this reasoning has its development, expansion of inferences: software enterprise software = + business model .
Software development phase jargon: 1. Toy Hobby stage 2. Stage 3. Stage 4. mature industry exploration stage
Software Engineering: is the orderly, quantifiable systematic approach used in the development of software, the process of maintenance operations.
Software-based software engineering, and software is unique, its particularity is divided into five categories, which is jargon:
1. 2. The complexity of invisibility variability 3. 4. 5. discontinuity obedience
Three basic knowledge of technical terms for the field of software engineering: life cycle 1 2. 3. specialized areas of theoretical basis.
Software engineering jargon goal: customer satisfaction, reliability, quality software process, and maintainability.
2. Read through some of the problems the textbook
1. I read this passage: After the unit tests must be written by people (author of the program) code --P25,2.1.2 most familiar part of me there is a problem: the purpose of the code written by the author defined by the author after the completion of the preparation of the code, there will be questions of themselves may not be aware of, such as special values for a particular range of values, special input sample and so on, only because the author felt the need to test their test part of the sample as well as function, and therefore miss out the special circumstances that may arise, leading to robustness and functionality of the code is reduced. After I reviewed the information and write your own code and test experience, I think the unit test, code debugging must be written by the author of this is problematic, I express my doubts.
2. After I read Chapter 5 Software team mode (P91), the text introduces many team model, we obviously feel that the removal of bad patterns, such as rush mode after which the rest of the best and most efficient mode? If the model is based on a variety of different team composition selected according to the actual situation, then under what circumstances should choose what kind of team model is better solution? Text and data network and not be fully explained, I am in doubt.
3. I read the seventh chapter 7.2.1 (P128) to promote information sharing and part-mentioned communication, all information is retained, and publicly, that can not be deleted, then save the information is bound to consume storage space for the software development industry, storage space must be very great, but consumption is huge, whether the case one day all the storage space running out of existence, then there must be for older information deleted, after deleted, delete older information led to the current error, there is a theoretical scenario can not be resolved. In this regard, if there is better information sharing solution? MSF whether the model would be out of business?
4. For tricks to improve the estimation capability needs analysis in Chapter VIII (P173), the method including the reference previous experience, there are rapid prototyping, there are estimated cottage poker, Guessing Game size estimation and T-shirts law. I want to know in these methods, the existence of one of the most reasonable estimation method, the write code that employees can maximize cost savings, and make the code has good integrity and functionality, easy to reach demand. In short, how to estimate capacity is the most scientific, most efficient?
5. After I read the chapter XIII test report section (P279), I doubt this, the software must go through before they can test all the software it? Whether the customer experience can be put to the test by the relevant correlation of certain types of software counterparts? This is a question of my existence.
3. Software classification
1.Safari browser
(1) This is the Apple phone comes with APP, is based on the Web App development.
(2) It has an efficient process efficiency and is compatible with a variety of different network modes strengths, its goal is not profit, but simply to optimize the user experience of Apple to attract more people to buy Apple phone.
(3) set during the launch of the new version.
(4) Its strength lies have better compatibility with various web formats.
2. Taobao
(1) When freshman need to buy something to the app store to download, it belongs to Mobile Apps category of software.
(2) Taobao online shopping service with a convenient, safe and efficient, so I downloaded it.
(3) Taobao trial version will be released regularly, invite customers to experience, will be updated regularly.
(4) it has its strengths better online shopping patterns and a better reputation.
3. Hearthstone legend
(1) Download the application from APP Store, Games belong to the class of software.
(2) I think this puzzle game is fun, so download it.
(3) will often update the software.
(4) its profit model is the need to invest money to unlock certain levels and accelerate access to the corresponding game props.