A framework for implementing ISO 14000 in construction Article in Environmental Management and Health 11(2):139-149 May 2000 with 234 Reads DOI: 10.11. Average of 88.5 points in 22 community wine reviews on 2005 Chevalier de Lascombes, plus professional notes, label images, wine details, and recommendations on when to drink. Redi chek et-732 remote thermometer manual; Daewoo dmq 2057 manual transfer. Camelot keypad deadbolt manually; Nec laptop computer manual; Fender stereo pak manual lymphatic drainage. Iso 9000 quality manual sample; Prodeco phantom x2 manual; Us epa bioscreen manual treadmill.

• Chevalier Et Camelot Iso 9000 2017
• Chevalier Et Camelot Iso 9000 Download

Coordinates: 45°02′29″N0°41′02″W / 45.04145°N 0.68376°W

Château Lascombes is a winery in the Margauxappellation of the Bordeaux region of France. The wine produced here was classified as one of fifteen Seconds Crus (Second Growths) in the original Bordeaux Wine Official Classification of 1855. In the 1950s, the estate was purchased by French wine writer Alexis Lichine who continued to own part of the estate till 1971 when Bass Charrington took over principal ownership. In 2001 it was purchased by Yves Vatelot and US-based Colony Capital, who in 2011 sold it to the French insurance group MACSF. In addition to its premier cuvee, a second wine is also produced, under the name Chevalier de Lascombes. Additional brands are Château Segonnes, Rosé de Lascombes, Vin Sec Chevalier de Lascombes and Gombaud.^[1]

History[edit]

In the 17th century the estate belonged to Antoine, chevalier de Lascombes, and has kept his name.^[2] Some locals suggest the estate, which is situated on the highest knoll of Margaux, takes its name from 'la côte' (French: height) via 'lascote' to 'lascombes'.^[3] Antoine de Lascombes (born 1625) inherited or had possession of the estate from the Durfort de Duras family, with whose properties in the Bordeaux it remained at first integrated; wine is first mentioned in 1700^[4] In the eighteenth century the domaine was separated from the property of the comtes de de Duras and was inherited by Jean-François and Anne de Lascombes. Jean-François de Lascombes was a councillor at the parlement of Bordeaux,^[5] king's procureur at the Admiralty and a member of the Académie de Bordeaux (1761). The vineyard remained the property of the Lascombes family for three generations until after the French Revolution.^[6] Until 1860 the estate bore the name Domaine de Lascombes.^[7]

Swap trick ps2 games. Swap Trick Ps2 Games. The 1-time Swap Trick & the Swap Time Trick work only if you have applied our patches to the backup copy As 'boot-disk' you must use the PS2 Utilities Disk delivered. PS2 Game Swap Trick PS2 Game. Written by JNABK If all you have is a PS2 and some PS2 retail games, then it may be. FMCB with just a backup disc. Try and get yourself an older model (SCPH-30001) and you will have a much better chance of using a game other than 007: Agent Under Fire. I used my SCPH-30002 to do the swap trick using Burnout 3: Takedown (I replaced the NFS: Underground 2 demo ELF since the network GUI won't start without a network adapter attached) and it worked the first time.

Through sales and inheritance the estate passed through a succession of owners, until it was formed into a company in 1926, with the Ginestet family, then owners of Château Margaux, as major shareholders. During the later stages of World War II the country house served as a headquarters for the Allied forces.^[6]

Château Lascombes was purchased by Alexis Lichine and a syndicate of American investors that included David Rockefeller, in 1952.^[3][8] Shortly before, Lichine also purchased another Margaux estate, Château Prieuré-Lichine. Lichine improved the vineyards through his expertise and commitment. In 1971 the backing company was taken over by the British brewing company Bass Charrington, bringing the Lichine era to an end.^[6]

Following the acquisition by the Bass Group, winemaker René Vanatelle was recruited as the winemaker. Vanatelle carried out extensive evaluation of the terroir, now extended to 84 hectares (208 acres) of Lascombes' vineyards and found that only 50 hectares (125 acres) actually produced wines of Deuxièmes Crus quality. In the 1980s, he began isolating these different segments of the vineyard and used the lesser quality terroir to produce a second wine known as Château Segonnes. In 1997, prior to his retirement, Vanatelle introduced a second wine of higher quality, Chevalier de Lascombes, which was matured in oak barrels (a third of which being new) for 14–20 months. Château Segonnes is still being produced, but now as a third wine. Following Vanatelle's retirement, Bruno Lemoine, formerly of Château Montrose, was named new winemaker.

In 2001, the estate was purchased for $67 million by US-based Colony Capital with the entrepreneur Yves Vatelot.^[6] The new owners invested heavily in modernizing Lascombes, which had been considered an underperformer in relation to its classification. While Lascombes has been awarded high notes for its wines by many wine critics (such as Robert M. Parker, Jr.) and managed to significantly increase the price of its Grand vin since the investment, the US owners made the château available for sale in late 2007.^[9] In 2011, Lascombes was sold to the French insurance group MACSF for 200 million euro, of which approximately 50 million euro was its stock of wine.^[10]

Currently Lascombes employs Michel Rolland as consultant of oenology.^[1]

Production[edit]

The vineyard area comprises 84 hectares (210 acres) with a grape variety distribution of 50% Merlot, 45% Cabernet Sauvignon and 5% Petit Verdot.^[6] The château annually produces 250,000 bottles of the Grand vin and 70,000 bottles of the second wine Chevalier de Lascombes.

In 2008, it was reported that Lascombes had rented vineyards that belong to Château Martinens, a former Cru Bourgeois, which had 28 hectares (69 acres) of vineyards within AOC Margaux plus 25 hectares (62 acres) of Haut-Médoc AOC.^[9] Classified growths are allowed to expand their vineyard holdings without losing their classification, but only with vineyards of the same appellation as their own, which makes it uncertain to which purpose the Haut-Médoc vineyards would be put.

For most vintages, the composition of the Grand vin is 55% Cabernet Sauvignon, 40% Merlot and 5% Petit Verdot. The second wine, Chevalier de Lascombes, will have a higher composition of Merlot. Château Lascombes is usually rich and full bodied with a concentration of ripe fruit and underlying aromas of cedar. Like many Margaux wines, the tannins can be supple. The wines typically are ready for drinking after eight years and can usually last up to thirty.^[1]

References[edit]

1. ^ ^abcT. Stevenson 'The Sotheby's Wine Encyclopedia' pg 95 Dorling Kindersley 2005 ISBN0-7566-1324-8
2. ^Clive Coates, The Wines of Bordeaux: Vintages and Tasting Notes 1952-2003 2004:160f.
3. ^ ^abLichine, Alexis (1967). Alexis Lichine's Encyclopedia of Wines and Spirits. London: Cassell & Company Ltd. p. 319.
4. ^Coates, ibid.; Guide des Peoducteurs régionaux: Château Lascombes.
5. ^Louis de La Roque and Edouard de Barthélemy, Catalogue des gentilshommes en 1789 et des familles anoblies ou titrées.., 1866:47, s.v. 'Guienne, Chambre de la Tourelle'.
6. ^ ^abcdeKissack, Chris, thewinedoctor.com. 'Chateau Lascombes'.
7. ^Peppercorn, David (2003). Bordeaux. London: Mitchell Beazley. pp. 81–82.
8. ^Prial, Frank J., The New York Times (1989-06-02). 'Alexis Lichine, 76, an Author and Expert on Wine'.
9. ^ ^abAnson, Jane, Decanter.com (February 7, 2008). Chateau Lascombes extends despite rumors of sale
10. ^Anson, Jane, Decanter.com (July 10, 2011). Chateau Lascombes sold for €200m

External links[edit]

• Château Lascombes official site(in French)(in English)

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.

Aug 10, 2011  Como instalar os drivers de rede da POSITIVO no windows 7 Tatu BR. Unsubscribe from Tatu BR? How to configure a Shared Network Printer in Windows 7, 8, or 10 - Duration: 45:12. Driver de rede positivo windows 7 ultimate 64 bits. Downoad do driver de rede para notebook positivo 3D sim+700 para Windows 7 32 bits e 64 bits. Jan 17, 2015  Jan 12, 2015 Driver rede windows 7 ultimate 32 bits download. 7 Driver rede windows 7 ultimate 32 bits download A library of Aug 10, 2011. Br//suporte/ drivers. Br//suporte/ drivers Download de Drivers de Inicio » Notebooks POSITIVO » Drivers Notebook Positivo 7975. Apr 03, 2018  Drivers positivo windows 7; driver positivo; download drivers drive-pack-solution driver driver-de-rede-positivo driver-pack-solution driver. Drivers Baixar driver de Rede Notebook Positivo Downoad do driver de rede para notebook positivo 3D sim+700 para Windows 7 32 bits e 64 DOWNLOAD DO DRIVER DE REDE DOWNLOAD Rede LAN Realtek Download.

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 a small organisations; ISO 29110 reflects that.

The need for lightweight Systems and Software Engineering standards[edit]

Industry recognizes 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.

Microsoft flight hawaiian adventure pack a6m2 zero dlc management program. 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.

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[edit]

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[edit]

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.

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 table below lists the number of work products and roles for each process of the software generic profile group.

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.

Published Standards (IS) and Technical Reports (TR)[edit]

Chevalier Et Camelot Iso 9000 2017

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.

Deployment Packages[edit]

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.

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.

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 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[edit]

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).

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:

• Very difficult to know the status of specific requests
• Very often, there is an incident when a change is put in production.
• There is a large number of faults detected by the quality assurance department
• The development process is painful and the documentation produced is not very useful.

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.

Implementation of ISO/IEC 29110 in systems engineering organizations[edit]

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[edit]

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

As an example, in the state of Zacatecas of Mexico, 4 universities have implemented the 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. Dumb and dumber 1994 movie dual audio 480p bluray. 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, the 4 SDCs achieved the certification in 2017.

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

Status[edit]

• Current version: ISO/IEC 29110-2-1 published in 2015 and ISO/IEC 29110-4-1, published in 2011.
• Current version: ISO/IEC TR 29110-1:2016, ISO/IEC TR 29110-3-1 and are freely available from ISO/ITTF as a free download
• Current version: ISO/IEC TR 29110-5-2-1:2016 - Organizational management guidelines

For Software Engineering:

• Current version: ISO/IEC TR 29110-5-1-1:2012 - Management and engineering guide for the software engineering Entry profile has been published in English and French in September 2012 and are freely available from ISO/ITTF as a free download
• Current version: ISO/IEC TR 29110-5-1-2:2011 - Management and engineering guide for the software engineering Basic profile has been published in English and French in September 2012 and are freely available from ISO/ITTF as a free download
• Current version: ISO/IEC TR 29110-5-1-3:2017 - Management and engineering guide for the software engineering Intermediate profile.
• Current version: ISO/IEC TR 29110-5-1-4:2018 Management and engineering guide for the software engineering Advanced profile.

For Systems Engineering:

• Current version: ISO/IEC TR 29110-5-6-1:2015 - Systems engineering Entry Profile - Management and engineering guide - Published in November 2015. Freely available from ISO/ITTF as a free download
• Current version: ISO/IEC TR 29110-5-6-2:2014 [1] Systems engineering Basic profile - Management and engineering guide. Published in August 2014. Freely available from ISO/ITTF as a free download

For Service Delivery:

• Current version: ISO/IEC TR 29110-5-3:2018 - Service Delivery Guidelines
• Current version ISO/IEC 29110-4-3:2018 - Service delivery – Profile specifications

In preparation[edit]

Chevalier Et Camelot Iso 9000 Download

For Systems Engineering:

• For the Systems engineering Intermediate Profile: ISO/IEC TR 29110-5-6-3 Management and engineering guide - publication expected in 2019.
• For Systems engineering: ISO/IEC 29110-4-6 Systems Engineering - Profile Specifications - publication expected in 2019
• For the Systems engineering Advanced Profile: ISO/IEC TR 29110-5-6-4 Management and engineering guide - publication expected in 2020.

For Agile:

• For Agile: ISO/IEC TR 29110-5-4 Agile Software Development Guidelines - publication expected in 2020.
• For Agile: ISO/IEC 29110-4-4 Agile Software Development - Profile specifications: Generic Profile - publication expected in 2020.

For DevOps:

• For DevOps: ISO/IEC TR 29110-5-5 DevOps Guidelines - publication expected in 2019.
• For DevOps: ISO/IEC 29110-4-5 DevOps - Profile specifications - publication expected in 2019.

Miscellaneous:

• For Organizational Management: ISO/IEC 29110-4-2 – Organizational Profile Specifications - publication expected in 2019.

Articles and other communications[edit]

• Munoz, M., Mejia, J., Laporte, C.Y., Implementación del Estándar ISO/IEC 29110 en Centros de Desarrollo de Software de Universidades Mexicanas: Experiencia del Estado de Zacatecas, XI Seminario Internacional de Ciencias de la Computación, October 10–12, 2018, Medellín, Colombia.
• Muñoz M., Mejia J., Laporte C.Y. (2019) Reinforcing Very Small Entities Using Agile Methodologies with the ISO/IEC 29110. In: Mejia J., Muñoz M., Rocha Á., Peña A., Pérez-Cisneros M. (eds) Trends and Applications in Software Engineering. CIMPS 2018. Advances in Intelligent Systems and Computing, vol. 865. Springer, Cham, October 17–19, 2018, Guadalajara, Mexico.
• 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.
• Muñoz M., Negrón A.P.P., Mejia J., Lopez G.L. (2018) ISO/IEC 29110 and curricula programs related to Computer Science and Informatics in Mexico: Analysis of practices coverage. In: Mejia J., Muñoz M., Rocha Á., Quiñonez Y., Calvo-Manzano J. (eds) Trends and Applications in Software Engineering. CIMPS 2017. Advances in Intelligent Systems and Computing, vol 688. Springer, Cham
• Laporte, C.Y., Munoz, M., Mejia Miranda, J., O’Connor, R.V., [2] Applying Software Engineering Standards in Very Small Entities-From Startups to Grownups, IEEE Software, Vol. 35, Issue 1, pp 99–103
• Marvin et al., A SE VSE Company Use Case, 27th Annual INCOSE International Symposium, Adelaide, Australia, July 15–20, 2017.
• Laporte, C.Y., O’Connor, R.V. (2016),[3] Systems and Software Engineering Standards for Very Small Entities: Accomplishments and Overview, IEEE Computer, volume 49, number 8, pp 84–87.
• X. Larrucea et al., “Software Process Improvement in Very Small Organizations,” IEEE Software, vol. 33, no. 2, 2016, pp. 85–89.
• Laporte, C.Y., O'Connor, R., [4] 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.
• Laporte, C. Y., Munoz, M., Gerançon, B., [5] 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
• Laporte, C.Y., Tremblay, N., Menaceur, J., Poliquin, D., Houde, R., [6] 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
• Sanchez-Gordon, M.L., O’Connor, R. V., Colomo-Palacios, R. and Sanchez-Gordon, S.: A Learning Tool for the ISO/IEC 29110 Standard: Understanding the Project Management of Basic Profile. In Proceedings 16th International Conference on Software Process Improvement and Capability dEtermination (SPICE 2016). Springer-Verlag. (2016)
• Sanchez-Gordon, M.L., O’Connor, R. V., Colomo-Palacios, R. and Herranz, E.: Bridging the Gap between SPI and SMEs in Educational Settings: A Learning Tool Supporting ISO/IEC 29110. 23nd European Conference on Systems, Software and Services Process Improvement (EuroSPI 2016), Springer-Verlag. (2016)
• Laporte, C.Y., Chevalier, F., An Innovative Approach to the Development of Project Management Processes for Small-scale Projects in a large Engineering Company, 25th Annual International Symposium of INCOSE (International Council on Systems Engineering), Seattle, US, July 13–16, 2015.
• Garcia, L., Laporte, C.Y., Arteaga, J., Bruggmann, M., Implementation and Certification of ISO/IEC 29110 in an IT Startup in Peru, Software Quality Professional Journal, ASQ, vol. 17, no. 2, pp 16–29, 2015.
• Laporte, C.Y., O'Connor, R, Software Process Improvement in Graduate Software Engineering Programs, in: O’Connor, R.V., Mitasiunas, A. and Ross, M. (Eds), Proceedings of the 1st International Workshop on Software Process Education, Training and Professionalism (SPETP 2015), CEUR Electronic Workshop Proceedings, Vol. 1368, 2015, pp. 18–24.
• Laporte, C.Y., O'Connor, R., Software Engineering Standards and Guides for Very Small Entities: Implementation in two start-ups, 10th International Conference on Evolution of Novel Approaches to Software Engineering (ENASE 2015), Barcelona, Spain, April 29–30, 2015.
• Laporte, C.Y., Chevalier, F., Maurice, J.-C., Improving Project Management for Small Projects, ISO Focus+, International Organization for Standardization, February 2013, pp 52–55.
• Laporte, C.Y., Séguin, N., Villas Boas, G., Seizing the benefits of software and systems engineering standards, ISO Focus+, International Organization for Standardization, February 2013, pp 32–36.
• Laporte, C.Y., O'Connor, R., Fanmuy, G., International Systems and Software Engineering Standards for Very Small Entities, CrossTalk - The Journal of Defense Software Engineering, May/June 2013, Vol. 26, No 3, pp 28–33.
• Laporte, C.Y., Hébert, C., Mineau, C., [7] 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.
• Laporte, Claude Y., Houde, R., Marvin, J., Systems Engineering International Standards and Support Tools for Very Small Enterprises, 24th Annual International Symposium of INCOSE (International Council on Systems Engineering), Las Vegas, US, June 30-July 3, 2014.
• Laporte, C.Y., O'Connor, R., Garcia Paucar, L.H., Gerançon, B., An Innovative Approach in Developing Standard Professionals by Involving Software Engineering Students in Implementing and Improving International Standards, International Cooperation for Education about Standardization Conference, August 14, 2014, Ottawa, Canada.
• Laporte, C.Y., O'Connor, R., A Systems Process Lifecycle Standard for Very Small Entities: Development and Pilot Trials, 21st European Software Process Improvement Conference (Euro SPI 2014), CCIS 425, pp. 13–24, Springer-Verlag, Heidelberg, Luxembourg, June 25–27, 2014.

See also[edit]

• Video in English about ISO/IEC 29110
• ISO/IEC/IEEE 12207, Systems and software engineering - Software life cycle processes.
• ISO/IEC/IEEE 15288, Systems and software engineering - System life cycle processes.
• ISO/IEC/IEEE 15289, Systems and software engineering - Content of systems and software life cycle process information products (Documentation)
• VSE support sites in English:
• VSE support sites in French:
• VSE support in Spanish
• ISO 29110 Wikipedia in Czech

References[edit]

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:2011Archived 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, 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, 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