[edit] hardware

changed the description

added NEXT UP label

changed milestone to %Release 1

added ForSprint label

assigned to @steinm01

removed NEXT UP label

changed the description

here some feedback:

i know you @steinm01 are really into functions and generally we could define EVERY class in terms of its role of function. However i think that is problematic because then the classes themselves loose semantic expressiveness themselves. Also it becomes very hard to define when we use the function/role pattern and when not. E.g. we do not have a "software role" or a "specification role"... . So i would say, lets define a class hardware based on its differentia and genus
Material entity is a good genus, maybe we.
i am not sure if "data processing" is a sufficiently wide differentia - i.e. instruments have hardware that record signals. Also data is usually interpreted in terms of digital data - how about analogue signals?
maybe it could be good to think about the class 'hardware' as a superclass for 'computer hardware', 'instrument' 'sensors' etc..?

Then what about:

def. hardware: 
  A material entity which is a whole or part of a system which 
    (1) processes data and 
    (2) may encode data as non-digital signals or vice versa.

for hardware i find the following things on the web (in addition to what you already gathered):

the machines, wiring, and other physical components of a computer or other electronic system.
technical/ physical components of a computer or other electronic system.
physical parts
typically directed by the software to execute any command or instruction

thus I find differentia such as:

physical components
parts of a computer or other electronic systems
typically directed by software (in a computer)
excecutes commands, programming / instructions

with your @steinm01 previous work together i would propose the following:

label: hardware
definition: A material entity which is a whole of part of a computer or electronic system, that executes commands or instructions, to process signals in digital or analogue form.
hasNarrowSyonym: Computer Hardware
comments: Could instantiate subclass computer hardware to accomodate classes like GPU, CPU or keyboard

label: sensor
definition: Hardware which... see discussion in #80

I like the specification of electronic system.
I also thought about the "software" bit for this definition since hardware is often defined as an opposite to software. But I can't really see how we should or would need to do that in our HDO context. Especially because the "software" is always part of the hardware. Be it the state of some modern memory or the wiring of those first "hardware-only" computers from back then.
Nonetheless, I feel unsure with saying that every piece of hardware executes instructions. E.g. power cables, computer cases or tubes for water cooling: Do they count as hardware? They at least don't really execute instructions. My suggestion on the other hand is in that sense maybe too broad. I.e. I can build things into my computer which I would definitely not call hardware. E.g. decorations.
Non-digital data would e.g. be text on a paper but signals/signifiers from the environment are not data. Therefore I would like to stick with something more similar to my last wording ("...may encode data as non-digital signals or vice versa.")
Why would you want to have "computer hardware"? Which system that processes data would you not call a computer?

discussed and changed in meeting on Feb. 9th - moving on to MR

mentioned in issue #80 (closed)

added ready for MR label and removed ForSprint label

added in MR label and removed ready for MR label

mentioned in merge request !38 (merged)

closed with merge request !38 (merged)

mentioned in commit 9d4a9766

[edit] hardware

Designs

Child items ...

Activity