Behavior Models: Specifying User's Expectations |
Common terms and phrases
action activities additional administrative analysis apply architectural attributes begin behavior model behavior patterns chapter client COACH communications complete condition consider consists contains continuous costs create customer's expectations data dictionary data elements data flow decision define definition dependent describe detail determine diagram Display document domain engineering enters entity data stores entry event example existing Fail-Safe FIELD Figure functional identify illustrates implement initiates input installation interactions interface limitations logic means Merchant messages motives necessary normal form object occurs operating option organize output perform PLAYER PLAYER-ADDR primary key problem processor real-time receives relationships represent request requirements requirements specification response scenario shown single specification statements stimulus structure systems planner TEAM TEAM-NAME temporal event update user's wants