Definition of the System Architecture

Analysis of the customer requirements, definition of the System Architecture

• Successfully recovered failed SOI2 audit
• Successfully passed SOI3 and SOI4 audit.

Elicitation of the customer requirements, generation of the BMS functional requirements.

Elicitation of the customer requirements, generation of the requirements for the Converter?s Diagnostic functionalities.

• of all ECUs on the MEB platform, the DCU was the first ECU to be successfully flashed over the air.

Elicitation of the customer requirements, generation of the ICAS1?s requirements for Diagnostic communication over Ethernet, using the DoIP Protocol (ISO-13400).

1. 23 000 customer requirements elicited and covered by around 2 000 System level requirements in 18 months,
2. Successfully audited against Automotive SPICE Capability Level 3.

Elicitation of the customer requirements, generation of the EIS? requirements and functional / physical architecture of diverse functions (Networks Management, Gateway/Routing, Vehicle Theft Alarm).

1. 7500 customer requirements elicited and covered by around 1 200 System level requirements in 12 months,
2. Successfully audited against Automotive SPICE Capability Level 3 (first time EVER for the Markdorf site).

Part of a team of western experts called in to support Shanghai Avionics Corporation with the CDS? Development and Certification.
Generation of the System and Equipment Architecture Specification Definition.
Responsible for the SW Integration of the Integrated Modular Avionics Hosted Applications and the implementation of the BITE functions.

Managing a team of 4 SW Development Engineers, responsible for the Development, Certification and Entry-Into Service of the Built-In-Test-Equipment and Instrumentation Services functions.

1. Successfully passed SOI4 audit.

Responsible for the planning and monitoring of the development of the Softwares embedded within various Aircraft systems:

1. Electrical System (Hamilton Sundstrand),
2. Landing Gear Steering and Control Unit (Liebherr),
3. Cabin Management System (Panasonic Avionics),
4. Air Data System (Goodrich),
5. Integrated Circuit and Control Panel (Korry Electronics),
6. Health Monitoring System (Pratt & Whittney).

LABOTRAIN for the REGIO2N Train, Crespin, France
Brought the Zefiro 380 Iron Bird experience to the Labotrain for the REGIO2N train, also a full scale Functional Integration Bench:

1. 5 Instrumentation racks with Real Time and Automatic Testing capabilities,
2. Responsible for the Validation of the Labotrain?s SW,
3. Responsible for the Configuration and Maintenance of the Labotrain,
4. Technical interface with the French supplier responsible for the SW development part of the project.

IRON BIRD for the ZEFIRO380 Very High Speed Train, Hennigsdorf, Germany

Designed, built and configured the very first Iron Bird in the Railway industry history, a full scale Functional Integration Bench:

1. 21 Instrumentation racks with Real Time and Automatic Testing capabilities,
2. Application of Aerospace concepts and methods in requirements management, system design, quality, validation and verification,
3. Integration of Train?s real systems (TCMS, Brake, HVAC, Pantograph, Batteries) together with Labview models for those not physically available (Propulsion, Bogie, Fire Detection, OTC) and the real Train OTC (wiring and buses like MVB, CAN and RS485),
4. Creation of tools to manage the bench?s configuration (which handles more than 10 000 signals),
5. Technical interface with the French supplier responsible for the SW development part of the project.

Responsible for System Implementation and Software Development of BITE related functions:

1. Main interface between Customer and Project team for Bite related topics,
2. Capture / Management of BITE Requirements @ System and SW Level,
3. Definition of BITE SW Detailed Design and modelisation in UML, Rhapsody,
4. Technical lead of 1 SW Developer.

Responsible for Tactical Terrain System functions (Tactical Terrain Awareness Display, Tactical Ground Collision Avoidance System, Minimum Height Alert):

• Perform Requirements Engineering and Equipment Design acc. to. Airbus Standards (esp. ABD200),
• Creation of Equipment Design Document,
• Perform Design Justification activities and creation of Design Justification Dossier(s),
• Preparation of (and participation to) System, Equipment and SW review meetings,
• Perform Maintenance of various Equipment documents (e.g. Internal Interface Control Documents, Equipment Development Plan),
• Support generation & validation of operational concepts,
• Support HW and SW-design teams w.r.t. system level aspects,
• Responsible for the overall SW Scheduling (3 mono cpu boards each with between 3 and 10 Arinc 653 partitions running),
• Cooperation within International teams (located in France, Spain and Germany),
• Technical Lead of 2 System Engineers.

Responsible for Software Quality Assurance, Software Design Review Boards and auditing activity in the Avionic Systems Division:

• Support the team of software engineers to work according to the DO-178B guidelines,
• Evaluation and assessment of the full software development life cycle,
• Preparation and guidance of the audits performed by controlling agencies and customers,
• Barco?s representant toward the international agencies.

Responsible for Software Quality Assurance, Software Design Review Boards and auditing activities:

• Work with System Designers to help them to understand software requirements and also supporting Suppliers in interpreting and meeting Airworthiness and Product Specific requirements,
• Negotiate and accept suppliers plans including Configuration, Design, Validation & Verification, Quality, Certification,
• Support the Designated Certification Specialist in organizing, chairing and reviewing documentation for meetings with the Airworthiness Authorities (EASA / FAA),
• Plan and implement software assurance activities tailored to the specific project,
• Review software documentation and negotiate compliance with Airworthiness Authority requirements,
• Attend Software Design and Delivery Reviews at major milestone,
• Monitor supplier software development including validation and verification activities, to ensure the integrity and maturity of the software and ensure issues are resolved as part of the Airbus Integrated team,
• Conducting supplier negotiation and performing independence evidence based assessments and audits.

Responsible for Requirements Management of HMI related functions:

• Analysis of the evolution to be brought to the Cluster according to Volkswagen?s specifications (in German) while ensuring that all legal requirements are also captured,
• Production of specifications document,
• Complete rewrite of the SRD Module related to displayed functions and features,
• Management of customer?s requirements,
• Interface with the software, hardware, validation and production teams,
• Development of specific strategies for both End-Of-Line test equipment usage and dealership usage,
• Improvement of Visteon?s process according to the software process assessment standard ISO 15504,
• Participation to Visteon?s Volkswagen Program?s Auditing to CMMi standards.

Responsible for SW development:

• Planning and management of the project?s team (4 people),
• Analysis of the evolutions to be brought to the SW of the controller to interface it with tools of automatic code generation?s new outputs,
• Production of specification and design documentation,
• Requirements capture and management,
• Coding of the evolutions for both architectures of the controller (i80386 and i80486),
• Realization of the phases of unit testing and of integration on test benches,
• Interface with the teams responsible for the modification / creation of the tools of automatic code generation,
• Realization of the validation of the mentioned tools,
• Production of the specification documents presenting the tools used for automatic code generation,
• Compliance with Airbus quality environment / DO-178B.

Responsible for the SW Unit Testing:

• Analysis of the specification and design documents provided by Siemens,
• 1st phase of tests realized under the Rational Test Real Time environment in ?black box? mode,
• 2nd phase of tests realized on target-emulator by Siemens?,
• Frequent phone contacts with the teams of developer located in Germany and Romania (communication in English),
• Production of internal technical documents formalizing the process of Unit Testing.