This is the use case description that models that textual model that lists and describes the processing details for a use case (Satzinger, 2015). This is the most formal method to use to document the use case, as having a good description helps the user understand what is happening. Another detail would be the preconditions or postconditions. It is useful for the user to enter something that is true or false, which depends on what the actor enters for the system. Using activity diagrams is another way to add more detail to use cases. These show the flow of activities that the system will process, which works well when a more complex system is in place. The last one uses the system sequence diagram, which is a diagram that shows the sequences of messages between an external actor and the system during the use case or scenario (Satzinger, 2015). What is the primary objective of systems design? The primary objective of system design is analysis to fully understand the organization's information needs or requirements to establish specifications (Satzinger, 2015). This system design consists of structuring the components of the final system, which serve to deploy the type of environment in which the user will find himself. When examining application software components within the system design, the analysis must identify the subsystems and relationships with each part of the system.