A framework for the requirements engineering process development
Pourquoi ce travail est dans la base
Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.
Notice bibliographique
Résumé
As one of the processes in software engineering, requirements engineering (RE) plays a vital role in ensuring the overall success of the software engineering process. However, many of the substantial problems that the software industry faces today are still the same as the ones discovered during the software engineering crisis 36 years ago. Poor RE practices have been blamed as one of the major reasons contributing to the vicious circle. RE is a discipline emphasizing the implementation of engineering disciplines into the RE process by using various good practices, techniques and methodologies. A sound RE process is the foundation for the overall quality of any software product. Even though numerous process models, good practices, and techniques have been developed which aim at providing necessary support for RE processes, a huge gap still exists between the theory and practices. One of the major reasons contributing to this phenomenon is that there is a lack of suitable tools and/or guidance to support developing the most suitable RE process model and selecting the most suitable RE techniques for a software project. The effective ways have to be found to help fill in the gap. The objectives of this research were, therefore, to investigate a theoretically sound and practically feasible framework which can provide constructive and productive solutions to the problems identified by combining the theories and technologies of advanced software engineering, requirements engineering, knowledge engineering, and decision support. The outcome of this is the A Fbramework for Rbequirements Ebngineering pRbocess dEbvelopment (FRERE), which consists of a requirements engineering knowledge base, methodologies for RE process development and RE techniques selection, RE process assessment models, and a prototype of the FRERE tool. The framework provides constructive methodologies, with the help of the requirements engineering knowledge base and process assessment models, to develop the most suitable RE process model and suitable RE techniques for the given software project. The FRERE tool is a knowledge-based decision support system which can advise the requirements engineers during the development of RE process. The case study conducted during the research has shown the feasibility of the framework.
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.
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,000 | 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,001 | 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écoule