Developing software and systems engineering standards

There are a great many Software and Systems Engineering standards such as those supported by organizations like the ISO (International Organization for Standardization). It is often said that many of these have a poor reputation with many sections of academia and industry. Whilst there may be many publicized business advantages of using standards, standardization is an often-neglected route for exploiting academic and commercial research. Often researchers have little experience of standardization to plan, implement and exploit their research utilizing standards. Involvement with standards development organizations in your research can positively increase international recognition and highlight in a world stage your research and enhance your international reputation. This keynote address examined the benefits of being directly involved in the standards community for both industry and academia and specifically how standards can inform your research. Based upon personal experience as Ireland Head of Delegation to ISO's Software and Systems Engineering group and that of being an ISO standards editor, this keynote will examine the issues and benefits of becoming actively involved inside the standardization community and how this can be translated into your personal research agenda

Mobile Application Usability: Heuristic Evaluation and Evaluation of Heuristics

Ger Joyce, Mariana Lilley, Trevor Barker, and Amanda Jefferies, 'Mobile Application Usability: Heuristic Evaluation and Evaluation of Heuristics', paper presented at AHFE 2016 International Conference on Human Factors, Software, and Systems Engineering. Walt Disney World, Florida USA, 27-31 July 2016Many traditional usability evaluation methods do not consider mobile-specific issues. This can result in mobile applications that abound in usability issues. We empirically evaluate three sets of usability heuristics for use with mobile applications, including a set defined by the authors. While the set of heuristics defined by the authors surface more usability issues in a mobile application than other sets of heuristics, improvements to the set can be made

Why and How Your Traceability Should Evolve: Insights from an Automotive Supplier

Traceability is a key enabler of various activities in automotive software and systems engineering and required by several standards. However, most existing traceability management approaches do not consider that traceability is situated in constantly changing development contexts involving multiple stakeholders. Together with an automotive supplier, we analyzed how technology, business, and organizational factors raise the need for flexible traceability. We present how traceability can be evolved in the development lifecycle, from early elicitation of traceability needs to the implementation of mature traceability strategies. Moreover, we shed light on how traceability can be managed flexibly within an agile team and more formally when crossing team borders and organizational borders. Based on these insights, we present requirements for flexible tool solutions, supporting varying levels of data quality, change propagation, versioning, and organizational traceability.Comment: 9 pages, 3 figures, accepted in IEEE Softwar

The EAST-ADL: A Joint Effort of the European Automotive Industry to Structure Distributed Automotive Embedded Control Software

International audienceAround ninety percent of vehicle innovations are driven mainly by electronics. Hence, software- and systems-engineering becomes a crucial discipline which vehicle manufacturers and their suppliers have to conquer. Automotive software runs on so-called Electronic Control Units (ECU). Besides a micro- controller and memory an ECU consists of power electronics to drive sensors and actuators

The Evolution of the ISO/IEC 29110 set of standards and guides

While the quality of products is a competitive advantage for very small software development organizations, the usage of Software and Systems Engineering standards amongst such very small organizations is extremely low. A key factor in the literature explaining this lack of quality standards adoption is the perception by small and very small organizations that such standards have been developed for large multi-national companies and not with small and very small organizations in mind. The ISO/IEC 29110 standard is unique amongst software and systems engineering standards, in that the working group (ISO/IEC JTC1/SC7 WG 24) mandated to develop a new standard approached industry to conduct a needs assessment and gather actual requirements for a new standard as part of the standards development process. This paper presents a historical perspective behind the development of the ISO/IEC 29110 systems and software engineering standard and its constituent components, including the rationale behind its development and the innovative design of implementation guides to assist very small companies in adopting the standards. Further this paper will present an overview of the various parts of the ISO/IEC 29110 family and briefly present the plans for the future evolution of this series of standards

Harmonizing Systems and Software Cost Estimation

The objective of this paper is to examine the gaps and overlaps between software and systems engineering cost models with intent to harmonize the estimates in engineering engineering estimation. In particular, we evaluate the central assumptions of the COSYSMO and COCOMO II models and propose an approach to identify gaps and overlaps between them. We provide guidelines on how to reconcile and resolve the identified gaps and overlaps. The ultimate purpose of this work is to develop effective techniques for accurately estimating the combined systems and software engineering effort for software-intensive systems

Decision-making in software development

There are many decisions made during the processes of software development and there are several decision-making methods that could be used in any specific circumstance. International standards for software and systems engineering tend to assume a specific decision-making method will be used in some processes while in others the decision-making method is implied rather than explicitly stated. An empirical study investigated which decision-making methods were used by practicing software developers. The study found that practitioners used a variety of methods, highlighting the need for flexible processes and flexible assessment of those processes where decision-making is concerned