![](bgb.png)
project, tool qualification has not been focused up to
now, but a tool qualification kit may be developed on
top later on.
Next step is the application of the tool on a large
multi-module project to evaluate its scalability. Also
other process workflows beyond DO-178C should be
integrated in subsequent projects to prove general ap-
plicability. Future research may also focus on a stron-
ger interaction with MATLAB, Simulink, and State-
flow. Instead of manually triggering a rescan of the
project, callbacks might be used to automatically up-
date the status of jobs in the background in situ, whe-
never a model or object has been changed.
8 CONCLUSIONS
The paper has introduced a build tool for MBD, which
seamlessly integrates process-oriented features, like
model scaffolding based on CoC, to improve standard
compliance and standardisation from the beginning.
Additionally, a unique interface for automatic, semi-
automatic, and manual tasks, including review and
justification capabilities, as well as traceability cap-
turing in the background has been presented.
A short example has demonstrated the necessity
for build automation on the one hand, and the high
process coverage, which is achievable by integrating
various tools into the build and parsing the individual
results, on the other hand. The discussion of related
work has highlighted the difference to existing soluti-
ons. Finally, a summary of limitations coming along
with the build tool and future enhancement plans has
been provided.
The presented tool has the ability to solve pro-
blems of different process participants. With the Life
Cycle Package, the Process Manager is able to dis-
tribute workflows, standards, checklists, and proce-
dures in a new level of detail. Model scaffolding
improves the structure and clarity of software mo-
dules. Developers must read less documents and a
much higher standard compliance is already expected
by construction. Additionally, less time is invested
in reviews, since checklists must only be re-reviewed
if the tool detects deprecation (in contrast to written
checklists). Traceability does not have to be created
retrospectively or manually, but is implicitly captured
during build. This eliminates deprecated traceability
links. Various methods to evaluate completeness of
artefacts, compliance to standards, consistency, and
cleanliness support assessors in their daily work or
are pluggable to other build automation systems, like
a CI server.
With the presented tool, higher process compli-
ance is achieved whilst investing less effort. It aligns
with the trends of modern software development and
has the potential to support increasing software com-
plexity and size, but also to accelerate development
cycles in high-integrity MBD.
REFERENCES
Asuncion, H. U., Asuncion, A. U., and Taylor, R. N. (2010).
Software traceability with topic modeling. In Kra-
mer, J., Bishop, J., Devanbu, P., and Uchitel, S., edi-
tors, Proc. of the 32nd ACM/IEEE International Con-
ference on Software Engineering - ICSE ’10, page 95,
New York, New York, USA. ACM Press.
Basagiannis, S. (2016). Software certification of airborne
cyber-physical systems under DO-178C. In Proc. of
2016 International Workshop on Symbolic and Nume-
rical Methods for Reachability Analysis (SNR), pages
1–6. IEEE.
Berglund, T. and McCullough, M. (2011). Building and
testing with Gradle. O’Reilly, Beijing and Sebastopol.
Bhatt, D., Madl, G., Oglesby, D., and Schloegel, K. (2010).
Towards Scalable Verification of Commercial Avio-
nics Software. In AIAA, editor, Proc. of AIAA Info-
tech@Aerospace 2010.
Broy, M., Kirstan, S., Krcmar, H., and Sch
¨
atz, B. (2014).
What is the Benefit of a Model-Based Design of Em-
bedded Software Systems in the Car Industry? In Ma-
nagement Association, I. R., editor, Software Design
and Development, pages 310–334. IGI Global.
Conrad, M., Englehart, M., Erkkinen, T., Lin, X., Nirakh,
A. R., Potter, B., Shankar, J., Szpak, P., Yan, J., and
Clark, J. (2012). Automating Code Reviews with Si-
mulink Code Inspector. In Dagstuhl, editor, Proc. of
VIII Dagstuhl-Workshop, M
¨
unchen. fortiss GmbH.
Conrad, M., Friedman, J., and Sandmann, G. (2009). Ve-
rification and Validation According to IEC 61508:
A Workflow to Facilitate the Development of High-
Integrity Applications. SAE International Journal of
Commercial Vehicles, 2(2):272–279.
Couto, R., Ribeiro, A. N., and Campos, J. C. (2014). The
Modelery: A Collaborative Web Based Repository.
In Hutchison, D., Kanade, T., Kittler, J., Kleinberg,
J. M., Kobsa, A., Mattern, F., Mitchell, J. C., Naor,
M., Nierstrasz, O., Pandu Rangan, C., Steffen, B., Ter-
zopoulos, D., Tygar, D., Weikum, G., Murgante, B.,
Misra, S., Rocha, A. M. A. C., Torre, C., Rocha, J. G.,
Falc
˜
ao, M. I., Taniar, D., Apduhan, B. O., and Gervasi,
O., editors, Computational Science and Its Applicati-
ons – ICCSA 2014, volume 8584 of Lecture notes in
computer science, pages 1–16. Springer International
Publishing, Cham.
Dillaber, E., Kendrick, L., Jin, W., and Reddy, V., editors
(2010). Pragmatic Strategies for Adopting Model-
Based Design for Embedded Applications. SAE In-
ternational.
A Process-oriented Build Tool for Safety-critical Model-based Software Development
201