Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Software Engineering For Students: A Programming Approach Part 43. This fully revised version of Doug Bell's Software Engineering: A Programming Approach continues to use the successful formula of the previous editions. The author's approach is to present the main principles, techniques and tools used in software engineering, one by one, chapter by chapter. This book is a unique introduction to software engineering for all students of computer science and its related disciplines. It is also ideal for practitioners wishing to remain current with new developments in the area | 398 Chapter 32 Conclusion Some people fear that more systematic methods will reduce the scope for individual creativity. In addition automation tends to mean that fewer people are needed than would otherwise be required. The introduction of new methods has always been linked with the erosion of skills and job losses. In England the Luddites revolted against employers who replaced their labor by machinery then reduced wages and the number of jobs. Thus more effective methods often imply reduced skill deskilling lower wages fewer jobs and at the same time a small highly skilled elite to carry out the difficult tasks. The argument for using systematic approaches is that simple tasks should be made simple - there is no point in struggling to design a software component when there is an easy way. So a method can be empowering creating time to spend on intrinsically difficult tasks. In conclusion there is a tension between on the one hand the desire of an individual software engineer to exercise their individual creativity and on the other hand the wish of organizations to systematize methods and exercise quality control. 32.7 Future methods and tools Reflecting the current diversity there are a number of suggestions for the future of methods and tools for software development. Software tools Some people see software tools as the future. They see such tools as UML editors compilers linkers debuggers version control software and test frameworks as a means of assisting or automating parts of development. This would improve productivity and software quality. This approach has as its apotheosis the complete automation of software development along with the elimination of creativity and skill. Amongst others the proponents of agile methods have reacted against this approach arguing that tools can constrain and debilitate development. They argue that tools should be used judiciously as appropriate. Indeed some valuable tools such as a whiteboard need not be automated at all. .
