外文翻译软件工程实践者研究方法.docxVIP

附　　录 Software Engineering-A PRACTITIONER’S APPROACH Written by Roger S. Pressman, Ph.D. （P.340-P.343） 13.3　DESIGN PRINCIPLES Software design is both a process and a model. The design process is a sequence of steps that enable the designer to describe all aspects of the software to be built. It is　important to note, however, that the design process is not simply a cookbook. Creative skill, past experience, a sense of what makes “good” software, and an overall commitment to quality are critical success factors for a competent design. The design model is the equivalent of an architect’s plans for a house. It begins by representing the totality of the thing to be built (e.g., a three-dimensional rendering of the house) and slowly refines the thing to provide guidance for constructing each detail (e.g., the plumbing layout). Similarly, the design model that is created for software provides a variety of different views of the computer software. Basic design principles enable the software engineer to navigate the design process.Davis suggests a set of principles for software design, which have been adapted and extended in the following list: ? The design process should not suffer from “tunnel vision.” A good designer should consider alternative approaches, judging each based on the requirements of the problem, the resources available to do the job, and the design concepts presented in Section 13.4. ? The design should be traceable to the analysis model. Because a single element of the design model often traces to multiple requirements, it is necessary to have a means for tracking how requirements have been satisfied by the design model. ? The design should not reinvent the wheel. Systems are constructed using a set of design patterns, many of which have likely been encountered before.These patterns should always be chosen as an alternative to reinvention.Time is short and resources are limited! Design time should be invested in representing truly new ideas and integrating