Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: THEend8_
COMP1046 Object Oriented Programming
In Assignment Part 2, OO Programming, you will work individually to implement a computer part store in Python. You will implement the classes and relationships that you designed in your UML diagram that you developed in Assignment Part 1, OO Design. while you are programming, you may find that parts of your UML design need to change. Please update your UML diagram to reflect the changes that you have made to your code. Your project, including your updated UML diagram, are due for submission in week 12.
If you are unsure about any instructions in this document, please ask your lecturer to explain.
Please open the provided folder in Visual Studio Code so that your Explorer tab looks like the red box in the screenshot below. This ensures that the database.csv file is at the top-level of the project – not inside a subfolder.You will write your program in “computer_shop.py”. You will write a unittest or pytest for the PartList class in “test_driver.py”. Your PartList will need to load in the computer parts lists in “database.csv”. “TODO How To Start.txt” contains a reminder of the requirements and tasks that you need to complete.
Please ensure you do the following while writing your code. DO NOT wait until the end of the project to start these things. Do the following throughout the project while writing each class and each method.
Please complete the following tasks to complete the assignment:
Please provide a descriptive docstring on the first line of each of your classes and methods. Docstrings are written in
”’triple quotes”’ on the first line inside a class or method, such as:
class ComputerPart(metaclass = abc.ABCMeta):
”’ The abstract ComputerPart class is the superclass for other ComputerPart types.
”’
def __init__(self, name, price):
”’Initialises name and price. Called by subclasses using super().__init__()
”’
pass
#TODO initialise name and price
Document your code as you go, not all at the end. Write a brief docstring about the one thing that the method is supposed to do before you write the code. Refer to that docstring to remind yourself of the problem you need to solve or the code you need to write. This helps maintain focus when implementing the method and should stop you from making it do more than the one thing that the docstring says it should do.