ISO/IEC 29110

Last updated
ISO/IEC TR 29110-1:2016 - Overview
Systems and software engineering -- Lifecycle profiles for Very Small Entities (VSEs)
StatusPublished
First publishedSeptember 2011 (2011-09)
Latest versionJune 2016
CommitteeISO/IEC JTC 1/SC 7 Software and systems engineering
Related standardsISO/IEC/IEEE 12207, ISO/IEC/IEEE 15288, ISO/IEC/IEEE 15289
DomainSystems and Software Engineering

ISO/IEC 29110: Systems and Software Life Cycle Profiles and Guidelines for Very Small Entities (VSEs) International Standards (IS) and Technical Reports (TR) are targeted at Very Small Entities (VSEs). A Very Small Entity (VSE) is an enterprise, an organization, a department or a project having up to 25 people. The ISO/IEC 29110 is a series of international standards and guides entitled "Systems and Software Engineering — Lifecycle Profiles for Very Small Entities (VSEs)". The standards and technical reports were developed by working group 24 (WG24) of sub-committee 7 (SC7) of Joint Technical Committee 1 (JTC1) of the International Organization for Standardization and the International Electrotechnical Commission.

Contents

Industries around the world have agreed that there are certain ways of working that produce predictable results. Companies that agree to use these agreed methods and then to have their compliance measured are called ISO certificated. Some ISO-certificated organizations require that their vendors also be ISO certificated. The general standard for software development, ISO/IEC/IEEE 12207, is appropriate for medium and large software development efforts. Similarly, the general standard for system development, ISO/IEC/IEEE 15288, is appropriate for medium and large system development efforts. Systems, in the context of ISO/IEC 29110, are typically composed of hardware and software components. Things work differently in small organisations; ISO 29110 reflects that.

The need for lightweight Systems and Software Engineering standards and guides

Industry and public organizations (e.g., government agency, non-profit organization) recognize that VSEs make valuable products and services. VSEs also develop and maintain systems and software used in larger systems, so there is a need to recognize VSEs as suppliers of high quality systems and software.

According to the Organisation for Economic Co-operation and Development (OECD) [1] SME and Entrepreneurship Outlook report (2005), Small and Medium Enterprises (SMEs) constitute the dominant form of business organisation in all countries worldwide, accounting for 95% to 99% of the business population depending on country. The challenge facing OECD governments is to provide a business environment that supports the competitiveness of this large heterogeneous business population and that promotes a vibrant entrepreneurial culture.

Studies and surveys [2] [3] conclude that the majority of International Standards do not address the needs of VSEs. Conformance with these standards is difficult, if not impossible, giving VSEs no way, or very limited ways, to be recognized as entities that produce quality software. Therefore, VSEs are often cut off from some economic activities.

It has been found that VSEs find it difficult to relate international standards to their business needs and to justify their application to their business practices. Most VSEs can neither afford the resources, in terms of number of employees, budget and time, nor see a net benefit in establishing software life cycle processes. To rectify some of these difficulties, a set of standards and technical reports has been developed according to a set of VSE characteristics. [4] [5]

The documents are based on subsets of appropriate standards elements, referred to as VSE profiles. The purpose of a VSE profile is to define a subset of international Standards relevant to the VSE context, for example, processes elements of ISO/IEC/IEEE 12207 for the software engineering ISO/IEC 29110, ISO/IEC/IEEE 15288 for the systems engineering ISO/IEC 29110, and products of ISO/IEC/IEEE 15289.

ISO/IEC 29110 series, targeted by audience, have been developed to improve product and/or service quality, and process performance, as shown in the table below. ISO/IEC 29110 is not intended to preclude the use of different life cycles such as: waterfall, iterative, incremental, evolutionary or agile.

ISO/IEC 29110 target audience
ISO/IEC 29110TitleTarget audience
Part 1OverviewVSEs and their customers, assessors, standards producers, tool vendors, and methodology vendors.
Part 2Framework for profile preparationProfile producers, tool vendors and methodology vendors. Not intended for VSEs
Part 3Certification and Assessment guidanceVSEs and their customers, assessors, accreditation bodies
Part 4Profile specificationsVSEs, customers, standards producers, tool vendors and methodology vendors.
Part 5Management, engineering and service delivery guidelinesVSEs and their customers
Part 6Specific Profile specificationsVSEs, customers, standards producers, tool vendors and methodology vendors
Part 7Specific Profile guidelinesVSEs and their customers

If a new profile is needed, ISO/IEC 29110-4 [6] and ISO/IEC 29110-5 [7] can be developed without impacting existing documents and they become ISO/IEC 29110-4-m and ISO/IEC 29110-5-m-n respectively through the ISO/IEC process.

Profiles

The core characteristic of the entities targeted by ISO/IEC 29110 is size, however there are other aspects and characteristics of VSEs that may affect profile preparation or selection, such as: Business Models (commercial, contracting, in-house development, etc.); Situational factors (such as criticality, uncertainty environment, etc.); and Risk Levels. Creating one profile for each possible combination of values of the various dimensions introduced above would result in an unmanageable set of profiles. Accordingly, VSE's profiles are grouped in such a way as to be applicable to more than one category. Profile Groups are a collection of profiles which are related either by composition of processes (i.e. activities, tasks), or by capability level, or both.

Generic Profile Group

The Generic Profile Group has been defined as applicable to a vast majority of VSEs that do not develop critical systems and/or software and have typical situational factors. The Generic Profile Group is a collection of four profiles (Entry, Basic, Intermediate, Advanced), providing a progressive approach to satisfying a vast majority of VSEs. The four-stage roadmap provides a progressive approach to satisfying a vast majority of VSEs. VSEs targeted by the Entry Profile are VSEs working on small projects (e.g. at most six person-months effort) and start-ups. The Basic Profile targets VSEs developing a single application by a single work team. The Intermediate Profile is targeted at VSEs developing more than one project in parallel with more than one work team. The Advanced Profile is target to VSEs that want to sustain and grow as an independent competitive system and/or software development business.

The Software Engineering Generic Profile Group is mainly based on the ISO/IEC/IEEE 12207 Software Life Cycle Processes standard. The ISO working group mandated to develop ISO/IEC 29110 used the Mexican software process model MoProSoft [8] to help the development of ISO/IEC 29110.

A process is composed of a set of activities, and an activity is composed of a set of tasks. The figure below illustrates the 2 processes and the activities of the software engineering Basic profile. The 2 processes are described at the task level in the ISO/IEC 29110 Software engineering Management and Engineering Guide of the Basic profile.

Processes and activities of the software engineering Basic profile SW Basic Profiles processes.jpg
Processes and activities of the software engineering Basic profile

The software engineering Entry profile has the same 2 processes and activities. But the number of tasks and the number of documents is lower than the Basic profile. The table below lists the number of tasks for each process of the software generic profile group. A conditional process is a process that can be mandatory under some specific conditions, can be optional under specified conditions, and can be out of scope or not applicable under specified conditions.

The 4-Step Software Roadmap ISO 29110 software Roadmap.jpg
The 4-Step Software Roadmap

The table below lists the number of work products and roles for each process of the software generic profile group.

Number of Work Products and Roles ISO 29110 software WP Roles.jpg
Number of Work Products and Roles

The Systems Engineering Generic Profile Group is mainly based on the ISO/IEC/IEEE 15288 System Life Cycle Processes standard. The figure below illustrates the systems engineering Basic profile. Systems, in the context of ISO/IEC 29110, are typically composed of hardware and software components.

Processes and activities of the systems engineering Basic profile SE Basic Profile Processes.jpg
Processes and activities of the systems engineering Basic profile

Published Standards (IS) and Technical Reports (TR)

ISO/IEC 29110 series is a set of five different Parts. Part 1, ISO/IEC TR 29110-1, [9] defines the business terms common to the VSE Profile Set of Documents. It introduces processes, lifecycle and standardization concepts, and the ISO/IEC 29110 series. It also introduces the characteristics and requirements of a VSE, and clarifies the rationale for VSE-specific profiles, documents, standards and guides. [10] introduces the concepts for software engineering standardized profiles for VSEs, and defines the terms common to the VSE Profile Set of Documents. It establishes the logic behind the definition and application of standardized profiles. It specifies the elements common to all standardized profiles (structure, conformance, assessment) and introduces the taxonomy (catalogue) of ISO/IEC 29110 profiles.

Part 3, ISO/IEC TR 29110-3-1, [11] defines the process assessment guidelines and compliance requirements needed to meet the purpose of the defined VSE Profiles. ISO/IEC TR 29110-3-1 also contains information that can be useful to developers of assessment methods and assessment tools. ISO/IEC TR 29110-3-1 is addressed to people who have direct relation with the assessment process, e.g. the assessor and the sponsor of the assessment, who need guidance on ensuring that the requirements for performing an assessment have been met. [12]

Part 4, ISO/IEC 29110-4-1, provides the specification for all the profiles of the Generic Profile Group. The Generic Profile Group is applicable to VSEs that do not develop critical software products. The profiles are based on subsets of appropriate standards elements. VSE Profiles apply and are targeted at authors/providers of guides and authors/providers of tools and other support material.

Part 5, ISO/IEC 29110-5-m-n, provides systems engineering or software engineering project management and engineering guides and service delivery guidelines for the VSE Profile described in ISO/IEC 29110-4-m.

The figure below illustrates the components of the ISO/IEC 29110 series. The boxes in light blue are documents in development.

Components of the ISO/IEC 29110 series ISO 29110 Components.jpg
Components of the ISO/IEC 29110 series

Deployment Packages

A Deployment Package (DP) is a set of artifacts developed to facilitate the implementation of a set of practices, of the selected framework, in a Very Small Entity (VSE). The Deployment Packages, described below, have been developed to help implement the processes of the Generic Profile Group. The Generic profile group is applicable to VSEs that do not develop critical systems or software. The Generic profile group is composed of 4 profiles: Entry, Basic, Intermediate and Advanced. The Generic profile group does not imply any specific application domain.

The content of a typical deployment package is listed in table 2. The mapping to standards and models is given as information to show that a Deployment Package has explicit links to Part 5 and to selected ISO standards, such as ISO/IEC/IEEE 15288, ISO/IEC/IEEE 12207, or models such as the CMMI developed by the Software Engineering Institute. By implementing a deployment package, a VSE can see its concrete step to achieve or demonstrate coverage to ISO/IEC 29110 Part 5. Deployment Packages are designed such that a VSE can implement its content, without having to implement the complete framework at the same time.

Table 2. Content of a Deployment Package (ISO/IEC 29110-5-1-2)
1. Technical Description
         Purpose of this document
         Why this Topic is important?
2. Definitions
3. Relationships with ISO/IEC 29110
4. Overview of Processes, Activities, Tasks, Roles and Products
5. Description of Processes, Activities, Tasks, Steps, Roles and Products
         Role Description
         Product Description
         Artefact Description
6. Template
7. Example
8. Checklist
9. Tool
10. References to other Standards and Models (e.g. ISO 9001, ISO/IEC 12207, CMMI®)
11. References
12. Evaluation Form

The systems engineering or software engineering Basic Profile describes development of a single application by a single project team with no special risk or situational factors. The set of DPs for the software Basic Profile is illustrated in figure 2.

Figure 2. Deployment Packages to support the Software Basic Profile Deployment Packages Distribution.jpg
Figure 2. Deployment Packages to support the Software Basic Profile

A set of DPs to support the Systems Engineering Basic profile is under development in collaboration with members of INCOSE as illustrated in the figure below.

Deployment Packages to support the ISO/IEC 29110 Systems Engineering Basic Profile SE DP.png
Deployment Packages to support the ISO/IEC 29110 Systems Engineering Basic Profile

Deployment packages as well as other support material, such as a plug-in, are available at no cost on Internet (see below).

Implementation of ISO/IEC 29110 in software development organizations

An implementation in an IT start-up VSE by a team of two developers. [13] Their web application allows users to collaborate, share and plan their trips simply and accessible to all. The use of the Basic profile of ISO 29110 has guided the start-up to develop an application of high quality while using proven practices of ISO 29110. The total effort of this project was nearly 1000 hours. The IT start-up has recorded the effort, in person-hours, spent on tasks of the project. Only 12.6% of total effort has been spent on rework (i.e. 125 hours/990.5 hours). This indicates that the use of appropriate standards can guide all the phases of the development of a product such that the wasted effort (i.e. rework) is about the same as a more mature organization.

An implementation in a large Canadian utility provider. [14] The IT division of a large Canadian utility provider has 1950 employees that support more than 2,100 software applications. The organization had already implemented 12 level 2 and 3 process areas of the CMMI-DEV. Traditional lifecycles were used for the development of this division.

A small department within the IT division, the Mobility and Georeferenced Solutions department, is composed of 6 developers and 3 analysts, an architect and a manager. Typical projects of the department are requests from internal customers to improve a few applications. The small department was required to develop applications more quickly, and with very different technologies. Increasingly, the department had to develop proof of concepts. The problem was that the deliverables requested by the current methodology for typical projects of the IT division were too numerous, the level of documentation required was not suitable for small projects and small teams.

A project was launched within the small department to tailor ISO 29110 to their needs and adapt it to a Scrum approach. A pilot project, involving the creation of a web application for property management, has been conducted. This application greatly facilitated geographic data consultation. The total effort of this project was 1,511 hours. The table below shows, for each major task, the effort to execute the task, the effort required to review a document, such as the software specification document, in order to detect errors and, the effort required to correct the errors (i.e. the rework).

Title of taskPrevention (hours)Execution (hours)Evaluation (hours)Correction (hours)
Environment installation35---
Project Management-25222
Requirement Specification-561414
Code development35798105112
Maintenance document-4972
Web site deployment17--
Project closure-4--
Total hours711166128146

About 8.5% of the effort was invested in prevention tasks while only 9.6% was spent in rework tasks. The ISO 29110 process improvement project allowed the small department to shine within the IT division, as it became a model for future small IT projects.

Implementation in a large financial institution. [15] The IT division of a large Canadian financial institution has over 3,000 employees developing new applications and maintaining over 1250 applications. The Cash Management IT department, of 6 developers, is responsible for the development and maintenance of software tools used by traders. Each year, the department is faced with an increase in the numbers of requests to add, correct or modify features related to supported applications.

Before the implementation of the ISO 29110-agile process, customers had the following complaints:

In response to these problems, processes were evaluated by comparing the activities of the actual maintenance process to those of the Basic profile. Some shortcomings were found in the actual project management process and in the software implementation process.

The new project management process has been adapted to the context of the division, by injecting a few tasks of the SCRUM methodology. The new agile process, using the Basic profile of the ISO 29110, has been tested on three pilot projects. Recently, a team of 5-person team was added to the department to carry out all non-urgent maintenance projects using the ISO 29110 agile process.

Implementations in Thailand. [16]

The table below shows the number of ISO29110-Basic profile certified Thai organizations.

Type of Organization201220132014201520162018201920202021Total
Private148405729481002033125600
Public46212----15
Totals152465930501002033125615

Implementation of ISO/IEC 29110 in systems engineering organizations

The systems engineering Basic profile has been used in a few systems engineering organizations. As an example, in the south of France, 6 organizations implemented the Basic profile in the development of their products. [17]

In Canada, a young company involved in the design and development of communication systems for public transport. The company has been successfully audited by a third-party audit composed of 2 auditors in 2016. [18]

ISO/IEC 29110 in Academia

Over 21 countries are known to be teaching ISO/IEC 29110 at the undergraduate and graduate levels. The figure below shows a few countries that are teaching ISO/IEC 29110.

Known countries teaching ISO 29110 Countries teaching ISO 29110.jpg
Known countries teaching ISO 29110

As an example, in the state of Zacatecas of Mexico, 11 universities have implemented the software Basic profile of the ISO/IEC 29110 in their Software Development Center (SDC). A SDC provides an environment in which students apply their knowledge in a software development project. The SDCs where audited against the Basic profile of ISO/IEC 29110 by auditors of NYCE (Normalización y Certificación Electrónica), the Mexican Certification Body. As an example, 4 SDCs achieved the ISO/IEC 29110 certification in 2017.

In Thailand, over 10 universities are teaching ISO/IEC 29110. [19]

Status

For Software Engineering:

For Systems Engineering:

For Service Delivery:

In preparation

For Systems Engineering:

For Agile:

For DevOps:

Miscellaneous:

Articles and other communications

See also

Related Research Articles

<span class="mw-page-title-main">Acceptance testing</span> Test to determine if the requirements of a specification or contract are met

In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve chemical tests, physical tests, or performance tests.

<span class="mw-page-title-main">Software architecture</span> High level structures of a software system

Software architecture is the set of structures needed to reason about a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.

The following outline is provided as an overview of and topical guide to software engineering:

ISO/IEC/IEEE 12207Systems and software engineering – Software life cycle processes is an international standard for software lifecycle processes. First introduced in 1995, it aims to be a primary standard that defines all the processes required for developing and maintaining software systems, including the outcomes and/or activities of each process.

ISO/IEC 15504Information technology – Process assessment, also termed Software Process Improvement and Capability Determination (SPICE), is a set of technical standards documents for the computer software development process and related business management functions. It is one of the joint International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) standards, which was developed by the ISO and IEC joint subcommittee, ISO/IEC JTC 1/SC 7.

Software quality assurance (SQA) is a means and practice of monitoring all software engineering processes, methods, and work products to ensure compliance against defined standards. It may include ensuring conformance to standards or models, such as ISO/IEC 9126, SPICE or CMMI.

This is an alphabetical list of articles pertaining specifically to software engineering.

Capability Immaturity Model (CIMM) in software engineering is a parody acronym, a semi-serious effort to provide a contrast to the Capability Maturity Model (CMM). The Capability Maturity Model is a five point scale of capability in an organization, ranging from random processes at level 1 to fully defined, managed and optimized processes at level 5. The ability of an organization to carry out its mission on time and within budget is claimed to improve as the CMM level increases.

The ISO/IEC 15288 is a technical standard in systems engineering which covers processes and lifecycle stages, developed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). Planning for the ISO/IEC 15288:2002(E) standard started in 1994 when the need for a common systems engineering process framework was recognized. The previously accepted standard MIL STD 499A (1974) was cancelled after a memo from the United States Secretary of Defense (SECDEF) prohibited the use of most U.S. Military Standards without a waiver. The first edition was issued on 1 November 2002. Stuart Arnold was the editor and Harold Lawson was the architect of the standard. In 2004 this standard was adopted by the Institute of Electrical and Electronics Engineers as IEEE 15288. ISO/IEC 15288 has been updated 1 February 2008 as well as on 15 May 2015.

The Standard CMMI Appraisal Method for Process Improvement (SCAMPI) is the official Software Engineering Institute (SEI) method to provide benchmark-quality ratings relative to Capability Maturity Model Integration (CMMI) models. SCAMPI appraisals are used to identify strengths and weaknesses of current processes, reveal development/acquisition risks, and determine capability and maturity level ratings. They are mostly used either as part of a process improvement program or for rating prospective suppliers. The method defines the appraisal process as consisting of preparation; on-site activities; preliminary observations, findings, and ratings; final reporting; and follow-on activities.

A concept of operations is a document describing the characteristics of a proposed system from the viewpoint of an individual who will use that system. Examples include business requirements specification or stakeholder requirements specification (StRS). CONOPS is used to communicate the quantitative and qualitative system characteristics to all stakeholders. CONOPS are widely used in the military, governmental services and other fields.

In software engineering, a software development process is a process of dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. It is also known as a software development life cycle (SDLC). The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

ISO/IEC JTC 1/SC 7 Software and systems engineering is a standardization subcommittee of the Joint Technical Committee ISO/IEC JTC 1 of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC), that develops and facilitates standards within the field of engineering of software products and systems. The international secretariat of ISO/IEC JTC 1/SC 7 is the Bureau of Indian Standards (BIS) located in India.

ISO/IEC/IEEE 29119Software and systems engineering -- Software testing is a series of five international standards for software testing. First developed in 2007 and released in 2013, the standard "defines vocabulary, processes, documentation, techniques, and a process assessment model for testing that can be used within any software development lifecycle."

ISO/IEC 33001Information technology -- Process assessment -- Concepts and terminology is a set of technical standards documents for the computer software development process and related business management functions.

References

  1. ↑ Organisation for Economic Co-operation and Development (OECD), Small and Medium Enterprise (SME) Outlook Report, 2005
  2. ↑ Land, S. K., Results of the IEEE Survey of Software Engineering Standards Users. Software Engineering Standards Symposium and Forum, 1997. Emerging International Standards. ISESS 97, Walnut Creek, CA, June 1–6, pp. 242 – 270, 1997.
  3. ↑ Laporte, C.Y., Alexandre, S., O'Connor, R., A Software Engineering Lifecycle Standard for Very Small Enterprise, in R.V. O'Connor et al. (Eds.): EuroSPI 2008, CCIS 16, pp. 129–141
  4. ↑ Habra, N., Alexandre, S., Desharnais, J-M, Laporte, C.Y., Renault, A., Initiating Software Process Improvement in Very Small Enterprises Experience with a Light Assessment Tool, Information and Software Technology , Volume 50, June 2008, Pages 763-771. (Draft Version)
  5. ↑ O'Connor, R., Sanders, M., Software Lifecycle Standards for Very Small Software Companies, Software and Systems Quality Conference, Dublin, Ireland, March 4, 2009.
  6. ↑ ISO/IEC 29110-4-1:2011, "Software Engineering -- Lifecycle Profiles for Very Small Entities (VSEs) - Part 4-1: Profile specifications: Generic profile group". Geneva: International Organization for Standardization (ISO), 2011.
  7. ↑ ISO/IEC TR 29110-5-1-2:2011 Archived 2012-12-24 at the Library of Congress Web Archives, "Software Engineering - Lifecycle Profiles for Very Small Entities (VSEs) - Part 5-1-2: Management and engineering guide: Generic Profile Group: Basic Profile". Geneva: International Organization for Standardization (ISO), 2011.
  8. ↑ Oktaba, H., Felix G., Mario P., Francisco R., Francisco P. and Claudia, A.; Software Process Improvement: The Competisoft Project Archived 2011-07-25 at the Wayback Machine , IEEE Computer, October 2007, Vol. 40, No 10
  9. ↑ ISO/IEC TR 29110-1, "Software Engineering - Lifecycle Profiles for Very Small Entities (VSEs) - Part 1: Overview". Geneva: International Organization for Standardization (ISO), 2016.
  10. ↑ Part 2-1, ISO/IEC 29110-2-1, Software Engineering - Lifecycle Profiles for Very Small Entities (VSEs) - Part 2-1: Framework and taxonomy, Geneva: International Organization for Standardization (ISO), 2015.
  11. ↑ ISO/IEC TR 29110-3-1, "Software Engineering - Lifecycle Profiles for Very Small Entities (VSEs) - Part 3: Assessment Guide". Geneva: International Organization for Standardization (ISO), 2015.
  12. ↑ Varkoi, T., Makinen, T., A Process Model for Very Small Software Entities Archived 2011-07-25 at the Wayback Machine , SPICE conference, 18–20 May 2010 - Pisa, Italy
  13. ↑ Laporte, C.Y., Hébert, C., Mineau, C., Development of a Social Network Website Using the New ISO/IEC 29110 Standard Developed Specifically for Very Small Entities, Software Quality Professional Journal, ASQ, vol. 16, no. 4, pp. 4-25 (2014).
  14. ↑ Laporte, C.Y., O'Connor, R., Software Process Improvement Standards and Guides for Very Small Organizations - An Overview of Eight Implementation, CrossTalk - The Journal of Defense Software Engineering, May/June 2017. Vol. 30, No 3, pp 23-27.
  15. ↑ Laporte, C.Y., O'Connor, R., Software Process Improvement Standards and Guides for Very Small Organizations - An Overview of Eight Implementation, CrossTalk - The Journal of Defense Software Engineering, May/June 2017. Vol. 30, No 3, pp 23-27.
  16. ↑ Laporte, C. Y., Munoz, M., Gerançon, B., The Education of Students About Software Engineering Standards and Their Implementations in Very Small Entities. IEEE Canada-International Humanitarian Technology Conference, July 20–21, 2017, Toronto, Ontario, Canada, pp. 94-98
  17. ↑ Galinier, S., Laporte, C. Y., Connecting Business Development and System Engineering with ISO/IEC 29110 Standard in Small and Medium Enterprises of France, 2018 IEEE International Systems Engineering Symposium (ISSE), Rome, Italy, 2018, pp. 1-7.
  18. ↑ Laporte, C.Y., Tremblay, N., Menaceur, J., Poliquin, D., Houde, R., Systems Engineering and Management Processes for Small Organizations with ISO/IEC 29110 - An Implementation in a Small Public Transportation Company, 11th Annual IEEE International Systems Conference, April 24–27, 2017, Montreal, Quebec, Canada, pp. 112-119
  19. ↑ Laporte, C. Y., Munoz, M., Gerançon, B., The Education of Students About Software Engineering Standards and Their Implementations in Very Small Entities. IEEE Canada-International Humanitarian Technology Conference, July 20–21, 2017, Toronto, Ontario, Canada, pp. 94-98
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.