More Requirements Models More Ways of Representing the Product

Various Models Data Flow Diagrams State Diagrams and Sequence Diagrams Not specifically part of UML, but still widely used. Particularly suited for systems designed with an I/O viewpoint (e.g., hardware-level design). Example decomposition and diagrams (see pgs 188-190 7/e, pgs 194-197 6/e) State Diagrams and Sequence Diagrams Useful for modeling applications controlled by events (i.e., user actions or sensor/switch inputs) Useful for modeling behavior where sequences of actions yield state transitions in the application objects. Example (pgs 195-198 7/e, pgs 199 and 216-220 6/e)

WebApps Models (new in 7/e) General Viewpoints for WebApps Content – the data of the webapp (e.g., graphics, video, text, etc.) Interaction – the behavorial aspect. Functional – the operations defined by the webapp. Navigational – specifies how the user moves within pages of the webapp. Configuration – describes the architecture of the webapp (i.e., system layout)