Chapter_06v1讲义.pptVIP

Actuator-Sensor Pattern—III See SEPA, 7/e for additional information on: Participants Collaborations Consequences * Requirements Modeling for WebApps Content Analysis. The full spectrum of content to be provided by the WebApp is identified, including text, graphics and images, video, and audio data. Data modeling can be used to identify and describe each of the data objects. Interaction Analysis. The manner in which the user interacts with the WebApp is described in detail. Use-cases can be developed to provide detailed descriptions of this interaction. Functional Analysis. The usage scenarios (use-cases) created as part of interaction analysis define the operations that will be applied to WebApp content and imply other processing functions. All operations and functions are described in detail. Configuration Analysis. The environment and infrastructure in which the WebApp resides are described in detail. * When Do We Perform Analysis? In some WebE situations, analysis and design merge. However, an explicit analysis activity occurs when … the WebApp to be built is large and/or complex the number of stakeholders is large the number of Web engineers and other contributors is large the goals and objectives (determined during formulation) for the WebApp will effect the business’ bottom line the success of the WebApp will have a strong bearing on the success of the business * The Content Model Content objects are extracted from use-cases examine the scenario description for direct and indirect references to content Attributes of each content object are identified The relationships among content objects and/or the hierarchy of content maintained by a WebApp Relationships—entity-relationship diagram or UML Hierarchy—data tree or UML * Data Tree * The Interaction Model Composed of four elements: use-cases sequence diagrams state diagrams a user interface prototype Each of these is an important UML notation and is described in Appendix I * Sequence Dia