Software Engineering for Manufacturing Systems: Methods and CASE tools. IFIP TC5 international conference on Software Engineering for Manufacturing Systems, 28 – 29 March 1996, Stuttgart, Germany

203 Pages·1996·12.961 MB·English

by  Prof. Dr.-Ing. A. Storr (auth.), Alfred Storr, Dennis Jarvis (eds.)

Software Engineering
for Manufacturing
Systems
IFIP - The International Federation for Information Processing
IFIP was founded in 1960 under the auspices of UNESCO, following the First World
Computer Congress held in Paris the previous year. An umbrella organization for societies
working in information processing, IFIP's aim is two-fold: to support information processing
within its member countries and to encourage technology transfer to developing nations. As
its mission statement clearly states,
IFIP's mission is to be the leading, truly international, apolitical organization which
encourages and assists in the development, exploitation and application of information
technology for the benefit of all people.
IFIP is a non-profitmaking organization, run almost solely by 2500 volunteers. It operates
through a number of technical committees, which organize events and publications. IFIP's
events range from an international congress to local seminars, but the most important are:
• the IFIP World Computer Congress, held every second year;
• open conferences;
• working conferences.
The flagship event is the IFIP World Computer Congress, at which both invited and
contributed papers are presented. Contributed papers are rigorously refereed and the rejection
rate is high.
As with the Congress, participation in the open conferences is open to all and papers may
be invited or submitted. Again, submitted papers are stringently refereed.
The working conferences are structured differently. They are usually run by a working
group and attendance is small and by invitation only. Their purpose is to create an atmosphere
conducive to innovation and development. Refereeing is less rigorous and papers are
subjected to extensive group discussion.
Publications arising from IFIP events vary. The papers presented at the IFIP World
Computer Congress and at open conferences are published as conference proceedings, while
the results of the working conferences are often published as collections of selected and
edited papers.
Any national society whose primary activity is in information may apply to become a full
member of IFIP, although full membership is restricted to one society per country. Full
members are entitled to vote at the annual General Assembly, National societies preferring a
less committed involvement may apply for associate or corresponding membership. Associate
members enjoy the same benefits as full members, but without voting rights. Corresponding
members are not represented in IFIP bodies. Affiliated membership is open to non-national
societies, and individual and honorary membership schemes are also offered.
Software Engineering
for Manufacturing
Systems
Methods and CASE tools
IFIP TC5 international conference on
Software Engineering for Manufacturing Systems,
28 - 29 March 1996, Stuttgart, Germany
Edited by
Alfred Storr
University of Stuttgart
Germany
and
Dennis Jarvis
CSIRO Division ofM anufacturing Technology
Australia
IUIII
SPRINGER-SCIENCE+BUSINESS MEDIA, B.V.
First edition 1996
© 1996 Springer Science+Business Media Dordrecht
Originally published by Chapman & Hall in 1996
Softcover reprint of the hardcover 1st edition 1996
ISBN 978-1-4757-6540-3 ISBN 978-0-387-35060-8 (eBook)
DOI 10.1007/978-0-387-35060-8
Apart from any fair dealing for the purposes of research or private study, or criticism or
review, as pennitted under the UK Copyright Designs and Patents Act, 1988, this publication
may not be reproduced, stored, or transmitted, in any fonn or by any means, without the prior
pennission in writing of the publishers, or in the case of reprographic reproduction only in
accordance with the tenns of the licences issued by the Copyright Licensing Agency in the
UK, or in accordance with the tenns of licences issued by the appropriate Reproduction
Rights Organization outside the UK. Enquiries concerning reproduction outside the tenns
stated here should be sent to the publishers at the London address printed on this page.
The publisher makes no representalion, express or implied, with regard to the accuracy of
the infonnation contained in this book and cannot accept any legal responsibility or liability
for any errors or omissions that may be made.
A catalogue record for this book is available from the British Library
@ Printed on permanent acid-free text paper. manufactured in accordance with
ANSIINISO Z39.48-1992 and ANSUNISO Z39.48-1984 (Permanence of Paper).
CONTENTS
Software engineering for control technology - definitions and requirements
A. Storr
2 Life cycle support for PLC controlled manufacturing systems
J. Jarvis and D. Jarvis 14
3 State diagrams: a new programming method for programmable logic controllers
H.-P. Otto and C. Rath 27
4 Applying simulation modeling techniques for the design and assessment of
control software
II Astinov and N. Todorov 38
5 A CP-net approach to control logic engineering
M. Farrington and J. Billington 46
6 Modeling and simulation of combined discrete event-continuous systems
using DEVS formalism and object-oriented paradigm
M. Teggar and R. Soenen 58
7 Principles of CASE tool design for automation control
W Brendel 71
8 VPLC - a CASE tool for the virtual programming. simulation and diagnosis
of PLC software
D. Spath, P. Cuinand, M. Lanza, U. Osmers 84
9 ASPECT - a CASE tool for control functions originating from
mechanical layout
T. Bralldl, R. Lutz, J. Reichenbiicher 95
10 Case tools for flexibile manufacturing systems
M. Weck, J. Friedrich, Th. Koch, R. Langen 107
11 An environment and algorithm for FMS controller testing
Z. Deng. Z. Bi, Y. Zhu 123
12 Reusability of function-oriented and object-oriented master control software
J. Uhl, J. Driller 139
13 A reusable software artifact library system as the core of a reuse-oriented
software enterprise
C. Jacucci, E. Mambella, C. Succi, C. Uhrik, M. Ronchetti, A. Lo Surd o,
S. Doublait, A. Valerio 153
14 Software design practice using two SCADA software packages
K.P. Basse, C.K. Christensen, P.K. Frederiksen 168
15 GENIUS: a generator for graphical user interfaces
H.-J. Bullillger, K.-P. Fiihllrich, A. Weisbecker 181
Index of contributors 197
Keyword index 199
1
Software Engineering for Control Techno
logy - Definitions and Requirements
Storr, A.
Prof Dr.-Ing.
Institut fur Steuerungstechnik der Werkzeugmaschinen und
Fertigungseinrichtungen, Seidenstr. 36, 70174 Stuttgart/Germany
Tel: [phone] Fax: [phone]
Abstract
Software for control technology is a significant part of a machine. The necessity of applying
systematically procedures and methods for the development of control software is
emphasised. The use of CASE tools and the specification of reusable software modules can
increase the productivity. When selecting the methods and procedures, various constraints
have to be considered. The selection is influenced by the hierarchical level of the control
architecture, the kind of control function that is to be implemented and the required quality
features. An important basic design method is the decomposition of control software
according to the decomposition of hardware features in mechanical engineering. This will
lead to an object-oriented structure. Additionally, using the description method of the state
graph, the reuse of control software is supported.
Keywords
Structures and demands of control technology; software engineering procedures and methods;
CASE (computer-aided software engineering) tools
2 Software Engineering for Manufacturing Systems
1 INTRODUCTION
Nowadays, the term 'software crisis' is often heard. What is generally implied is that there is a
shortage of software engineers. The outcome is that engineer-like systematical procedures and
methods are often not applied to software development and especially not to software design.
The significance of software as a time and cost factor as well as a product and manufacturing
component and consequently as machine element has not yet been completely rerognized.
1. Software development is differentiated from the software application cycle. Application
includes also maintenance and service i. e. further development. Experience has shown
that the expenditure concerning the maintenance can be higher than that concerning the
software engineering.
2. The engineering cycle consists of different actions. The sequence of these actions reflects
a systematical process or procedure. It is important that much time is dedicated to the
"early" actions and that they are characterized by thorough and extensive analyses.
3. Furthermore, the figure illustrates that errors often occur relatively early in the process but
are usually discovered late. This results in cost-intensive corrections.
Fig. 1 shows some features of software development.
..
... ... ~ 01 d.e.w. iIoDmaI1I • ~ 01+ 00If1 I1b1
m
30% ~ 30% I!l 15-~% ~ 15-20% ~ 5%
P_anaIysIs
and",:::,~ Des9I knpIemerdaIion Test Co-nwnissioni1g U1iizatJon
Resouf08 plaMing System design PIOgIWMIIng ProgrwnleSl .t.ccepOOal MdlIanatlC<!
-()~ Cocilg Systemlll$l saenMd ce
F~ ktegrdonlesl
ProjecllJllde .,.. CotrfOI*'I design
(sInICln. daIa,
P- prncoclns)
spocificatlons
Erro-r -;;a;;;y0 0 II Error rettN8f'/ 58'1. I
r Error m. 64 'lI. II Em>< raIe 36 'lI.
CosIs 0I4Iiri1a1i1g f. ..... (reUied 10 Ihe phases 01 c:cdng)
0.2 OJ; 1 2 5 10·20
-.
J:..--- ~:,,?--~r:--
~
~
:=
,""",tor
40% 01 procldonCOS1S 20'10 01 prod. *\$ 40 'lI.0I pn>clICIIor1 COS1S 1rin._01~
Fig. 1: Phases of software engineering, time and cost (according to Hering and others)
(104348)
Software engineering for control technology 3
The figure does not explicitly demonstrate the necessity of re-usable software and the
resulting advantages as, for example, cost reduction and a reduced number of errors.
Furthermore, systematical engineer-like software development requires methods e.g. for
design modelling, in addition to the above mentioned process. CASE (Computer Aided
Software Engineering) tools -are based on procedures and methods (fig. 2). The development
and the application of function-specific CASE tools is required urgently.
J
~
( Engineering
' - - - - - - '
~qect octriristraioo
qJality~
rep;ns
general dfioo setVioos
- ---------,.
~a b Tools
- ~c t
~~
Ac B
rUes ~ rdaicns fa- ~ ..,
~em~ia1 ~
SLW01 d the sdtware
deveIqJrrert
Fig. 2: Components of software engineering (104 258)
2 DEFINITIONS
2.1 Software Engineering -Software Technology
Presently both terms are used. Software engineering is according. to IEEE "the systematic
approach to the development, operation, maintenance and retirement of software". According
to Fig. 3, software engineering is principle-oriented, whereas software technology is
understood as application-oriented software engineering. Here it is clearly seen that software
technology is, to a high degree, an engineering discipline and serves for the systematical
production of software. In this paper, software design in regard to the application "control
technology" stands in the forefront.
4 Software Engineering for Manufacturing Systems
neenng
prird~EHlI'iEned
generally ~ia:tie
persco-irdeper Dlrt
tdistic view instlU'l13lt view
integairYJ irtoodial ro irtoodial
J)'OCtioo ct scttv.ere d3ve1cp aTJiBsis CIl theay
rrert in thefaelrtn
feecm::k from irdJsby little feecm::k
I1'BIIllc:S, hrdirYJ
tEdTicai ~Eml wth
scttv.are<oTpcn
poJJXlle<lriooted
Ir icmatics = Bgreer scien:e fer the desigl
ct ci3Ia processirYJ S)'StEml
Sf-;tEmllical rrettms fer the
~ ct scttv.ere praLds
@)ISW'!15 Transdsci~irary insteal ct interdsci~irary
Fig. 3: Comparison software technology and software engineering (acc. to Gohner)(l04 323)
2.2 Activities and Methods
Methods can support the execution of single or multiple tasks. When supporting multiple
tasks, a method is comprehensive and continuous. Fig. 4 compares methods according to the
mentioned differentiation. Furthermore, function-, data- and object-oriented methods are
distinguished. It is important that a method is supported by a graphically describing or
representation function. In Fig. 5 additional methods and such functions are listed. Both
figures show clearly the problems with the selection of methods, especially since these do not
cover the broad range of requirements. They must be assessed by their performance in regard
to the application area -in our case control technology. A single method is not sufficient, but,
for example, a data-oriented and a function-oriented method have to be combined.
Software engineering for control technology 5
-
I IocUI point>:
Activity- D Il.ndicJn.
comprehen-I
I
siva
-
O~·
Activity
oriented I
slJuClll'ed pr1og r.1
Fig. 4: Methods for software engineering (306 518)
Type
Description methods Abbr. Standards Aulhors
FO DO DO
-Decisiontab-le ET DIN 66241 - • -
Programloodlart PAP D1NII6!JOI - • -
- • -
sIrucIogIams NS DIN 66261 Nassi&S'meiderman
I_a~1h-n:tion HF - - •• - --
PC
• - -
Structured Analysis SA Ross, Yourdon. Constantine,
De Marco, Gane & Sarson. • - -
SA-RealrllTl8 SMlT W8Id &M alor
Oes;gn Te chnque and SAOT Ross • - -
- • -
S_ee,;gn SO Yourdon, Constantine, Myers ·
SOpeecsifiacaitio"n "an,d "~ SOl - • · ·
Petri's networks PN . Petri • ·
State graphs ZG • - •
• -
Sru:tu"ed c:onl"oI doo:ription SR
- • -
Enli\yReIa~ ER Cadd. Chen. Marlin
• •
Jackson struct. progrc.rwning JSP Jackson
• •
DatafloM:t\art OFP 01N66001
•
Design after Eiffel EiIfeI - ·
•
C~Oeosacodri spYctoirounir dpaofttnei ro n-- - Coad. Yourdoo - - •
Booch
•
OescriptionafterSh ..... Shlaer,MeIor -
MeIor
FO... function-orienled 00 ... object-orienled • yes
® ISW '96 00 ... data-oriented '"
Fig. 5: Description methods (104 214)