1. Soporte a sistemas y software
embebido de la solución de
Visure.
Fernando Valera
2. Soporte a sistemas y software embebido
¿Qué es la ingeniería de sistemas?
•Engineering is an interdisciplinary approach and means to enable the
realization of successful systems. It focuses on defining customer needs and
required functionality early in the development cycle, documenting
requirements, then proceeding with design synthesis and system validation while
considering the complete problem:
Operations Cost & Schedule
Performance Training & Support
Test Disposal
Manufacturing
•Systems Engineering integrates all the disciplines and specialty groups into a
team effort forming a structured development process that proceeds from concept
to production to operation. Systems Engineering considers both the business
and the technical needs of all customers with the goal of providing a quality
product that meets the user needs.
2
3. Soporte a sistemas y software embebido
Reto #1:
Desarrollar sistemas complejos de mayor calidad en menor
tiempo
3
4. Soporte a sistemas y software embebido
Reto #2:
Desarrollar sistemas en entornos de colaboración cada vez
más distribuidos
4
5. Soporte a sistemas y software embebido
Reto #3:
Cumplir con las normativas y regulaciones de forma
eficiente (IEC 61508, ISO 26262, IEC 62304, CENELEC, …)
5
7. Soporte a sistemas y software embebido
Representación gráfica y flexible de los elementos del proyecto
7
8. Soporte a sistemas y software embebido
Reutilización y líneas de producto y variantes
8
9. Soporte a sistemas y software embebido
Reutilización: Identificación de los elementos reutilizables
Proyecto original
9
10. Soporte a sistemas y software embebido
Reutilización: Creación del componente
Proyecto original
10
11. Soporte a sistemas y software embebido
Reutilización: Reutilización del componente en destino
Proyecto original Proyecto destino
11
12. Soporte a sistemas y software embebido
Reutilización: Reutilización del componente en destino
Proyecto original Proyecto destino
12
13. Soporte a sistemas y software embebido
Reutilización: Cambios!!
Proyecto original – comp v2 Proyecto destino
13
14. Soporte a sistemas y software embebido
Reutilización: Propagación de los cambios
Proyecto original – comp v2 Proyecto destino – comp v2‘
14
15. Soporte a sistemas y software embebido
Gestión de riesgos: FMEA – Identificación de riesgos y acciones
15
16. Soporte a sistemas y software embebido
Gestión de riesgos: FMEA –
Generación de documentación
16
17. Soporte a sistemas y software embebido
Cumplimiento de normativas:
• Avionics (DO-178B, DO-254)
• General ISO 61508
• Road vehicles ISO 26262
• Medical devices ISO 62304
• Railway CENELEC/EN 50128
• …
17
18. Soporte a sistemas y software embebido
Cumplimiento de normativas:
Integración con RiskCAT
18
19. Soporte a sistemas y software embebido
Cumplimiento de normativas:
Integración con RiskCAT
19
20. Soporte a sistemas y software embebido
Cumplimiento de normativas:
Integración con LDRA
• Software de análisis y pruebas unitarias para la verificación automática
del software embebido
20
Increasingly complex products Shorter release cycles Reduced budgets Obsolete and changing requirements Communications breakdowns Processes must be more agile than ever
Geographically dispersed development teams Diversity of platforms and architecture Architecturally critical requirements do not receive proper emphasis System engineers cannot consider all aspects when designing the solution
Most embedded software are critical systems Many systems must be certified to support industry standards, such as DO-178B/C, IEC 61508, ISO 26262, IEC 62304, FMEA, FMECA and GAMP5 Not only must these systems comply with stands and regulations, that compliance must be documented This often requires a lot of manual work, resulting in errors and delays
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
So, we just derive another action... In this case related to the previous action, but – of course – you could also relate it to the risk if you prefer. Like always this is just a question of your process...
Unfortunately companies typically need to provide paper printouts to prove their efforts analyzing risks because the receivers of such reports (e.g. Certification bodies) do not have access to IRQA (bad luck to them...). Report Manager is the answer here: you can define reports with any layout and then generate the report containing the latest data by a single click (or during the night using the batch mode). Another use case for Report Manager: You can create a certain dashboard of your project(s) – e.g. In HTML format – which is put on the intranet making your management happy (nice pictures showing the status of the project(s))...
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.
Reusing requirements of known high quality improves the quality of the specification. Increasing of productivity by eliminating redundant effort: work of re-capturing, re-analyzing and re-specifying.