Why SCADE (Areva) Adapted to our deployed development process
{"Image DocumentName": "Why SCADE (Areva) Adapted to our deployed development process", "Image ImageDescription": "SCADE formalism (node and data flow) is equivalent to the. Structured Analysis SA-RT/SD method used at AREVA TA (Structured Analysis, Structured Design) Understood by both system and software engineers. Improvement of mutual comprehension is required by the IEC60680:2006 standard. Supporting our generic design policy. SCADE cycle-based language is well adapted to the way embedded safety-critical software are designed at AREVA TA. Easier to reach SIL4 than with the former classic development method. SCADE simulator : early detection of errors in specification. SCADE KCG : no unit testing at code level. Less expensive deployment than other formal methods. Only one week to design with the principal SCADE functions. Improved software validation. Formal proof techniques are enabled.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}