| Work requirements | https://edu.cnblogs.com/campus/jssf/infor_computation17-31/homework/10584 |
|---|---|
| My aim in this course is | Master the software development knowledge |
| This job helped me in terms of what specific goals | Methodology for software engineering |
| Text of the job | https://www.cnblogs.com/dragonD/p/12652714.html |
| References | https://www.cnblogs.com/katniss-smile/p/5982643.html https://www.baidu.com/ |
waterfall
The core idea of the waterfall model is based on the problem of simplifying the step, to be implemented separately from the design features, to facilitate division of labor, i.e. using structured analysis and design and implement physical logic implemented separately. The waterfall model of software life cycle is divided into software plans, requirements analysis and definition, software design, software implementation, software testing, software operation and maintenance of the six stages of spelling out their top-down, mutual convergence of fixed order, like a waterfall water progressively falling.
Waterfall model conducive to the organization and management of large-scale software development staff, it is conducive to research and the use of software development methods and tools to improve the quality and efficiency of large-scale software development projects.
Advantage of the waterfall model
1) for the project to provide a checkpoint in stages divided.
2) After the completion of the previous stage, you just need to focus on subsequent phases.
3) can be applied to the waterfall model in an iterative model. Incremental iterative waterfall model applied. 1 iteration to solve the biggest problem. Each iteration produces a version that can run while adding more features. Each iteration must be quality and integration testing.
4) It provides a template that makes the analysis, design, coding, testing, and support the method can have a common guidance on this template.
Big Ball of Mud
The so-called Big Ball of Mud, refers to the chaotic and complex, dirty unbearable, collage of random piles of code. Over the years, in order to deal with this mud ball, appeared together a variety of methods to guide, but the actual situation is not much change, "Big Ball of Mud" still seems to be the most common way to design software architecture. We are now customary in many ways agility will directly lead to the development of mud balls, including: the lack of pre-design, fragmented response to the growing demand change too late, too late to deal with architectural changes.
I think that in this situation should strengthen the control of the code, such as strict management team to strengthen the code, review code in order to increase accuracy and improve code readability.
church
Cathedral mode (The Cathedral model): software source code after public release, but by a dedicated team Controls in each version of the software development process. The author GNU Emacs and GCC both software as an example.
market
Bazaar (The Bazaar model): i.e., source code is disclosed on the Internet in the development process, the development and available for viewing. The author of the Linux kernel founder Linus Torvalds led by the Linux kernel development, for example, is also cited as an example for fetchmail.
Silver Bullet
Wolf: Western legend of the most horrible kind of monster, often clump familiar faces otherwise programming monster, so the most difficult to prepare, is used to describe a variety of thorny issues encountered during software development.
Silver Bullet: Long used to shoot people silver bullet, effective way to solve the problem of software development process analogy.
Brooks in his most famous "no silver bullet - the nature of software engineering and contingencies," the article pointed out that in the software development process is no panacea in the final killing weapons (ie silver bullet), only the integrated use of a variety of methods, It is the solution. The various claims how how magical theory or method, are not able to kill the "software crisis" This headman wolf silver bullet.
And I also tend to view "no silver bullet", the internal design of the software itself has a certain degree of complexity, I think this is necessary, sometimes unavoidable. Sophisticated software necessary to consider all aspects of the complexity of the actual process can not rely solely on technology to solve the.
agile
Agile Manifesto follow 12 principles:
- Our most important goal is through continuous delivery of valuable software as soon as possible so that customer satisfaction.
- We are pleased to face changes in demand, too even late in development. For customers' competitive advantage, agile process control change.
- Software often deliver working, separated by a few weeks or a month or two, they tend to take a shorter period.
- Business people and developers must cooperate with each other every day projects are no exception.
- Stimulate individual morale, in order to build their core projects. Environment and provide the required support, combined with trust, so as to achieve the goal.
- Regardless of inside and outside the team, the best transmission of information is also the most efficient way is face to face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development. Sponsors, developers and users together to be able to maintain its steady pace continues.
- Perseverance in pursuit of technical excellence and good design, thereby enhancing agility.
- With simple faith, which is trying to reduce unnecessary workload of art.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- Team regularly reflect on how to improve the effectiveness and adjust their behavior so performance.
Agile points
1, focusing on the concept and architecture design, detailed design light
2, using SWOT analysis (Reference: https://www.cnblogs.com/katniss-smile/p/5982643.html )
3, and demand-driven market, rather than technology-driven
4, always consider the compatibility version
5, light documents, but not without documents