MISY430 Lecture Notes - Lecture 8: Functional Decomposition

• School: University of Delaware
• Department: Management Information Systems
• Course: MISY430
• Professor: Clinton White

Document Summary

Identify the goal: to clearly identify all of the functionality, be toward the end of the requirements gathering phase. Identify the value/goal for the actor: focus on what not how , use action verbs, keep it simple, use includes, extends, and generalizations only if they clarify the system. Things to avoid in use case diagramming: process views i. e. make payment or record transaction this will be included in documentation, but not in the actual use case because they are not the primary goals. Information flows associations are simply interactions don"t include to many associations/relationships: information flows both ways, ex: student logs in and accesses course catalog, registers for class. Document them: show preconditions, ex: logging into the system, dual authentication, etc, show trigger events, ex, anything else that"s important to explicate your use case.