Skip to content
Tiago edited this page Sep 8, 2023 · 5 revisions

Welcome to the la-vie-spring Wiki

Introduction

Welcome to the home page of the la-vie-spring project. This project is a Minimum Viable Product (MVP) designed to provide essential features for managing a Psychology Clinic. Created by a professional with dual expertise in Psychology and Software Development, this project aims to focus on the most crucial aspects of clinic management software, considering constraints like manpower and time.

Core Features

The project aims to implement two fundamental domains of features:

  1. Therapy Progress Notes Management for Psychologists: Enables Psychologists to document each therapy session in a secure, persistent manner.

  2. Administration Control: System Administrators have full control over user management, including the creation, update, and deletion of Psychologists and Client data.

For more details on each feature domain, please visit the linked Wiki pages below.

Wiki Contents

  1. The Story: A comprehensive explanation of the rationale behind this project, its scope, and the essential domains of features.

  2. Functional Requirements: Detailed enumeration of what the software is intended to do.

  3. Non-Functional Requirements: Specifies how well the system performs its functions, such as performance, security, and other non-functional aspects.

  4. Business Rules: The logic and constraints that define the behavior of the software and its components.

  5. UML Class Diagram: A visual representation of the system architecture.

Future Scope

While the project is currently designed as an MVP, there are numerous additional features and improvements that could be incorporated. These include encrypted Therapy Notes, appointment scheduling, automated notifications, payment systems, and more.

Limitations and Caveats

  • Data Security: At present, the encryption of Therapy Notes is beyond the scope of this MVP due to limited resources.

  • Administrator Role: The System Administrators currently have full control over the system, which may require reevaluation and changes in subsequent versions.

To understand the limitations and the decision-making process, please refer to The Story.