tailieunhanh - A Guide to MATLAB Object-Oriented Programming phần 2

Những ngôi nhà có chiều cao tương tự như máy nghe nhạc (giả định, tất nhiên, rằng ông không thể bay). Bạn đặt vị trí thông tin này vào thư mục gốc của cây. Tại mỗi nút, bạn quyết định, trong đó trẻ em là viết tắt của người chơi và bạn đẩy vị trí xuống các chi nhánh thích hợp. Điều này được thực hiện cho đến khi vị trí cuối cùng | Introduction 13 the average From experience we know that some bugs are unbelievably hard to find. Consequently it is very difficult to predict how long it will take to fix a broken module. The span around the average is very wide indeed. When you stop and consider the typical environment it becomes obvious why workdays are long and slipped schedules are considered normal. Now consider high-reliability practices. The previous four hours of programming time increase by 50 percent to six hours. Development is longer true but there are now one fourth the number of defects. If on average the time to fix an error does not change debugging should take one fourth as long as before. Now debugging adds only one hour instead of four. The total time to bug-free software with high-reliability practices is seven hours. Compare that to eight hours without them. Both produced the same code however high-reliability practices give you extra time to learn new development techniques keep your desk tidy or be even more productive. What about the span It is extremely difficult to estimate how long it will take to find and fix a bug. If you dedicate four of every eight hours to a task that is extremely difficult to predict how good is your predicted schedule We know from experience that the schedule is often wrong. Bringing the debug time down to one of every eight hours fosters much more confidence in the schedule. As strange as this may sound it is easier to estimate how long it will take to develop error-free code compared to developing sloppy code and debugging it. Reducing the expected span of the estimate has an enormous impact on planning scheduling and product rollout. At the beginning of this subsection we dismissed productivity in deference to quality. It is empowering to understand that quality and productivity are not at odds with one another. It might seem counterintuitive that the quest for high reliability results in on-time delivery less stress on the development team and