As one of today’s avionics system engineers, you have a difficult task — integrating a diverse range of functionally complex components, provided by multiple suppliers, into a system that is reliable enough to ensure consistent aircraft performance and passenger safety. You also need to understand and meet numerous regulatory operating systems and protocols, including ARINC 653, ARINC 429, CAN and ARINC 664. Continue reading
“A picture is worth a thousand words.” Pictures, or model-based designs, as engineers refer to them, provide a natural means of communication. With the newest release of ANSYS SCADE System 15.2, systems engineers can use models and interface control documents (ICDs), rather than text files and long lists of data, to create and manage their systems designs.
However, when precision and complexity come forth, “data dictionaries” enter the game. A dictionary is a way to manage information in an exhaustive way but without the model, it’s not easy to get an overview of your system. The issue you’re then faced with is the consistency between the model and the dictionaries — if inconsistent, the situation is worse than without the model. Continue reading
Traditional systems engineering practices are no longer good enough to help you fully realize your smart product promise. To manage the complexities of today’s product architectures and truly understand and manage the countless dependencies across subsystems, the practice has evolved to model-based systems engineering — a concept that is the foundation of the latest ANSYS product release, SCADE System 2.0. More on that later.
Today, an accurate system definition is no longer a set of static text-based design documents, the kind that served traditional systems practices. The evolved model-based systems engineering practice consists of a living model, a model that provides a thorough understanding of the dependencies and interfaces between the various subsystems. The method represents large amounts of information in more sophisticated, interrelated ways. In addition, you can easily share and communicate models across teams. Models are more amenable to change management, and they support automated and comprehensive traceability from stakeholder requirements to implementation. Models also allow for automated verification of design rules, customized to match the methodology defined for the project. Continue reading
In today’s ultra-competitive environment, product differentiation increasingly depends on embedded software. From automobiles to airplanes to medical devices, systems architecture and embedded software are important parts of product development cycles. Being able to manage these processes effectively so that you get the desired results is becoming a differentiator.
Today, the cars that we drive have more that 10 million lines of code! Can you imagine the hours it takes to come up with the definitions of what the car should do and how it should do it — let alone implement all this correctly through software code? It’s a time-consuming process, and getting it right the first time is challenging. We’ve all seen examples of what happens when the code isn’t correct. Incorrect code can cost companies millions of dollars, and more importantly, it erodes customers’ trust in that brand.
By using model-based, production-proven software tools for the development of embedded code, products can be developed in a faster and safer manner. And, when coupled with a certified automatic code generator, compliance for standards like DO-178B/C in aerospace, ISO 26262 in automotive and EN 50128 in rail is more rapidly achieved. Continue reading