The Development of International Standards to Facilitate Process Improvements for Very Small Entities

2014 ◽  
pp. 1335-1361
Author(s):  
Claude Laporte ◽  
Edgardo Palza Vargas

Industry recognizes that Very Small Entities (VSEs) that develop software are very important to the economy. A Very Small Entity (VSE) is an entity (enterprise, organization, department or project) with up to 25 people..Failure to deliver a quality product on time and within budget threatens the competitiveness of VSEs and impacts their customers. One way to mitigate these risks is to put in place proven software engineering practices. Many international standards and models, like ISO/IEC 12207 or CMMI®1, have been developed to capture proven engineering practices. However, these documents were not designed for VSEs and are often difficult to apply in such settings. This chapter presents a description of the development of process improvement international standards (IS) targeting VSEs developing or maintaining software as a standalone product or software as a component of a system. The documents used by ISO/IEC JTC1/SC72 Working Group 24 (WG24), mandated to develop a set of standards and guides, and the approach that led to the development, balloting of the ISs, and TRs (Technical Reports) for VSEs are also presented. The chapter focuses on the ISO/IEC 29110 Standard3, the development of means to help VSEs improve their processes, and the description of a few pilot projects conducted to implement the processes of ISO/IEC 29110 standard.

Author(s):  
Claude Laporte ◽  
Edgardo Palza Vargas

Industry recognizes that Very Small Entities (VSEs) that develop software are very important to the economy. A Very Small Entity (VSE) is an entity (enterprise, organization, department or project) with up to 25 people..Failure to deliver a quality product on time and within budget threatens the competitiveness of VSEs and impacts their customers. One way to mitigate these risks is to put in place proven software engineering practices. Many international standards and models, like ISO/IEC 12207 or CMMI®1, have been developed to capture proven engineering practices. However, these documents were not designed for VSEs and are often difficult to apply in such settings. This chapter presents a description of the development of process improvement international standards (IS) targeting VSEs developing or maintaining software as a standalone product or software as a component of a system. The documents used by ISO/IEC JTC1/SC72 Working Group 24 (WG24), mandated to develop a set of standards and guides, and the approach that led to the development, balloting of the ISs, and TRs (Technical Reports) for VSEs are also presented. The chapter focuses on the ISO/IEC 29110 Standard3, the development of means to help VSEs improve their processes, and the description of a few pilot projects conducted to implement the processes of ISO/IEC 29110 standard.


Author(s):  
William G. Tuohey

Many years of effort have been expended by experienced practitioners and academic experts in developing software engineering standards. Organizations should see it as a positive advantage—rather than as a costly negative necessity—when they are required to develop software to a recognized standard. A genuine, constructive program of measures to ensure compliance with an objective standard will achieve development process improvements that would otherwise be difficult to motivate and bring to fruition. This chapter provides an overview and comparison of a number of software engineering standards specific to safety-critical and regulated sectors. It goes on to describe implications and benefits that flow from these standards. Informed by current software engineering research, suggestions are made for effective practical application of the standards, both at individual project and at organizational level.


Author(s):  
William G. Tuohey

Many years of effort have been expended by experienced practitioners and academic experts in developing software engineering standards. Organizations should see it as a positive advantage—rather than as a costly negative necessity—when they are required to develop software to a recognized standard. A genuine, constructive program of measures to ensure compliance with an objective standard will achieve development process improvements that would otherwise be difficult to motivate and bring to fruition. This chapter provides an overview and comparison of a number of software engineering standards specific to safety-critical and regulated sectors. It goes on to describe implications and benefits that flow from these standards. Informed by current software engineering research, suggestions are made for effective practical application of the standards, both at individual project and at organizational level.


Author(s):  
Ennio Visconti ◽  
Christos Tsigkanos ◽  
Zhenjiang Hu ◽  
Carlo Ghezzi

AbstractEngineering cyber-physical systems inhabiting contemporary urban spatial environments demands software engineering facilities to support design and operation. Tools and approaches in civil engineering and architectural informatics produce artifacts that are geometrical or geographical representations describing physical spaces. The models we consider conform to the CityGML standard; although relying on international standards and accessible in machine-readable formats, such physical space descriptions often lack semantic information that can be used to support analyses. In our context, analysis as commonly understood in software engineering refers to reasoning on properties of an abstracted model—in this case a city design. We support model-based development, firstly by providing a way to derive analyzable models from CityGML descriptions, and secondly, we ensure that changes performed are propagated correctly. Essentially, a digital twin of a city is kept synchronized, in both directions, with the information from the actual city. Specifically, our formal programming technique and accompanying technical framework assure that relevant information added, or changes applied to the domain (resp. analyzable) model are reflected back in the analyzable (resp. domain) model automatically and coherently. The technique developed is rooted in the theory of bidirectional transformations, which guarantees that synchronization between models is consistent and well behaved. Produced models can bootstrap graph-theoretic, spatial or dynamic analyses. We demonstrate that bidirectional transformations can be achieved in practice on real city models.


1998 ◽  
Vol 41 (1) ◽  
pp. 3-15 ◽  
Author(s):  
Danny C.C Poo ◽  
Mui Ken Chung

Author(s):  
Jorge Melegati ◽  
Rafael Chanin ◽  
Afonso Sales ◽  
Rafael Prikladnicki

Abstract In this position paper, our goal is to argue the need for specific software development practices to early-stage startups. In order to reach this goal, we discuss the consequences of innovative and market-driven contexts, which are two of the key elements when describing software startups. We also argue that these practices could be applied to innovative initiatives within established companies since they share similar characteristics and challenges as those from startups.


Sign in / Sign up

Export Citation Format

Share Document