李彤《软件工程》教学课件ch17.pptVIP

Visual programming with reuse 画布 Problems with visual development Difficult to coordinate team-based development. No explicit system architecture. Complex dependencies between parts of the program can cause maintainability problems. COTS reuse An effective approach to rapid development is to configure and link existing off the shelf systems. For example, a requirements management system could be built by using: A database to store requirements; A word processor to capture requirements and format reports; A spreadsheet for traceability management; Compound documents For some applications, a prototype can be created by developing a compound document. This is a document with active elements (such as a spreadsheet) that allow user computations. Each active element has an associated application which is invoked when that element is selected. The document itself is the integrator for the different applications. Application linking 17.4 Software prototyping A prototype is an initial version of a system used to demonstrate concepts and try out design options. A prototype can be used in: The requirements engineering process to help with requirements elicitation and validation; In design processes to explore options and develop a UI design; In the testing process to run back-to-back tests. Benefits of prototyping Improved system usability. A closer match to users’ real needs. Improved design quality. Improved maintainability. Reduced development effort. Back to back testing T est data Results comparator S ystem prototype Application system Difference report The prototyping process Esta b lish pr ototype objecti v es Define prototype functionality De v elop pr ototype Ev alua te pr ototype Pr ototyping plan Outline definition Ex ecuta b le pr ototype Ev alua tion r epor t Throw-away prototypes Prototypes should be discarded after development as they are not a good basis for a production system: It may be impossible to tune the system to meet non-functional requirements; Proto