Introduction to Software Engineering Chapter II reading notes

In this chapter, I learned about several models of software lifetime.

The first is the waterfall model. The advantages are: 1 forcing developers to adopt a standardized approach 2 strictly stipulates that each stage must submit a document 3 requires that each stage of the product must be verified. The disadvantages are: 1 The final product may not match the customer's requirements 2 The model is only used when the project starts with a known requirement. On the basis of the waterfall model, V model has been developed, which combines the design and testing organically.

The second is the rapid prototyping model. Its advantages are: 1 to meet the real needs of customers 2 specification documents can correctly describe customer needs 3 product development basically in the linear order 4 development process will not be found in the specification document errors for large rework 5 errors in the design and coding stages are less likely to occur.

Next is the incremental model. The advantages are: 1 in a relatively short period of time to submit to the user some useful work products 2 gradually increase the product function allows users to learn and adapt to the product more ample time. 3 Project Failure Risk 4 The most important part of the system is that it can be tested multiple times to increase reliability due to early delivery. Some of the issues to be aware of are: 1 The new build cannot break the already developed product 2 software body structure must be open when joining.

Here is the spiral model. The advantages are: 1 Emphasizing the reuse of software 2 reduces the risk of excessive testing or inadequate testing 3 there is no essential difference between maintenance and development

Fountain model. The iteration is emphasized.

Another important concept in this chapter is agility. It has 12 principles, as follows. 1 The best thing to do is to make your customers happy by delivering valuable software early and consistently. 2 even in late development, it is also welcome to change the demand 3 frequently deliver the operational software 4 project development, business people and developers must work together every day 5 work around motivated individuals, giving them the environment and support they need. 6 The most effective way to communicate within the team is to talk to each other in person. 7 Operational software is the primary metric for progress 8 responsible people, developers and users should be able to maintain stable development speed for a long time 9 constantly focus on excellent skills and good design will enhance agility 10 so that do not have to do the work to maximize 11 best architecture, design, requirements and design from the self-organizing team 12 every once in a while, the team will reflect on how to work more effectively.

Introduction to Software Engineering Chapter II reading notes