The Inspector Pool application is built on a core use case and the opportunity to automate a common bottleneck in the process: report generation. Below is the driving use case scenario with the area of opportunity, followed by the use case with the solution, and an architecture overview.
Use Case:
The real world presents multiple pool inspection use cases, with the following identified as a common scenario representing many aspects, including the time-consuming process of manually creating inspection reports.
Sequence Diagrams are used to illustrate the use case.
Basic Use Case Scenario
- Scenario: A requester contacts a Pool Inspector for an inspection. The inspector captures all necessary details, performs the inspection, and compiles the information into a formal Pool Inspection Report, which is then shared back to the requester.
Sequence diagram for the manual inspection process.
- Point of Opportunity: Generating the inspection report requires compiling all details into a formal document, which can take hours to days depending on the inspector’s resources and skills.
Use Case with Inspector Pool Solution Applied
Sequence diagram with Inspector Pool implemented.
- Objective Achieved: Streamlined the process, and the generation of the inspection report is accomplished with just a click and immediately ready for review.
Architecture Overview
Inspector Pool is designed for simplicity and offline use. The following illustrates a general and highlevel overview of the architecture.
