243,962 research outputs found
FQMaP: Towards a Framework Quantitative Management of Processes in Small Software Development Organizations
Software development organizations need to control and improve their practices, seeking to reduce variability when executing the necessary processes to elaborate software; therefore, these organizations implement improvement plans to identify factors that affect the processes. Quantitative Management deals with identification, tracing, and control of those incident factors, using data proactively to predict performance and the effect of possible changes in a process. Reference models in software processes development such as CMMI V2.0 and ISO/IEC 33061:2021 address Quantitative Management, but are aimed at big enterprises. Other models such as MoProSoft, COMPETISOFT, and MPS.BR are aimed at small enterprises, but do not include enough elements on Quantitative Management. Execution of a systematic literature review permitted searching for works on Quantitative Management intended for small software development enterprises, indicating necessary practices and how to perform them. This search showed that a proposal is not available that incorporates Quantitative Management practices for software processes aimed small software development enterprises. The referred aspects make it difficult to adopt a Quantitative Management culture within these organizations, it which has become a problem, consisting in that small software development enterprises that do not execute quantitative management practices will have difficulty identifying and focusing on the factors that impact the process performance and, therefore, on the results of their projects. This work sought to tackle this problem by proposing the âframework for quantitative management of processes in small software development organizationsâ (FQMaP), which allows incorporating practices and techniques that support Quantitative Management of software development processes in these kinds of enterprises. From the evaluation of FQMaP, carried out by following Focus Group technique guidelines, it can be demonstrated that it is a simple proposal and with elements that can serve a company to quantitatively manage software development processes. Also, it has clearly specified its components, showing that its structure is familiar with other process patterns, that would facilitate their interpretation
Process capability assessments in small development firms
[Abstract}: Assessment-based Software Process Improvement (SPI) programs such as the Capability Maturity Model (CMM), Bootstrap, and SPICE (ISO/IEC 15504) are based on formal frameworks and promote the use of systematic processes and management practices for software development. These approaches identify best practices for the management of software development and when applied, enable organizations to understand, control and improve development processes. The purpose of a SPI assessment is to compare the current processes used in an organization with a list of recommended or âbestâ practices.
This research investigates the adoption of SPI initiatives by four small software development firms. These four firms participated in a process improvement program which was sponsored by Software Engineering Australia (SEA) (Queensland). The assessment method was based on SPICE (ISO/IEC 15504) and included an initial assessment, recommendations, and a follow-up meeting. For each firm, before and after snapshots are provided of the capability as assessed on eight processes. The discussion which follows summarizes the improvements realized and considers the critical success factors relating to SPI adoption for small firms
Measuring Software Process: A Systematic Mapping Study
Context: Measurement is essential to reach predictable performance and high capability processes. It provides
support for better understanding, evaluation, management, and control of the development process
and project, as well as the resulting product. It also enables organizations to improve and predict its processâs
performance, which places organizations in better positions to make appropriate decisions. Objective:
This study aims to understand the measurement of the software development process, to identify studies,
create a classification scheme based on the identified studies, and then to map such studies into the scheme
to answer the research questions. Method: Systematic mapping is the selected research methodology for this
study. Results: A total of 462 studies are included and classified into four topics with respect to their focus
and into three groups based on the publishing date. Five abstractions and 64 attributes were identified,
25 methods/models and 17 contexts were distinguished. Conclusion: capability and performance were the
most measured process attributes, while effort and performance were the most measured project attributes.
Goal Question Metric and Capability Maturity Model Integration were the main methods and models used
in the studies, whereas agile/lean development and small/medium-size enterprise were the most frequently
identified research contexts.Ministerio de EconomĂa y Competitividad TIN2013-46928-C3-3-RMinisterio de EconomĂa y Competitividad TIN2016-76956-C3-2- RMinisterio de EconomĂa y Competitividad TIN2015-71938-RED
A quality management based on the Quality Model life cycle
Managing quality is a hard and expensive task that involves the execution and control of processes and techniques.
For a good quality management, it is important to know the current state and the objective to be
achieved. It is essential to take into account with a Quality Model that specifies the purposes of managing
quality. QuEF (Quality Evaluation Framework) is a framework to manage quality in MDWE (Model-driven
Web Engineering). This paper suggests managing quality but pointing out the Quality Model life cycle. The
purpose is to converge toward a quality continuous improvement by means of reducing effort and time.Ministerio de Ciencia e InnovaciĂłn TIN2010-20057-C03-02Ministerio de Ciencia e InnovaciĂłn TIN 2010-12312-EJunta de AndalucĂa TIC-578
Understanding the perception of very small software companies towards the adoption of process standards
This paper is concerned with understanding the issues that affect the adoption of software process standards by Very Small Entities (VSEs), there needs from process standards and there willingness to engage with the new ISO/IEC 29110 standard in particular. In order to achieve this goal, a series of industry data collection studies were undertaken with a collection of VSEs. A twin track approach of a qualitative data collection (interviews and focus groups) and quantitative data collection (questionnaire), with data analysis being completed separately and finally results merged, using the coding mechanisms of grounded theory. This paper serves as a roadmap for both researchers wishing to understand the issues of process standards adoption by very small companies and also for the software process standards community
Agile, Web Engineering and Capability Maturity ModelI ntegration : A systematic literature review
Context
Agile approaches are an alternative for organizations developing software, particularly for those who develop Web applications. Besides, CMMI (Capability Maturity Model Integration) models are well-established approaches focused on assessing the maturity of an organization that develops software. Web Engineering is the field of Software Engineering responsible for analyzing and studying the specific characteristics of the Web. The suitability of an Agile approach to help organizations reach a certain CMMI maturity level in Web environments will be very interesting, as they will be able to keep the ability to quickly react and adapt to changes as long as their development processes get mature.
Objective
This paper responds to whether it is feasible or not, for an organization developing Web systems, to achieve a certain maturity level of the CMMI-DEV model using Agile methods.
Method
The proposal is analyzed by means of a systematic literature review of the relevant approaches in the field, defining a characterization schema in order to compare them to introduce the current state-of-the-art.
Results
The results achieved after the systematic literature review are presented, analyzed and compared against the defined schema, extracting relevant conclusions for the different dimensions of the problem: compatibility, compliance, experience, maturity and Web.
Conclusion
It is concluded that although the definition of an Agile approach to meet the different CMMI maturity levels goals could be possible for an organization developing Web systems, there is still a lack of detailed studies and analysis on the field
Web engineering security: essential elements
Security is an elusive target in todayâs high-speed and extremely complex, Web enabled, information rich business environment. This paper presents the idea that there are essential, basic organizational elements that need to be identified, defined and addressed before examining security aspects of a Web Engineering Development process. These elements are derived from empirical evidence based on a Web survey and supporting literature. This paper makes two contributions. The first contribution is the identification of the Web Engineering specific elements that need to be acknowledged and resolved prior to the assessment of a Web Engineering process from a security perspective. The second contribution is that these elements can be used to help guide Security Improvement Initiatives in Web Engineering
A DISCUSSION ON ASSURING SOFTWARE QUALITY IN SMALL AND MEDIUM SOFTWARE ENTERPRISES: AN EMPIRICAL INVESTIGATION
Under the studies of general core activities including software inspection, review and testing to achieve quality objectives in small-medium size enterprises (SMEs), the paper presents a contemporary view of such companies against quality measures. The results from a local empirical investigation of quality standards in the Turkish software industry are reported.Around 150 software companies have been approached from which 17 detailed feedback inform that in order to ensure software quality, standards including internationally recognized International Standards Organization (ISO) and Capability Maturity Model Integration (CMMI) are given credit. However the substantial workload and resources required to obtain them are also reported as serious; downscaled
frameworks of such large models proposed in the literature are not well known by the SMEs either. The paper also discusses "work around" that bypasses such
standards to ease delivery of products while keeping certificates as labels just to acquire new jobs for the business
- âŠ