La Muerte De Ff

Modeling System Behavior

Have you found all the use cases? Those you have found must be able to perform all system behaviors. If they don't, some use cases are missing. Do the use casesmeet all the functional requirements? If you have intentionally left any requirements to be dealt with in the object models, such as non-functional requirements, you must mention thissomewhere. If a requirement of this type concerns a specific use case, state this in the special requirements section of the use case. Does the use-case model contain any superfluous behavior? Doesit present more functions than were called for in the requirements? Have you found all the actors? Have you accounted for and modeled all the roles in the system's environment? You can't besure until you have found and described all the use cases. Is each actor involved with at least one use case? Remove any actors not mentioned in the use-case descriptions, or any actors withoutcommunicates associations with a use case. Note that an actor mentioned in a use-case description is likely to have a communicates association with that particular use case. Can you name atleast two people who would be able to perform as a particular actor? If not, check the role the actor models. If it's part of another role, merge the actor with another actor. Are thereactors playing similar roles in relation to the system? If so, merge them into a single actor. The communicates associations and use-case descriptions show how the actors and the systeminterrelate. Will a particular actor use the system in several different ways or does the actor have several different purposes for using the use case? If so, you should probably have more than oneactor. Do the actors have intuitive and descriptive names? Can both users and customers understand the names? It is important that actor names correspond to their roles. If not, change them.