intoductionto fowlers analysis patterns（intoductionto福勒的分析模式）.docVIP

Creating a Reusable GUI Component By Dr. Sara Stoecklin Dr. Clement Allen Introduction When building large systems requiring many screens and on-line reports, it becomes a time-consuming activity to build all the GUI components and write the methods for validation of the components which require user entries. There exist a need for some reusable self-validating GUI components that extends the capability of the noted swing components supplied by the Java Development Kit. To develop these re-usable self-validating GUI components, we use an abstraction called an analysis pattern. Analysis Patterns is defined by Fowler [Fow97] as a higher level knowledge abstractions of a needed software entity. In this case, this refers to a GUI component. Popular design patterns deal with those patterns useful in programming [Gam95] , [Cop95], [Gra98a], [Gra98b]. Design patterns represent reusable software structures needed for implementation. In contrast, Fowler’s Analysis Patterns represent reusable abstractions for reuse in building many user related software components. In this case they are used to create a GUI text component that validates itself using a standard data dictionary definition of the field entered in the text component. 2.0 Why Use Analysis Patterns We have used patterns in structured programming and they proved beneficial. When writing a new program, most programmers copied examples of similar programs (program patterns) and modified those similar programs to meet the needs of the new program rather than writing the new program from scratch and risk simple compile errors as well as logic errors. Structured pattern programs proved beneficial because they saved in the development time needed for new programs and the maintenance time for reviewing existing programs where programmers understood the commonly used pattern programs. Object-oriented analysis, design and programming, when introduced, proclaimed the notable advantage of reuse. These pr