Defining every atomic process-actor scenario, the permutation and combination sequence of which define the new / modified process.

A Use Case defines the “Who” does “What” to the System. The perspective is one of a third person viewing the Actor (user) and System (application / process) as two separate entities. The “what” is the activity that a Use Case Diagram is designed to illustrate. Modeling each use case around each requirement will ensure that all the requirements have been accounted for and greatly reduce chances of error or situations where requirements are missed.

NOTE: A Traceability Matrix plays a very prominent role in Software Development. A Traceability Matrix is defined as a matrix where a straight line can be drawn between the below elements from inception to implementation:

• Requirement/s
• Use Case/s
• Unit Test Case
• Integration Test Case
• Implemented Feature in Application or Module Version (Release)

This matrix will provide visibility to the business, as to what the implementation contains – specific to each requirement, and will enable them to understand the application implementation.