A multiprocess quality model: identification of of key processes in the integration approach

In this paper we investigate the use of multiprocess quality model in the adoption of process improvement frameworks. We analyze an improvement effort based on multiple process quality models adoption. At present, there is a possibility of a software development organization to adopt multi-quality and improvement models in order to remain competitive in the IT market place. Various quality models emerge to satisfy different improvement objective such as to improve capability of models, quality management and serve as IT government purpose. The heterogeneity characteristics of the models require further research on dealing with multiple process models at a time. We discuss on the concept of software process and overview on software maintenance and evolution which are important elements in the quality models. The concepts related to process quality model and improvement models are discussed. The research outlined in this paper shows that software processes, maintenance, evolution, quality and improvement have become really important in software engineering. The synergy among the multi-focused process quality model is examined with respect to process improvement. The research outcome is to determine key processes vital to the implementation of multi-process quality model

Measuring the Impact of Quality Improvement in a Software Company

The quality issue is not only a matter of developing and implementing a quality system. It mandatory this system to function precisely on a long term basis. The evaluation of quality impact as a consequence of its improvement is a scary thing the quality specialists prefer to be apart due to its complexity. That’s the reason why the article emphasize on: the need and justification of quality impact evaluation, particularities of quality in software domain generated by its specificity, what evaluation of economic effects means in the context of a quality improvement particularly in a software company, a proposed method to calculate the impact of quality (on the costs structure), a practical example of how the method should be used and the results interpreted based on two simulated case.quality improvement; quality management; software industry; quality impact evaluation; measure quality.

Integrating automated support for a software management cycle into the TAME system

Software managers are interested in the quantitative management of software quality, cost and progress. An integrated software management methodology, which can be applied throughout the software life cycle for any number purposes, is required. The TAME (Tailoring A Measurement Environment) methodology is based on the improvement paradigm and the goal/question/metric (GQM) paradigm. This methodology helps generate a software engineering process and measurement environment based on the project characteristics. The SQMAR (software quality measurement and assurance technology) is a software quality metric system and methodology applied to the development processes. It is based on the feed forward control principle. Quality target setting is carried out before the plan-do-check-action activities are performed. These methodologies are integrated to realize goal oriented measurement, process control and visual management. A metric setting procedure based on the GQM paradigm, a management system called the software management cycle (SMC), and its application to a case study based on NASA/SEL data are discussed. The expected effects of SMC are quality improvement, managerial cost reduction, accumulation and reuse of experience, and a highly visual management reporting system

Software Development Standard and Software Engineering Practice: A Case Study of Bangladesh

Improving software process to achieve high quality in a software development organization is the key factor to success. Bangladeshi software firms have not experienced much in this particular area in comparison to other countries. The ISO 9001 and CMM standard has become a basic part of software development. The main objectives of our study are: 1) To understand the software development process uses by the software developer firms in Bangladesh 2) To identify the development practices based on established quality standard and 3) To establish a standardized and coherent process for the development of software for a specific project. It is revealed from this research that software industries of Bangladesh are lacking in target set for software process and improvement, involvement of quality control activities, and standardize business expertise practice. This paper investigates the Bangladeshi software industry in the light of the above challenges.Comment: 13 pages, 3 figures, 11 table

Quality plan to improvement of software company

Hoy en día las empresas de fabricación de software optan por realizar diferentes actividades que conlleven a aplicar los conceptos de calidad en el ámbito del desarrollo del software. Hablar de calidad del producto (software) implica la necesidad de contar con diferentes lineamientos que permitan establecer los niveles mínimos que un producto debe alcanzar para que se considere de calidad. La calidad en la fabricación de software no es algo que se puede añadir en la etapa final; sino por el contrario es algo que se realiza, se controla y se verifica durante todo el ciclo de vida del desarrollo del software. El plan de mejoramiento planteado se centra en aplicar el modelo de madurez de la capacidad el cual es un enfoque para la mejora de los procesos; cuenta con los elementos esenciales para el desarrollo de un proceso efectivo y mide la madurez del desarrollo del software. En la empresa, caso de estudio, se presentan falencias en la calidad del desarrollo de software lo que permite evidenciar la necesidad de proponer un plan de mejoramiento que permita mejorar la calidad de los procesos del desarrollo del software. Como bien lo sabemos la calidad es una filosofía que debe ser aplicada a todos los procesos de las compañías; esto implica un proceso de mejoramiento continuo que no tiene final, dicho proceso permite visualizar un panorama más amplio, en búsqueda de la excelencia y de la innovación que permitan aumentar la competitividad en las compañías de fabricación de software.Nowadays software manufacturing companies choose different activities that lead to apply the concepts of quality in the field of software development. Speaking of product quality (software) implies the need to have different guidelines that establish minimum standards that a product must meet to be considered quality. The quality software is not something that can be added in the final stage, but rather is something that is done is controlled and verified throughout the life cicle of software development. The proposed improvement plan focuses on applying the model capability maturity which is an approach to process improvement, has the essentials for developing an effective process and measures the maturity of software development. Failures occur in the quality of software development which makes evident the need to propose an improvement plan that will improve the quality of software development processes in the business, case study. As you know the quality is a philosophy that must be applied to all processes of the companies, this implies a continuous improvement process that has no end, this process allows you to view a bigger picture, in pursuit of excellence and innovation that will increase competitiveness in software manufacturing companies

The Measurement of Quality of Semantic Standards: the Application of a Quality Model on the SETU standard for eGovernment

eGovernment interoperability should be dealt with using high-quality standards. A quality model for standards is presented based on knowledge from the software engineering domain. In the tradition of action research the model is used on the SETU standard, a standard that is mandatory in the public sector of the Netherlands in order to achieve eGovernment interoperability. This results in improvement suggestions for the SETU standards, just as improvement suggestions for the quality model have been identified. Most importantly it shows that a quality model can be used for several purposes, including selecting standards for eGovernment interoperability

Improving (Software) Patent Quality Through the Administrative Process

The available evidence indicates that patent quality, particularly in the area of software, needs improvement. This Article argues that even an agency as institutionally constrained as the U.S. Patent and Trademark Office (“PTO”) could implement a portfolio of pragmatic, cost-effective quality improvement strategies. The argument in favor of these strategies draws upon not only legal theory and doctrine but also new data from a PTO software examination unit with relatively strict practices. Strategies that resolve around Section 112 of the patent statute could usefully be deployed at the initial examination stage. Other strategies could be deployed within the new post-issuance procedures available to the agency under the America Invents Act. Notably, although the strategies the Article discusses have the virtue of being neutral as to technology, they are likely to have a very significant practical impact in the area of software