Scribd
Upload
158 views3 pages

Todo Application (1 Week) : 2.1 Required Tasks

The document outlines requirements for developing a ToDo application over 1 week. It includes: 1. Goals of developing a ToDo application and CLI tool for core functionality. 2. Required stories around authentication, user management, ToDo list management, task management and assignment grading criteria. Stories include creating, editing, deleting and sharing users, ToDo lists and tasks. Project must be submitted to a GitHub repo by September 10th with code that builds without errors or warnings and satisfies required functionalities. Code quality and understanding of concepts are important for receiving full points.

Uploaded by

Жаклин Георгиева
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
158 views3 pages

Todo Application (1 Week) : 2.1 Required Tasks

The document outlines requirements for developing a ToDo application over 1 week. It includes: 1. Goals of developing a ToDo application and CLI tool for core functionality. 2. Required stories around authentication, user management, ToDo list management, task management and assignment grading criteria. Stories include creating, editing, deleting and sharing users, ToDo lists and tasks. Project must be submitted to a GitHub repo by September 10th with code that builds without errors or warnings and satisfies required functionalities. Code quality and understanding of concepts are important for receiving full points.

Uploaded by

Жаклин Георгиева
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

ToDo Application (1 week)

The ToDo application introduces organization in day-to-day tasks. It is a great


performance booster for organizations and individuals, working on multiple projects.

1. Assignment Goals
1. Development of ToDo application for management ToDo lists;
2. Development of machine usable CLI tool for access to core system functionality.

2. Assignment Description
2.1 Required Tasks
Authentication

Storty 1. As a User I need to be able to log into the ToDo application with my
username and password.If this is the first execution of the application and there are
no users in the database I need to be able to log-in with the following user:Username:
adminPassword: adminpass

Story 2. As a User without administrative privileges my access to the Users Management


View needs to be restricted.

Users Management

Story: 3. As a User with administrative privileges I need to be able to access the


Users Management View where I can list all users, create, edit and delete a user.

Story: 4. As a User with administrative privileges I need to be able to create a user


and persist the following information: Id Username Password First Name Last Name Date
of creation Id of the creator Date of last change Id of the user that did the last
change

Story: 5. As a User with administrative privileges I need to be able to delete a user


by Id

Story: 6. As a User with administrative privileges I need to be able to edit a user by


Id by providing the following information: Username Password First Name Last Name Date
of creation and Id of the creator remain unchanged Date of last change and Id of the
user that did the last change are updated automatically

ToDo Lists Management

Story: 7.As a User I need to be able to access the ToDoLists Management View where I
can access all ToDo lists that are created by me or are shared with me -list all ToDo
lists, create, edit and delete a ToDo list.

Story: 8. As a User I need to be able to create a ToDo list and persist the following
information:IdTitleDate of creationId of the creatorDate of last changeId of the user
that did the last change

Story: 9. As a User I need to be able to delete a ToDo list by Id. If the ToDo list is
not created by me (is shared with me by another user) then the delete action removes
the share.
Story: 10. As a User I need to be able to edit a ToDo list by Id by providing the
following information:IdTitle(Date of creation and Id of the creator remain unchanged)
(Date of last change and Id of the user that did the last change are updated
automatically)

Story: 11.As a User I need to be able to share a ToDo list with other users.

Task Management

Story: 12.As a User I need to be able to access the Tasks Management View where I can
access all Tasks from a single ToDo listthat is either created by me or is shared with
me. I should be able to list all Tasks in the ToDo list, create, edit and delete a
Task in the ToDo list.

Story: 13.As a User I need to be able to create a Task in a ToDo list and persist the
following information:IdId of the List (the Id of the ToDo list that the Task belongs
to)TitleDescriptionIsCompleteDate of creationId of the creatorDate of last changeId of
the user that did the last change

Story: 14.As a User I need to be able to delete a Task by Id.

Story: 15.As a User I need to be able to edit a Task by Id by providing the following
information:IdTitleDescriptionIsComplete(Date of creation and Id of the creator remain
unchanged)(Date of last change and Id of the user that did the last change are updated
automatically)

Story: 16.As a User I need to be able to assign a Task to one or more Users in the
system that have access to the ToDo list that the Task belongs to.

Story: 17.As a User I need to be able to complete a Task by Id through a fast access
menu in the Task Management View.

3. Assignment Grading
In all the assignments, writing quality code that builds without warnings or errors,
and then testing the resulting application and iterating until it functions properly
is the goal.Here are the most common reasons assignments receive low points:•Project
does not build.

One or more items in the Required functionalities section was not satisfied.
A fundamental concept was not understood.
Project does not build without warnings.
Code Quality -Your solution is difficult (or impossible) for someone reading
the code to understand due to:
Code is visually sloppy and hard to read (e.g. indentation is not
consistent, etc.).
No meaningful variable, method and class namesoNot following Java code
styleguidesoOver/under used methods, classes, variables, data structures
or code comments.
Assignment is not submitted as per Assignment Submission section below.

4. Assignment Submission
Create a GitHub repo that you have to use through all of the working process. Use
branches and create meaningful commits. Add your teacher as collaborator to your repo.
Deadline: 10.09.2022

You might also like