Using UML Patterns and Java ObjectOriented Software Engineering

Using UML, Patterns, and Java Object-Oriented Software Engineering Art for Chapter 4, Requirements Elicitation

Figure 4 -1, Products of requirements elicitation and analysis. problem statement Requirements elicitation Requirements Specification nonfunctional requirements functional model Analysis Model dynamic model analysis object model Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 2

Figure 4 -4, Actors for the Sat. Watch system. Watch. Owner moves the watch (possibly across time zones) and consults it to know what time it is. Sat. Watch interacts with GPS to compute its position. Webify. Watch upgrades the data contained in the watch to reflect changes in time policy (e. g. , changes in daylight savings time start and end dates). GPS Watch. Owner Sat. Watch Webify. Watch Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 3

Figure 4 -5, Actors of the FRIEND system. Field. Officers not only have access to different functionality, they use different computers to access the system. Field. Officer Bernd Bruegge & Allen H. Dutoit FRIEND Dispatcher Object-Oriented Software Engineering: Using UML, Patterns, and Java 4

Figure 4 -11, Example of communication relationships among actors and use cases in FRIEND. <<initiate>> Field. Officer Dispatcher Report. Emergency Bernd Bruegge & Allen H. Dutoit Open. Incident Allocate. Resources Object-Oriented Software Engineering: Using UML, Patterns, and Java 5

Figure 4 -12, Example of use of extend relationship. Connection. Down Field. Officer Report. Emergency Bernd Bruegge & Allen H. Dutoit <<extend>> Object-Oriented Software Engineering: Using UML, Patterns, and Java 6

Figure 4 -13, Example of include relationships among use cases. <<include>> Open. Incident View. Map <<include>> Allocate. Resources Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 7

Project definition Management definition guide Research Preliminary specification Session agenda Preparation Session script Working document Figure 4 -15, Activities of JAD Scribe forms Final document preparation Bernd Bruegge & Allen H. Dutoit Session Object-Oriented Software Engineering: Using UML, Patterns, and Java Final document 8

Figure 4 -20, High-level scenarios identified for ARENA. define. Knock. Out. Style alice: Operator install. Tic. Tac. Toe. Game joe: League. Owner mary: Player organize. Tic. Tac. Toe. Tournament bill: Spectator analyze. Tic. Tac. Toe. Tournament sponsor. Tic. Tac. Toe. Beginners. League Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java zoe: Advertiser 9

Figure 4 -21, High-level use cases identified for ARENA. «initiate» Manage. User. Accounts «initiate» Operator «initiate» Manage. Components «initiate» Define. League «participate» «initiate» League. Owner Register Anonymous «initiate» Manage. Own. Profile Player Organize. Tournament «initiate» «participate» Advertiser Manage Advertisements Bernd Bruegge & Allen H. Dutoit Spectator Browse. Tournament. History Object-Oriented Software Engineering: Using UML, Patterns, and Java 10

Figure 4 -23, Detailed use cases refining the Organize. Tournament high-level use case League. Owner «initiate» «include» Organize. Tournament Archive. Tournament «include» Announce. Tournament «include» Play. Match Process. Applications Apply. For. Tournament Kickoff. Tournament «participate» Player Advertiser Spectator Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 11

Figure 4 -25, Exceptions occurring in Announce. Tournament represented as extending use cases. «extend» Announce. Tournament Invalid. Date «extend» Advertiser. Credit. Exceeded «extend» No. Matching. Sponsor. Found Name. In. Use Max. Number. Of. Tournaments. Exceeded Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 12