@inproceedings {25544,
	title = {A Restricted Natural Language based Use Case Modeling Methodology for Real-time Systems},
	journal = { 9th Workshop on Modelling in Software Engineering (MiSE{\textquoteright}2017)},
	year = {2017},
	publisher = {IEEE},
	author = {Zhang, Huihui and Yue, Tao and Ali, Shaukat and Wu, Ji and Liu, Chao}
}
@article {24520,
	title = {Assessing the Quality of Industrial Avionics Software: An Extensive Empirical Evaluation},
	journal = {Empirical Software Engineering},
	year = {2016},
	publisher = {Springer},
	author = {Wu, Ji and Ali, Shaukat and Yue, Tao and Tian, Jie and Liu, Chao}
}
@techreport {25290,
	title = {Modelling and Validating Real-Time Properties at the Requirements Level},
	number = {2015-2},
	year = {2015},
	note = {This technical report is an earlier version of a published paper.},
	publisher = {Simula Research Laboratory},
	author = {Zhang, Huihui and Yue, Tao and Ali, Shaukat and Wu, Ji}
}
@article {Simula.simula.2764,
	title = {A Modeling Methodology to Facilitate Safety-Oriented Architecture Design of Industrial Avionics Software},
	journal = {Software: Practice and Experience},
	year = {2014},
	publisher = {John Wiley and Sons},
	abstract = {Ensuring that avionics software meets safety requirements at each development stage is very important to warrant the safe operation of an avionics system. Many safety requirements are imposed by various standards and industrial regulations that must be met by avionics software. One of such standards is DO-178B/C, which provides guidelines (e.g., development process and objectives to satisfy in development activities) for meeting safety requirements. This paper presents a modeling methodology including a UML profile for specifying safety requirements on a component-based architecture model and a set of design guidelines on avionics software. These safety requirements were identified from both standards (mainly DO-178B/C) and current engineering practices in the domain of avionics systems. The methodology automatically enforces these safety requirements. We have applied the methodology on an industrial autopilot system and several previously uncaught faults were revealed.},
	author = {Wu, Ji and Yue, Tao and Ali, Shaukat and Zhang, Huihui}
}
@inproceedings {Simula.simula.2822,
	title = {A Systematic Approach to Automatically Derive Test Cases From Use Cases Specified in Restricted Natural Languages},
	journal = {8th System Analysis and Modelling Conference (SAM{\textquoteright}14)},
	year = {2014},
	publisher = {Springer},
	type = {Conference},
	address = {Switzerland},
	abstract = {In many domains, such as avionics, oil and gas, and maritime, a common practice is to derive and execute test cases manually from requirements, where both requirements and test cases are specified in NL by domain experts. The manual execution of test cases is largely dependent on the domain experts who wrote the test cases. The process of manual writing of requirements and test cases introduce ambiguity in their description and in addition test cases may not be effective since they may not be derived by systematic applying coverage criteria. In this paper, we report a systematic approach to support automatic derivation of manually executable test cases from use cases. Both use cases and test cases are specified in restricted NLs along with carefully defined templates implemented in a tool. We evaluate our approach with four case studies (in total having 30 use cases and 579 steps of flow of events), two of which are industrial case studies from the oil and gas and avionics domains. Results show that our tool was able to correctly process all the case studies and systematically (by following the carefully defined structure coverage criterion) generate 30 TCSs and 389 test cases. Moreover our approach allows defining different test coverage criteria on requirements other than the one already implemented in our tool.},
	keywords = {Conference},
	author = {Zhang, Man and Yue, Tao and Ali, Shaukat and Zhang, Huihui and Wu, Ji},
	editor = {Amyot, Daniel and Pau Fonseca i. {Casas} and Mussbacher, Gunter}
}
@inproceedings {Simula.simula.2066,
	title = {Assessing the Reliability of an Industrial Avionics Software: Results, Insights and Recommendations},
	journal = {The 24th IEEE International Symposium on Software Reliability Engineering},
	year = {2013},
	publisher = {IEEE},
	type = {Conference},
	address = {Pasadena, CA},
	abstract = {Real Time Operating System for Avionics (RTOS4A) is responsible for providing an operating environment for avionics application software. Avionics software being safety-critical in nature poses several safety and reliability requirements on RTOS4A in addition to the requirements imposed by standards, for instance, DO-178B. Due to this reason, reliability assessment of RTOS4A is very critical to demonstrate confidence about its reliability to its relevant stakeholders. One common way of assessing reliability is by systematic analyses of testing data such as number of tests, number of failures, and coverage using appropriate statistical tests. In this paper, we report our experience of assessing the reliability of an industrial RTOS4A based on testing data collected for 17 months on eight continuous releases. We studied correlation among various measures including: Testing Effort Measures (e.g., complexity of test cases), Testing Effectiveness Measures (e.g., number of failures), and Complexity Measures (e.g., number of functions in a release) and provide a set of recommendations to assess the reliability of RTOS4A that serve as guidelines to practitioners in the domain of RTOS4A.},
	author = {Wu, Ji and Ali, Shaukat and Yue, Tao and Tian, Jie}
}
@inproceedings {27059,
	title = {Ensuring Safety of Avionics Software at the Architecture Design Level, An Industrial Case Study},
	journal = {The 13th International Conference on Quality Software (QSIC 2013)},
	year = {2013},
	author = {Wu, Ji and Yue, Tao and Ali, Shaukat}
}
@inproceedings {Simula.simula.2014,
	title = {Ensuring Safety of Avionics Software at the Architecture Design Level: an Industrial Case Study},
	journal = {The 13th International Conference on Quality Software (QSIC 2013)},
	year = {2013},
	publisher = {IEEE},
	type = {Conference},
	address = {.},
	abstract = {Ensuring that avionics software meets safety requirements at each development stage is very important to warrant the safe operation of an avionics system. Many safety requirements are imposed by various standards and industrial regulations that must be met by avionics software. One of such standards is DO-178B/C, which provides guidelines (e.g. development process and the objectives to satisfy in development activities) for meeting the safety requirements. This paper presents a modeling methodology including a UML profile for specifying safety requirements on a component-based architecture model and a set of design guidelines on avionics software. These safety requirements were identified from both standards (mainly DO-178B/C) and current engineering practices in the domain of avionics system. The methodology enforces safety requirements automatically. We have applied the methodology on an industrial autopilot system and several previously uncaught faults were revealed.},
	keywords = {Conference},
	author = {Wu, Ji and Yue, Tao and Ali, Shaukat}
}
