|
|
|
|
| LEADER |
03666nam a22005415i 4500 |
| 001 |
978-1-4020-7997-9 |
| 003 |
DE-He213 |
| 005 |
20151204154616.0 |
| 007 |
cr nn 008mamaa |
| 008 |
100301s2004 xxu| s |||| 0|eng d |
| 020 |
|
|
|a 9781402079979
|9 978-1-4020-7997-9
|
| 024 |
7 |
|
|a 10.1007/b116264
|2 doi
|
| 040 |
|
|
|d GrThAP
|
| 050 |
|
4 |
|a QA75.5-76.95
|
| 072 |
|
7 |
|a UY
|2 bicssc
|
| 072 |
|
7 |
|a UYA
|2 bicssc
|
| 072 |
|
7 |
|a COM014000
|2 bisacsh
|
| 072 |
|
7 |
|a COM031000
|2 bisacsh
|
| 082 |
0 |
4 |
|a 004.0151
|2 23
|
| 245 |
1 |
0 |
|a Formal Methods for Embedded Distributed Systems
|h [electronic resource] :
|b How to master the complexity /
|c edited by Fabrice Kordon, Michel Lemoine.
|
| 264 |
|
1 |
|a Boston, MA :
|b Springer US,
|c 2004.
|
| 300 |
|
|
|a XX, 263 p. 28 illus.
|b online resource.
|
| 336 |
|
|
|a text
|b txt
|2 rdacontent
|
| 337 |
|
|
|a computer
|b c
|2 rdamedia
|
| 338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
| 347 |
|
|
|a text file
|b PDF
|2 rda
|
| 505 |
0 |
|
|a The BART Case Study -- Formal Specifcation and Refinement of a Safe Train Control Function -- From UML to Z -- Environmental Modeling with UML -- Checking BART Test Scenarios with UML’s Object Constraint Language -- Modeling and verifying behavioral aspects -- Mastering the Complexity of Reactive Systems - The AutoFocusApproach -- Conclusions.
|
| 520 |
|
|
|a The development of any Software (Industrial) Intensive System, e.g. critical embedded software, requires both different notations, and a strong devel- ment process. Different notations are mandatory because different aspects of the Software System have to be tackled. A strong development process is mandatory as well because without a strong organization we cannot warrantee the system will meet its requirements. Unfortunately, much more is needed! The different notations that can be used must all possess at least one property: formality. The development process must also have important properties: a exha- tive coverage of the development phases, and a set of well integrated support tools. In Computer Science it is now widely accepted that only formal notations can guarantee a perfect de?ned meaning. This becomes a more and more important issue since software systems tend to be distributed in large systems (for instance in safe public transportation systems), and in small ones (for instance numerous processors in luxury cars). Distribution increases the complexity of embedded software while safety criteria get harder to be met. On the other hand, during the past decade Software Engineering techniques have been improved a lot, and are now currently used to conduct systematic and rigorous development of large software systems. UML has become the de facto standard notation for documenting Software Engineering projects. UML is supported by many CASE tools that offer graphical means for the UML notation.
|
| 650 |
|
0 |
|a Computer science.
|
| 650 |
|
0 |
|a Microprocessors.
|
| 650 |
|
0 |
|a Software engineering.
|
| 650 |
|
0 |
|a Computers.
|
| 650 |
|
0 |
|a Computer-aided engineering.
|
| 650 |
1 |
4 |
|a Computer Science.
|
| 650 |
2 |
4 |
|a Theory of Computation.
|
| 650 |
2 |
4 |
|a Software Engineering/Programming and Operating Systems.
|
| 650 |
2 |
4 |
|a Computing Methodologies.
|
| 650 |
2 |
4 |
|a Processor Architectures.
|
| 650 |
2 |
4 |
|a Computer-Aided Engineering (CAD, CAE) and Design.
|
| 700 |
1 |
|
|a Kordon, Fabrice.
|e editor.
|
| 700 |
1 |
|
|a Lemoine, Michel.
|e editor.
|
| 710 |
2 |
|
|a SpringerLink (Online service)
|
| 773 |
0 |
|
|t Springer eBooks
|
| 776 |
0 |
8 |
|i Printed edition:
|z 9781402079962
|
| 856 |
4 |
0 |
|u http://dx.doi.org/10.1007/b116264
|z Full Text via HEAL-Link
|
| 912 |
|
|
|a ZDB-2-SCS
|
| 912 |
|
|
|a ZDB-2-BAE
|
| 950 |
|
|
|a Computer Science (Springer-11645)
|
