The following use case diagram shows the requirement for the dashboard, which is nicknamed Bloggest:

The actors are the User and Administrator of Bloggest. It has the following use cases:

• Login: This use case is required to authenticate users so that each article author can be uniquely identified.
• Add Article: This use case is where a user creates a new article in the Bloggest system. It requires the user to be authenticated.
• Edit Article: This use case is where a user edits an article he/she created or an administrator edits an article created by any user of the Bloggest system. It requires the user/administrator to be authenticated.

• Delete Article: This use case is where a user deletes an article he/she created or an administrator deletes an article created by any user of the Bloggest system. It requires the user/administrator to be authenticated.
• List Articles: This use case is where any user of the Bloggest system can list all the articles available in the system. This step doesn't require authentication and is public to everyone.
• Search Articles: This use case is where any user of the Bloggest system can search for articles available in the system. This step doesn't require authentication and is public to everyone.
• Show Article: This use case is where any user of the Bloggest system can view a particular article of interest. This step doesn't require authentication and is public to everyone.
• Logout: This use case is where a logged-in user can log out of the Bloggest system.