Formal Methods for Embedded Distributed Systems: How to master the complexity
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...
Gespeichert in:
| Weitere Verfasser: | , |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
New York, NY
Springer US
2004
|
| Ausgabe: | 1st ed. 2004 |
| Schlagworte: | |
| Online-Zugang: | UBY01 Volltext |
| Zusammenfassung: | 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 |
| Beschreibung: | 1 Online-Ressource (XX, 263 p. 28 illus) |
| ISBN: | 9781402079979 |
| DOI: | 10.1007/b116264 |
Internformat
MARC
| LEADER | 00000nmm a2200000zc 4500 | ||
|---|---|---|---|
| 001 | BV047064598 | ||
| 003 | DE-604 | ||
| 005 | 00000000000000.0 | ||
| 007 | cr|uuu---uuuuu | ||
| 008 | 201216s2004 |||| o||u| ||||||eng d | ||
| 020 | |a 9781402079979 |9 978-1-4020-7997-9 | ||
| 024 | 7 | |a 10.1007/b116264 |2 doi | |
| 035 | |a (ZDB-2-SCS)978-1-4020-7997-9 | ||
| 035 | |a (OCoLC)1227476997 | ||
| 035 | |a (DE-599)BVBBV047064598 | ||
| 040 | |a DE-604 |b ger |e aacr | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-706 | ||
| 082 | 0 | |a 004.0151 |2 23 | |
| 084 | |a ST 153 |0 (DE-625)143597: |2 rvk | ||
| 245 | 1 | 0 | |a Formal Methods for Embedded Distributed Systems |b How to master the complexity |c edited by Fabrice Kordon, Michel Lemoine |
| 250 | |a 1st ed. 2004 | ||
| 264 | 1 | |a New York, NY |b Springer US |c 2004 | |
| 300 | |a 1 Online-Ressource (XX, 263 p. 28 illus) | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b c |2 rdamedia | ||
| 338 | |b cr |2 rdacarrier | ||
| 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 | 4 | |a Theory of Computation | |
| 650 | 4 | |a Software Engineering/Programming and Operating Systems | |
| 650 | 4 | |a Artificial Intelligence | |
| 650 | 4 | |a Processor Architectures | |
| 650 | 4 | |a Computer-Aided Engineering (CAD, CAE) and Design | |
| 650 | 4 | |a Computers | |
| 650 | 4 | |a Software engineering | |
| 650 | 4 | |a Artificial intelligence | |
| 650 | 4 | |a Microprocessors | |
| 650 | 4 | |a Computer-aided engineering | |
| 650 | 0 | 7 | |a Eingebettetes System |0 (DE-588)4396978-1 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Formale Methode |0 (DE-588)4333722-3 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Verteiltes System |0 (DE-588)4238872-7 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Eingebettetes System |0 (DE-588)4396978-1 |D s |
| 689 | 0 | 1 | |a Verteiltes System |0 (DE-588)4238872-7 |D s |
| 689 | 0 | 2 | |a Formale Methode |0 (DE-588)4333722-3 |D s |
| 689 | 0 | |5 DE-604 | |
| 700 | 1 | |a Kordon, Fabrice |4 edt | |
| 700 | 1 | |a Lemoine, Michel |4 edt | |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |z 9781441954596 |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |z 9781475788723 |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |z 9781402079962 |
| 856 | 4 | 0 | |u https://doi.org/10.1007/b116264 |x Verlag |z URL des Eerstveröffentlichers |3 Volltext |
| 912 | |a ZDB-2-SCS | ||
| 940 | 1 | |q ZDB-2-SCS_2000/2004 | |
| 999 | |a oai:aleph.bib-bvb.de:BVB01-032471710 | ||
| 966 | e | |u https://doi.org/10.1007/b116264 |l UBY01 |p ZDB-2-SCS |q ZDB-2-SCS_2000/2004 |x Verlag |3 Volltext | |
Datensatz im Suchindex
| _version_ | 1804182062849064960 |
|---|---|
| adam_txt | |
| any_adam_object | |
| any_adam_object_boolean | |
| author2 | Kordon, Fabrice Lemoine, Michel |
| author2_role | edt edt |
| author2_variant | f k fk m l ml |
| author_facet | Kordon, Fabrice Lemoine, Michel |
| building | Verbundindex |
| bvnumber | BV047064598 |
| classification_rvk | ST 153 |
| collection | ZDB-2-SCS |
| ctrlnum | (ZDB-2-SCS)978-1-4020-7997-9 (OCoLC)1227476997 (DE-599)BVBBV047064598 |
| dewey-full | 004.0151 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 004 - Computer science |
| dewey-raw | 004.0151 |
| dewey-search | 004.0151 |
| dewey-sort | 14.0151 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| discipline_str_mv | Informatik |
| doi_str_mv | 10.1007/b116264 |
| edition | 1st ed. 2004 |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>03848nmm a2200625zc 4500</leader><controlfield tag="001">BV047064598</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">00000000000000.0</controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">201216s2004 |||| o||u| ||||||eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781402079979</subfield><subfield code="9">978-1-4020-7997-9</subfield></datafield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1007/b116264</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ZDB-2-SCS)978-1-4020-7997-9</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1227476997</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV047064598</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">aacr</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-706</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">004.0151</subfield><subfield code="2">23</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 153</subfield><subfield code="0">(DE-625)143597:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Formal Methods for Embedded Distributed Systems</subfield><subfield code="b">How to master the complexity</subfield><subfield code="c">edited by Fabrice Kordon, Michel Lemoine</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">1st ed. 2004</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">New York, NY</subfield><subfield code="b">Springer US</subfield><subfield code="c">2004</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (XX, 263 p. 28 illus)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="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</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Theory of Computation</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software Engineering/Programming and Operating Systems</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Artificial Intelligence</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Processor Architectures</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer-Aided Engineering (CAD, CAE) and Design</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computers</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Software engineering</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Artificial intelligence</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Microprocessors</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Computer-aided engineering</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Eingebettetes System</subfield><subfield code="0">(DE-588)4396978-1</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Formale Methode</subfield><subfield code="0">(DE-588)4333722-3</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Verteiltes System</subfield><subfield code="0">(DE-588)4238872-7</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Eingebettetes System</subfield><subfield code="0">(DE-588)4396978-1</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Verteiltes System</subfield><subfield code="0">(DE-588)4238872-7</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="2"><subfield code="a">Formale Methode</subfield><subfield code="0">(DE-588)4333722-3</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Kordon, Fabrice</subfield><subfield code="4">edt</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Lemoine, Michel</subfield><subfield code="4">edt</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe</subfield><subfield code="z">9781441954596</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe</subfield><subfield code="z">9781475788723</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe</subfield><subfield code="z">9781402079962</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://doi.org/10.1007/b116264</subfield><subfield code="x">Verlag</subfield><subfield code="z">URL des Eerstveröffentlichers</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-2-SCS</subfield></datafield><datafield tag="940" ind1="1" ind2=" "><subfield code="q">ZDB-2-SCS_2000/2004</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-032471710</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">https://doi.org/10.1007/b116264</subfield><subfield code="l">UBY01</subfield><subfield code="p">ZDB-2-SCS</subfield><subfield code="q">ZDB-2-SCS_2000/2004</subfield><subfield code="x">Verlag</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
| id | DE-604.BV047064598 |
| illustrated | Not Illustrated |
| index_date | 2024-07-03T16:12:22Z |
| indexdate | 2024-07-10T09:01:35Z |
| institution | BVB |
| isbn | 9781402079979 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-032471710 |
| oclc_num | 1227476997 |
| open_access_boolean | |
| owner | DE-706 |
| owner_facet | DE-706 |
| physical | 1 Online-Ressource (XX, 263 p. 28 illus) |
| psigel | ZDB-2-SCS ZDB-2-SCS_2000/2004 ZDB-2-SCS ZDB-2-SCS_2000/2004 |
| publishDate | 2004 |
| publishDateSearch | 2004 |
| publishDateSort | 2004 |
| publisher | Springer US |
| record_format | marc |
| spelling | Formal Methods for Embedded Distributed Systems How to master the complexity edited by Fabrice Kordon, Michel Lemoine 1st ed. 2004 New York, NY Springer US 2004 1 Online-Ressource (XX, 263 p. 28 illus) txt rdacontent c rdamedia cr rdacarrier 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 Theory of Computation Software Engineering/Programming and Operating Systems Artificial Intelligence Processor Architectures Computer-Aided Engineering (CAD, CAE) and Design Computers Software engineering Artificial intelligence Microprocessors Computer-aided engineering Eingebettetes System (DE-588)4396978-1 gnd rswk-swf Formale Methode (DE-588)4333722-3 gnd rswk-swf Verteiltes System (DE-588)4238872-7 gnd rswk-swf Eingebettetes System (DE-588)4396978-1 s Verteiltes System (DE-588)4238872-7 s Formale Methode (DE-588)4333722-3 s DE-604 Kordon, Fabrice edt Lemoine, Michel edt Erscheint auch als Druck-Ausgabe 9781441954596 Erscheint auch als Druck-Ausgabe 9781475788723 Erscheint auch als Druck-Ausgabe 9781402079962 https://doi.org/10.1007/b116264 Verlag URL des Eerstveröffentlichers Volltext |
| spellingShingle | Formal Methods for Embedded Distributed Systems How to master the complexity Theory of Computation Software Engineering/Programming and Operating Systems Artificial Intelligence Processor Architectures Computer-Aided Engineering (CAD, CAE) and Design Computers Software engineering Artificial intelligence Microprocessors Computer-aided engineering Eingebettetes System (DE-588)4396978-1 gnd Formale Methode (DE-588)4333722-3 gnd Verteiltes System (DE-588)4238872-7 gnd |
| subject_GND | (DE-588)4396978-1 (DE-588)4333722-3 (DE-588)4238872-7 |
| title | Formal Methods for Embedded Distributed Systems How to master the complexity |
| title_auth | Formal Methods for Embedded Distributed Systems How to master the complexity |
| title_exact_search | Formal Methods for Embedded Distributed Systems How to master the complexity |
| title_exact_search_txtP | Formal Methods for Embedded Distributed Systems How to master the complexity |
| title_full | Formal Methods for Embedded Distributed Systems How to master the complexity edited by Fabrice Kordon, Michel Lemoine |
| title_fullStr | Formal Methods for Embedded Distributed Systems How to master the complexity edited by Fabrice Kordon, Michel Lemoine |
| title_full_unstemmed | Formal Methods for Embedded Distributed Systems How to master the complexity edited by Fabrice Kordon, Michel Lemoine |
| title_short | Formal Methods for Embedded Distributed Systems |
| title_sort | formal methods for embedded distributed systems how to master the complexity |
| title_sub | How to master the complexity |
| topic | Theory of Computation Software Engineering/Programming and Operating Systems Artificial Intelligence Processor Architectures Computer-Aided Engineering (CAD, CAE) and Design Computers Software engineering Artificial intelligence Microprocessors Computer-aided engineering Eingebettetes System (DE-588)4396978-1 gnd Formale Methode (DE-588)4333722-3 gnd Verteiltes System (DE-588)4238872-7 gnd |
| topic_facet | Theory of Computation Software Engineering/Programming and Operating Systems Artificial Intelligence Processor Architectures Computer-Aided Engineering (CAD, CAE) and Design Computers Software engineering Artificial intelligence Microprocessors Computer-aided engineering Eingebettetes System Formale Methode Verteiltes System |
| url | https://doi.org/10.1007/b116264 |
| work_keys_str_mv | AT kordonfabrice formalmethodsforembeddeddistributedsystemshowtomasterthecomplexity AT lemoinemichel formalmethodsforembeddeddistributedsystemshowtomasterthecomplexity |