...Title:The Relationship between Software Metrics and their respective Quality Factors Introduction The major goal of Software Engineering is to produce ‘Quality’ Software that meets the user’s needs. Software quality is defined as “an effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it”. (Pressman 2010: 400) For quality software to be designed, the problem must be understood, requirements gathered in order to produce a high-quality software solution, which must contain all the functional features that are required by the end user. McCall (1977) developed a Software Quality model which is vital to obtain data to improve the performance of a piece of software. The McCall quality model defines and identifies the quality of a software product by addressing the three perspectives, product operation; the ability of the product to be easily understood and operated to produce the required results of the user, product revision; the ability of the software product to undergo changes which include error correction, flexibility, system adaptation, product transition; the ability of the software to adapt to new environments and adapt to rapidly changing hardware (Jamwal 2010). The model gives a relationship between Software Quality Factors and Metrics used to quantify the quality of software. Software Quality factors represent attributes or characteristics of software that a user would use to...
Words: 1313 - Pages: 6
...The major goal of Software Engineering is to produce ‘Quality’ Software that meets the user’s needs. Software quality is defined as “an effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it”. (Pressman 2010: 400) For quality software to be designed, the problem must be understood, requirements gathered in order to produce a high-quality software solution, which must contain all the functional features that are required by the end user. McCall (1977) developed a Software Quality model which is vital to obtain data to improve the performance of a piece of software. The McCall quality model defines and identifies the quality of a software product by addressing the three perspectives, product operation; the ability of the product to be easily understood and operated to produce the required results of the user, product revision; the ability of the software product to undergo changes which include error correction, flexibility, system adaptation, product transition; the ability of the software to adapt to new environments and adapt to rapidly changing hardware (Jamwal 2010). The model gives a relationship between Software Quality Factors and Metrics used to quantify the quality of software. Software Quality factors represent attributes or characteristics of software that a user would use to relate or determine the overall quality of a piece of software. While Software metrics provide...
Words: 295 - Pages: 2
.../m'cCall, Gene F./Waiters Software Quality for an Vk~~ '4 Paul K./RichA'rds -General Electric Company .,..... . 4- Approved for public release; distribution unlimited. ROME AIR DEVELOPMENT CENTER Air Force Systems Command Griffiss Air Force Base, New York 13441 This report has been reviewed by the PADC Information Office (01) and is releasable to the National Technical Information Service (NTIS). At NTIS it will be releasable to the general public, including foreign nations. RADC-TR-77-369, Vo] III (of three) has been reviewed and approved for publication. APPROVED: JOSEPH P. CAVANO Project Engineer APPROVED: (2 &4~L ( ALAN R. BARNUM, Assistant Chief information Sciences Division FOR THE COMMANDER: JOH" F . HUSS Acting Clief, Plans Office If your address has changed or if you wish to be removed from the RADC mailing list, or if the addressee is no longer employed by your organization, please notify RADC (ISIS) Griffiss AFB NY 13441. This will assist us in maintaining a current mailing list. Do not return this copy. Retain or destroy. SECURITY CLASSIFICATION OF THIS PAGE (IW.i, Vt e En eed)RE REPORT DOCUMENJATIO4 PAGE I. REPORT NU bER . D I S UC ON BFRE COMPTING ORM ... ' j2. GOVT ACCESSION NO. 3. ft9CIPIkNTIS CATALOG NUMBER RADC-TR-77-369, 4. TITLE (and Subtlfe) Vol III (of three) COVERED S. TYPE OF REPORT A P91111O0 Final Technical Report FACTORS IN SOFTWARE QUALITY Aug 76 - Jul 77 ...
Words: 6344 - Pages: 26
...Chapter 16 – Software Quality Assurance Overview This chapter provides an introduction to software quality assurance. Software quality assurance (SQA) is the concern of every software engineer to reduce costs and improve product time-to-market. A Software Quality Assurance Plan is not merely another name for a test plan, though test plans are included in an SQA plan. SQA activities are performed on every software project. Use of metrics is an important part of developing a strategy to improve the quality of both software processes and work products. Software Quality Assurance • Umbrella activity applied throughout the software process • Planned and systematic pattern of actions required to ensure high quality in software • Responsibility of many stakeholders (software engineers, project managers, customers, salespeople, SQA group) SQA Questions • Does the software adequately meet its quality factors? • Has software development been conducted according to pre-established standards? • Have technical disciplines performed their SQA roles properly? Quality Assurance Elements • Standards – ensure that standards are adopted and follwed • Reviews and audits – audits are reviews performed by SQA personnel to ensure hat quality guidelines are followed for all software engineering work • Testing – ensure that testing id properly planned and conducted • Error/defect collection and analysis – collects and analyses error and defect data to better...
Words: 999 - Pages: 4
...Computing (E-ISSN: 2045-5364) Volume 1, Issue 2, December 2010 19 Analysis of Software Quality Models for Organizations Dr. Deepshikha Jamwal University of Jammu Department Of Computer Science & IT jamwal.shivani@gmail.com Abstract Software Quality model is a vital to obtained data so that actions can be taken to improve the performance. Such improvement can be measured quality, increased customer satisfaction and decreased cost of quality. Software metrics and quality models play a pivotal role in measurement of software quality. A number of well known qualities models are used to build quality software. Different researchers have proposed different software quality models to help measure the quality of software products. In our research, we are discussing the different software quality models and compare the software quality models with each other. Also a framework containing steps is proposed by authors. Some recommendations are also framed hereby in the following research paper. Keywords Software Quality Models, McCall model, Dromey‟s model, FURPS model, ISO 9126 model. Objectives To begin with there are some common objectives: To analysis various software quality models w.r.t various attributes. The presence, or absence, of these attributes can be measured objectively. The degree to which each of these attributes is present reflects the overall quality of the software product. These attributes facilitate continuous improvement, allowing cause and...
Words: 3104 - Pages: 13
...However, to make this decision, management must know what the reengineering will cost. This contribution describes an eight step tool supported process for calculating the time and the costs required to reengineer an existing system. The process is derived from the author’s 20 year experience in estimating reengineering projects and has been validated by several real life field experiments in which it has been refined and calibrated. Keywords: Reengineering, cost estimation, risk analysis, software measurement, gap analysis. It has been 15 years since the first studies on the economics of software reengineering projects appeared and since then a great deal of research has been done and a wide range of practical experience gathered.[1] At that time, reengineering projects were being calculated on the basis of the size alone, without consideration of complexity and quality. In the meantime, we have learned a lot more about how the complexity and quality of the software effect reengineering costs. The topic of estimating the costs of a reengineering project has also become more important to decision makers in industry since they have other alternatives to choose from. Reengineering is an alternative to redevelopment, to purchasing a standard package or to doing nothing at all. Therefore, management wants to know, what the return on investment is for each alternative. Without having a cost estimation it is not...
Words: 6450 - Pages: 26
...A Software Quality Assurance and Management System Er.Ashish Kumar Tripathi, Er. Sachin Kumar Dhar Dwivedi, Mr. Saurabh Upadhyay Abstract- Software quality objectives covers a variety of techniques and measurements, including gathering code metrics, enforcing coding rules, and proving the absence of run-time errors. The guide also takes into account the origin of the code, its stage in the software life cycle, and the safety aspects of the application. The guide explains how to gradually adapt the code verification process to achieve targeted quality objectives Index Terms- Application and System S/W, System efficiency, testing and good designing tools. -------------------------------------------------------- 1-Introduction Quality assurance for automotive systems can require different types of verification activities throughout the development process. Early verification focuses on evaluating intermediate software builds and removing defects at coding time. This represents an emerging trend because performing verification early in the process can improve overall quality and reduce development time. Post-production verification focuses on evaluating final build quality or finding defect root causes after the product is complete. This is the most common approach to automotive system verification. 3-About Software ProductsSoftware products may be • Custom - developed for a particular customer, according to its specifications Generic (“package”) - developed for...
Words: 1104 - Pages: 5
...Evaluation of Software Quality Krzysztof Sacha Warsaw University of Technology, Nowowiejska 15/19 00-665 Warszawa, Poland k.sacha@ia.pw.edu.pl Abstract. The paper describes a method, which we used to evaluate the expected quality of software that was developed for a huge governmental system. The evaluation lasted nearly two years and was performed along with the software development process. The output that was expected by our customer consisted of a quality assessment accompanied by a set of recommendations on what to do in order to enhance the quality of the product. 1 Introduction The ultimate goal of software engineering is to find methods for developing high quality software products at reasonable cost. As computers are being used in more and more critical areas of the industry, the quality of software becomes a key factor of business success and human safety. Two approaches can be followed to ensure software quality. One is focused on a direct specification and evaluation of the quality of software product, while the other is focused on assuring high quality of the process by which the product is developed. The software industry is currently entering a period of maturity, in which particular informal approaches are specified more precisely and are supported by the appropriate standards. Quality characteristics of software products are defined in ISO/IEC 9126 [1]. For each characteristic, a set of attributes which can be measured is determined. Such a definition...
Words: 3803 - Pages: 16
...Introduction The use of software solutions to support business-critical processes has a decisive influence on the commercial success of the banks. At present, they are faced with the challenge of selecting optimal solutions to fit their particular needs, and implementing them. Information technology is indisputably crucial to the activities of financial service providers. A considerable proportion of funds should be spent on core banking systems, which provide indispensable support for bank-specific business processes. For some years now, banking software has been the source of lively debate. The advanced age of many business-critical systems, as well as their rigidity and complexity, have proven to be a burden to banks. Concern exists that they might no longer be able to meet the demands of today’s market. The triggers of this concern have been software systems that have been in use for a number of years and have been further developed over the course of time; in many instances they have been linked up – as effectively as possible – to bolt-on applications. Many core banking systems have grown up over the years that are lacking in the necessary flexibility, which has been compensated by workarounds. The technical problems that affected RBS Group has caused the banks to rethink their IT strategy. The transformation of the software environment is not merely giving banks the flexibility and agility they need. The use of appropriate applications also constitutes an effective...
Words: 4147 - Pages: 17
...2277-8616 44 IJSTR©2015 www.ijstr.org A Framework For Software Quality Assurance Using Agile Methodology Maria Sagheer, Tehreem Zafar, Mehreen Sirshar Abstract: Agile methodology that uses iterative and incremental approach is widely used in the industry projects as they can satisfy to the change of requirements. Efficient product delivery is achieved by using short iterations. But assuring the quality in any system is essential and imperative part which is very difficult task, which raises a question that: Is quality is assured in the software which is developed using agile methodology? The research paper proposed a solution and summarizes that how the quality is achieved or assure in agile software development using different factors. The major focus of this research paper is to analyse the quality parameter which assure quality in the agile methodology. The research paper includes the brief overview of the parameters which assure quality in agile. ———————————————————— I. INTRODUCTION. For the successful software engineering, the delivery of high quality software is needed. Mainly the customer satisfaction level is considered as the quality attribute which defines high quality of any system. Traditionally waterfall approach is used for the software development in which system is developed by freezing the requirements. To achieve high quality Agile methods rather than waterfall approach for the software development are adapted by many organizations to compete...
Words: 5336 - Pages: 22
...Software Engineering 1.) What does the term requirement mean? Explain the process of determining the requirement for a software system. ‘Requirements’ suggests that there is someone out there doing the ‘requiring’ – a specific customer who knows what she wants. In some projects, requirements are understood to be the list of features (or functions, properties, constraints, etc.) Demanded by the customer. In practice, there is rarely a single customer, but rather a diverse set of people who will be affected in one way or another by the system. These people may have varied and conflicting goals. Their goals may not be explicit, or may be hard to articulate. They may not know what they want or what is possible. Under these circumstances, asking them what they ‘require’ is not likely to be fruitful. 2.) Describe the various steps of requirement engineering? Is it essential to follow these steps? Requirements engineering is an important aspect of any software project, and is a general term used to encompass all the activities related to requirements. The four specific steps in software requirements engineering are: • Requirements elicitation is the practice of obtaining the requirements of a system from users, customers and other stakeholders. • Requirements analysis encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various...
Words: 1772 - Pages: 8
...System Quality Factors and The role that Standards play in the System Development Process [CMGT 555 / Systems Analysis and Development August 1, 2011 Bob Mattus System Quality Factors System quality factors are important to both hardware and software applications. There are several factors that need to be considered when examining hardware and software quality. Functionality, reliability, usability, efficiency, maintainability, efficiency, and portability are among several considerations when examining system quality factors. Reliability and functionality are two system quality factors that can often affect other functions and components of system quality. One of the county governments in Buncombe County, NC, which is not far from where I live realized the importance of functionality when it comes to system quality factors. With a $200 million annual operating budget, Buncombe County’s mission is to provided and effective and efficient government to its citizens while maintaining a responsive workforce and viable economy (Wimmer, 2005). In 2000, Buncombe relied on a aging DOS-based financial system that consisted of multiple and disparate databases which caused the system to be very unfriendly, unreliable and slow. Functionality was a deciding factor in Buncombes decision to move forward to new technology. System functionality can save organizations time and money by creating and quickly allowing advancing upgrades that could be put implemented to improve...
Words: 1105 - Pages: 5
...Proceedings: Pacific Northwest Software Quality Conference, 2006 The Challenge of Productivity Measurement David N. Card Q-Labs, Inc dca@q-labs.com Biography- David N. Card is a fellow of Q-Labs, a subsidiary of Det Norske Veritas. Previous employers include the Software Productivity Consortium, Computer Sciences Corporation, Lockheed Martin, and Litton Bionetics. He spent one year as a Resident Affiliate at the Software Engineering Institute and seven years as a member of the NASA Software Engineering Laboratory research team. Mr. Card is the author of Measuring Software Design Quality (Prentice Hall, 1990), co-author of Practical Software Measurement (Addison Wesley, 2002), and co-editor ISO/IEC Standard 15939: Software Measurement Process (International Organization for Standardization, 2002). Mr. Card also serves as Editor-in-Chief of the Journal of Systems and Software. He is a Senior Member of the American Society for Quality. Abstract - In an era of tight budgets and increased outsourcing, getting a good measure of an organization’s productivity is a persistent management concern. Unfortunately, experience shows that no single productivity measure applies in all situations for all purposes. Instead, organizations must craft productivity measures appropriate to their processes and information needs. This article discusses the key considerations for defining an effective productivity measure. It also explores the relationship between quality and productivity. It...
Words: 4342 - Pages: 18
...Total Quality Management in the Software World Abstract This paper examines total quality management (TQM) against the backdrop of the software world. First an overview of the background and evolution of total quality management will be detailed, then an article will be examined that discusses total quality management on an organizational level, and how it can be beneficial. After that an empirical study is reviewed that discusses the relationship between TQM and software quality. Finally this paper is wrapped up with a look at how TQM development methods should be introduced and the different ways in which is benefits both the employee and customer. Keywords: tqm, total quality management, software total quality management, tqm software methodologies Total Quality Management in the Software World According to Dale, Dewhurst, and Martínez-Lorente (1998), Total quality management is now being applied by a considerable number of companies and the topic itself is now a popular subject of many books and papers. While total quality management began to be used in the mid 1980’s (Dale et. al., 1998) it wasn’t until the late 1980’s it became a part of quality related language and even later still until it was put to use in the world of software and I.T. (information technology). This paper will examine the following total quality management topics: 1. What is the background and history of total quality management? 2. What value does TQM add to software quality? ...
Words: 2125 - Pages: 9
...Organizations. A link to the Virtual Organizations can be found on the Course Materials page. Boardman Management Group manages the Baderman Island resort. They are considering whether to upgrade the word processing software currently in use at the resort or to purchase a new word processing software application. Boardman plans to hire Smith Systems Consulting to help them analyze their options and to prepare an implementation plan. Submit a 3-4 page plan for how Boardman Management Group should utilize Smith Systems Consulting as an outside consultant for this project. Include a discussion of why the specific elements of your plan are important, how they will achieve the results you intend and why they were chosen over alternative methods. Week 3 Individual Assignment Boardman Management Group has decided to upgrade the Microsoft Word, word processing software for Baderman Island Resort. Smith Systems Consulting has provided Boardman with an analysis of the factors that need to be considered in upgrading the software. Using the analysis prepared by your Learning Team during Week Two, submit a Request For Proposal (RFP) that would be sent to software vendors seeking their proposals for the purchase and implementation of the upgraded software application. An RFP template can be found in the Supplements section of the Links Library. Week 4 Individual Assignment Submit a 3-4 page paper that discusses how you will assess the responses you received...
Words: 1699 - Pages: 7
