System requirements engineering: a SysML supported requirements engineering method
Gespeichert in:
1. Verfasser: | |
---|---|
Format: | Elektronisch E-Book |
Sprache: | English |
Veröffentlicht: |
London, UK
ISTE
2020
Hoboken, NJ Wiley |
Online-Zugang: | TUM01 |
Beschreibung: | Cover -- Half-Title Page -- Title Page -- Copyright Page -- Contents -- Foreword -- Preface -- Background information -- Objectives and structure of the book -- Acknowledgments -- PART 1: Requirements Engineering -- 1. The Requirements Engineering Process -- 1.1. Background and main definitions -- 1.2. Requirements engineering process -- 1.2.1. Requirements engineering and ISO 15288 processes -- 1.2.2. Requirements engineering and ISO 29110 processes -- 1.2.3. Problem versus solution -- 1.3. Requirements engineering process and modeling -- 1.4. Engineering processes and project management -- 2. A Method for Requirements Engineering -- 2.1. Proposal of a requirements engineering method -- 2.1.1. Requirement diagram -- 2.1.2. Block definition diagram -- 2.1.3. Use case diagram -- 2.1.4. State machine diagram -- 2.1.5. Sequence diagram -- 2.1.6. Activity diagram -- 2.2. Define the system framework -- 2.2.1. Goal -- Contents -- 2.2.2. Define the system framework using SysML -- 2.2.3. Systematization and verification -- 2.3. Define the system life cycle -- 2.3.1. Goal -- 2.3.2. Define the system life cycle using SysML -- 2.3.3. Systematization and verification -- 2.4. Define contexts -- 2.4.1. Goal -- 2.4.2. Define contexts using SysML -- 2.4.3. Systematization and verification -- 2.5. Define uses -- 2.5.1. Goal -- 2.5.2. Define uses using SysML -- 2.5.3. Systematization and verification -- 2.6. Describe the use scenarios -- 2.6.1. Goal -- 2.6.2. Describe the use scenarios using SysML -- 2.6.3. Systematization and verification -- 2.7. Define functional requirements -- 2.7.1. Goal -- 2.7.2. Define functional requirements using SysML -- 2.7.3. Systematization and verification -- 2.8. Define non-functional requirements -- 2.8.1. Goal -- 2.8.2. Define non-functional requirements using SysML -- 2.8.3. Systematization and verification 2.9. Ensure traceability -- 2.9.1. Goal -- 2.9.2. Ensure traceability using SysML -- 2.9.3. Systematization and verification -- 2.10. Conclusion -- PART 2: Case Study, Application of the Method -- 3. Definition of Stakeholders' Needs -- 3.1. Case study -- 3.1.1. Context of the case study -- 3.1.2. Structure of the SysML project -- 3.1.3. Presentation of the results -- 3.2. Definition of needs -- 3.2.1. Define the system framework -- 3.2.2. Define the system life cycle -- 3.2.3. Define contexts -- 3.2.4. Define uses -- 3.2.5. Describe the use scenarios -- 3.2.6. Define functional requirements -- 3.2.7. Define non-functional requirements -- 3.2.8. Ensure traceability -- 3.3. Stakeholder needs definition documents -- 3.3.1. Use a document template -- 3.3.2. Use a list of needs -- 4. System Requirements Engineering -- 4.1. Case study -- 4.1.1. Structure of the SysML project -- 4.1.2. Presentation of the results -- 4.2. Definition of system requirements -- 4.2.1. Define the system framework -- 4.2.2. Define the system life cycle -- 4.2.3. Define contexts -- 4.2.4. Define uses -- 4.2.4. Define uses -- 4.2.5. Describe the use scenarios -- 4.2.6. Define functional requirements -- 4.2.7. Define non-functional requirements -- 4.2.8. Ensure traceability -- 4.3. System requirements analysis document -- 4.4. Requirements management -- 4.4.1. Fundamental elements -- 4.4.2. Management workflows -- 4.4.3. Use in student projects -- 5. Integration with Other Methods -- 5.1. Context -- 5.2. Integration with the Harmony SE method -- 5.2.1. Modification of the project structure -- 5.2.2. The Harmony SE method and requirements engineering -- 5.2.3. Definition of stakeholders' needs -- 5.2.4. Analysis of system requirements -- 5.2.5. Conclusion -- 5.3. Integration with the Arcadia method -- 5.3.1. The Arcadia method and requirements engineering 5.3.2. Definition of stakeholders' needs -- 5.3.3. Analysis of system requirements -- 5.3.4. Conclusion -- 5.4. Integration with the CESAM method -- 5.4.1. The CESAM method and requirements engineering -- 5.4.2. Definition of stakeholders' needs -- 5.4.3. Analysis of system requirements -- 5.4.4. Conclusion -- References -- Index -- Other titles from iSTE in Systems and Industrial Engineering - Robotics -- EULA. |
Beschreibung: | 1 Online-Ressource Illustrationen |
ISBN: | 9781119751533 |
Internformat
MARC
LEADER | 00000nmm a2200000zc 4500 | ||
---|---|---|---|
001 | BV047017287 | ||
003 | DE-604 | ||
005 | 20230817 | ||
007 | cr|uuu---uuuuu | ||
008 | 201119s2020 |||| o||u| ||||||eng d | ||
020 | |a 9781119751533 |9 978-1-119-75153-3 | ||
035 | |a (ZDB-30-PQE)EBC6268185 | ||
035 | |a (OCoLC)1224012724 | ||
035 | |a (DE-599)BVBBV047017287 | ||
040 | |a DE-604 |b ger |e rda | ||
041 | 0 | |a eng | |
049 | |a DE-91 | ||
084 | |a DAT 335 |2 stub | ||
100 | 1 | |a Bron, Jean-Yves |e Verfasser |4 aut | |
245 | 1 | 0 | |a System requirements engineering |b a SysML supported requirements engineering method |c Jean-Yves Bron |
264 | 1 | |a London, UK |b ISTE |c 2020 | |
264 | 1 | |a Hoboken, NJ |b Wiley | |
300 | |a 1 Online-Ressource |b Illustrationen | ||
336 | |b txt |2 rdacontent | ||
337 | |b c |2 rdamedia | ||
338 | |b cr |2 rdacarrier | ||
500 | |a Cover -- Half-Title Page -- Title Page -- Copyright Page -- Contents -- Foreword -- Preface -- Background information -- Objectives and structure of the book -- Acknowledgments -- PART 1: Requirements Engineering -- 1. The Requirements Engineering Process -- 1.1. Background and main definitions -- 1.2. Requirements engineering process -- 1.2.1. Requirements engineering and ISO 15288 processes -- 1.2.2. Requirements engineering and ISO 29110 processes -- 1.2.3. Problem versus solution -- 1.3. Requirements engineering process and modeling -- 1.4. Engineering processes and project management -- 2. A Method for Requirements Engineering -- 2.1. Proposal of a requirements engineering method -- 2.1.1. Requirement diagram -- 2.1.2. Block definition diagram -- 2.1.3. Use case diagram -- 2.1.4. State machine diagram -- 2.1.5. Sequence diagram -- 2.1.6. Activity diagram -- 2.2. Define the system framework -- 2.2.1. Goal -- Contents -- 2.2.2. Define the system framework using SysML -- 2.2.3. Systematization and verification -- 2.3. Define the system life cycle -- 2.3.1. Goal -- 2.3.2. Define the system life cycle using SysML -- 2.3.3. Systematization and verification -- 2.4. Define contexts -- 2.4.1. Goal -- 2.4.2. Define contexts using SysML -- 2.4.3. Systematization and verification -- 2.5. Define uses -- 2.5.1. Goal -- 2.5.2. Define uses using SysML -- 2.5.3. Systematization and verification -- 2.6. Describe the use scenarios -- 2.6.1. Goal -- 2.6.2. Describe the use scenarios using SysML -- 2.6.3. Systematization and verification -- 2.7. Define functional requirements -- 2.7.1. Goal -- 2.7.2. Define functional requirements using SysML -- 2.7.3. Systematization and verification -- 2.8. Define non-functional requirements -- 2.8.1. Goal -- 2.8.2. Define non-functional requirements using SysML -- 2.8.3. Systematization and verification | ||
500 | |a 2.9. Ensure traceability -- 2.9.1. Goal -- 2.9.2. Ensure traceability using SysML -- 2.9.3. Systematization and verification -- 2.10. Conclusion -- PART 2: Case Study, Application of the Method -- 3. Definition of Stakeholders' Needs -- 3.1. Case study -- 3.1.1. Context of the case study -- 3.1.2. Structure of the SysML project -- 3.1.3. Presentation of the results -- 3.2. Definition of needs -- 3.2.1. Define the system framework -- 3.2.2. Define the system life cycle -- 3.2.3. Define contexts -- 3.2.4. Define uses -- 3.2.5. Describe the use scenarios -- 3.2.6. Define functional requirements -- 3.2.7. Define non-functional requirements -- 3.2.8. Ensure traceability -- 3.3. Stakeholder needs definition documents -- 3.3.1. Use a document template -- 3.3.2. Use a list of needs -- 4. System Requirements Engineering -- 4.1. Case study -- 4.1.1. Structure of the SysML project -- 4.1.2. Presentation of the results -- 4.2. Definition of system requirements -- 4.2.1. Define the system framework -- 4.2.2. Define the system life cycle -- 4.2.3. Define contexts -- 4.2.4. Define uses -- 4.2.4. Define uses -- 4.2.5. Describe the use scenarios -- 4.2.6. Define functional requirements -- 4.2.7. Define non-functional requirements -- 4.2.8. Ensure traceability -- 4.3. System requirements analysis document -- 4.4. Requirements management -- 4.4.1. Fundamental elements -- 4.4.2. Management workflows -- 4.4.3. Use in student projects -- 5. Integration with Other Methods -- 5.1. Context -- 5.2. Integration with the Harmony SE method -- 5.2.1. Modification of the project structure -- 5.2.2. The Harmony SE method and requirements engineering -- 5.2.3. Definition of stakeholders' needs -- 5.2.4. Analysis of system requirements -- 5.2.5. Conclusion -- 5.3. Integration with the Arcadia method -- 5.3.1. The Arcadia method and requirements engineering | ||
500 | |a 5.3.2. Definition of stakeholders' needs -- 5.3.3. Analysis of system requirements -- 5.3.4. Conclusion -- 5.4. Integration with the CESAM method -- 5.4.1. The CESAM method and requirements engineering -- 5.4.2. Definition of stakeholders' needs -- 5.4.3. Analysis of system requirements -- 5.4.4. Conclusion -- References -- Index -- Other titles from iSTE in Systems and Industrial Engineering - Robotics -- EULA. | ||
776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe |z 978-1-78630-594-7 |
912 | |a ZDB-30-PQE | ||
999 | |a oai:aleph.bib-bvb.de:BVB01-032424822 | ||
966 | e | |u https://ebookcentral.proquest.com/lib/munchentech/detail.action?docID=6268185 |l TUM01 |p ZDB-30-PQE |q TUM_PDA_PQE_Kauf |x Aggregator |3 Volltext |
Datensatz im Suchindex
_version_ | 1804181979128659968 |
---|---|
adam_txt | |
any_adam_object | |
any_adam_object_boolean | |
author | Bron, Jean-Yves |
author_facet | Bron, Jean-Yves |
author_role | aut |
author_sort | Bron, Jean-Yves |
author_variant | j y b jyb |
building | Verbundindex |
bvnumber | BV047017287 |
classification_tum | DAT 335 |
collection | ZDB-30-PQE |
ctrlnum | (ZDB-30-PQE)EBC6268185 (OCoLC)1224012724 (DE-599)BVBBV047017287 |
discipline | Informatik |
discipline_str_mv | Informatik |
format | Electronic eBook |
fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>05300nmm a2200361zc 4500</leader><controlfield tag="001">BV047017287</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20230817 </controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">201119s2020 |||| o||u| ||||||eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781119751533</subfield><subfield code="9">978-1-119-75153-3</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ZDB-30-PQE)EBC6268185</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)1224012724</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV047017287</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">DAT 335</subfield><subfield code="2">stub</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Bron, Jean-Yves</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">System requirements engineering</subfield><subfield code="b">a SysML supported requirements engineering method</subfield><subfield code="c">Jean-Yves Bron</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">London, UK</subfield><subfield code="b">ISTE</subfield><subfield code="c">2020</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Hoboken, NJ</subfield><subfield code="b">Wiley</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource</subfield><subfield code="b">Illustrationen</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="500" ind1=" " ind2=" "><subfield code="a">Cover -- Half-Title Page -- Title Page -- Copyright Page -- Contents -- Foreword -- Preface -- Background information -- Objectives and structure of the book -- Acknowledgments -- PART 1: Requirements Engineering -- 1. The Requirements Engineering Process -- 1.1. Background and main definitions -- 1.2. Requirements engineering process -- 1.2.1. Requirements engineering and ISO 15288 processes -- 1.2.2. Requirements engineering and ISO 29110 processes -- 1.2.3. Problem versus solution -- 1.3. Requirements engineering process and modeling -- 1.4. Engineering processes and project management -- 2. A Method for Requirements Engineering -- 2.1. Proposal of a requirements engineering method -- 2.1.1. Requirement diagram -- 2.1.2. Block definition diagram -- 2.1.3. Use case diagram -- 2.1.4. State machine diagram -- 2.1.5. Sequence diagram -- 2.1.6. Activity diagram -- 2.2. Define the system framework -- 2.2.1. Goal -- Contents -- 2.2.2. Define the system framework using SysML -- 2.2.3. Systematization and verification -- 2.3. Define the system life cycle -- 2.3.1. Goal -- 2.3.2. Define the system life cycle using SysML -- 2.3.3. Systematization and verification -- 2.4. Define contexts -- 2.4.1. Goal -- 2.4.2. Define contexts using SysML -- 2.4.3. Systematization and verification -- 2.5. Define uses -- 2.5.1. Goal -- 2.5.2. Define uses using SysML -- 2.5.3. Systematization and verification -- 2.6. Describe the use scenarios -- 2.6.1. Goal -- 2.6.2. Describe the use scenarios using SysML -- 2.6.3. Systematization and verification -- 2.7. Define functional requirements -- 2.7.1. Goal -- 2.7.2. Define functional requirements using SysML -- 2.7.3. Systematization and verification -- 2.8. Define non-functional requirements -- 2.8.1. Goal -- 2.8.2. Define non-functional requirements using SysML -- 2.8.3. Systematization and verification</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">2.9. Ensure traceability -- 2.9.1. Goal -- 2.9.2. Ensure traceability using SysML -- 2.9.3. Systematization and verification -- 2.10. Conclusion -- PART 2: Case Study, Application of the Method -- 3. Definition of Stakeholders' Needs -- 3.1. Case study -- 3.1.1. Context of the case study -- 3.1.2. Structure of the SysML project -- 3.1.3. Presentation of the results -- 3.2. Definition of needs -- 3.2.1. Define the system framework -- 3.2.2. Define the system life cycle -- 3.2.3. Define contexts -- 3.2.4. Define uses -- 3.2.5. Describe the use scenarios -- 3.2.6. Define functional requirements -- 3.2.7. Define non-functional requirements -- 3.2.8. Ensure traceability -- 3.3. Stakeholder needs definition documents -- 3.3.1. Use a document template -- 3.3.2. Use a list of needs -- 4. System Requirements Engineering -- 4.1. Case study -- 4.1.1. Structure of the SysML project -- 4.1.2. Presentation of the results -- 4.2. Definition of system requirements -- 4.2.1. Define the system framework -- 4.2.2. Define the system life cycle -- 4.2.3. Define contexts -- 4.2.4. Define uses -- 4.2.4. Define uses -- 4.2.5. Describe the use scenarios -- 4.2.6. Define functional requirements -- 4.2.7. Define non-functional requirements -- 4.2.8. Ensure traceability -- 4.3. System requirements analysis document -- 4.4. Requirements management -- 4.4.1. Fundamental elements -- 4.4.2. Management workflows -- 4.4.3. Use in student projects -- 5. Integration with Other Methods -- 5.1. Context -- 5.2. Integration with the Harmony SE method -- 5.2.1. Modification of the project structure -- 5.2.2. The Harmony SE method and requirements engineering -- 5.2.3. Definition of stakeholders' needs -- 5.2.4. Analysis of system requirements -- 5.2.5. Conclusion -- 5.3. Integration with the Arcadia method -- 5.3.1. The Arcadia method and requirements engineering</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">5.3.2. Definition of stakeholders' needs -- 5.3.3. Analysis of system requirements -- 5.3.4. Conclusion -- 5.4. Integration with the CESAM method -- 5.4.1. The CESAM method and requirements engineering -- 5.4.2. Definition of stakeholders' needs -- 5.4.3. Analysis of system requirements -- 5.4.4. Conclusion -- References -- Index -- Other titles from iSTE in Systems and Industrial Engineering - Robotics -- EULA.</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">978-1-78630-594-7</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-PQE</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-032424822</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">https://ebookcentral.proquest.com/lib/munchentech/detail.action?docID=6268185</subfield><subfield code="l">TUM01</subfield><subfield code="p">ZDB-30-PQE</subfield><subfield code="q">TUM_PDA_PQE_Kauf</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
id | DE-604.BV047017287 |
illustrated | Not Illustrated |
index_date | 2024-07-03T15:58:21Z |
indexdate | 2024-07-10T09:00:15Z |
institution | BVB |
isbn | 9781119751533 |
language | English |
oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-032424822 |
oclc_num | 1224012724 |
open_access_boolean | |
owner | DE-91 DE-BY-TUM |
owner_facet | DE-91 DE-BY-TUM |
physical | 1 Online-Ressource Illustrationen |
psigel | ZDB-30-PQE ZDB-30-PQE TUM_PDA_PQE_Kauf |
publishDate | 2020 |
publishDateSearch | 2020 |
publishDateSort | 2020 |
publisher | ISTE Wiley |
record_format | marc |
spelling | Bron, Jean-Yves Verfasser aut System requirements engineering a SysML supported requirements engineering method Jean-Yves Bron London, UK ISTE 2020 Hoboken, NJ Wiley 1 Online-Ressource Illustrationen txt rdacontent c rdamedia cr rdacarrier Cover -- Half-Title Page -- Title Page -- Copyright Page -- Contents -- Foreword -- Preface -- Background information -- Objectives and structure of the book -- Acknowledgments -- PART 1: Requirements Engineering -- 1. The Requirements Engineering Process -- 1.1. Background and main definitions -- 1.2. Requirements engineering process -- 1.2.1. Requirements engineering and ISO 15288 processes -- 1.2.2. Requirements engineering and ISO 29110 processes -- 1.2.3. Problem versus solution -- 1.3. Requirements engineering process and modeling -- 1.4. Engineering processes and project management -- 2. A Method for Requirements Engineering -- 2.1. Proposal of a requirements engineering method -- 2.1.1. Requirement diagram -- 2.1.2. Block definition diagram -- 2.1.3. Use case diagram -- 2.1.4. State machine diagram -- 2.1.5. Sequence diagram -- 2.1.6. Activity diagram -- 2.2. Define the system framework -- 2.2.1. Goal -- Contents -- 2.2.2. Define the system framework using SysML -- 2.2.3. Systematization and verification -- 2.3. Define the system life cycle -- 2.3.1. Goal -- 2.3.2. Define the system life cycle using SysML -- 2.3.3. Systematization and verification -- 2.4. Define contexts -- 2.4.1. Goal -- 2.4.2. Define contexts using SysML -- 2.4.3. Systematization and verification -- 2.5. Define uses -- 2.5.1. Goal -- 2.5.2. Define uses using SysML -- 2.5.3. Systematization and verification -- 2.6. Describe the use scenarios -- 2.6.1. Goal -- 2.6.2. Describe the use scenarios using SysML -- 2.6.3. Systematization and verification -- 2.7. Define functional requirements -- 2.7.1. Goal -- 2.7.2. Define functional requirements using SysML -- 2.7.3. Systematization and verification -- 2.8. Define non-functional requirements -- 2.8.1. Goal -- 2.8.2. Define non-functional requirements using SysML -- 2.8.3. Systematization and verification 2.9. Ensure traceability -- 2.9.1. Goal -- 2.9.2. Ensure traceability using SysML -- 2.9.3. Systematization and verification -- 2.10. Conclusion -- PART 2: Case Study, Application of the Method -- 3. Definition of Stakeholders' Needs -- 3.1. Case study -- 3.1.1. Context of the case study -- 3.1.2. Structure of the SysML project -- 3.1.3. Presentation of the results -- 3.2. Definition of needs -- 3.2.1. Define the system framework -- 3.2.2. Define the system life cycle -- 3.2.3. Define contexts -- 3.2.4. Define uses -- 3.2.5. Describe the use scenarios -- 3.2.6. Define functional requirements -- 3.2.7. Define non-functional requirements -- 3.2.8. Ensure traceability -- 3.3. Stakeholder needs definition documents -- 3.3.1. Use a document template -- 3.3.2. Use a list of needs -- 4. System Requirements Engineering -- 4.1. Case study -- 4.1.1. Structure of the SysML project -- 4.1.2. Presentation of the results -- 4.2. Definition of system requirements -- 4.2.1. Define the system framework -- 4.2.2. Define the system life cycle -- 4.2.3. Define contexts -- 4.2.4. Define uses -- 4.2.4. Define uses -- 4.2.5. Describe the use scenarios -- 4.2.6. Define functional requirements -- 4.2.7. Define non-functional requirements -- 4.2.8. Ensure traceability -- 4.3. System requirements analysis document -- 4.4. Requirements management -- 4.4.1. Fundamental elements -- 4.4.2. Management workflows -- 4.4.3. Use in student projects -- 5. Integration with Other Methods -- 5.1. Context -- 5.2. Integration with the Harmony SE method -- 5.2.1. Modification of the project structure -- 5.2.2. The Harmony SE method and requirements engineering -- 5.2.3. Definition of stakeholders' needs -- 5.2.4. Analysis of system requirements -- 5.2.5. Conclusion -- 5.3. Integration with the Arcadia method -- 5.3.1. The Arcadia method and requirements engineering 5.3.2. Definition of stakeholders' needs -- 5.3.3. Analysis of system requirements -- 5.3.4. Conclusion -- 5.4. Integration with the CESAM method -- 5.4.1. The CESAM method and requirements engineering -- 5.4.2. Definition of stakeholders' needs -- 5.4.3. Analysis of system requirements -- 5.4.4. Conclusion -- References -- Index -- Other titles from iSTE in Systems and Industrial Engineering - Robotics -- EULA. Erscheint auch als Druck-Ausgabe 978-1-78630-594-7 |
spellingShingle | Bron, Jean-Yves System requirements engineering a SysML supported requirements engineering method |
title | System requirements engineering a SysML supported requirements engineering method |
title_auth | System requirements engineering a SysML supported requirements engineering method |
title_exact_search | System requirements engineering a SysML supported requirements engineering method |
title_exact_search_txtP | System requirements engineering a SysML supported requirements engineering method |
title_full | System requirements engineering a SysML supported requirements engineering method Jean-Yves Bron |
title_fullStr | System requirements engineering a SysML supported requirements engineering method Jean-Yves Bron |
title_full_unstemmed | System requirements engineering a SysML supported requirements engineering method Jean-Yves Bron |
title_short | System requirements engineering |
title_sort | system requirements engineering a sysml supported requirements engineering method |
title_sub | a SysML supported requirements engineering method |
work_keys_str_mv | AT bronjeanyves systemrequirementsengineeringasysmlsupportedrequirementsengineeringmethod |