Design database.

[arupcse]

User

• Can login
• CRUD task
• Mark task as completed.
• Set date to task
• Postpone task
• Mark as "Won't Do".

[shimanbb]

You can apply OOP principle while designing a database. Seek for re-usability, consistency. The design should be manageable, extendable and scalable in the long run. Think about the following:

User
-------------
* Id
- Username
- Password
- IsDeleted
- IsActive
* CreateDate
* UpdateDate
* CreatedBy  (UserId)
* UpdatedBy  (UserId)

Task
-------------
* Id
- Title
- StartDateTime
- EndDateTime
- Assignee (UserId)
- Status (TaskStatusId)
- IsDeleted
* CreateDate
* UpdateDate
* CreatedBy  (UserId)
* UpdatedBy  (UserId)

Status
--------------
* Id
- Name
- Description
- IsDeleted
* CreateDate
* UpdateDate
* CreatedBy  (UserId)
* UpdatedBy  (UserId)

• The '*' marked fields are common across all tables and they are consistent in all. They enables the tracking of every record that is created or updated in the system. The naming of the tables are consistent and meaningful.
• The naming of the fields Assignee, CreatedBy and UpdatedBy are meaningful though everyone of them references the same table.
• The field 'IsDeleted' enables the entities to be deleted softly. But the way of hard deletion is always open.