Industrial robots like FANUC, or for our purposes 'a robot", is described by the roboť's identification number and sensor type. Robots need to be maintained regularly, meaning that a robot will go for maintenance many times, and a maintenance is associated with a robot. Maintenance will keep information like the maintenance number, the date of maintenance and the cost for that maintenance effort. For proper maintenance you may use many parts, and a part may be used for many maintenances. The problem here is that a certain part may be use many times in different maintenance efforts: this relate to quantity information for a certain part. The problem is then where must we store this attribute quantity: in the class maintenance or class part? The solution suggested is to create an association class with the attribute quantity. Parts will be described by the part number, price and status. Maintenance can be very specialised when it comes to the vision system and the force system maintenance. Special attention for the vision system will be the video camera and for the force system the strain gauge, described by its identification number. A supplier may supply many robots, but a robot is supplied by a supplier. The supplier is described by its identification number and name. A robot consists of two CPU's, and a motherboard. The CPU is described by the processor name and speed. These CPU's will be mounted on a motherboard, meaning a robot also consist of a motherboard, described by its chipset name and micro controller identification.
Industrial robots like FANUC, or for our purposes 'a robot", is described by the roboť's identification number and sensor type. Robots need to be maintained regularly, meaning that a robot will go for maintenance many times, and a maintenance is associated with a robot. Maintenance will keep information like the maintenance number, the date of maintenance and the cost for that maintenance effort. For proper maintenance you may use many parts, and a part may be used for many maintenances. The problem here is that a certain part may be use many times in different maintenance efforts: this relate to quantity information for a certain part. The problem is then where must we store this attribute quantity: in the class maintenance or class part? The solution suggested is to create an association class with the attribute quantity. Parts will be described by the part number, price and status. Maintenance can be very specialised when it comes to the vision system and the force system maintenance. Special attention for the vision system will be the video camera and for the force system the strain gauge, described by its identification number. A supplier may supply many robots, but a robot is supplied by a supplier. The supplier is described by its identification number and name. A robot consists of two CPU's, and a motherboard. The CPU is described by the processor name and speed. These CPU's will be mounted on a motherboard, meaning a robot also consist of a motherboard, described by its chipset name and micro controller identification.
Principles of Information Systems (MindTap Course List)
12th Edition
ISBN:9781285867168
Author:Ralph Stair, George Reynolds
Publisher:Ralph Stair, George Reynolds
Chapter1: An Introduction To Information Systems
Section: Chapter Questions
Problem 4PSE
Related questions
Question
1. Identify all the relationships/business rules based on the below abstract.
Transcribed Image Text:Industrial robots like FANUC, or for our purposes 'a robot', is described by the robot's identification number and
sensor type. Robots need to be maintained regularly, meaning that a robot will go for maintenance many times,
and a maintenance is associated with a robot. Maintenance will keep information like the maintenance number,
the date of maintenance and the cost for that maintenance effort. For proper maintenance you may use many
parts, and a part may be used for many maintenances. The problem here is that a certain part may be use many
times in different maintenance efforts: this relate to quantity information for a certain part. The problem is then
where must we store this attribute quantity: in the class maintenance or class part? The solution suggested is to
create an association class with the attribute quantity. Parts will be described by the part number, price and
status.
Maintenance can be very specialised when it comes to the vision system and the force system maintenance.
Special attention for the vision system will be the video camera and for the force system the strain gauge,
described by its identification number.
A supplier may supply many robots, but a robot is supplied by a supplier. The supplier is described by its
identification number and name.
A robot consists of two CPU's, and a motherboard. The CPU is described by the processor name and speed.
These CPU's will be mounted on a motherboard, meaning a robot also consist of a motherboard, described by its
chipset name and micro controller identification.
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 with 2 images
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
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781285867168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Management Of Information Security
Computer Science
ISBN:
9781337405713
Author:
WHITMAN, Michael.
Publisher:
Cengage Learning,
Principles of Information Systems (MindTap Course…
Computer Science
ISBN:
9781285867168
Author:
Ralph Stair, George Reynolds
Publisher:
Cengage Learning
Management Of Information Security
Computer Science
ISBN:
9781337405713
Author:
WHITMAN, Michael.
Publisher:
Cengage Learning,