Have any queries? send us an email
Using the provided case study, develop a solution from a software architect’s perspective that includes the following:
Produce a use case diagram to model the functional requirements from the scenario narrative.
Showing actors and the use cases they perform.
Use inheritance where necessary of both use cases and actors.
Use of <>and <> where necessary.
Use house style model to document one primary use case.
Produce a class diagram to model the system structure you propose for your potential solution. Decouple as much as possible with Boundary, Control and Entity classes. Consider a design pattern for this (In your commentary, justify the use of the chosen design pattern, on the other hand, if you do not use it, justify why). This should include:
Detailed classes with all key variables/attributes and datatypes with access modifiers (private, public or protected) clearly shown in adherence to encapsulation principal of OOP and multiplicities of the relationships.
Procedures or functions with (parameters and their datatypes shown) as well as return type for the class functions. (see diagram below)
Use of class relationships (e.g. dependency association, aggregation, composition and inheritance).
Consider the use of design patterns in your proposed solution.