System modelling
Introduction
System modeling is a framework utilizing graphical documentation, which is often dependent on documentations in the Unified Modeling Language (UML). It is used to convey the usefulness of the framework and the models to be utilized.
Different models can be developed to represent the system from different perspectives:
An external perspective, where you model the context or environment of the system.
An interaction perspective, where you model the interactions between a system and its environment, or between the components of a system.
A structural perspective, where you model the organization of a system or the structure of the data that is processed by the system.
A behavioural perspective, where you model the dynamic behaviour of the system and how it responds to events.
Types of Unified Modelling Language (UML):
Activity diagrams, which show the activities involved in a process or in data processing.
Use case diagrams, which show the interactions between a system and its environment.
Sequence diagrams, which show interactions between actors and the system and between system components.
Class diagrams, which show the object classes in the system and the associations between these classes.
State diagrams, which show how the system reacts to internal and external events.
With this in mind, these graphical diagrams will be used to visually represent the structure of the system being created for the Hotel. Several scenarios will be handled to show how this system would and should react. Coupled with these graphical representations will be another, which will display the overall architecture of the system by linking these subsystems in place.
Types of UML Diagrams being used:
Activity Diagrams:
In the case of Activity Diagrams, the exact purpose of it in the case of the requirements given previously was made to demonstrate the process of how a customer would book for a room in a Hotel Room. To do this, the Microsoft program Visio was used for the reason that it had all the appropriate graphical UML diagrams. From there, the “UML Activity” option was picked to get the necessary parts for the diagram. The requirements given previously, involving the conditions of what to do when a “Single room is full” was also combined to the diagram. Each step was carefully decided and compared with what booking is like in real life hotels. Overall, a graphical representation was created in its place to display what the system would look like in this scenario.
State Chart Diagram:
A state chart diagram is used to model the behavior of a class when faced with outward forces. This is shown here . There are few different notations for state chart diagrams. Those notations are: states, transition, initial state, final state ,synchronization and splitting of the control. In this case a state chart diagram was used to show how each user would interact with the system. This was created using Microsoft Visio using the “UML State Machine” option.
Use Case Diagram:
Use case diagram is summarising all the users and software's details. Use case diagram shows all the functions which software should include and normally it will divide into two parts: actor and use case diagram as it is available at the Appendix part, our actors are administrator and receptionist . For better understanding of the software and its functions more details has been added to the table at the Appendix. All the information which has been added in this use case diagram has been answered by the hotel company.
Class Diagram:
The program Visio was used to create the Class diagram by using the “UML Class” option to demonstrate each of the classes in the system, their properties, methods and relationship to the other classes in systems. All of the properties and methods were decided based on the information provided from the client, this helped to construct the relationship among the classes. Note in the class diagram that the relationships are denoted by a blue line with the exception being where the lines cross each other. Thus, a different color line was chosen so that it would be easier to read.
Sequence Diagram:
A sequence diagram is a kind of communication diagram since it portrays how—and in what order—a gathering of articles cooperates. These diagrams are utilized by programming designers and business experts to comprehend necessities for other requirements or to report a current interaction. Sequence diagrams are here and there known as occasion diagrams or occasion situations. The program Visio was utilized to make the arrangement outline by utilizing the "UML Sequence" choice to show the sequence.
Overall Architecture:
The architectural design of the system is a way in which a graphical representation
is used to show how a software system should be organised according to the given requirements and through abstraction. This is tasked with linking the most high-priority requirements to create a basis for how a program should run. This diagram was constructed using Visio. Lines were coloured differently so that it would be easier to see where a particular line was going.
Appendix
This section will contain the UML diagrams representing each part of the system. Each Diagram was created by realcode4you team members:
