In one of my experieces developing a software engineering approach for my company, I established in the standards that the programmers hired for a project, had to work on the user manual and graphical user interfaces before knowing much about the software solution and absolutely no code writen. The idea was the the programmers familiar with what they write are the worth candidates to write user communication systems such as user manuals and user interfaces. Much of the users interface engineering was defined in advance by the software engineering team in contact with the customers while defining the set of requirement specification documents.
In an age of globalization and rapid changes through scientific progress, two of our societies' (and economies') main concerns are to satisfy the needs and wishes of the individual and to save precious resources. Cloud computing caters to both of these.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.