Before we could create the website for the KHBPA, our group needed to collect the functions that they required from their new website. After collecting these requirements, we could then begin to visualize how we wanted the design of their new system to look. In order to visualize this design, we used Unified Modeling Language (UML) to create use cases, use case diagrams, sequence diagrams, and class diagrams.
Use Cases
One of the functions that the KHBA required from their new website was that there needed to be a place to submit claims for approval. The KHBPA provided coverage to members whenever incidents would occur, such as fire or flood. This use case describes the functionality of the claims processing function of the new website. It describes the basic flow of information from the user to the KHBPA site, as well as any pre- and post-conditions required to trigger this event.
Use Case Diagram
In the following example, I have created a use case diagram of four different functions of the new KHBPA website. A use case diagram describes who can interact with the system and what they can do with it. In this diagram, there are two actors who ‘act’ on the system: the member and the employee. The diagram describes that the member acts on 3 different functions while the employee only acts on one.
Class Diagram
The class diagram defines what attributes or actions the use case will perform. An attribute is a piece of data, such as a member first name or address. An event or method is something that the use case will perform, such as creating or submitting a claim. This diagram describes the attributes and methods of four different use cases, including the claims processing function.
Sequence Diagram
Now that I know the flow of information from the use case, as well as the attributes and methods from the class diagram, I can now create a sequence diagram. The sequence diagram visualizes the flow of information described in the use case.
Data Dictionary
A data dictionary describes the type of data that is collected from the site. It contains the table in which the data is held, the attribute name of the data being stored, data type, size, and a nullable field. Data dictionaries help fully understand the data and the databases that store it.
Adam Passanisi 