Professional designers' adaptations of IEC 61499 to their individual work practices

The IEC 61499 standard enables a number solutions to the same application development problem, and this can result in components that are incompatible even though they are standards based. IEC 61499 underpins a vision for an open object-oriented knowledge economy, so the application of component-based software development principles needs further research. Such principles are not broadly used in the industry, so our goal is to understand how industrial practice needs to be changed. What are the practices that need to be replaced before the object-oriented, component-based paradigm can be accepted? We organized an intensive course on IEC 61499, where professionals and researchers automated a process in teams. Our results show that the background of a designer has a strong impact on the choice of the problem solving approach, and that this can prevent the use of many new and progressive features in IEC 61499

[1]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[2]  David J. Buttler,et al.  Encyclopedia of Data Warehousing and Mining Second Edition , 2008 .

[3]  KruchtenPhilippe.  The 4+1 View Model of Architecture , 1995 .

[4]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[5]  Kleanthis Thramboulidis,et al.  Model-integrated mechatronics - toward a new paradigm in the development of manufacturing systems , 2005, IEEE Transactions on Industrial Informatics.

[6]  Klaus Turowski,et al.  Modularity of the Software Industry: A Model for the Use of Standards and Alternative Coordination Mechanisms , 2005, Int. J. IT Stand. Stand. Res..

[7]  Kleanthis Thramboulidis,et al.  Real-time Java in control and automation: a model driven development approach , 2005, 2005 IEEE Conference on Emerging Technologies and Factory Automation.

[8]  Richard Baskerville,et al.  Amethodical systems development: the deferred meaning of systems development methods , 2000 .

[9]  Luca Ferrarini,et al.  IEC 61499 implementation of a modular control model for manufacturing systems , 2005, 2005 IEEE Conference on Emerging Technologies and Factory Automation.

[10]  Judy McKay,et al.  The dual imperatives of action research , 2001, Inf. Technol. People.

[11]  Lucas D. Introna,et al.  Against method-ism: Exploring the limits of method , 1997, Inf. Technol. People.

[12]  Kent L. Beck,et al.  Embracing Change with Extreme Programming , 1999, Computer.

[13]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

[14]  David E. Avison,et al.  The fiction of methodological development: a field study of information systems development , 1999, Inf. Technol. People.

[15]  Bruce Powel Douglass,et al.  Real Time UML: Advances in the UML for Real-Time Systems (3rd Edition) , 2004 .

[16]  Alex M. Andrew.  Modelling Control Systems using IEC 61499: Applying function blocks to distributed systems , 2002 .

[17]  Enid Mumford,et al.  Advice for an action researcher , 2001, Inf. Technol. People.

[18]  T. Oko.  Interviewing as Qualitative Research: A Guide for Researchers in Education and the Social Sciences. , 1992 .

[19]  Valeriy Vyatkin,et al.  OOONEIDA: an open, object-oriented knowledge economy for intelligent industrial automation , 2005, IEEE Transactions on Industrial Informatics.

[20]  Björn Lundell,et al.  2G.">On the adaptation of Grounded Theory procedures: insights from the evolution of the 2G , 2005, Inf. Technol. People.

[21]  Johann Rost.  Software Engineering Theory in Practice , 2005, IEEE Softw..

[22]  Lars Mathiassen,et al.  Collaborative Practice Research , 2000, Scand. J. Inf. Syst..

[23]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[24]  S. Sierla,et al.  Control software reuse strategies with IEC 61499 , 2005, 2005 IEEE Conference on Emerging Technologies and Factory Automation.