 |
Software Quality Assurance
|
|
|
Software Quality Assurance
|
|
This Software Quality Assurance describes the procedure and activities for the development, maintenance and provision of software at EMOTIVE. It essentially applies to the software products of the OTX tool chain: Open Test System. But also for their customer-specific extensions and for independent software services. All the Software activities are defined and planned in this plan. The Software Quality Assurance is continuously updated and maintained. The basis for the software development are approved requirements.
Important: We want to work efficiently. All employees involved in software development are computer scientists with a university degree. We therefore do not describe the basics of software development here, but only the way we actually work.
Note: Quality assurance (QA) is a way of preventing bugs and gaps in software products and avoiding problems when delivering to customers.
The Open Test System Tool Chain is a complete solution for using the OTX standard according to ISO 13209 (OTX) in automotive environment. It consists of the OTX development environment OTX Development Environment, the OTX runtime environment OTX Runtime API, and the OTX Player, a generic tester for the simple execution of OTX procedures, see user documentation.
With the OTX development environment Open Test Framework (short OTF) the user can design, maintain and handle OTX projects, he can import, export and create executable PTX files, ensure OTX data consistency, execute and debug OTX projects and manage OTX mappings.
The OTX-Runtime API (short OTX Runtime) is a programming interface for the easy, fast and reliable execution of OTX procedures in own applications. It works independently even without the OTX Development Environment and is available for Windows and Linux. The API is available for C++, DotNet and Java.
The OTX Runtime Converter API (short OTX Compiler) is a programming interface for the easy, fast and reliable validation and compilation of OTX procedures in own applications. It works independently even without the OTX Development Environment and is available for Windows and Linux. The API is available for DotNet. It works on Window via Net Framework and on Linux via Mono.
The Open Test Player (short OTP) is a complete generic, OTX based tester for the simplest distribution and execution of test sequences. It is based 100% on the Open Test Runtime API and can easily be adapted to company look and feel. It works with Windows. Implementations for iOS and Android are planned. A player project (PPX) can be graphically created and tested in the Open Test Framework without any programming knowledge.
The aim of software development is the provision of software products (tools) for the editing, safeguarding and execution of OTX documents. The products are used by vehicle manufacturers or their suppliers in development, production, sales and inside the vehicle.
Due to the nature of product development, there is no clear end of development. As long as the market requires OTX products in sufficient numbers, the software products will be constantly improved, adapted and further developed. This concerns in particular:
All changes, enhancements and error corrections are managed via the Issue Tracking System (REDMINE). The code is managed via SVN.
The following guidelines apply to product development:
Mission Statement: "Profit is not a goal, but rather the result that comes about by itself if you have done everything right and, in particular, carefully consider the interests of customers and employees."
Scope of Open Test Framework:
Scope of Open Test Player
Scope of OTX Runtime API
Scope of OTX Runtime Converter API