Introduction › Project Management Application

Project Management Application

In this tutorial, you create a basic project management application. In the application, a project consists of a group of tasks, and each task is assigned to one employee. It contains three entities:

• A project entity, with information about projects
• An employee entity, with information about employees
• A task entity, with information about tasks

For the purpose of this tutorial, the model is very simplistic. If you have developed project management systems, you may find parts of the model that you would do differently. Keep in mind that it is only an example.

The following is an entity-attributes diagram of the application:

Look at what this diagram shows about the application. If you have worked with entity-attributes or entity-relations diagrams before, you can see that:

• It tracks projects and projects have tasks
• A project can have more than one task, but a task can only belong to one project
• A task is owned by a project, which means that if the owning project is deleted, you will want to delete all of its tasks

• Employees are assigned to tasks—One employee can be assigned to more than one task, but each task can only have one employee assigned to it
• An employee is not dependent on any particular task, which means that if a task is deleted, the employee assigned to it is not deleted

You can see all of this without having to look at any code or a database schema. This diagram shows useful information, which CA Plex uses to generate the application. You will learn how to create this diagram in the chapter “Diagramming Entity Relationships.”