Behavior Models: Specifying User's Expectations |
From inside the book
Results 1-3 of 47
Page 130
... Performance Requirements Reliability Requirements Security Requirements Time Relationships External Interfaces Other Requirements EVENT DIAGRAMS CONTEXT DIAGRAM SYSTEM PURPOSE E - R DIAGRAMS DATA DICTIONARY Figure 5.1 We express these ...
... Performance Requirements Reliability Requirements Security Requirements Time Relationships External Interfaces Other Requirements EVENT DIAGRAMS CONTEXT DIAGRAM SYSTEM PURPOSE E - R DIAGRAMS DATA DICTIONARY Figure 5.1 We express these ...
Page 208
... Performance Requirements - What are the customer's expectations for the performance of a specific behavior ? The customer may expect the system to perform a behavior within a minimum amount of time . Here is where we document the ...
... Performance Requirements - What are the customer's expectations for the performance of a specific behavior ? The customer may expect the system to perform a behavior within a minimum amount of time . Here is where we document the ...
Page 276
... requirements . In addition , it allows for very specific requirements to be included in the model such as processor characteristics , processing priorities , performance , capacity , time relationships , interface standards , fail ...
... requirements . In addition , it allows for very specific requirements to be included in the model such as processor characteristics , processing priorities , performance , capacity , time relationships , interface standards , fail ...
Common terms and phrases
action diagrams activities analysis BEHAVIOR DIAGRAM behavior model behavior patterns behavior specification BUSINESS-NAME candidate keys chapter client COACH common processing routine Community Little League context diagram control flow costs CURRENT-TEAM customer expects Customer wants customer's expectations data dictionary data flow diagrams decision table define document domain E-R diagram entity data stores entry event diagram example external event Figure finite-state foreign key HOME-FIELD identify illustrates INFO input data interactions interface League Baseball System Little League Baseball logic Merchant messages motives and events notation output data palatial behaviors PARENT-NAME PASSWORD perform PLAYER PLAYER-ADDR PLAYER-NAME PLAYER-PHONE PREVIOUS-YR primary key process-spec real-time systems relationships requirements specification response scenario diagram scenario specification second normal form set the customer's shopper shown in Fig software products stored data structured specification subtypes systems analyst systems planner target process TEAM TEAM-NAME temporal event third normal form update Usage Motive user's expectations