Advertisement

A Dependable Open Platform for Industrial Robotics – A Case Study

  • Goran Mustapić
  • Johan Andersson
  • Christer Norström
  • Anders Wall
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3069)

Abstract

Industrial robots are complex systems with strict real time, reliability, availability, and safety requirements. Robot controllers are the basic components of the product-line architecture of these systems. They are complex real time computers which control the mechanical arms of a robot. By their nature, robot controllers are generic and open computer systems, because to be useful, they must be programmable by end-users. This is typically done by using software configuration parameters and a domain and vendor-specific programming language. For some purposes, this may not be sufficient. A means of adding low-level software extensions to the robot controller, basically extending its base software platform is needed when, for example, a third party wants to add a completely new sensor type that is not supported by the platform. Any software platform evolution in this direction introduces a new set of broad quality issues and other concerns. Dependability concerns, especially safety, reliability and availability, are among the most important for robot systems. In this paper, we use the ABB robot controller to show how an architecture transformation approach based on quality attributes can be used in the design process for increasing the platf openness.

Keywords

Quality Attribute Software Architecture Software Product Line Platform Service Open Platform 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Avizienis, A., Laprie, J.C., Randell, B.: Fundamental Concepts of Dependability, report 01-145, LAAS (2001)Google Scholar
  2. 2.
    Baragry, J., Reed, K.: Why we need a different view of software architecture. In: Working IEEE/IFIP Conference on Software Architecture (2001)Google Scholar
  3. 3.
    Bass, L., Clements, P., Kazman, R.: Software Architecture in Practice. Addison-Wesley, Reading (2003)Google Scholar
  4. 4.
    Bosch, J.: Design & Use of Software Architectures. Addison-Wesley, Reading (2000)Google Scholar
  5. 5.
    Dromey, G.: Cornering the Chimera. IEEE Software 13(1) (1996)Google Scholar
  6. 6.
    Dromey, G.: Software Product Quality: Theory, Model, and Practice, Software Quality Institute Griffith University Australia (1998), http://www.sqi.gu.edu.au
  7. 7.
    Fowler, M.: Who needs an architect? IEEE Software (2003)Google Scholar
  8. 8.
    Graaf, B., Lormans, M., Toetenel, H.: Embedded Software Engineering: The State of the Practice. IEEE Software (2003)Google Scholar
  9. 9.
    Issarny, V.: Software Architectures of Dependable Systems: From Closed To Open Systems. In: ICSE 2002 Workshop on Architecting Dependable Systems (2002)Google Scholar
  10. 10.
    Kaaniche, M., Laprie, J.C., Blanquart, J.P.: Dependability Engineering of Complex Computing Systems. In: 6th IEEE Conference on Engineering of Complex Computer Systems ICECCS (2000)Google Scholar
  11. 11.
    Kotonya, G., Sommerville, I.: Requirements Engineering - Processes and Techniques. John Wiley & Sons Ltd, Chichester (1997)Google Scholar
  12. 12.
    Lawrence, C. (ed.): Non-Functional Requirements in Software Engineering. Kluwer, Dordrecht (2000)MATHGoogle Scholar
  13. 13.
    Liu, J.W.S., et al.: Imprecise computations. Proceedings of the IEEE 82(1) (1994)Google Scholar
  14. 14.
    Microsoft Corporation, Windows Hardware and Driver Central homepage (2003), http://www.microsoft.com/whdc/
  15. 15.
    Microsoft Research SLAM Project (2003), http://research.microsoft.com/slam/
  16. 16.
    Musa, J.D.: Operational profiles in software-reliability engineering. IEEE Software 10(2) (1993)Google Scholar
  17. 17.
    Mustapic, G., et al.: Influences between Software Architecture and its Environment in Industrial Systems - a Case Study Technical Report, Mälardalen University, Sweden (2004), http://www.idt.mdh.se
  18. 18.
    Preiss, O., Wegmann, A.: Stakeholder discovery and classification based on systems science principles. In: Second Pacific-Asia Conference on Quality Software (2001)Google Scholar
  19. 19.
    Takashio, K., Tokoro, M.: An Object-Oriented Language for Distributed Real-Time Systems. In: OOPSLA 1992, Vancouver (1992)Google Scholar
  20. 20.
    Thane, H.: Monitoring, Testing and Debugging of Distributed Real-Time Systems, Doctoral Thesis, Royal Institute of Technology, KTH, Mechatronics Laboratory, TRITAMMK 2000:16, Sweden (2000)Google Scholar
  21. 21.
    Thane, H., et al.: Replay Debugging of Real-Time Systems using Time Machines. In: Parallel and Distributed Processing Symposium, Nice, France (2003)Google Scholar
  22. 22.
    Wall, A., Andersson, J., Norstrom, C.: Probabilistic Simulation-based Analysis of Complex Real-Time Systems. In: 6th IEEE International Symposium on Object-oriented Real-time distributed Computing, Hakodate, Hokkaido, Japan (2002)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Goran Mustapić
    • 1
  • Johan Andersson
    • 1
  • Christer Norström
    • 2
  • Anders Wall
    • 2
  1. 1.ABB Automation Technology Products, RoboticsVästeråsSweden
  2. 2.Dept. of Computer Science and EngineeringMälardalen UniversityVästeråsSweden

Personalised recommendations