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.
Chapter2: Database Design Fundamentals
Section: Chapter Questions
Problem 11RQ
Related questions
Question
100%
Please help with this program
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
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
This is a popular solution!
Trending now
This is a popular solution!
Step by step
Solved in 2 steps
Knowledge Booster
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
A Guide to SQL
Computer Science
ISBN:
9781111527273
Author:
Philip J. Pratt
Publisher:
Course Technology Ptr
A Guide to SQL
Computer Science
ISBN:
9781111527273
Author:
Philip J. Pratt
Publisher:
Course Technology Ptr