Crosstalk May 2013- International Systems and Software Engineering Standards for Very Small Entities...

7/27/2019 Crosstalk May 2013- International Systems and Software Engineering Standards for Very Small Entities Laporte

1/68 CrossTalkMay/June 2013

LARGE SCALE AGILE

Claude Y. Laporte, cole de technologie suprieureRory V. OConnor, Dublin City UniversityGauthier Fanmuy, ADN

Abstract. Very Small Entities (VSEs) developing systems or sotware are verymportant to the military since the components they develop are oten integratednto products made by larger organizations. Failure to deliver a quality product onme and within budget may threaten both customers and suppliers. One way to

mitigate these risks is to put in place proven engineering practices. ISO has ap-roved recently the publication o standards and technical reports, known as ISO/EC 29110, to address the needs o VSEs.

International Systemsand Software Engineering

Standards for VerySmall Entities

VSEs since a system integrator as well as its prime suppliershave also very small projects.

Research shows that small and very small enterprises canfnd it difcult to relate to ISO standards to their business needsand to justiy the application o the standards to their businesspractices [4]. Most o these enterprises do not have the expertisor can not aord the resourcesin number o employees, cost,

and timeor see a net beneft in establishing liecycle processeThere is sometimes a disconnect between the short-term visiono an enterprise, looking at what will keep it in business oranother six months or so, and the long-term or mid-term benefto gradually improving the ways the enterprise can manage itsdevelopment and maintenance processes. A primary reason citeby many small enterprises or this lack o adoption o systems osotware engineering standards, is the perception that they havebeen developed by and or large companies and not with verysmall organizations in mind [5]. To date, VSEs have no or very limited ways to be recognized, by large organizations, as enterprisethat produce quality products within budget and calendar in thei

domain and may thereore be cut o rom some economic activties. Accordingly there was a need to help VSEs understand anduse the concepts, processes and practices proposed in the ISO/IEC JTC1/SC7s1 international engineering standards.

The recently published set o ISO/IEC 29110 internationalstandards (IS) and technical reports (TR) are aimed at addressingthese issues as well as the specifc needs o VSEs. The engineeringstandards and guides developed by an ISO working group, WorkingGroup 24 (WG24)2, are targeted at VSEs which do not have experience or expertise in selecting, or a specifc project, the appropriateprocesses rom liecycle standards such as ISO/IEC 12207 [6] orISO/IEC 15288 [7], tailor them to the needs o a specifc project.

In the next section, a high level summary o the approach

used to develop the ISO/IEC 29110 standard and discusssome o its key concepts, including project management andsotware implementation processes. We will then present theinitial support work on deployment assistance or VSE in usingthis standard and fnish by discussing the planned uture work

The WG24 Approach to the Development o

Standards or VSEs Developing Sotware

Since an international standard dedicated to the sotwareliecycle processes was already available, i.e. ISO/IEC 12207,WG24 used the concept o ISO standardized profles (SP)to develop the new standards or VSEs developing sotware.

From a practical point o view, a profle is a kind o matrix whicidentifes precisely the elements that are taken rom existingstandards rom those that are not. The overall approach olloweby WG24 to develop this new standard or VSE consisted o thollowing steps:

1. Develop a set o profles or VSEs not involved in criticalsotware development,

2. Select the ISO/IEC 12207 process subsets applicable tVSEs having up to 25 people,

3. Select the description o the products, to be produced byproject, using ISO/IEC 15289 standard [8],

4. Develop guidelines, checklists, templates, and examples support the subsets selected.

Introduction

More than ever, integrators o military systems depend ontheir numerous suppliers to deliver sub-systems meeting evolv-ing requirements correctly, predictably, rapidly, and cost eec-tively. A supply chain o a large system oten has a pyramidalstructure. I an undetected deect is let in a low level com-ponent, once this component is integrated into a higher levelcomponent, the deect may still be undetected. For example, asillustrated in Figure 1, a large manuacturer integrated into one

o its products a component, with an undetected sotware error,which was produced by one o its lowest-level suppliers. Thisdeective component resulted in a loss o millions o dollars bythe manuacturer.

Figure 1: Example o the supply chain o a large manuacturer (adapted rom [1])

Prime Suppliers (60)

Second-level Suppliers (600)

Third-level Suppliers (~6,000)

Manufacturer

The ability o organizations to compete, adapt, and survivedepends increasingly on quality, productivity, cycle time and cost.Systems and sotware are getting bigger and more complexevery year. As an example, a top o the line cars have up to 100million lines o code, 80 processors and 5 bus systems [2].

Industry recognizes the value o VSEs, i.e. enterprises, orga-nizations, projects or departments with up to 25 people [3], incontributing valuable products and services. There is a need tohelp these organizations understand the beneft o the concepts,processes and practices described in systems and sotwareengineering standards, and to help them in their implementation.At every level o the supply chain, illustrated in fgure 1, we fnd


2/6CrossTalkMay/June 2013

LARGE SCALE AG

Generic Profle Group

Profle Groups are a collection o profles. The Generic ProfleGroup has been defned as applicable to a vast majority oVSEs that do not develop critical systems or critical sotware [9].This Profle Group is a collection o our profles (Entry, Basic,Intermediate, Advanced) providing a progressive approach tosatisying a vast majority o VSEs. VSEs targeted by the Entry

Profle are VSEs working on small projects (e.g. at most sixperson-months eort) and or start-up VSEs. The Basic Profledescribes sotware development practices o a single applica-tion by a single project team o a VSE. The Intermediate Profleis targeted at VSEs developing multiple projects within the orga-nizational context taking advantage o it. The Advanced Profleis targeted to VSEs which want to sustain and grow as anindependent competitive sotware development business. Table1 illustrates this profle group as a collection o our profles,providing a progressive approach to satisying the requirementso a profle group.

Generic Profile Group

Entry Basic Intermediate Advanced

ISO/IEC

29110

Title Target audience

Part 1 Overview VSEs, customers, assessors, standard

producers, tool vendors, and methodo

vendors.

Part 2 Framework and taxonomy Standards producers, tool vendors and

methodology vendors. Not intended fo

VSEs.

Part 3 Assessment guide Assessors, customers and VSEs

Part 4 Profile specifications Standards producers, tool vendors and

methodology vendors. Not intended fo

VSEs.

Part 5 Management and engineering

guide

VSEs and customers

Table 1: Graduated profles o the Generic profle group(adapted rom [9])

The ISO/IEC 29110 standards and technical reports targetedby audience are described in Table 2.

The set o documents, listed in table 2, or the Basic pro-

fle ([9], [10], [11], [12], [13]) were published in 2011. At therequest o WG24, all ISO/IEC 29110 TRs are available at nocost rom ISO . The Management and Engineering Guide,the most valuable document or VSEs, has being translated toFrench by Canada and to Spanish by Peru and adopted as aPeruvian national standard. The set o 5 documents has beentranslated to Portuguese by Brazil and adopted as a Braziliannational standard. Japan has translated and adopted ISO/IEC29110 as a Japanese national standard. The Management andEngineering guide o the Entry profle has been published inSeptember 2012 in English [14] and in French [15].

Overview o the Basic Profle or VSEs

Developing Sotware

The purpose o the Basic Profle is to defne Sotware Imple-mentation (SI) and Project Management (PM) processes rom asubset o ISO/IEC 12207 and ISO/IEC 15289 appropriate orVSEs. The main reason to include project management is thatthe core business o VSEs is sotware development and theirfnancial success depends on successul project completionwithin schedule and on budget, as well as on making a proft.The high-level relationship between the SI and the PM process-es is illustrated in Figure 2.

Table 2: ISO/IEC 29110 target audience (adapted rom [3])

As illustrated in fgure 2, the customers statement o work isused to initiate the PM process. The project plan will be used toguide the execution o the sotware requirements analysis, sot-ware architectural and detailed design, sotware construction,and sotware integration and test, and product delivery activities.

Verifcation, validation, and test tasks are included in the SI pro-cess. The PM process closure activity will deliver the SotwareConfguration (i.e. a set o sotware products) and will obtain thecustomers acceptance to ormalize the end o the project.

Overview o the Project Management Process

The purpose o the Project Management process is to establishand carry out the tasks o the sotware implementation projectin a systematic way, which allows compliance with the projectsobjectives in terms o expected quality, time, and costs [12]. Theseven objectives o the PM process are listed in table 3.

Figure 2: Basic profle process relationship [12]

PM.O1. The Project Plan for the execution of the project is developed according to the State

Work and reviewed and accepted by the Customer. The tasks and resources necessary to compwork are sized and estimated.

PM.O2. Progress of the project is monitored against the Project Plan and recorded in the P

Status Record.

PM.O3. The Change Requests are addressed through their reception and analysis. Changes to s

requirements are evaluated for cost, schedule and technical impact.

PM.O4. Review meetings with the Work Team and the Customer are held. Agreements are re

and tracked.

PM.O5. Risks are identified as they develop and during the conduct of the project.

PM.O6. A software Version Control Strategy is developed. Items of Software Configuration are iddefined and baselined. Modifications and releases of the items are controlled and made availabl

Customer and Work Team including the storage, handling and delivery of the items.

PM.O7. Software Quality Assurance is performed to provide assurance that work produ

processes comply with the Project Plan and Requirements Specification.

Table 3: Objectives o the Project Management process o the Basic Profle [
http://standards.iso.org/ittf/PubliclyAvailableS-tandards/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableS-tandards/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableS-tandards/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableS-tandards/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableS-tandards/index.html



LARGE SCALE AGILE

Project

Planning

Statement of Work

Project

Assessment

and Control

Project Plan

Execution

Project Closure

Verification Results

Meeting Record Project Repository

Project Plan

Project Repository

Backup

Meeting Record

Progress StatusRecord

Correction Register

Acceptance Record

Software

Configuration

Change Request

Figure 3: Project management process diagram or sotware [12]

Role Task List Input Products Output Products

PM

CUS

PM.1.2 Define with the Customer the Delivery

Instructions of each one of the Deliverables

specified in the Statement of Work.

Statement of Work

[reviewed]

Project Plan

- Delivery Instructions

PM

CUS

PM.1.14 Review and accept the Project Plan.

Customer reviews and accepts the Project Plan,

making sure that the Project Plan elements match

with the Statement of Work.

Project Plan [verified] Meeting Record

Project Plan [accepted]

Table 4: Example o 2 tasks o the Project Planning Activity [12]

Table 5: Objectives o the Sotware Implementation process o the Basic Profle [12]

SI.O1. Tasks of the activities are performed through the accomplishment of the current Project Plan.

SI.O2. Software requirements are defined, analyzed for correctness and testability, approved by the

Customer, baselined and communicated.

SI.O3. Software architectural and detailed design is developed and baselined. It describes the Software

Components and internal and external interfaces of them. Consistency and traceability to software

requirements are established.

SI.O4. Software Components defined by the design are produced. Unit test are defined and performed

to verify the consistency with requirements and the design. Traceability to the requirements and design

are established.

SI.O5. Software is produced performing integration of Software Components and verified using Test

Cases and Test Procedures. Results are recorded at the Test Report. Defects are corrected and

consistency and traceability to Software Design are established.

SI.O6. A Software Configuration, that meets the Requirements Specification as agreed to with the

Customer, which includes user, operation and maintenance documentations, is integrated, baselined

and stored at the Project Repository. Needs for changes to the Software Configuration are detected and

related change requests are initiated.

SI.O7. Verification and Validation Tasks of all required work products are performed using the defined

criteria to achieve consistency among output and input products in each activity. Defects are identified,

and corrected; records are stored in the Verification/Validation Results.

Figure 3 illustrates the 4 activities o theproject management process as well as theirinput and output products. Each activity is composed o tasks. The task description does notimpose any technique or method to perorm it

For illustration purposes, two tasks o theProject Planning activity are listed in Table 4.On the let side o the table are listed the roleinvolved in a task. The project manager (PM)and the customer are involved in these 2 task

The customer is involved, during the execu-tion o the project, when he submits changerequests, during project review meetings, orthe validation and approval o the requirementspecifcations and or the acceptance othe deliverables.

Overview o the SotwareImplementation Process

The purpose o the (SI) process is to achievesystematic perormance o the analysis, designconstruction, integration, and test activities ornew or modifed sotware products accordingto the specifed requirements [12]. The sevenobjectives o the SI process are listed in table 5

Figure 4 illustrates the 4 activities o the SIprocess as well as their input and output productsEven though, a sequential view is presented infgures 3 and 4, ISO/IEC 29110 is not intended preclude the use o dierent liecycles such as w

terall, iterative, incremental, evolutionary or agile.

Deployment Packages to Facilitate

the Implementation o ISO/IEC 2911

As a novel approach taken to assist VSEswith the deployment o ISO/IEC 29110 and tprovide guidance on the actual implementatioo the Management and Engineering Guides iVSEs, a series o Deployment Packages (DPshave been developed to defne guidelines andexplain in more detail the processes defned ithe ISO/IEC 29110 profles [16]. The ele-

ments o a typical DP are: description o pro-cesses, activities, tasks, steps, roles, productstemplates, checklists, examples, reerences anmapping to standards and models, and a list otools. The mapping shows that a deploymentpackage has explicit links to standards, such aISO/IEC 12207, or models, such as the CMMor Development [17]. Hence by implement-ing a DP, a VSE can see its concrete step toachieve or demonstrate coverage [18].

DPs were designed such that a VSE canimplement its content, without having to



LARGE SCALE AG

Figure 4: Sotware implementation process diagram [12]

implement the complete ramework, i.e. o themanagement and engineering guide, at thesame time. A set o nine DPs have been devel-oped to date and are reely available rom [19].Figure 5 illustrates the set o DPs developed to

support the Basic Profle.

The Development o Systems Engi-

neering Standards and Guides or

VSEs Developing Systems

In 2009, the International Council on Sys-tems Engineering (INCOSE) Very Small andMicro Entities Working Group (VSME) was es-tablished to evaluate the possibility o develop-ing a standard, using the Generic profle groupscheme o the ISO/IEC 29110 series, basedon ISO/IEC 15288, or organizations develop-

ing systems. The ISO/IEC 29110 standard istargeted at VSEs which do not have experienceor expertise in tailoring ISO/IEC 15288 [20].

In November 2011, WG24 met in Irelandto launch the ofcial development o thesystems engineering ISs and TRs or VSEs.Delegates rom Brazil, Canada, France,Japan, Thailand, United States and INCOSEparticipated to the frst meeting. A frst dratwas sent or a round o review within ISOin January 2012. More than 450 commentshave been submitted by seven countries.A second drat [21] was sent or a second

round o review in December 2012. Lessthan 150 comments have been submittedand will be processed at the next WG meet-ing. A third and fnal cycle o review shouldstart in July. The systems engineering Basicprofle should be published by ISO eitherlate 2013 or early 2014. A set o systemsengineering DPs is also under developmentby systems engineers members o INCOSEto support the Basic Profle.

Conclusion and Future Work

A large majority o organizations worldwidehave up to 25 people. The collection o ISO/IEC JTC1 SC7 standards was not easily appliedin VSEs, which generally fnd engineering andmanagement standards difcult to understandand implement. WG24 developed a series oISO/IEC 29110 ISs and TRs or VSEs involvedin the development o systems or sotware.

As ISO/IEC 29110 is an emerging standardthere is much work yet to be completed. Themain remaining work item is to fnalize thedevelopment o the remaining two sotware

!

Requirements

Analysis

Version

Control

Integration

and

Tests

Project

Management

Architecture

andDetailed Design

ProductDelivery

Self-Assessment

Constructionand

Unit testing

Verificationand

Validation

Figure 5. Deployment Packages to support the Sotware Basic Profle [18]



LARGE SCALE AGILE

profles o the Generic Profle Group: (a) Intermediatemanage-

ment o more than one project and (b) Advancedbusinessmanagement and portolio management practices. Once thesesotware profles are ready, WG24 will develop matching sys-tems engineering profles or VSEs.

For most enterprises, but in particular or VSEs, internationalcertifcations can enhance credibility, competitiveness and ac-cess to national and international markets. Brazil has led thedevelopment o an ISO/IEC 29110 certifcation process. AnISO/IEC 29110 auditor should be competent in auditing tech-niques, have expertise in ISO/IEC 29110 and have experiencein sotware development. For VSEs, such a certifcation shouldnot be too expensive and short. The certifcation process hasbeen successully piloted in a ew VSEs. For these pilots, it took

about 4 sta-days o work by the auditors.The publication by ISO, o the systems engineering Basic pro-

fle, is anticipated or either late 2013 or early 2014. Similar tothe existing set o sotware ISO/IEC 29110 TRs, the Manage-ment and Engineering Guide or systems engineering shouldalso be made available at no cost by ISO. A set o DPs, tosupport the uture systems engineering standard, will be madereely available to VSEs on public Web sites. These DPs will useas a main reerence the INCOSE Handbook [22].

Since many VSEs developing systems are also involved in thedevelopment o critical systems, WG24 will conduct an analysisto determine i a set o systems/sotware standards or VSEs

developing critical systems should be developed.

Additional Inormation

The ollowing Web site provides more inormation about ISO/IEC 29110:

Disclaimer:

CMMI is registered in the U.S. Patent and Trademark Ofceby Carnegie Mellon University.

Dr. Claude Y Laporte has worked in deenseand transportation organizations or morethan 20 years. He is a proessor, since 2000at the cole de technologie suprieure, a6,000-student engineering school in Montr

where he teaches sotware engineering. Heis the Project Editor o ISO/IEC 29110 set systems and sotware engineering standardand Technical Reports. He is the co-author oa textbook about sotware quality assurancewhich should be published by John Wiley& Sons in 2013. Website address:



LARGE SCALE AG

REFERENCES

NOTES

1. Shintani, K., Empowered Engineers are Key Players in Process Improvement,

Presentation at the First International Research Workshop or Process Improvement

in Small Settings, Sotware Engineering Institute, CMU/SEI-2006-SR-01,

Pittsburgh, PA, 2006.

2. Charette, R. N., Why Sotware Fails, IEEE Computer Society, Spectrum, September

2005, pp 42-49.

3. Laporte, C.Y., Alexandre, S., and OConnor, R. A Sotware Engineering LiecycleStandard or Very Small Enterprises, R.V. OConnor et al (Eds) Proceedings o

EuroSPI Springer-Verlag, CCIS Vol. 16, pp. 129-141, 2008.

4. Coleman, G., OConnor, R., Sotware Process in Practice: A Grounded Theory o the

Irish Sotware Industry. In: Richardson, I., Runeson, P., Messnarz, R. (eds.) EuroSPI

2006. LNCS, vol. 4257, pp. 2839. Springer, Heidelberg (2006)

5. OConnor, R. and Laporte, C.Y., Deploying Liecycle profles or Very Small Entities:

An Early Stage Industry View, Proceedings o 11th International SPICE Conerence

on Process Improvement and Capability dEtermination, CCIS Vol. 155, Springer-

Verlag, May 2011.

6. ISO/ IEC 12207:2008, Inormation technology Sotware liecycle processes.

International Organization or Standardization/International Electrotechnical

Commission: Geneva, Switzerland.

7. ISO/ IEC 15288:2008, Systems and sotware engineering - System liecycle

processes, International Organization or Standardization/International

Electrotechnical Commission: Geneva, Switzerland, 2008.

8. ISO/ IEC 15289:2011, Systems and sotware engineering Content o liecycle

inormation products (documentation), International Organization or Standardiza

tion/International Electrotechnical Commission: Geneva, Switzerland, 2011.

9. ISO/ IEC 29110-2:2011 Sotware Engineering - Liecycle Profles or Very Small

Entities (VSEs) - Part 2: Framework and Taxonomy, Geneva: International

Organization or Standardization (ISO), 2011. Available rom ISO at:

http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.

htm?csnumber=51151

10. ISO/ IEC TR 29110-1:2011, Sotware Engineering - Liecycle Profles or Very

Small Entities (VSEs) - Part 1: Overview. Geneva: International Organization or

Standardization (ISO), 2011. Available at no cost rom ISO at: http://standards.iso.

org/itt/ PubliclyAvailableStandards/c051150_ISO_IEC_TR_29110-1_2011.zip11. ISO/ IEC TR 29110-3:2011, Sotware Engineering - Liecycle Profles or Very

Small Entities (VSEs) - Part 3: Assessment Guide. Geneva: International

Organization or Standardization (ISO), 2011. Available at no cost at:

http://standards.iso.org/itt/PubliclyAvailableStandards/c051152_ISO_IEC_

TR_29110-3_2011.zip

12. ISO/ IEC TR 29110-5-1-2:2011- Sotware Engineering - Liecycle Profles or Very

Small Entities (VSEs) - Part 5-1-2: Management and engineering guide -

Generic profle group: Basic profle, International Organization or Standardization/

International Electrotechnical Commission: Geneva, Switzerland. Available at

no cost rom ISO at: http://standards.iso.org/itt/PubliclyAvailableStandards/

c051153_ISO_IEC_TR_29110-5-1_2011.zip

13. ISO/ IEC 29110-4-1:2011, Sotware Engineering -- Liecycle Profles or Very

Small Entities (VSEs) - Part 4-1: Profle specifcations: Generic profle group.

Geneva: International Organization or Standardization (ISO), 2011.Available rom ISO at:

http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.

htm?csnumber=51154

14. ISO/IEC TR 29110-5-1-1:2012- Sotware Engineering - Liecycle Profles or Very

Small Entities (VSEs) - Part 5-1-1: Management and engineering guide - Generic

profle group: Entry profle, International Organization or Standardization/

International Electrotechnical Commission: Geneva, Switzerland. Available at no

cost rom ISO at: http://standards.iso.org/itt/PubliclyAvailableStandards/index.html

1. ISO/ IEC JTC1/SC7 stands or International Organization or Standardization/

International Electrotechnical Commission Joint Technical Committee

1/Sub Committee 7.

2. A previous Crosstalk article describes the establishment o Working

Group 24 [7] [23].

15. ISO/IEC TR 29110-5-1-1:2012, Ingnierie du logiciel Profls de cycle de vie pour

les trs petits organismes (TPO) Partie 5-1-1: Guide de gestion et dingnierie

Groupe de profls gnriques : Profl dentre. International Organization or

Standardization/International Electrotechnical Commission: Geneva, Switzerland.

Available at no cost rom ISO at:

http://standards.iso.org/itt/PubliclyAvailableStandards/index.html

16. Laporte, C.Y., Alexandre, S., Renault, A., The Application o International SotwareEngineering Standards in Very Small Enterprises, Sotware Quality Proessional

Journal, ASQ, Vol. 10, No 3, June 2008, p 4-11.

17. Sotware Engineering Institute. (2010). CMMI or Development, Version 1.3,

Pittsburgh PA: Carnegie Mellon University. CMU/SEI-2010-TR-033.

18. Laporte, C.Y., Palza Vargas, E., The Development o International Standards to

acilitate Process Improvements or Very Small Enterprises, Book: Sotware Process

Improvement and Management: Approaches and Tools or Practical Development

IGI Global Publisher. USA. 2012, p 34-61.

19. ISO/IEC JCT1/SC7 Working Group 24 Deployment Packages repository, [online]

available rom http://pros.logti.etsmtl.ca/claporte/English/VSE/index.html

20. Laporte, C. Y., Fanmuy, G., Ptack, K., The Development o Systems Engineering

International Standards and Support Tools or Very Small Enterprises, International

Council on Systems Engineering (INCOSE) International Symposium,

July 9 12, 2012, Rome Italy.21. ISO/IEC DTR 29110-5-6-2: 2012 - Systems Engineering Liecycle Profles or Very

Small Entities (VSEs) - Management and engineering guide: Generic profle group:

Basic profle, International Organization or Standardization/International

Electrotechnical Commission: Geneva, Switzerland.

22. Systems Engineering Handbook A Guide For System Lie Cycle Processes And

Activities, INCOSETP200300203.2, International Council on Systems Engineering

(INCOSE), 7670 Opportunity Rd, Suite 220, San Diego, CA 921112222,

January 2010.

23. Laporte, C.Y., April, A., Renault, A., Applying ISO/IEC JTC 1/SC7 Sotware

Engineering Standards in Very Small Enterprises, CrossTalk - The Journal o Deense

Sotware Engineering, February 2007, Vol. 20, No 2, pp 29-30
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detailhttp://standards.iso/http://standards.iso.org/ittf/PubliclyAvailableStandards/c051152_ISO_IEC_http://standards.iso.org/ittf/PubliclyAvailableStandards/http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detailhttp://standards.iso.org/ittf/PubliclyAvailableStandards/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableStandards/index.htmlhttp://profs.logti.etsmtl.ca/claporte/English/VSE/index.htmlhttp://profs.logti.etsmtl.ca/claporte/English/VSE/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableStandards/index.htmlhttp://standards.iso.org/ittf/PubliclyAvailableStandards/index.htmlhttp://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detailhttp://standards.iso.org/ittf/PubliclyAvailableStandards/http://standards.iso.org/ittf/PubliclyAvailableStandards/c051152_ISO_IEC_http://standards.iso/http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail

Crosstalk May 2013- International Systems and Software Engineering Standards for Very Small Entities...

Documents

Transcript of Crosstalk May 2013- International Systems and Software Engineering Standards for Very Small Entities...