2007
Journal article
Closed Access
An empirical study on the impact of automation on the requirements analysis process
Lami G., Ferguson R. W.
Requirements analysis is an important phase in a software project. The analysis is often performed in an informal way by specialists who review documents looking for ambiguities, technical inconsistencies and incomplete parts. Automation is still far from being applied in requirements analyses, above all since natural languages are informal and thus difficult to treat automatically. There are only a few tools that can analyse texts. One of them, called QuARS, was developed by the Istituto di Scienza e Tecnologie dell'Informazione and can analyse texts in terms of ambiguity. This paper describes how QuARS was used in a formal empirical experiment to assess the impact in terms of effectiveness and efficacy of the automation in the requirements review process of a software company.Source: Journal of Computer Science and Technology 22 (2007): 338–347. doi:10.1007/s11390-007-9045-3
DOI: 10.1007/s11390-007-9045-3
Metrics:
Lami G., Ferguson R. W.
Requirements analysis is an important phase in a software project. The analysis is often performed in an informal way by specialists who review documents looking for ambiguities, technical inconsistencies and incomplete parts. Automation is still far from being applied in requirements analyses, above all since natural languages are informal and thus difficult to treat automatically. There are only a few tools that can analyse texts. One of them, called QuARS, was developed by the Istituto di Scienza e Tecnologie dell'Informazione and can analyse texts in terms of ambiguity. This paper describes how QuARS was used in a formal empirical experiment to assess the impact in terms of effectiveness and efficacy of the automation in the requirements review process of a software company.Source: Journal of Computer Science and Technology 22 (2007): 338–347. doi:10.1007/s11390-007-9045-3
DOI: 10.1007/s11390-007-9045-3
Metrics:
See at:
Journal of Computer Science and Technology 
| www.springerlink.com | CNR ExploRA
2004
Journal article
Unknown
Introduction to SPLYR The First Software Product Lines Young Researchers Workshop
Geppert B., John I., Lami G.
The workshop theme addresses research activities in the field of Software Product Lines (SPL). Topics of interest include all aspects of the development phases, management, evaluation, reuse, and maintenance of SPL. The workshop itself aims at providing a platform for young researchers to present their work to an international audience and discuss it among each other and with experts in the field. Experienced panelists will comment on the presentations and will give feedback for the further development of the presented work.Source: Lecture notes in computer science 3154 (2004): 327–328.
Geppert B., John I., Lami G.
The workshop theme addresses research activities in the field of Software Product Lines (SPL). Topics of interest include all aspects of the development phases, management, evaluation, reuse, and maintenance of SPL. The workshop itself aims at providing a platform for young researchers to present their work to an international audience and discuss it among each other and with experts in the field. Experienced panelists will comment on the presentations and will give feedback for the further development of the presented work.Source: Lecture notes in computer science 3154 (2004): 327–328.
See at: CNR ExploRA
2009
Journal article
Restricted
Analytic effectiveness evaluation of techniques for natural language sotware requirements testability
Lami G.
Testability is a quality characteristic that addresses the efficacy and effectiveness of software testing. In the literature testability has been principally considered from the point of view of design methodologies and coding techniques. Although these two aspects are very important for software testability, they are not the only ones that influence it. Requirements are another factor that can heavily affect software testability. In this paper, natural language requirements are considered and their impact on software testability is discussed. The causes of poor testability originating from natural language requirements are identified and state-of-the-art techniques to improve requirements testability are classified, discussed and their effectiveness evaluated.Source: Computer systems science and engineering 24 (2009): 121–137.
Lami G.
Testability is a quality characteristic that addresses the efficacy and effectiveness of software testing. In the literature testability has been principally considered from the point of view of design methodologies and coding techniques. Although these two aspects are very important for software testability, they are not the only ones that influence it. Requirements are another factor that can heavily affect software testability. In this paper, natural language requirements are considered and their impact on software testability is discussed. The causes of poor testability originating from natural language requirements are identified and state-of-the-art techniques to improve requirements testability are classified, discussed and their effectiveness evaluated.Source: Computer systems science and engineering 24 (2009): 121–137.
See at:
www.crlpublishing.co.uk | CNR ExploRA
2005
Conference article
Unknown
Learning metrics for natural language requirements in an under-graduate course
Lami G.
In this paper the experience of an under-graduate course focused on the requirements elicitation, specification and quantitative analysis is presented. The object (natural language requirements) and methodological approach adopted in the course are discussed to evaluate their suitability to learn metrics.Source: 1st Methods for Learning Metrics International Workshop, Como, 2005
Lami G.
In this paper the experience of an under-graduate course focused on the requirements elicitation, specification and quantitative analysis is presented. The object (natural language requirements) and methodological approach adopted in the course are discussed to evaluate their suitability to learn metrics.Source: 1st Methods for Learning Metrics International Workshop, Como, 2005
See at: CNR ExploRA
2005
Conference article
Unknown
Teaching requirements engineering in the small: an under-graduate course experience
Lami G.
In this paper a short (16 hours) newly designed course on practical software engineering is described. This course has been designed according to specific objectives (i.e. orientation to the practice, generality and adequacy to the current software engineering community trends) and focused on the requirements elicitation, documentation, and analysis topics. In the course an innovative tool for natural language requirements analysis has been used for the first time with educational purpose. The outcomes from this pilot experience are discussed along with the lessons learned.Source: 1st International Workshop on Requirements Engineering Education and Training, REET, Paris, 2005
Lami G.
In this paper a short (16 hours) newly designed course on practical software engineering is described. This course has been designed according to specific objectives (i.e. orientation to the practice, generality and adequacy to the current software engineering community trends) and focused on the requirements elicitation, documentation, and analysis topics. In the course an innovative tool for natural language requirements analysis has been used for the first time with educational purpose. The outcomes from this pilot experience are discussed along with the lessons learned.Source: 1st International Workshop on Requirements Engineering Education and Training, REET, Paris, 2005
See at: CNR ExploRA
2006
Conference article
Unknown
An empirical study on the relationship between defective requirements and test failures
Ferguson R. W., Lami G.
The quality of software products depends on the quality of the requirements used to create them. Expressiveness (i.e., the ability to convey the intended meaning by avoiding ambiguities and readability problems) is an important quality characteristic of natural language requirements. This paper describes an empirical study that used data from an industrial software project to identify possible relationships between expressiveness defects in natural language requirements and failures during testing. The study shows that test failures occur more frequently when there exist requirements cases with expressiveness defects.Source: IEEE/NASA Software Engineering Workshop, pp. 7–10, Columbia, MD - USA, 24-28/04/2017
Ferguson R. W., Lami G.
The quality of software products depends on the quality of the requirements used to create them. Expressiveness (i.e., the ability to convey the intended meaning by avoiding ambiguities and readability problems) is an important quality characteristic of natural language requirements. This paper describes an empirical study that used data from an industrial software project to identify possible relationships between expressiveness defects in natural language requirements and failures during testing. The study shows that test failures occur more frequently when there exist requirements cases with expressiveness defects.Source: IEEE/NASA Software Engineering Workshop, pp. 7–10, Columbia, MD - USA, 24-28/04/2017
See at: CNR ExploRA
2008
Conference article
Unknown
SPI in the Italian automotive industry: issues from the automotive SPIN Italy
Lami G., Panaroni P.
Today automotive is an application field where innovation is growing at the highest rate. Innovation in automotive is principally due to the market-driven demand of new features that only electronic devices on the vehicles can provide. Electronic devices, more and more complex and connected by CANs (Control Area Networks), control more than 85% of the automobile's functionalities. The way the automotive industry is facing the challenges arisen in the last years is the subject of this paper. The authors, starting from the experience of the Automotive SPIN Italy, give a picture of the achievements and the open issues in the Italian automotive industry.Source: International SPICE Days Software Process Improvement and Capability Determination, pp. 1–10, Prague, Czech Republic, 23-25 June 2008
Lami G., Panaroni P.
Today automotive is an application field where innovation is growing at the highest rate. Innovation in automotive is principally due to the market-driven demand of new features that only electronic devices on the vehicles can provide. Electronic devices, more and more complex and connected by CANs (Control Area Networks), control more than 85% of the automobile's functionalities. The way the automotive industry is facing the challenges arisen in the last years is the subject of this paper. The authors, starting from the experience of the Automotive SPIN Italy, give a picture of the achievements and the open issues in the Italian automotive industry.Source: International SPICE Days Software Process Improvement and Capability Determination, pp. 1–10, Prague, Czech Republic, 23-25 June 2008
See at: CNR ExploRA
2002
Contribution to book
Unknown
Software Process Assessment as a Mean to Improve the Acquisition Process of an Automotive Manufacturer
Fabbrini F., Fusani M., Lami G., Sivera E.
An abstract is not availableSource: Software Process Improvement CMM & SPICEin practice, edited by Nora Koch, pp. 142–154, 2002
Fabbrini F., Fusani M., Lami G., Sivera E.
An abstract is not availableSource: Software Process Improvement CMM & SPICEin practice, edited by Nora Koch, pp. 142–154, 2002
See at: CNR ExploRA
2009
Conference article
Restricted
Is ISO/IEC 15504 Applicable to Agile Methods?
Lami G., Falcini F.
n the last two decades several models for evaluating software process capability have been defined and became more and more popular. The application of such models, and in particular the ISO/IEC 15504, determined a general software process improvement in many domains. Nevertheless, the application of the ISO/IEC 15504 standard is still considered by many agile developers as incompatible with agile approaches. Such an attitude is mainly based on common misunderstandings on what the ISO/IEC 15504 is and on what its application involves. This paper aims at showing that this standard, if genuinely applied, can be effectively used also in agile contexts.Source: XP 2009 - Agile Processes in Software Engineering and Extreme Programming. 10th International Conference, pp. 130–135, Pula, Sardinia, Italy, 25-29 May 2009
DOI: 10.1007/978-3-642-01853-4_16
Metrics:
Lami G., Falcini F.
n the last two decades several models for evaluating software process capability have been defined and became more and more popular. The application of such models, and in particular the ISO/IEC 15504, determined a general software process improvement in many domains. Nevertheless, the application of the ISO/IEC 15504 standard is still considered by many agile developers as incompatible with agile approaches. Such an attitude is mainly based on common misunderstandings on what the ISO/IEC 15504 is and on what its application involves. This paper aims at showing that this standard, if genuinely applied, can be effectively used also in agile contexts.Source: XP 2009 - Agile Processes in Software Engineering and Extreme Programming. 10th International Conference, pp. 130–135, Pula, Sardinia, Italy, 25-29 May 2009
DOI: 10.1007/978-3-642-01853-4_16
Metrics:
See at:
doi.org | www.springerlink.com | CNR ExploRA
2005
Report
Open Access
QuARS a tool for analysing requirements
Lami G.
Numerous tools and techniques are available for managing requirements. Many are designed to define requirements, provide configuration management, and control distribution. However, there are few automatic tools to support the quality analysis of natural language (NL) requirements. Ambiguity analysis and consistency and completeness verification are usually carried out by human reviewers who read requirements documents and look for defects. This clerical activity is boring, time consuming, and often ineffective. This report describes a disciplined method and a related automated tool that can be used for the analysis of NL requirements documents. The tool, called the Quality Analyzer for Requirements Specifications (QuARS), makes it easier to extract structured information and metrics for detecting linguistic inaccuracies and defects. QuARS allows requirements engineers to perform an initial parsing of requirements by automatically detecting potential linguistic defects that can cause ambiguity problems at later stages of software product development. The tool also provides support for the consistency and completeness analysis of the requirements.Source: ISTI Technical reports, 2005
Lami G.
Numerous tools and techniques are available for managing requirements. Many are designed to define requirements, provide configuration management, and control distribution. However, there are few automatic tools to support the quality analysis of natural language (NL) requirements. Ambiguity analysis and consistency and completeness verification are usually carried out by human reviewers who read requirements documents and look for defects. This clerical activity is boring, time consuming, and often ineffective. This report describes a disciplined method and a related automated tool that can be used for the analysis of NL requirements documents. The tool, called the Quality Analyzer for Requirements Specifications (QuARS), makes it easier to extract structured information and metrics for detecting linguistic inaccuracies and defects. QuARS allows requirements engineers to perform an initial parsing of requirements by automatically detecting potential linguistic defects that can cause ambiguity problems at later stages of software product development. The tool also provides support for the consistency and completeness analysis of the requirements.Source: ISTI Technical reports, 2005
See at:
ISTI Repository 
| www.sei.cmu.edu | CNR ExploRA
2005
Contribution to conference
Open Access
Second international software product lines young researchers workshop (SPLYR). Introduction: Family Planning beyond the Software: the second sibling
Geppet B., John I., Lami G.
Different to many other software engineering techniques, product-line engi-neering arose from practical experience in industry. But as with every successful technique product line-engineering can also be considered only a real standard approach when it is not only applied in practice but also widely researched and especially taught in academia. Practice and academia are the two sides of the same coin. While industry sets the requirements, academia prepares the practi-tioners of tomorrow. The peculiarity of the SPLYR workshop is that it is specifi-cally addressed to young researchers, in particular Ph.D. students, having origi-nal ideas and initiatives in the product line field. The first SPLYR workshop was successfully held at SPLC 2004 in Boston, the second SPLYR workshop is now part of SPLC Europe 2005. Different from the standard procedure of most workshops, we have no blind peer reviews at SPLYR. Each student was assigned to the product line expert who reviewed the proposal and discussed pros and cons of the work with the student. We would like to thank Len Bass, Stuart Faulk, Stefania Gnesi and Robyn Lutz for review-ing the proposals and for the effort they spent. We selected four proposals for presentation at the workshop. The topics range from organizational issues to enterprise applications, variability management and evolution. For many of the students this is the first time to present their work to an inter-national audience. The workshop aims at providing the right platform for this and for discussing the presented work among each other and with experts in the field. We hope that with this workshop each of the students will get valu-able feedback for the further development of the work.
Geppet B., John I., Lami G.
Different to many other software engineering techniques, product-line engi-neering arose from practical experience in industry. But as with every successful technique product line-engineering can also be considered only a real standard approach when it is not only applied in practice but also widely researched and especially taught in academia. Practice and academia are the two sides of the same coin. While industry sets the requirements, academia prepares the practi-tioners of tomorrow. The peculiarity of the SPLYR workshop is that it is specifi-cally addressed to young researchers, in particular Ph.D. students, having origi-nal ideas and initiatives in the product line field. The first SPLYR workshop was successfully held at SPLC 2004 in Boston, the second SPLYR workshop is now part of SPLC Europe 2005. Different from the standard procedure of most workshops, we have no blind peer reviews at SPLYR. Each student was assigned to the product line expert who reviewed the proposal and discussed pros and cons of the work with the student. We would like to thank Len Bass, Stuart Faulk, Stefania Gnesi and Robyn Lutz for review-ing the proposals and for the effort they spent. We selected four proposals for presentation at the workshop. The topics range from organizational issues to enterprise applications, variability management and evolution. For many of the students this is the first time to present their work to an inter-national audience. The workshop aims at providing the right platform for this and for discussing the presented work among each other and with experts in the field. We hope that with this workshop each of the students will get valu-able feedback for the further development of the work.
See at:
www.iese.fraunhofer.de | CNR ExploRA
2006
Report
Unknown
Proceedings of the Software Product Lines Doctoral Symposium
John I., Bass L., Lami G.
Different from other software engineering techniques, product-line engineering arose from practical experience in industry. But as with every successful technique product line engineering can also be considered only a real standard approach when it is not only applied in practice but also widely researched and especially taught in academia. Practice and academia are the two sides of the same coin. While industry sets the requirements, academia prepares the practitioners of tomorrow. The SPLC doctoral symposium provides a platform for young researchers to present their work to an international audience and discuss it with each other and with experts in the field. The SPLC doctoral symposium originates from the successful experience of the past two editions of the SPLYR (Software Product Lines Young Researchers) workshop held in conjunction with SPLC '04 and SPLC '05. Experienced researchers will comment on the presented work and give feedback for further development, research goals, methods, and results to provide useful guidance in completion of the dissertation research. This event is a unique opportunity for the presenting young researchers and doctoral students to receive invaluable expert feedback, make contact with other researchers in the field, professionally present their work, and become familiar with other approaches and future research topics. The doctoral symposium addresses research activities in the field of software product lines (SPLs). The peculiarity of this doctoral symposium is that it is addressed specifically to young researchers with original ideas and initiatives in the SPL field. Although it mainly addresses PhD work in progress, we also encouraged the submission of other work in progress such as master's degree or diploma theses. Different from the standard procedure of other doctoral symposiums and workshops, we have no blind peer reviews. Each student was assigned to one or two product line experts who reviewed the proposal and discussed pros and cons of the work with the student. We would like to thank our reviewers and panelists.Source: ISTI Technical reports, 2006
John I., Bass L., Lami G.
Different from other software engineering techniques, product-line engineering arose from practical experience in industry. But as with every successful technique product line engineering can also be considered only a real standard approach when it is not only applied in practice but also widely researched and especially taught in academia. Practice and academia are the two sides of the same coin. While industry sets the requirements, academia prepares the practitioners of tomorrow. The SPLC doctoral symposium provides a platform for young researchers to present their work to an international audience and discuss it with each other and with experts in the field. The SPLC doctoral symposium originates from the successful experience of the past two editions of the SPLYR (Software Product Lines Young Researchers) workshop held in conjunction with SPLC '04 and SPLC '05. Experienced researchers will comment on the presented work and give feedback for further development, research goals, methods, and results to provide useful guidance in completion of the dissertation research. This event is a unique opportunity for the presenting young researchers and doctoral students to receive invaluable expert feedback, make contact with other researchers in the field, professionally present their work, and become familiar with other approaches and future research topics. The doctoral symposium addresses research activities in the field of software product lines (SPLs). The peculiarity of this doctoral symposium is that it is addressed specifically to young researchers with original ideas and initiatives in the SPL field. Although it mainly addresses PhD work in progress, we also encouraged the submission of other work in progress such as master's degree or diploma theses. Different from the standard procedure of other doctoral symposiums and workshops, we have no blind peer reviews. Each student was assigned to one or two product line experts who reviewed the proposal and discussed pros and cons of the work with the student. We would like to thank our reviewers and panelists.Source: ISTI Technical reports, 2006
See at: CNR ExploRA
2004
Other
Open Access
International Software Product Lines Young Researcher Workshop (SPLYR)
Geppert B., John I., Lami G.
In the past years product-line engineering has emerged as the standard practice in industry for large-scale software reuse. Different to many other techniques, product-line engineering arose from practical experience in industry. But as with every successful technique product line-engineering can also be consid-ered only a real standard approach when it is not only applied in practice but also widely researched and especially taught in academia. Practice and acade-mia are the two sides of the same coin. While industry sets the requirements, academia prepares the practitioners of tomorrow. The peculiarity of the SPLYR workshop is that it is specifically addressed to young researchers, in particular Ph.D. students, having original ideas and initiatives in the product line field.
Geppert B., John I., Lami G.
In the past years product-line engineering has emerged as the standard practice in industry for large-scale software reuse. Different to many other techniques, product-line engineering arose from practical experience in industry. But as with every successful technique product line-engineering can also be consid-ered only a real standard approach when it is not only applied in practice but also widely researched and especially taught in academia. Practice and acade-mia are the two sides of the same coin. While industry sets the requirements, academia prepares the practitioners of tomorrow. The peculiarity of the SPLYR workshop is that it is specifically addressed to young researchers, in particular Ph.D. students, having original ideas and initiatives in the product line field.
See at:
ISTI Repository | CNR ExploRA
2011
Conference article
Unknown
ISO/IEC 15504-10 vs. ISO 26262: Mutual Relationships
Dussa-Zieger Klaudia, Earthy Jonathan, Johansson Mika, Lami Giuseppe
ISO/IEC 15504 Part 10 Safety Extension has been recently developed in order to make consistent judgment regarding process capability or improvement priorities for safety related systems development. To avoid misunderstanding and confute reluctance and worry related to such a safety extension, its contents, purpose and intended usage are explained in this paper. The authors provide also a comparison between the ISO/IEC 15504 Part 10 and other existing safety standards for software (with particular focus on the ISO 26262) as well as a discussion on possible integrations and consequent benefits of its usage.Source: 1st VDA Automotive SYS Conference, Berlin, 5-6 July 2011
Dussa-Zieger Klaudia, Earthy Jonathan, Johansson Mika, Lami Giuseppe
ISO/IEC 15504 Part 10 Safety Extension has been recently developed in order to make consistent judgment regarding process capability or improvement priorities for safety related systems development. To avoid misunderstanding and confute reluctance and worry related to such a safety extension, its contents, purpose and intended usage are explained in this paper. The authors provide also a comparison between the ISO/IEC 15504 Part 10 and other existing safety standards for software (with particular focus on the ISO 26262) as well as a discussion on possible integrations and consequent benefits of its usage.Source: 1st VDA Automotive SYS Conference, Berlin, 5-6 July 2011
See at: CNR ExploRA
2011
Conference article
Unknown
A proposal for a new common scope for automotive SPICE: six reasons for adding the MAN.6 process
Buglione L., Lami G.
A proposal arising few months ago from an Italian Automotive SPIN meeting was therefore to include also MAN.6 in a process assessment scope for the Automotive sector . Of course such position must be supported by analysis and this contribution would aim to stimulate a discussion on the possible advantages in including one process more in such assessment scope. In order to do it, we decided to create a list with the six main reasons for including itSource: 1st VDA Automotive SYS conference, Automotive SYS 2011, pp. C1.1, Berlin, Germany, 5-6 July 2011
Buglione L., Lami G.
A proposal arising few months ago from an Italian Automotive SPIN meeting was therefore to include also MAN.6 in a process assessment scope for the Automotive sector . Of course such position must be supported by analysis and this contribution would aim to stimulate a discussion on the possible advantages in including one process more in such assessment scope. In order to do it, we decided to create a list with the six main reasons for including itSource: 1st VDA Automotive SYS conference, Automotive SYS 2011, pp. C1.1, Berlin, Germany, 5-6 July 2011
See at: CNR ExploRA
2012
Conference article
Restricted
Measuring software sustainability from a process-centric perspective
Lami G., Buglione L.
There is growing attention paid to the increasing in the global carbon dioxide production and to the subsequent issue of sustainability in ICT-related projects. But very few information and time has been spent right now for determining a set of related measures from sustainable processes. Moving from a new set of three sustainable processes in the SPICE (ISO/IEC 15504) format, this paper proposes a related approach for creating a sustainability measurement plan, with the aim to integrate further information elements for improving the decision-making process.Source: 22nd International Workshop on Software Measurement and the 2012 Seventh International Joint Conference on Software Process and Product Measurement, pp. 53–59, Assisi, Italy, 17-19 October 2012
DOI: 10.1109/iwsm-mensura.2012.16
Metrics:
Lami G., Buglione L.
There is growing attention paid to the increasing in the global carbon dioxide production and to the subsequent issue of sustainability in ICT-related projects. But very few information and time has been spent right now for determining a set of related measures from sustainable processes. Moving from a new set of three sustainable processes in the SPICE (ISO/IEC 15504) format, this paper proposes a related approach for creating a sustainability measurement plan, with the aim to integrate further information elements for improving the decision-making process.Source: 22nd International Workshop on Software Measurement and the 2012 Seventh International Joint Conference on Software Process and Product Measurement, pp. 53–59, Assisi, Italy, 17-19 October 2012
DOI: 10.1109/iwsm-mensura.2012.16
Metrics:
See at:
doi.org | ieeexplore.ieee.org | CNR ExploRA
2013
Conference article
Restricted
Leveraging reuse-related maturity issues for achieving higher maturity & capability levels
Buglione L., Lami G., Gresse Von Wangenheim C., Mc Caffrey F., Rossa Hauck J. C.
During the past 20 years Maturity & Capability Models (MCMs) become a buzzword in the ICT world. Since the initial Crosby's idea in 1979, plenty of models have been created in the Software & Systems Engineering domains, addressing various perspectives. By analyzing the content of the Process Reference Models (PRM) in many of them, it can be noticed that reuse-related issues have unfortunately often little importance in the appraisals of the capabilities of software organizations while in practice they are considered as significant contributors in traditional process and organizational performance appraisals. While MCMs represent a good mean for assessing the status of a set of processes, integrating two or more models with a common area of focus can offer more information and value for an organization. The aim of this paper is to present some information about Reuse best practices and models, keep the best components from each model and - using the LEGO (Living EnGineering prOcess) approach to process improvement - merge those best practices from several types of maturity models into an organizational Business Process Model (BPM) in order to achieve in an easier and faster way higher organizational maturity and capability levels.Source: ICSR 2013 - Safe and Secure Software Reuse. 13th International conference, pp. 343–354, 18-20 June 2013, Pisa, Italy
DOI: 10.1007/978-3-642-38977-1_26
Metrics:
Buglione L., Lami G., Gresse Von Wangenheim C., Mc Caffrey F., Rossa Hauck J. C.
During the past 20 years Maturity & Capability Models (MCMs) become a buzzword in the ICT world. Since the initial Crosby's idea in 1979, plenty of models have been created in the Software & Systems Engineering domains, addressing various perspectives. By analyzing the content of the Process Reference Models (PRM) in many of them, it can be noticed that reuse-related issues have unfortunately often little importance in the appraisals of the capabilities of software organizations while in practice they are considered as significant contributors in traditional process and organizational performance appraisals. While MCMs represent a good mean for assessing the status of a set of processes, integrating two or more models with a common area of focus can offer more information and value for an organization. The aim of this paper is to present some information about Reuse best practices and models, keep the best components from each model and - using the LEGO (Living EnGineering prOcess) approach to process improvement - merge those best practices from several types of maturity models into an organizational Business Process Model (BPM) in order to achieve in an easier and faster way higher organizational maturity and capability levels.Source: ICSR 2013 - Safe and Secure Software Reuse. 13th International conference, pp. 343–354, 18-20 June 2013, Pisa, Italy
DOI: 10.1007/978-3-642-38977-1_26
Metrics:
See at:
doi.org | link.springer.com | CNR ExploRA
2004
Doctoral thesis
Unknown
Quality evaluation of natural language software requirements: methods, techniques and tools
Lami G.
In this Ph.D. thesis the original results achieved by Giuseppe Lami in his doctoral course are collected. The objective of this thesis is to define methods, techniques and tools for the analysis of natural language requirements. First, a method to systematically evaluate the quality of natural language requirements is described along with a tool able to make this evaluation automatic. Then a method to verify the conformance of product-specific Use Cases to the Software Product Line constraints is also described. This method is based on a extention of the Use Case formalism to make it suitable to represent the variabilities of a Software Product Line.
Lami G.
In this Ph.D. thesis the original results achieved by Giuseppe Lami in his doctoral course are collected. The objective of this thesis is to define methods, techniques and tools for the analysis of natural language requirements. First, a method to systematically evaluate the quality of natural language requirements is described along with a tool able to make this evaluation automatic. Then a method to verify the conformance of product-specific Use Cases to the Software Product Line constraints is also described. This method is based on a extention of the Use Case formalism to make it suitable to represent the variabilities of a Software Product Line.
See at: CNR ExploRA
1999
Report
Unknown
Towards an automatic quality evaluation of natural language software specifications
Lami G.
Requirements Specification is a crucial phase of the software life-cycle. Providing the software engineer with tools and techniques for evaluating quality of Software Requirements may solve some of the problems due to possible lacks of quality of them. In this paper, first a feasible Quality Model is defined for Software Requirements written in Natural Language (NL). The term feasible means that the Quality Properties of this Quality Model can be evaluated by means of Indicators automatically and numerically measurable. Then, the results of the validation of this Quality Model on industrial cases are presented. The encouraging outcomes of the validation have been taken into account for starting the realization of an automatic tool for verifying the adherence to syntax/lexical constraints of the requirement sentences to guarantee the conformance to the Quality Model. This tool should be a valid support for the reviewer of NL Software Requirements.Source: ISTI Technical reports, pp.1–10, 1999
Lami G.
Requirements Specification is a crucial phase of the software life-cycle. Providing the software engineer with tools and techniques for evaluating quality of Software Requirements may solve some of the problems due to possible lacks of quality of them. In this paper, first a feasible Quality Model is defined for Software Requirements written in Natural Language (NL). The term feasible means that the Quality Properties of this Quality Model can be evaluated by means of Indicators automatically and numerically measurable. Then, the results of the validation of this Quality Model on industrial cases are presented. The encouraging outcomes of the validation have been taken into account for starting the realization of an automatic tool for verifying the adherence to syntax/lexical constraints of the requirement sentences to guarantee the conformance to the Quality Model. This tool should be a valid support for the reviewer of NL Software Requirements.Source: ISTI Technical reports, pp.1–10, 1999
See at: CNR ExploRA
2004
Journal article
Unknown
A methodology for the derivation and verification of use cases for product lines
Fantechi A., Gnesi S., Lami G., Nesti E.
In this paper, we present a methodology to express, in a formal way, the requirements of products belonging to a product line. We relied on a formalism allowing the representation of variabilities at the family level and the instantiation of them in order to move to the requirements of a single product. The proposed methodology also allows the formalization of the family constraints to be taken into account for the construction of the products belonging to it, along with the verification of the compliance to those constraints of a single product requirements document. This approach is promising due to its simplicity and effectiveness for being supported by automatic tools.Source: Lecture notes in computer science 3154 (2004): 255–265.
Fantechi A., Gnesi S., Lami G., Nesti E.
In this paper, we present a methodology to express, in a formal way, the requirements of products belonging to a product line. We relied on a formalism allowing the representation of variabilities at the family level and the instantiation of them in order to move to the requirements of a single product. The proposed methodology also allows the formalization of the family constraints to be taken into account for the construction of the products belonging to it, along with the verification of the compliance to those constraints of a single product requirements document. This approach is promising due to its simplicity and effectiveness for being supported by automatic tools.Source: Lecture notes in computer science 3154 (2004): 255–265.
See at: CNR ExploRA