Experiences With Quality On A RecentSoftware Development Project

2000

NEC do Brasil -NDB is a telecommunication company that encompasses Brazilian and Latin America markets by providing products and solutions to its customers. With its business, NDB has four areas, which are concerned in the software development: Switching, Wireless, Transmission and Radio. NDB software teams perform customization of systems developed by other companies as well as the complete development of software systems. These are real time systems and they control the functionality of the telecommunications equipment, operate in commercial computers and in embedded systems. NDB has been developing since 1996 a specific program for Software Process Improvement. This R&D program is a partnership with University of Sao Paulo -USP and has been the first Brazilian Telecommunication Company to apply the model SW-CMM and achieving Level 2 in 1997. The aim of this paper is to present NDB's experience in the implementation of Software Quality Management -SQM, by applying the experience, culture and successful practices already institutionalized in an environment of Total Quality Management -TQM. The paper also proposes to answer doubts of implementation, problems faced in development of activities as well as the found solutions, lessons learned and SQM benefits. SW-CMM is an application of TQM concepts to software development [1,2] and the success of TQM has inspired the software process improvement . NDB's experience shows that a Management structure established with TQM concepts is applicable and tailored, in many aspects and features, for a SQM establishment. In spite of this experience and knowledge have great relation with SW-CMM, some practices and the general concept can be applied in any of current models or standards for software process improvement like ISO/IEC 15504 -SPICE; ISO 9000-3 and TL 9000.

The understanding of the difficulties for producing software with quality has lead the software development Brazilian Industries to search for methods, techniques and tools to give support to software development and to guarantee its quality. However, researches in this area have demonstrated that, in most cases the use of these new technologies does not guarantee a software product with quality, since technical and management aspects related to activities planning and control of a specific development process are not considered.

2017

In modern age, each and every users want to certain level of quality in software for achieving the desired performance. The sense of quality could not be limited but in general sense “ it is fitness for use of software is much enough ‘there was so many investigations were performed previously by the various research scholars in respect of quality of the software. in this papers we were focus on the quality aspects , steps associated to improving the quality of the software , software quality tools and phase of software developments There by we were achieved an improvement in software quality. Key word: software quality, quality aspect, quality tools ( pareto-charts , fish-born diagram) , development phases --------------------------------------------------------------------------------------------------------------------------------------Date of Submission: 08-09-2017 Date of acceptance: 22-09-2017 -------------------------------------------------------------------------------------...

2014

Proceedings 26th Annual International Computer Software and Applications CMPSAC-02, 2002

This paper describes research on the perceived impact of process improvement activities on the quality of the services provided to the (internal) customers. A questionnaire was developed to map the notion 'quality of service' from the point of view from both ITdepartments and business customers. These assessments were measures against a subjective scale that runs from 'insufficient' to 'sufficient'. This survey was used in 9 different IT-development organisations, all part of the same holding. On the basis of the internal report on this survey top-management accepted those SPI-investments were providing sufficient benefits and required a repeat at one-year intervals.

1994

The Borland Quattro Pro for Windows (QPW) development is one of the most remarkable organizations, processes, and development cultures we have encountered in the AT&T Bell Laboratories Pasteur process research project. The project assimilated requirements, completed design and implementation of 1 million lines of code, and completed testing in 31 months. Coding was done by no more than eight people at a time, which means that individual coding productivity was higher than 1000 lines of code per staff-week. The project capitalized on its small size by centering development activities around daily meetings where architecture, design, and interface issues were socialized. Quality assurance and project management roles were central to the development sociology, in contrast to the developer-centric software production most often observed in our studies of AT&T telecommunications software. Analyses of the development process are ''off the charts'' relative to most other processes we have studied. Jim -Thanks again for speaking at BIC '93. I'm also glad you could stop by Borland and experience what we call Borland Software Craftsmanship. We are a young company, started by a Frenchman, with young bright and excited developers. In my 8 years at Borland I have been in the center of it all and can't imagine another place to be. Let us know if there is anything else we can do for you.

Staffordshire University, School of Computing Report, 1996

This paper contains two sections relating to software quality issues. First, the various definitions of software quality are examined and an alternative suggested. It continues with a review of the quality model as defined by McCall, Richards and Walters in 1977 and mentions the later model of Boëhm published in 1978. Each of McCall's quality factors is reviewed and the extent to which they still apply in the late 1990s is commented on. The factors include, integrity, reliability, usability, accuracy, efficiency, maintainability, testability, flexibility, interface facility (interoperability), re-usability and transferability (portability). They are subdivided into external and internal quality factors. Interrelationships between the different factors are shown in Perry's model. Issues of quality management and the prioritising of these factors are included. The second section examines the strategic impact of quality from both the supplier's and the purchaser's point of view. In particular product differentiation, tendering and estimating, system acquisition and employee productivity are considered. Product differentiation is mapped to Porter's generic business strategy. The COCOMO model for software costing and estimating is used to show that quality factors influence the cost of a product. As quality impacts on all classes of people in systems, human resources and the consequences for productivity are explored. Finally, system evaluation and selection techniques involve quantitative (weighting and rating) techniques and Robson's example and the influence of quality are examined.

2009

International Journal of Computer Applications, 2013

To achieve a quality product it is necessary for the developer to understand how it can be achieved. Theoretical study is the preliminary phase of understanding how to perform any activity and knowing its pros and cons. For achieving a quality product this paper shows a quick and elaborative review for a quality product.