QuickSoft Associates
Memorandum
| To: |
Python Development Team |
| From: |
QuickSoft Principal |
| Subject: |
New contract – Auto repair records system |
I’m glad that you will be able to focus on the contract we
landed this week with Dermico Auto to develop a maintenance records
system. This is a small auto repair shop that is preparing
for growth. The mechanics will have access to computers on
the floor and they need a car’s maintenance history attached
to each car that comes into the shop.
This isn’t a huge project since we won’t be doing their
billing system. But this could be a profitable product for
us in this niche. We are lucky to have your expertise on the
project. Welcome aboard!
The Auto Repair Records System will allow office personnel and mechanics to enter data about customers including name, address, contact info, car type(s) and maintenance needs and operations. The data will be stored (persist) so that when the car returns, the mechanic can view it.
I included notes below on technical requirements while I am thinking of them... in no particular order.
Technical Guidelines
- Your solution must be object oriented. Our company does all new development using objects, and only maintains legacy products with a functional architecture.
- Decouple data persistence from the business logic. This gives us increased flexibility for future deployment of your program.
- Each module, class, function and method must have its own docstring.
- Each section of code must be clearly marked with both the author's name and the reviewer's name.
- Testing from the console is not acceptable for this project. You must write a separate testing class.
Your four deliverables will be detailed in subsequent memorandums; they are just listed here:
Deliverable 1. Requirements Document
Use Cases
System Requirements
Choice of GUI library
Choice of data persistence
Deliverable 2. Implement one use case
Deliverable 3. Implement a second use case
Deliverable 4. Implement all use cases and system requirements
Please submit your deliverables by email to your manager by 5:00pm on the date due.
Clearly state "Python Team X Deliverable Y" in the subject line.
Please cc: each member of your team, so that when
your manager replies
all the team members will all see the manager's feedback.
