UML Designs and OOP considerations

 

Task 2 UML Designs and OOP considerations (Group work)        10 marks 

The following shows the UML diagram hat will be used in making the application function as per the user requirements.  

The diagram shows the diagram that will be used in making the application for the hospital 

Factory design pattern is very common in many programing languages including C#, Java. It is one of the best design patterns for creating objects. As you can see in the UML diagram, we use Factory design pattern as the system requires as to create many objects. For example, we need to create patients and staffs. Both the patient and the staff objects pass information to the PatientFactory and the StaffFactory respectively.  

 

Although we did not use in our system, builder design patterns are also can be beneficial in this system. This is because builder pattern builds complicated objects by Appling simple objects one by one methods. It is believed one of the required methods to create objects.  

 

 

 

 

 

 

 

Task 3 Implementing the technical Solution (Group work)  20 marks 

C# is an Object-oriented programming language that can be used to make desktop applications, and it is commonly known for Windows Form applications. It is an in-built library that gives the developer the ability to develop event-driven applications. These are applications that whose operations are triggered by invoking a given event in the application. In this project, such application will be built based on an in-built database system and the events that will be provided to trigger the application’s running.  

 

We build the system based on enterprise visual studio 2019, and the database we use is inbuilt database. We make the username and password for the system to be generated by the system. Which is Username: johndoe and password: password.  For more information, the application can be run and tested.  

 

Task 4 Testing (Group work) 10 marks 

 

Conclusion 

It is always advisable to adhere to a given procedure when developing software applications to ensure quality software and ensure that the software is relevant to what it was intended for. This is a professional practice that should be addressed with professionalism as illustrated in the sections above.