Example: Proposal for Pet Clinic Management Application

Home » Blog » General » Example: Proposal for Pet Clinic Management Application

1. Goal

The Pet Clinic Management application is supposed to replace manual paper-based management processes in pet clinics, particularly when it comes to appointment scheduling.

2. Product Use

The application is to be used in a standard office environment with network and internet access. The application requires a modern browser (Chrome, Firefox, Safari, Edge, most current version).

3. Product Overview

Use case diagram

4. Product Features

4.1 Actors

4.1.1 Owner

4.1.2 Receptionist

4.1.3 Vet

4.2 Business Processes

4.2.1 Register a new owner

4.2.2 Register a new pet

4.2.3 Manager owners and pets

4.2.4 Make an appointment

4.2.5 Visit pet clinic

5. Product Data

Entity-relationship diagram

6. Product Requirements

6.1 User and Role Management

The application generally is only available after user authentication. There’s no anonymous access to the application. A user and role management system is used for authentication and authorisation.

Each user has only one role.

Users can log in with username and password and are able to change their passwords themselves. Passwords are hashed before being stored in the database.

6.2 Multitenancy

Multiple pet clinics should be able to use the application. Each pet clinic and its respective employees and vets should only be able to access data belonging to that clinic.

7. Design Constraints

The pet clinic application is a server-based web application. It’s supposed to run on standard 2019 office PCs with operating systems such as Windows, macOS, or Linux and a modern browser (see 2.). The application is supposed to completely and conveniently usable with a screen resolution of 1280 x 1024 pixels. Mobile devices such as smartphones are not supported.

8. Performance

The application must not exceed common response times for web applications. A user request will be responded to by the application within 2 seconds at the most.

9. Quality Requirements

PropertyVery goodGoodNormalNot relevant
Functionality
AdequacyX
CorrectnessX
InteroperabilityX
ComplianceX
SecurityX
Reliability
MaturityX
Fault toleranceX
RecoverabilityX
Usability
ComprehensibilityX
LearnabilityX
UsabilityX
Efficiency
Performance development over timeX
Resource consumptionX
Changeability
AnalysabilityX
ModifiabilityX
StabilityX
AudibilityX
Portability
CustomisabilityX
InstallabilityX
ConformityX
ExchangeabilityX

10. User Interface

UI

11. Non-functional Requirements

The application has to ensure secure data transfer. Therefore, the HTTP Secure (HTTPS) protocol has to be used at all times.

12. Technical Product Environment

Technical environment diagram

13. Planing

13.1 Effort and Realisation

MilestoneEffortDone by
1€6,000
2€4,000
Total€10,000

Version: 1.0

About the author: Bjoern
Entrepreneur

Leave a Comment