document title / titre du document TRP W ORK PLAN ... - emits - ESA

More documents

Recommendations

Info

TRP Work Plan 2005-2007 Description of Activities TEC-SB/7935/dc 12/Feb/09 TRP Reference: EME-100 (EME-011, T- Title: Effective Use of autocoded Comp. Deliverables: Current TRL: Target TRL: Application Need/Date: Application/Mission: Contract Duration: SW Clause : - Dossier0 Ref.: Consistency with Harmonisation Roadmap and Conclusions: TRP Reference: T603-28QQ Validation of Safety and Dependability Critical Software Componenets with Model Title: Based Requirements The validation of safety and dependability critical software components starts with ensuring that the requirements have been confirmed as fully testable and that they are complete and consistent. One approach that promises to facilitate the requirements definition process to achieve those three objectives is the use of models that can be analysed and simulated. Suitable models would need to be able to cope with incomplete and vague requirements at the early stages of a project’s definition and support the evolution towards formal or semiformal requirements at the end of the requirements definition phase. The simulations and analysis that would be possible on requirements models would support the preparation of high quality validation test suites. Deliverables: Technical notes (incl.: requirements models/quality requirements, and associated metrics; analysis techniques and simulation techniques for the requirements models; proof-of-concept through application to a case study). Current TRL: - Target TRL: Algorithms Application Need/Date: SW operational by 2010 Application/Mission: all missions Contract Duration: 18 months SW Clause : - Dossier0 Ref.: T-1259 Consistency with Harmonisation Roadmap and Conclusions: Not directly linked to harmonised technology. Page 133 of 227
TRP Work Plan 2005-2007 Description of Activities TEC-SB/7935/dc 12/Feb/09 TRP Reference: Title: T603-29SW System and Software Functional Requirements Techniques The activity will investigate how to integrate the two processes (system and software) through the use of complementary and integrable modelling technologies in phase A and B. The expected benefit is to arrive at the PDR with consolidated system functional requirements easily transferable to the software life cycle development. This will ensure a better continuity of the overall life cycle, from mission level modelling to software implementation through incremental model translation. The new method will complement the ASSERT results and both could be integrated in the long term in the CDF for final experimentation. The activity will include: (i) selection of a mission appropriate for mission level functional modelling and associated software requirements modelling. (ii) survey and selection of system and software modelling techniques (not limited to aerospace, but including also railway and automotive) (iii) implementation of the case study (iv) definition of the appropriate process and tools in reference with ECSS-E10Part1 and ECSS-E40Part1 (v) possible experimentation in the CDF. Deliverables: Suitable modelling methods, prototype environment, case study covering phase A and B. Current TRL: - Target TRL: Prototype Application Need/Date: SW operational >=2010 Application/Mission: All missions Contract Duration: 15 months SW Clause : - Dossier0 Ref.: T-5224 Consistency with Harmonisation Roadmap and Conclusions: On-Board SW TRP Reference: T607-01EM Title: Automation of the life cycle: automatic test generation The existence of more and more models of the system requirements allows to derive automatically sequences of test from the models. The issue is the selection of the tests which are appropriate for the test goal, and therefore the selection of the test goal itself. The selection criteria may be based on the test coverage, or on the activation of given internal states of the system, or selected use cases of the system that should be verified. The automatic tools will try to find all the test scenarios that oftwa the goal of the tests, either in a systematic way or through the use of statistic (statistical testing), or trying to achieve a coverage rate. The activity will select modelling languages on which automatic testing is possible, propose a test vector generator for given test goals, and give the process to use the tool. The activity will also investigate the statistical testing as a mean to target the test effort, precise its application to space oftware, and define how to use it in accordance with the software standards. Deliverables: Report (selection of appropriate modelling languages for automatic testing; testing criteria/statistics). Testing tool implementing the various testing policies. Report on adequacy of statistical testing with SW standards and a case study. Current TRL: Target TRL: Opeartional Application Need/Date: - tool / demontstrat SW operational >=2007 ion Application/Mission: all space project Contract Duration: 12 months SW Clause : Operational SW Dossier0 Ref.: T-5224 Consistency with Harmonisation Roadmap and Conclusions: Page 134 of 227
Page 1 and 2:
document title / titre du document
Page 3 and 4:
s TRP WORKPLAN 2008-2010 Complete L
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
f Chapter 2 TRP Work Plan 2005-2007
Page 11 and 12:
TRP Work Plan 2005-2007 Complete Li
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
f Chapter 3 TRP Work Plan 2005-2007
Page 109 and 110:
TRP Work Plan 2005-2007 Description
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190: TRP Work Plan 2005-2007 Description
Page 239: TRP Work Plan 2005-2007 Description
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
show all

document title / titre du document TRP W ORK PLAN ... - emits - ESA

Create successful ePaper yourself

Delete template?

Save as template?