You are working at an enterprise solution company. A new client approaches you for an ERP software they need for the administration of their daily operations. Naturally, you have multiple complex solutions for this job.
The problem is that the client is extremely suspicious about cloud technologies and the web in general. They say that what is on the net, or just on a computer that is connected to the Internet, is already compromised, and at least four countries' secret services come and go there regularly.
So they want to see a solution that is super secure: a short and clean codebase that works on local files, strictly on offline computers. It is your team's job to create such an application from scratch.
They require a highly modularized structure where the code for different content areas are separated, and every user and file I/O operations go through one and only one channel. You decide to create a variant of the MVC (model-view-controller) architecture for terminal and local data files.
As the client wouldn't provide any real data, only the general structure, you had to create some dummy data for the development.
- modular design, MVC pattern
- searching, filtering, and transforming data
- clean code
- conform to requirements
- collaborate with your team
-
Implement the CRM module with basic and special operations.
- Once the CRM module is selected, choosing option 1 will ask the user to type the name, email and subscribed status for a new customer. After the last field is introduced a new customer is introduced with an random id.
- Once the CRM module is selected, choosing option 2 will print all the customers.
- Once the CRM module is selected, choosing option 3 will ask the user for the id of a customer. If the id belongs to an existent customer then the user will enter new values for the name, email and subscribe status. Once the last field is entered, the customer fields are updated with the given values.
- Once the CRM module is selected, choosing option 4 will ask the user for the id of a customer. If the id belongs to an existent customer then that it will be deleted from the database.
- (5) Get the emails of subscribed customers.
-
Implement the Sales module with basic and special operations.
- (1-4) Provide basic CRUD operations.
- (5) Get the transaction that made the biggest revenue.
- (6) Get the product that made the biggest revenue altogether.
- (7) Count number of transactions between two given dates.
- (8) Sum the price of transactions between two given dates.
-
Implement the HR module with basic and special operations.
- (1-4) Provide basic CRUD operations.
- (5) Return the names of the oldest and the youngest employees as a tuple.
- (6) Return the average age of employees.
- (7) Return the names of employees having birthdays within the two weeks starting from the given date.
- (8) Return the number of employees with at least the given clearance level.
- (9) Return the number of employees per department in a dictionary (like
{'dep1': 5, 'dep2': 11}).
- You mustn't use any external modules except for those already in the files.
- Only model files import
data_manager, and model files don't import the view at all.
- This project contains many similar requirements, try to unite as many common parts as possible!
- Do not spend much time on input checking. This time it is not a problem if a badly formatted data breaks your code.
- In the model's directory for each area (crm, hr, sales)
you'll find two files.
One is a CSV data file (i.e.
crm.csv) that holds some example records and the other one is a model's module (i.e.crm.py) in which you'll implement your CRUD functions. You'll find an explanation to the data file contents (what are the columns and what type of data they should store) in the docstring of the model's module (you'll find the docstring at the start of the file).
- MVC intro
- About Python modules (until the section "Python Packages")
- File handling
- Magic numbers
- Clean code