Assignment 1-Business Rules and Conceptual Model Fix\'em Equipment Maintenance G
ID: 3744904 • Letter: A
Question
Assignment 1-Business Rules and Conceptual Model Fix'em Equipment Maintenance Group LLC. You have a technical manger role in your company and your scheduling is not very efficient because there is no way to understand how many a skills and what kind of skills they have therefore you need to have new scheduling solution that shows people with their skills Your business rules are very clear; 1.) The company has 35 technical people and some of them have multiple skills 2.) The company also has 300+ tools and equipment for technical people that is required to perform their job in field. 3.)Explanation / Answer
I assume you need Design for the given scenario. Please feel free to comment if not. Also, please rate the answer if you find it helpful.
1. Company has technical people. So we need an entity named TechnicalPeople. So, the entity is as follows.
TechnicalPeople(Id, Name, Phone, ..... , Other Employee Related Attributes)
2. Skills are usually a limited set. Lets consider this as a master table for skills and have another entity for this. This entity can be optional as well. Just putting my views here.
Skill(Name, Type)
3, Since an employee can multiple skills, we need to have a employee-skill mapping table. Be noted that, we can't store multiple skills in a single field in the employee table since that violates the 1st Normal Form of Database rules. Also, having a separate mapping table allows the company/application can perform search for employees based on specific skills.
So, an entity or this can be written as..
EmployeeSkills(EmployeeID, Skill, Level)
EmployeeID is a foriegn key which refers to ID of the Employee Entity and Skills is another foreign key which refers to name of the Skill table. Level can be the degree of expertise in the skill (1-10).
4. We also need a separate entity for Tools
Tools(Name, Type, .........Other auxiliary attributes)
5. Own business rules based on my views.
Company might want to maintain the tool utilization/usage so that they can be allocated properly. So we can have another entity (transactional) which maintains the tool usage.
ToolUsage(EmployeeID, Toolname, StartTime, EndTime)
EmployeeID is a foriegnkey which refers to ID of Employee entity and Toolname is a foreignkey which refers to name of the Tool Entity.
Similarly, company might want to maintain the status of employee (regarding his occupancy of work) to schedule his/her next work. So, we can have one more entity (transactional) for this.
EmployeeStatus(EmployeeID, Status, WorkName, StartTime, EndTime)
Conclusion
Since this concept is around finding/scheduling technical people based on their skill, company can easily perform a search for specific skills and get list of employees, Also, they can make use of EmployeeStatus to check the availability of specific employee to schedule next work for them.