javadch / jenplane Goto Github PK

• architectural redesign to hexagonal design
• rewriting the backend with fast API (issues with flask, auth, performance, async)
• split the backend layers
• persistence layer to work with MongoDB and GraphDB, configurable via a config file
• documentation

Each user may have access to multiple projects and/or organizations having different roles. such as admin, contributor or member.

• member can only see the resources without being able to edit, create, or delete the resource or sub-resources (for example an organization member can see the organization info, the projects info and the plans, but is not able to edit, delete or add anything)
• contributor: can edit the resource itself as well as create/delete/edit/lock/unlock sub-resources.
• admin: can perform any operation on any resource. For example, an organization admin can lock the organization or a specific project in that organization.

An authorized user can create a new organization.
Basic data are: short name, full name, country of origin, description, logo, address, email, phone,

• no duplicate short nad full name is accepted.
• no duplicate email address is accepted

The system should have a default sysAdmin with a default password so that after installation/deployment of the application, the user can start managing the application.

A prjAdmin is able to:

• edit the project's data (short name, full name, description)
• lock/unlock the project
• invite a user to be member or contributor of the project (member can view, contributor can view and edit)
• members and contributors of the parent organization are automatically members and contributors to the project. this information is displayed at the project management dashboard. The prjAdmin has the right to revoke those permissions from the project.

• Sign up, sign in, log out
• user can receive a role/access level
• a user can be disables/enabled

A sysAdmin should be able to:

• create a new organization
• make a user the admin of an organization or detach the user from the organization
• lock/unlock an existing organization: No one is able to operate on the organization
• delete an organization: the organization and all its projects are deleted from the system
• approve user registrations
• block/unblock users
• edit data or organizations and users

an orgAdmin is able to:

• edit the organization's data (short name, full name, description, address, logo, phone, email, etc)
• lock/unlock the organization
• create/edit/delete projects in the organization
• invite a user to be member or contributor of the organization (member can view, contributor can view and edit)

The overall architecture, components, UI, layout, DB, and other important elements should be put together and tested so that the features can be developed.
The result must be demonstrated on the remote server.

An authorized user can create a new project.

• Basic data are: short name, full name, description, logo
• Each project belongs to one and only one organization
• no duplicate short nad full name in any organization is accepted.
• user assigns a specific process template/version to the project (from the process repository)
• A visual process design canvas is rendered based on the process template
• User can interact with the canvas to change/customize the process. The changes do not affect the process template but are stored separately in the process instance repository as a process instance. This repository can (and is desired) to be the app's DB (MongoDB)