关键词 > Excel代写
Project Release-3 Requirements
发布时间：2023-07-28
Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit
Project Release-3 Requirements
Submission deadline: July 25, 2023
In Release-2, you implemented functionality to create and manage workspace and boards. Your project is now ready to add tasks related features. In this final iteration of your project, you will be developing the following features.
Feature details
Task Management
a. Create tasks: Create tasks in the form of cards. Note that tasks area part of boards and a workspace contains any number of boards.
b. Date field: Create a date field for a task; it is used as due date for the task.
c. Change status of tasks: Allow users to change the status of tasks. For example,a user should be able to move a task from To-Do list to Doing list. Any user who is a part of the workspace can
change the status of the task. Obviously, changes in the status are persistent (i.e., another user should be able to see the changes).
d. Assign member to a task: Allow users to assign a member of the workplace to a task.
Search and filter
a. Search tasks: Search for task cards based on task names. You would have a searchbox on the same page (i.e., board page where you are displaying the tasks in lists).
b. Filter tasks: Filter the tasks based on the due date. You will offer at least three filters.
a. Due today
b. Due in this week
c. Overdue
c. This feature (i.e., Search and Filter) is only required for the frontend. It does not require
backend implementations. In other words, you only need to create the search and filter using the components’ own states, or through react-redux or through any other way you are
managing your components’ states.
Other requirements
a. You are expected to have testcases for the backend with min. 70% line coverage. You need to have testcases for business logic; you may use mocked database objects wherever necessary.
b. Test Driven Development (TDD): You must follow TDD for your backend; the minimum
expectation is two unit testcases per API. Please note that we will observe whether you
follow TDD in its spirit i.e., write test first, and commit the changes before writing code for your APIs.
c. Working CI pipeline (both compile and test stages are passing without any issue).
d. Run DesigniteJava on your backend code. Prepare an Excel sheet where you will analyze each reported smell (all except testability smells) and provide a justification.
o If the identified smell is genuine, you will refactor the smell and write “Refactored” in justification.
o If the identified smell could not be refactored, justify your understanding.
Marking Rubric
|
Task |
Description |
The task is complet ewith at least 70% code coverage |
75% of the task is complet e with test cases |
50% of the task is complet e with test cases |
25% of the task is complet e with test cases |
Neither the task nortest cases are complet e |
|
Create tasks |
API to create tasks |
2 |
1.5 |
1 |
0.5 |
0 |
|
|
Task cards on the UI |
1 |
0.75 |
0.5 |
0.25 |
0 |
|
Date field |
Save the selected date in your database using the API |
1 |
0.75 |
0.5 |
0.25 |
0 |
|
|
Have a date field on the UI to add completion date of a task |
1 |
0.75 |
0.5 |
0.25 |
0 |
|
Assign a task to a member |
API to assign a member to a task |
2 |
1.5 |
1 |
0.5 |
0 |
|
|
Option on the UI to add assignee for a task |
1 |
0.75 |
0.5 |
0.25 |
0 |
|
Change status of tasks |
API for changing the status of tasks. Fore.g., to-do to in progress |
2 |
1.5 |
1 |
0.5 |
0 |
|
|
Option on the UI to change the status of tasks |
1 |
0.75 |
0.5 |
0.25 |
0 |
|
Search for tasks on the board. |
Search box to accept the search keyword and display results on the UI |
2 |
1.5 |
1 |
0.5 |
0 |
|
Filter for tasks |
Filter option on the UI to choose one of the three |
2 |
1.5 |
1 |
0.5 |
0 |
|
|
filters mentioned in feature details section, and display the results. |
|
|
|
|
|
|
Test Driven Developmen t |
TDD process is followed |
2 |
1.5 |
1 |
0.5 |
0 |
|
Working CI pipeline |
Compile and test stages passing without any issues |
2 |
1.5 |
1 |
0.5 |
0 |
|
Smell analysis and refactoring |
List of detected smell along with corresponding action/justificatio n |
2 |
1.5 |
1 |
0.5 |
0 |
Remarks
• In this release, the expectation is not only for you to implement the features, but also to include tests that cover at least 70% of each one.
Delivery Instructions
All the source code related to these features should be in your group’s Gitlab repository before the
deadline. The Excel sheet related to refactored smells should also be present on your Gitlab repository.
