-
Notifications
You must be signed in to change notification settings - Fork 20
SysML modelling of SRS
cyrilcornu edited this page Mar 15, 2013
·
13 revisions
This pages describes concerns and solutions for modelling SUBSET-026 (SRS, System Requirement Specification) with SysML.
Please list here your modelling activity.
General attempt to model some parts of the SRS using SysML. No specific goal for now.
Tool tested (for now):
- Topcased
- Enterprise Architect
- Modelisation aspects of the subset 026: state machines, procedures, data flows and data structures
- Proof aspect : MBT (Matelo), Safety Analysis (Safety Architect)
- Requirements : Requirement diagram
- Diagrams used : IBD, BDD, requirement diagram, Sequence diagram, State charts
- The model: to be provided ASAP
- Documentation: to be provided ASAP
- Tools : Papyrus (Eclipse), MaTeLo, Diversity
- Modelisation aspects state machines, timeouts, data structures
- Proof aspect : MBT
- Requirements : Requirement diagram
- Diagrams use : State charts, class diagram, requirement diagram
- The model https://github.com/openETCS/model-evaluation/tree/master/model/EA-SysML
- Documentation: https://github.com/openETCS/model-evaluation/blob/master/model/EA-SysML/doc/descriptionReport.pdf?raw=true
- Tools : enterprise architect, RT-tester
FIXME: to fill
FIXME: to fill
@MariellePetitDoche : Which formalism do you use to express requirements ?
- SysML requirement diagrams ?
- ReqIF standard ?
- other ?