软件需求分析课件：Chap 11-Iteration 3--More Topics

1、Elaboration Iteration 3Intermediate TopicsCh27.Iteration 3-Intermediate TopicsCh28. UML Activity Diagrams and ModelingCh29. UML State Machine Diagrams and Modeling1Chapter 27.Iteration 3-Intermediate TopicsObjectivesDefine the requirements for iteration-3.2IntroductionInception and iteration-1 Basic

2、 OOA/D modeling basicsIteration-2Object designIteration-3Broader analysis and design topics3Iteration-3More GoF design pattern, and their application to the design of frameworksin particular, a persistence frameworkArchitectural analysisdocumenting architecture with the N+1 view modelProcess modelin

3、g with UML activity diagramsGeneralization and SpecializationThe design of packages4NextGen POSRequirements in iteration-3 include:Provide failover to local services when the remote services cannot be accessedProvide support for POS device handlingsuch as the cash drawer and coin dispenserHandle cre

4、dit payment authorizationSupport for persistent objects5MonopolyRequirements in iteration-3 include:Implement a basic, key scenario of the Play Monopoly Game use caseMore of the complete set of rules applyThere are now Lots, Railroads, and Utility squaresIf not owned, the player who landed on the sq

5、uare may buy itIf owned by the player that landed on it, nothing happensIf owner by a player other than the player that landed on it, the player that landed on the square must pay its owner rent6Chapter 28. UML Activity Diagrams and ModelingObjectivesIntroduce UML activity diagram notation, with exa

6、mples, and various modeling applications7IntroductionA UML activity diagram shows sequential and parallel activities in a process. Modeling business processes, workflows, data flows, and complex algorithms.Basic notation include action, partition, fork, join, and object nodeActivity diagram can show

7、 both control flow and data flow8Example(Business Process Modeling)9Data Flow ModelingData flow diagrams (DFD) became a popular way to visualize the major steps and data involved in software system processes.10Classic DFD in Gane-Sarson notationExample(data flow Modeling)11More UML Activity Diagram

8、Notation12Signals in UML Activity Diagrams 13 model events such as time triggering an action, or a cancellation requestGuidelinesThis technique proves most valuable for very complex processes, usually involving many parties. Use-case text suffices for simple processes.If modeling a business process,

9、 take advantage of the rake notation and sub-activity diagrams. Strive to make the level of abstraction of action nodes roughly equal within a diagram. 14Example: NextGen Activity Diagram15Chapter 29. UML State Machine Diagrams and ModelingObjectivesIntroduce UML state machine diagram notation, with

10、 examples, and various modeling applications.16ExampleA UML state machine diagram, illustrates the interesting events and states of an object, and the behavior of an object in reaction to an event.17State machine diagram for a telephoneDefinitions: Events, States, and TransitionsAn event is a signif

11、icant or noteworthy occurrence. A state is the condition of an object at a moment in timethe time between events. A transition is a relationship between two states that indicates that when an event occurs, the object moves from the prior state to the subsequent state. 18State-dependent objectIf an o

12、bject always responds the same way to an event, then it is considered state-independent (or modeless) with respect to that event. By contrast, state-dependent objects react differently to events depending on their state or mode.19How to Apply State Machine Diagrams?Consider state machines for state-

13、dependent objects with complex behavior, not for state-independent objects.In general, business information systems have few complex state-dependent classes. It is seldom helpful to apply state machine modeling.By contrast, process control, device control, protocol handlers, and telecommunication do

14、mains often have many state-dependent objects. If you work in these domains, definitely know and consider state machine modeling.20Modeling State-dependent ObjectsState machines are applied in two ways:To model the behavior of a complex reactive object in response to events.To model legal sequences

15、of operationsprotocol or language specifications.21Complex Reactive ObjectsPhysical Devices controlled by softwarePhone, car, microwave ovenTransactions and related Business Objectssale, order, paymentRole MutatorsThese are objects that change their role.Person changing roles from being a civilian t

16、o a veteran22Protocols and Legal SequencesCommunication ProtocolsUI Page/Window Flow or NavigationUI Flow Controllers or SessionsUse Case System OperationsIndividual UI Window Event Handling23More UML State Machine Diagram NotationTransition Actions and GuardsA transition can cause an action to fire

17、A transition may also have a conditional guard boolean test24Nested StatesA state allows nesting to contain substates.A substate inherits the transitions of its superstate (the enclosing state).25Example: UI Navigation Modeling with State MachinesState machines are a great way to model page flows fo

18、r Web UI applications during creative design.26Example: NextGen Use Case State Machine Diagram27A sample state machine for legal sequence of use case operationsSummaryUML Activity Diagrams and ModelingUML State Machine Diagrams and Modeling28Ex. Secret panel controllerSuppose there is a controller for a secret panel in a Gothic castle(哥特式城堡). In this castle, you want to keep your valuables in a safe（保险箱） thats hard to find. So to r