Atnaujinkite slapukų nuostatas

System Requirements Engineering: A SysML Supported Requirements Engineering Method [Kietas viršelis]

4.00/5 (4 ratings by Goodreads)
  • Formatas: Hardback, 224 pages, aukštis x plotis x storis: 236x160x20 mm, weight: 499 g
  • Išleidimo metai: 31-Jul-2020
  • Leidėjas: ISTE Ltd and John Wiley & Sons Inc
  • ISBN-10: 1786305941
  • ISBN-13: 9781786305947
Kitos knygos pagal šią temą:
System Requirements Engineering: A SysML Supported Requirements Engineering MethodDidesnis paveikslėlis
  • Formatas: Hardback, 224 pages, aukštis x plotis x storis: 236x160x20 mm, weight: 499 g
  • Išleidimo metai: 31-Jul-2020
  • Leidėjas: ISTE Ltd and John Wiley & Sons Inc
  • ISBN-10: 1786305941
  • ISBN-13: 9781786305947
Kitos knygos pagal šią temą:
Pastovi nuoroda: https://www.kriso.lt/db/9781786305947.html
Raktažodžiai:
The book deals with requirements engineering in the context of System Engineering. He proposes a method to guide this activity engineering. The method is supported by the SysML modeling language. A first chapter aims to present the context and the associated definitions, to position the requirements engineering in the processes system engineering, to define the modeling and its contributions, and to make the link with the management of IS projects. The second chapter is devoted to the proposed method for implementing the requirements engineering subprocesses. Each of the 8 activities the component is first described before specifying how the SysML language can be exploited to achieve it effectively. Proposal for a book Please fill out the questionnaire below and send it back to Chantal Menasc : c.menasce@iste.co.uk The 3rd chapter is an application of the method to define the needs of the stakeholders of a system. The example is built on the basis of the RobAFIS'2018 competition. The 4th chapter continues the application of the method in the continuity of the IS processes to define the requirements of the same system. The appendices present at the same time a toolbox to realize the engineering of the requirements but also the complete results of engineering in Chapters 3 and 4.
Foreword ix
Preface xiii
Part 1 Requirements Engineering
1(76)
Chapter 1 The Requirements Engineering Process
3(28)
1.1 Background and main definitions
3(7)
1.2 Requirements engineering process
10(9)
1.2.1 Requirements engineering and ISO 15288 processes
11(3)
1.2.2 Requirements engineering and ISO 29110 processes
14(4)
1.2.3 Problem versus solution
18(1)
1.3 Requirements engineering process and modeling
19(7)
1.4 Engineering processes and project management
26(5)
Chapter 2 A Method for Requirements Engineering
31(46)
2.1 Proposal of a requirements engineering method
31(9)
2.1.1 Requirement diagram
36(2)
2.1.2 Block definition diagram
38(1)
2.1.3 Use case diagram
38(1)
2.1.4 State machine diagram
39(1)
2.1.5 Sequence diagram
39(1)
2.1.6 Activity diagram
40(1)
2.2 Define the system framework
40(3)
2.2.1 Goal
40(1)
2.2.2 Define the system framework using SysML
41(2)
2.2.3 Systematization and verification
43(1)
2.3 Define the system life cycle
43(2)
2.3.1 Goal
43(1)
2.3.2 Define the system life cycle using SysML
44(1)
2.3.3 Systematization and verification
45(1)
2.4 Define contexts
45(2)
2.4.1 Goal
45(1)
2.4.2 Define contexts using SysML
45(2)
2.4.3 Systematization and verification
47(1)
2.5 Define uses
47(6)
2.5.1 Goal
47(2)
2.5.2 Define uses using SysML
49(3)
2.5.3 Systematization and verification
52(1)
2.6 Describe the use scenarios
53(9)
2.6.1 Goal
53(1)
2.6.2 Describe the use scenarios using SysML
53(9)
2.6.3 Systematization and verification
62(1)
2.7 Define functional requirements
62(5)
2.7.1 Goal
62(3)
2.7.2 Define functional requirements using SysML
65(2)
2.7.3 Systematization and verification
67(1)
2.8 Define non-functional requirements
67(5)
2.8.1 Goal
67(1)
2.8.2 Define non-functional requirements using SysML
68(2)
2.8.3 Systematization and verification
70(2)
2.9 Ensure traceability
72(3)
2.9.1 Goal
72(1)
2.9.2 Ensure traceability using SysML
72(3)
2.9.3 Systematization and verification
75(1)
2.10 Conclusion
75(2)
Part 2 Case Study, Application of the Method
77(114)
Chapter 3 Definition of Stakeholders' Needs
79(46)
3.1 Case study
79(6)
3.1.1 Context of the case study
80(1)
3.1.2 Structure of the SysML project
81(3)
3.1.3 Presentation of the results
84(1)
3.2 Definition of needs
85(13)
3.2.1 Define the system framework
85(1)
3.2.2 Define the system life cycle
86(1)
3.2.3 Define contexts
87(2)
3.2.4 Define uses
89(3)
3.2.5 Describe the use scenarios
92(1)
3.2.6 Define functional requirements
92(3)
3.2.7 Define non-functional requirements
95(1)
3.2.8 Ensure traceability
95(3)
3.3 Stakeholder needs definition documents
98(27)
3.3.1 Use a document template
98(21)
3.3.2 Use a list of needs
119(6)
Chapter 4 System Requirements Engineering
125(50)
4.1 Case study
125(1)
4.1.1 Structure of the SysML project
125(1)
4.1.2 Presentation of the results
126(1)
4.2 Definition of system requirements
126(13)
4.2.1 Define the system framework
126(1)
4.2.2 Define the system life cycle
127(1)
4.2.3 Define contexts
127(1)
4.2.4 Define uses
128(4)
4.2.5 Describe the use scenarios
132(3)
4.2.6 Define functional requirements
135(1)
4.2.7 Define non-functional requirements
136(1)
4.2.8 Ensure traceability
136(3)
4.3 System requirements analysis document
139(22)
4.4 Requirements management
161(14)
4.4.1 Fundamental elements
162(6)
4.4.2 Management workflows
168(5)
4.4.3 Use in student projects
173(2)
Chapter 5 Integration with Other Methods
175(16)
5.1 Context
175(1)
5.2 Integration with the Harmony SE method
175(5)
5.2.1 Modification of the project structure
176(1)
5.2.2 The Harmony SE method and requirements engineering
176(2)
5.2.3 Definition of stakeholders' needs
178(1)
5.2.4 Analysis of system requirements
179(1)
5.2.5 Conclusion
180(1)
5.3 Integration with the Arcadia method
180(6)
5.3.1 The Arcadia method and requirements engineering
181(1)
5.3.2 Definition of stakeholders' needs
182(1)
5.3.3 Analysis of system requirements
183(2)
5.3.4 Conclusion
185(1)
5.4 Integration with the CESAM method
186(5)
5.4.1 The CESAM method and requirements engineering
186(1)
5.4.2 Definition of stakeholders' needs
187(2)
5.4.3 Analysis of system requirements
189(1)
5.4.4 Conclusion
189(2)
References 191(4)
Index 195
Jean-Yves BRON: University of Lorraine