1 / 12

Art for Chapter 4, Requirements Elicitation

Art for Chapter 4, Requirements Elicitation. Requirements. Requirements. elicitation. Specification. Figure 4-1, Products of requirements elicitation and analysis. problem. statement. nonfunctional. requirements. functional. model. Analysis. Analysis Model. dynamic model.

oprah-charles
Download Presentation

Art for Chapter 4, Requirements Elicitation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Art for Chapter 4,Requirements Elicitation

  2. Requirements Requirements elicitation Specification Figure 4-1, Products of requirements elicitation and analysis. problem statement nonfunctional requirements functional model Analysis Analysis Model dynamic model analysis object model

  3. GPS SatWatch WatchOwner WebifyWatch Figure 4-4, Actors for the SatWatch system. WatchOwner moves the watch (possibly across time zones) and consults it to know what time it is. SatWatch interacts with GPS to compute its position. WebifyWatch upgrades the data contained in the watch to reflect changes in time policy (e.g., changes in daylight savings time start and end dates).

  4. FRIEND FieldOfficer Dispatcher Figure 4-5, Actors of the FRIEND system. FieldOfficers not only have access to different functionality, they use different computers to access the system.

  5. <<initiate>> FieldOfficer OpenIncident Dispatcher ReportEmergency AllocateResources Figure 4-11, Example of communication relationships among actors and use cases in FRIEND.

  6. ConnectionDown FieldOfficer <<extend>> ReportEmergency Figure 4-12, Example of use of extend relationship.

  7. Figure 4-13, Example of include relationships among use cases. <<include>> OpenIncident ViewMap <<include>> AllocateResources

  8. Project definition Figure 4-15, Activities of JAD Management definition guide Research Preliminary specification Session agenda Preparation Session script Session Working document Scribe forms Final document preparation Final document

  9. Figure 4-20, High-level scenarios identified for ARENA. defineKnockOutStyle alice:Operator installTicTacToeGame mary:Player organizeTicTacToeTournament joe:LeagueOwner bill:Spectator analyzeTicTacToeTournament sponsorTicTacToeBeginnersLeague zoe:Advertiser

  10. Figure 4-21, High-level use cases identified for ARENA. «initiate» ManageUserAccounts «initiate» Operator «initiate» ManageComponents Register Anonymous «initiate» DefineLeague «initiate» «participate» «initiate» ManageOwnProfile LeagueOwner Player OrganizeTournament «initiate» «initiate» «participate» BrowseTournamentHistory Manage Advertisements Advertiser Spectator

  11. Figure 4-23, Detailed usecases refining theOrganizeTournamenthigh-level use case LeagueOwner «initiate» «include» OrganizeTournament ArchiveTournament «include» «include» «include» «include» AnnounceTournament PlayMatch ProcessApplications ApplyForTournament KickoffTournament «participate» «participate» Player Advertiser Spectator

  12. Figure 4-25, Exceptions occurring in AnnounceTournament represented as extending use cases. «extend» «extend» InvalidDate AnnounceTournament «extend» AdvertiserCreditExceeded «extend» «extend» NoMatchingSponsorFound MaxNumberOfTournamentsExceeded NameInUse

More Related