The Development and Experimentation of an International Standard for Very Small Entities Involved in Software Development
Notice bibliographique
Résumé
Very Small Entities (VSEs) are enterprises, departments, or projects having up to 25 people. IT VSEs are very important to the world economy, as their software components are often integrated into the products of larger entities. A large percentage of software entities worldwide have up to 25 employees. In Europe, for instance, 85% of Information Technology (IT) sector companies have 1 to 10 employees. A survey of the Montreal, Canada, area has revealed that 78% of software development enterprises have up to 25 employees and 50% have fewer than 10 (Gauthier 2004). Their software components are often integrated into the products of larger entities. Failure to deliver a quality product on time and within budget threatens the competitiveness of VSEs and impacts customers. Also, with the current trend towards outsourcing, it is critical for customers to be able to depend on VSEs to deliver their products, or the business will go elsewhere. Failure to deliver a quality product on time and within budget threatens the competitiveness of organizations of all sizes. One way to mitigate these risks is for the suppliers of a product chain to put in place proven software engineering practices, such as those documented in standards. Many international standards and models, like ISO/IEC12207 or the Capability Maturity Model Integration developed by the Software Engineering Institute, have been developed to capture proven engineering practices. However, these standards and models were not designed having in mind VSEs and are consequently difficult to apply in such settings. Also, research shows that VSEs often find it difficult to relate ISO/IEC standards to their business needs and to justify the application of the standards to their business practices. Most of them cannot afford the resources in number of employees, cost, or time to establish software life cycle processes, or see a net benefit to doing so. An ISO/IEC JTC1/SC7 1 Working Group, Working Group 24, was established in 2005 to address these difficulties by producing an international software engineering standard, the ISO/IEC 29110, which is specifically tailored to the problems and needs of VSEs. An international survey was developed and translated into 9 languages. It was conducted among VSEs and concerned their utilization of standards. The data collected were used to validate the list of needs and problems that had been documented by working group 24. Over 435 responses were received from 32 countries. The working group used the results to define the requirements that would form the basis for the standards to be developed for VSEs. This paper presents a perspective on the development of ISO/IEC 29110 standards and technical reports and outlines the development of a series of deployment packages facilitating the implementation of a set of ISO/IEC 29110 practices. A deployment package is a set of artifacts developed to facilitate the implementation of 1 ISO/IEC JTC 1/SC7 stands for the International Organization for Standardization / International Electrotechnical Commission Joint Technical Committee 1 / Sub Committee 7, which is in charge of the development and maintenance of software and systems engineering standards
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,000 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».