Homework Help is Here – Start Your Trial Now!
Engineering
Computer Science
Specifications • Use the three-tier architecture (presentation, business, and database) for this program, and store the code for each tier in a separate file. • Use the database file (task_list_db.sqlite) that contains a Task table that stores the tasks. The ID is managed by the table and the user will not supply an ID for any new tasks. When the complete column in the database is set to 1 the task is completed. The database module should have methods to get a list of tasks, add a task, update the status of a task to completed, and delete a task. The business class for a Task will have three public attributes: description, completed, and ID. The constructor for the class will take a parameter for each attribute. The class will override the_str_method and return the description and the output "(DONE!)" if the status is complete. The presentation class will have the following commands with corresponding functions: • The view command will only display tasks that have not been completed. It will call a database function which gets a list of non-completed tasks. • The history command will allow the user to view tasks that have been completed, but not deleted. It will call a database function which returns a list of complete tasks and then displays this list. The add command will add a new task to the database. • The complete command will only mark a task as completed, not delete it from the database. The delete command will remove a task from the database based on the most recently displayed list of tasks. In the presentation class, use a single variable to store the list of tasks retrieved from the database, whether it was retrieved by the history or view methods. Use this task list variable in the delete command so that the user selects a number from the most recently displayed list.

Specifications • Use the three-tier architecture (presentation, business, and database) for this program, and store the code for each tier in a separate file. • Use the database file (task_list_db.sqlite) that contains a Task table that stores the tasks. The ID is managed by the table and the user will not supply an ID for any new tasks. When the complete column in the database is set to 1 the task is completed. The database module should have methods to get a list of tasks, add a task, update the status of a task to completed, and delete a task. The business class for a Task will have three public attributes: description, completed, and ID. The constructor for the class will take a parameter for each attribute. The class will override the_str_method and return the description and the output "(DONE!)" if the status is complete. The presentation class will have the following commands with corresponding functions: • The view command will only display tasks that have not been completed. It will call a database function which gets a list of non-completed tasks. • The history command will allow the user to view tasks that have been completed, but not deleted. It will call a database function which returns a list of complete tasks and then displays this list. The add command will add a new task to the database. • The complete command will only mark a task as completed, not delete it from the database. The delete command will remove a task from the database based on the most recently displayed list of tasks. In the presentation class, use a single variable to store the list of tasks retrieved from the database, whether it was retrieved by the history or view methods. Use this task list variable in the delete command so that the user selects a number from the most recently displayed list.

Database System Concepts
Database System Concepts
7th Edition
ISBN:9780078022159
Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Chapter1: Introduction
Section: Chapter Questions
Problem 1PE
See similar textbooks
icon
Related questions
Question
100%

Please help with this program

Specifications • Use the three-tier architecture (presentation, business, and database) for this program, and store the code for each tier in a separate file. • Use the database file (task_list_db.sqlite) that contains a Task table that stores the tasks. The ID is managed by the table and the user will not supply an ID for any new tasks. When the complete column in the database is set to 1 the task is completed. The database module should have methods to get a list of tasks, add a task, update the status of a task to completed, and delete a task. The business class for a Task will have three public attributes: description, completed, and ID. The constructor for the class will take a parameter for each attribute. The class will override the_str__method and return the description and the output "(DONE!)" if the status is complete. The presentation class will have the following commands with corresponding functions: The view command will only display tasks that have not been completed. It will call a database function which gets a list of non-completed tasks. The history command will allow the user to view tasks that have been completed, but not deleted. It wil1 call a database function which returns a list of complete tasks and then displays this list. The add command will add a new task to the database. The complete command will only mark a task as completed, not delete it from the database. The delete command will remove a task from the database based on the most recently displayed list of tasks. In the presentation class, use a single variable to store the list of tasks retrieved from the database, whether it was retrieved by the history or view methods. Use this task list variable in the delete command so that the user selects a number from the most recently displayed list.
Transcribed Image Text:Specifications • Use the three-tier architecture (presentation, business, and database) for this program, and store the code for each tier in a separate file. • Use the database file (task_list_db.sqlite) that contains a Task table that stores the tasks. The ID is managed by the table and the user will not supply an ID for any new tasks. When the complete column in the database is set to 1 the task is completed. The database module should have methods to get a list of tasks, add a task, update the status of a task to completed, and delete a task. The business class for a Task will have three public attributes: description, completed, and ID. The constructor for the class will take a parameter for each attribute. The class will override the_str__method and return the description and the output "(DONE!)" if the status is complete. The presentation class will have the following commands with corresponding functions: The view command will only display tasks that have not been completed. It will call a database function which gets a list of non-completed tasks. The history command will allow the user to view tasks that have been completed, but not deleted. It wil1 call a database function which returns a list of complete tasks and then displays this list. The add command will add a new task to the database. The complete command will only mark a task as completed, not delete it from the database. The delete command will remove a task from the database based on the most recently displayed list of tasks. In the presentation class, use a single variable to store the list of tasks retrieved from the database, whether it was retrieved by the history or view methods. Use this task list variable in the delete command so that the user selects a number from the most recently displayed list.
Expert Solution
trending now

Trending now

This is a popular solution!

steps

Step by step

Solved in 2 steps

SEE SOLUTIONCheck out a sample Q&A here
Blurred answer
Knowledge Booster
Linux
Learn more about
Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.
Recommended textbooks for you
Database System Concepts
Database System Concepts
Computer Science
ISBN:
9780078022159
Author:
Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan
Publisher:
McGraw-Hill Education
Starting Out with Python (4th Edition)
Starting Out with Python (4th Edition)
Computer Science
ISBN:
9780134444321
Author:
Tony Gaddis
Publisher:
PEARSON
Digital Fundamentals (11th Edition)
Digital Fundamentals (11th Edition)
Computer Science
ISBN:
9780132737968
Author:
Thomas L. Floyd
Publisher:
PEARSON
C How to Program (8th Edition)
C How to Program (8th Edition)
Computer Science
ISBN:
9780133976892
Author:
Paul J. Deitel, Harvey Deitel
Publisher:
PEARSON
Database Systems: Design, Implementation, & Manag…
Database Systems: Design, Implementation, & Manag…
Computer Science
ISBN:
9781337627900
Author:
Carlos Coronel, Steven Morris
Publisher:
Cengage Learning
Programmable Logic Controllers
Programmable Logic Controllers
Computer Science
ISBN:
9780073373843
Author:
Frank D. Petruzella
Publisher:
McGraw-Hill Education
SEE MORE TEXTBOOKS