At the end of this specific task, students should be able to:• Create and work with Loops• Handle and manipulate strings • (Learning Units 4 and 5).It is good practice to leave your main branch as your long live branch, this means that the code on this branch is always in perfect working order and tested. We make use of feature branches in order to ensure that any code we push to GitHub does not break our main branch. You can create a feature branch by running the following command.git checkout -b KhanbanTasks (you can use any branch name)** You are welcome to make use of GitHub desktop or your IDE to push code to GitHub if you are not comfortable with using the command line.You can now add the following functionality to your application:1. The users should only be able to add tasks to the application if they have logged in successfully.2. The applications must display the following welcome message: “Welcome to EasyKanban”.3. The user should then be able to choose one of the following features from a numeric menu:a. Option 1) Add tasks21; 22; 23 2022b. Option 2) Show report - this feature is still in development and should display the following message: “Coming Soon”.c. Option 3) Quit4. The application should run until the users selects quit to exit. 5. Users should define how many tasks they wish to enter when the application starts, the application should allow the user to enter only the set number of tasks. 6. Each task should contain the following information: 21: 22: 232027assigned to the task's name. The ID should bedisplayed in all caps:AD:0:INATask StatusThe user should be given a menu to select thefollowing task statuses from:To DoDoneDoing1. The full details of each task should be displaved on the screen (using JOptionPane) after ithas been entered and should show all the information requested in the table above in thefollowing order: Task Status, Developer Details, Task Number, Task Name, TaskDescription, Task ID and Duration;7. The total number of hours across all tasks should be accumulated and displayed once allthe tasks has been entered.Create a Task class that contains the following messages:Method FunctionalityMethod NameThis method ensures that the task descriptionBoolean: checkTaskDescription()is not more than 50 characters.This method creates and returns the taskIDString: createTaskID()This method returns the task full task detailsString: printTaskDetails()of each task.This method returns the total combined hoursInt: returnTotalHours()of all entered tasks.8.Please use the following the following test data to create unit tests.Test Data:2Num TasksTest Data for Task 1"Login Feature"Task NameAuto generated.Task Number"Create Login to authenticate users"Task Description loper DetailsTask DurationRobyn HarrisonTaskID8hrsTask StatusAuto generatedTo DoTest Data for Task 2Task Name"Add Task Feature"Task NumberAuto generated.Task Description"Create Add Task feature to add task users"Developer DetailsMike SmithTask Duration10hrsTaskIDAuto generatedTask StatusDoing9.Create the following unit tests:Test AssertEquals:Test for both success and failureTask Description should not be moreThe system should return:than 50 CharactersSuccess"Task successfully captured"Failure:"Please enter a task description of less than 50characters"They system should return:TaskID is correctAD:1:BYN When supplied with the data from Testcase 1The system should test the remainder of the TaksIDsin a loop (refer to video):CR:0:IKE, CR:1:ARD, CR:2:THA, CR:3:NDTotal Hours Correctly accumulated inAdditional test data:loop1)Test Data for Task1 and Task2.2: Num Tasks: 5, Durations: 10,12,55,11,1

The class Task is provided in the next step

At the end of this specific task, students should be able to: • Create and work with Loops • Handle and manipulate strings • (Learning Units 4 and 5). It is good practice to leave your main branch as your long live branch, this means that the code on this branch is always in perfect working order and tested. We make use of feature branches in order to ensure that any code we push to GitHub does not break our main branch. You can create a feature branch by running the following command. git checkout -b KhanbanTasks (you can use any branch name) ** You are welcome to make use of GitHub desktop or your IDE to push code to GitHub if you are not comfortable with using the command line. You can now add the following functionality to your application: 1. The users should only be able to add tasks to the application if they have logged in successfully. 2. The applications must display the following welcome message: “Welcome to EasyKanban”. 3. The user should then be able to choose one of the following features from a numeric menu: a. Option 1) Add tasks 21; 22; 23 2022 b. Option 2) Show report - this feature is still in development and should display the following message: “Coming Soon”. c. Option 3) Quit 4. The application should run until the users selects quit to exit. 5. Users should define how many tasks they wish to enter when the application starts, the application should allow the user to enter only the set number of tasks. 6. Each task should contain the following information

Computer Networking: A Top-Down Approach (7th Edition)

7th Edition

ISBN:9780133594140

Author:James Kurose, Keith Ross

Publisher:James Kurose, Keith Ross

Chapter1: Computer Networks And The Internet

Section: Chapter Questions

Problem R1RQ: What is the difference between a host and an end system? List several different types of end...

See similar textbooks

Related questions

Question

At the end of this specific task, students should be able to:
• Create and work with Loops
• Handle and manipulate strings
• (Learning Units 4 and 5).
It is good practice to leave your main branch as your long live branch, this means that the code on
this branch is always in perfect working order and tested. We make use of feature branches in
order to ensure that any code we push to GitHub does not break our main branch. You can create
a feature branch by running the following command.
git checkout -b KhanbanTasks (you can use any branch name)
** You are welcome to make use of GitHub desktop or your IDE to push code to GitHub if you
are not comfortable with using the command line.
You can now add the following functionality to your application:
1. The users should only be able to add tasks to the application if they have logged in
successfully.
2. The applications must display the following welcome message: “Welcome to EasyKanban”.
3. The user should then be able to choose one of the following features from a numeric menu:
a. Option 1) Add tasks
21; 22; 23 2022
b. Option 2) Show report - this feature is still in development and should display the
following message: “Coming Soon”.
c. Option 3) Quit
4. The application should run until the users selects quit to exit.
5. Users should define how many tasks they wish to enter when the application starts, the
application should allow the user to enter only the set number of tasks.
6. Each task should contain the following information: