Quote in his article Brooks said: "The complexity of security software are necessary characteristics" (Brooks Jr., 1986, p.3). Most difficult to influence the project is the complex requirements set out, and these complications are the most he Brook commentary in the paper.
The project does also have difficulties in the development, problems here is how to find solutions to overcome it. It can cause difficulties in managing, scaling and control the test run, the credibility of software development. Along with corruption issues yet, it will create a chain of complex issues and lead to the lack of such control, the wrong set requirements for products, extending the progress, development costs are push up. Software development methods based on this is not a "No Silver Bullet" to solve all complex problems. But also know everything in this life, nothing is perfect, it always has its strengths parallel to it are weak. It's just that the method plays a role in creating a development process, and we will apply it to the project process. Here it will be resolved in many cases small difficulty Brook given as: flaws of the product; cost overruns; schedule delays.
• Sai control of the product: the product regularly test will help detect and repair small damage, but still happens that the two cases. First, the error was detected during the manufacturing process, this is very good for the end user Tomorrow will never know about these errors, can fix this slow progress, but the user will receive perfect product. Second, user error detection is a very serious error and as a result the project was canceled due to wrong application development process.
• Exceeding costs: there are many reasons leading to cost overruns that would list here were: lack of control of the hidden costs; incorrect assumptions; market volatility; unclear requirements, and failed to change the technical requirements of the project
• Delays progress: this is the cause of cost overruns.
đang được dịch, vui lòng đợi..