A Framework for Software Quality Assurance Using Agile Methodology

In: Computers and Technology

Submitted By maria051
Words 5336
Pages 22
INTERNATIONAL JOURNAL OF SCIENTIFIC & TECHNOLOGY RESEARCH VOLUME 4, ISSUE 02, FEBRUARY 2015 ISSN 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 in the volatile market where the customer requirements are changing at the internet speed, changing organizational infrastructure and need for the short time deliverables. Agile methods that are most popular in use are:
Extreme Programming (XP), Scrum, Feature Driven
Development and…...

Similar Documents

Software Quality Assurance

...Introduction………………………………………………………..…..1-2 1.1 Software Quality…………………………………………..……..2 1.2 Software Quality Assurance……………………………..……….2 1.3 Software Testing………………………………………..………2-3 2. Software Quality Assurance Tools………………………………..…….3-7 3. Selected QA Tools…………………………………………………………8 3.1 Selenium IDE…………………………………………………..9-14 3.2 FabaSoft………………………………………………………15-19 4. Future and Conclusion……………………………………………………20   1. Introduction Software Quality Assurance (SQA) Tools play a major role in common software user community and in the field of software development. SQA tools are the specially developed software tools for the purpose of assisting in the QA processes. 1.1 Software Quality The quality of software is assessed by a number of variables. These variables can be divided into external and internal quality criteria. External quality is what the user experiences when running the software in its operational mode. Internal quality refers to the aspects that are code-dependent, and are not visible to the end-user. External quality is critical to the user, while internal quality is meaningful to the developer only. When the quality comes to software quality conformance, requirement consider as software functional quality and fitness for use named as software structural quality. 1.2 Software Quality Assurance Software quality assurance (SQA) consists of a means of monitoring the software engineering process and methods used to ensure quality. The methods by......

Words: 2186 - Pages: 9

A Software Quality Assurance and Management System

...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......

Words: 1104 - Pages: 5

Improving the Management of Cost and Scope in Software Projects Using Agile Practices

...5, No 1, February 2013 IMPROVING THE MANAGEMENT OF COST AND SCOPE IN SOFTWARE PROJECTS USING AGILE PRACTICES Mariana de Azevedo Santos1, Paulo Henrique de Souza Bermejo2, Marcelo Silva de Oliveira3, Adriano Olímpio Tonelli2, Enio Júnior Seidel4 1 2 3 Mitah Technologies, Lavras, Minas Gerais, Brazil mariana@bsi.ufla.br Department of Computer Science – Universidade Federal de Lavras (UFLA) bermejo@dcc.ufla.br, tonelli@dcc.ufla.br marcelo.oliveira@dex.ufla.br 4 Department of Mathematical Sciences – Universidade Federal de Lavras (UFLA) Universidade Federal do Pampa (UNIPAMPA) ejrseidel@hotmail.com ABSTRACT While organizations want to develop software products with reduced cost and flexible scope, stories about the applicability of agile practices to improve project development and performance in the software industry are scarce and focused on specific methodologies such as Scrum and XP. Given these facts, this paper aims to investigate, through practitioners' perceptions of value, which agile practices are being used to improve two performance criteria for software projects—cost and scope. Using a multivariate statistical technique known as Exploratory Factor Analysis (EFA), the results suggest that the use of agile practices can be represented in factors which describe different applications in software development process to improve cost and scope. Also, we conclude that some agile practices should be used together in order to get better efficiency on......

Words: 3283 - Pages: 14

Agile vs. Scrum Methodology

...Agile vs. Scrum Methodology Everyone involve in software engineering is driven by cost, schedule, and time by market. Customer wants software of yesterday and at the same time they want at high quality but at the cheaper price. The demand for faster delivery has been become more demand especially during the internet era and little likely hood and little more relax attitude toward budget and time to market will occur anytime soon at the same time change affect for software engineering requirement emerged development work is conducted as consequence that software team must react to new functions and features that impose by stakeholders and within the team itself. Modern software engineering is driven by the need to be agile. Works need to execute in the agile manner, communication must be conduct in the agile fashion, and change must be conduct in an easy way. Agile is a technique that delivery technologies or IT solutions. It focuses on changing business needs and technologies. In February 2001, a group of software developers got together to create what so called “Agile Manifesto” that declared and agreed among other things. * Highest priority is to satisfy customers through early and continue provides them with valuable software. * Changing in requirement during software development is welcome. * Business people and developers must work together daily in order to complete a project. * Face to face conversation is the most efficient and......

Words: 1382 - Pages: 6

Software Quality Assurance and Testing Methodologies

...CSC 415 / Software Engineering Date of Submission: September 20, 2013 Software Quality Assurance and Testing Techniques Subject: This memo delves into unit testing, integration testing, and other aspects of software quality assurance. Software quality assurance is essential for any business that provides products that are to be used by others. This memo serves as a documentation of software testing methodologies that support a recommendation for GF Software Solutions approach to SQA. Addressed are various components of the software development lifecycle and the different techniques that exist for their implementation. Unit tests focus on the verification of the smallest unit of software design, or the software module. Integration testing can be performed using a number of different methods including top-down, bottom-up, and big bang integration. Integration tests address problems or bugs that may occur when interfacing individual software components and building the complete system architecture. System tests are applied when the software is incorporated with other systems elements such as hardware, people, or information. Stress testing is a method of determining the stability of an application when tested beyond the bounds of normal operation. Each of the aforementioned steps is crucial to the software quality assurance procedure and is defined more thoroughly in the following sections. A critical component of software quality......

Words: 1958 - Pages: 8

Agile Methodology

...Case Study:- Agile Methodology is one of the best practices which is brought into consideration with respect to the practical purpose as well as in terms of theoretical bases. One of the benefits which is observed while adapting agile methodologies in the companies is that software development process takes place quickly, meeting customer needs is fulfilled, and keeping pace with the rapidly changing requirements can be done easily. However, agile practices and Scrum in particular have been mainly tested in mid- to large-size projects. One of the case studies adopting agile practices in a small-scale, time-intensive web development project at a college-level IT competition is discussed. IT-Competition:- Case study focuses on a project in the Web Application Development category at a college-level Competition. A team of 3-5 students were given an assignment of developing a community-based code review web site to work on within a two-week time period. Implementing Effective Scrum Practices:- a) Daily Scrum:-Daily Scrum was used for the purpose of effective communication. The team adopted means of communications such as Skype, or video conferencing or any other means of communication so that they could discuss their work done, any new ideas that needed to be implemented and also the outstanding task that needed to be done. The team daily used to have communication among their team members and used to discuss their work. b) Backlogs:-The Scrum method uses two types of......

Words: 665 - Pages: 3

Quality Assurance in It

...Quality Systems in IT Assignment Implementing Quality Assurance in IT Systems Name: Elise Xuereb Group: 1HND6 Table of Contents Question 1 (P1.1) 2 ISO 9000:2005: ‘Quality Management Systems - Fundamentals and Vocabulary’ 2 ISO 9001:2008: Quality Management Systems - Requirements 3 ISO 19011:2011: Guidelines for auditing management systems 3 Question 7 (D2.1) Take responsibility for managing and organizing quality assurance activities. For 2 quality assurance practices in each stage identified above, you need to do a plan of implementing it. You need to discuss at least 3 people involved and the work operations that need to be done. Criteria: • Correctly write a plan of action for 2 quality assurance practices including 3 people involved and work operations involved. Plan of Action: System Initiation People involved: Project Manager, System Analyst and Quality Assurance Tester. Work that needs to be done and a plan of how it needs to be implemented: 1. Developing a Quality Assurance (QA) Plan: As indicated in Question 6, this step should be implemented by, initially having an exploration phase. In this phase, the client comes up with the procedures that ensures that quality assurance is present in the project. For instance, when having a robust and secure system, the performance of the system should be constant so that no system downtime will take place. Here, one must take into consideration whether the stakeholders have experience......

Words: 6690 - Pages: 27

Quality Assurance

...Quality assurance Contents ISO 9000……………..…………………………………………………………………………4 Gemba Kaizen………….………………………………………………………………………….7 References………………………….………………………………………………….................12 According to scenario, Susan Douglas is the vice president of quality at Flyrock tires. She was not sure how to communicate the quality standards of Six Sigma to the people of her organization. Flyrock had five manufacturing plants in the United States, and had another 20 facilities for other components used in the tire. Though Flyrock has always emphasized on quality issues, it has had a bigger concern over quality in the recent times, because of the recent fatal accidents involving tires made by other manufacturers due to tread separation. There was significant media coverage over the incidents and the manufacturers had a lot of pressure in improving quality. Douglas wanted to push through a quality control management program in order to improve the quality at Flyrock. For that she needed to build a solid case first (Article). There was a major quality issue at Flyrock. It had very little or no monitoring during the processes for quality control. “Given the large number of steps in building a tire, errors tended to accumulate. As a result, even if each step produced only 1 percent defects, at the end of 20 steps only 81.2 percent of the product would be of good quality. Since each factory produced about 10,000 tires per hour, such a process would result in about 1,880 defects...

Words: 2427 - Pages: 10

Software Quality Assurance

...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......

Words: 999 - Pages: 4

Software Quality Assurance

...applications, developers currently write test cases in frameworks such as Selenium. On the other hand, most web test generation techniques rely on a crawler to explore the dynamic states of the application. The first approach requires much manual effort, but benefits from the domain knowledge of the developer writing the test cases. The second one is automated and systematic, but lacks the domain knowledge required to be as effective. We believe combining the two can be advantageous. In this paper, we propose to (1) mine the human knowledge present in the form of input values, event sequences, and assertions, in the human-written test suites, (2) combine that inferred knowledge with the power of automated crawling, and (3) extend the test suite for uncovered/unchecked portions of the web application under test. Our approach is implemented in a tool called Testilizer. An evaluation of our approach indicates that Testilizer (1) outperforms a random test generator, and (2) on average, can generate test suites with improvements of up to 150% in fault detection rate and up to 30% in code coverage, compared to the original test suite. these interactions at runtime is manifested through the Document Object Model (DOM) and presented to the end-user in the browser. To avoid dealing with all these complex interactions separately, many developers treat the web application as a black-box and test it via its manifested DOM, using testing frameworks such as Selenium [6]. These DOMbased test......

Words: 10932 - Pages: 44

Software Quality Assurance

...italic type, within parentheses, following the example. Some components, such as multi-leveled equations, graphics, and tables are not prescribed, although the various table text styles are provided. The formatter will need to create these components, incorporating the applicable criteria that follow. Ease of Use 1 Selecting a Template (Heading 2) First, confirm that you have the correct template for your paper size. This template has been tailored for output on the A4 paper size. If you are using US letter-sized paper, please close this file and download the file “MSW_USltr_format”. 2 Maintaining the Integrity of the Specifications The template is used to format your paper and style the text. All margins, column widths, line spaces, and text fonts are prescribed; please do not alter them. You may note peculiarities. For example, the head margin in this template measures proportionately more than is customary. This measurement and others are deliberate, using specifications that anticipate your paper as one part of the entire proceedings, and not as an independent document. Please do not revise any of the current designations. Prepare Your Paper Before Styling Before you begin to format your paper, first write and save the content as a separate text file. Keep your text and graphic files separate until after the text has been formatted and styled. Do not use hard tabs, and limit use of hard returns to only one return at the end of a......

Words: 2394 - Pages: 10

Agile Methodology

...procedures on how to operate it and solutions for the problem encountered on it. For programmers, they understand it as the codes and interfaces of the software they’re doing. As an IS student, documenting everything on our future software is essential and it is a must. We must make sure that we always have clear precise documentation of every single important process, and action that takes place. This will also allow us to have a strong reference point whenever anything is in question. “Real programmers don't comment their code, if it was hard to write, it should be hard to understand and harder to modify.” Programmers don’t just stay on what they have learned, they continuous educating themselves by exploring innovative ideas and modify systems to a better ones. Statement from the owner of a small industrial control software company: "We do not want our (end-user) documentation to be too clear. We make a lot of money doing training." For me, this attitude gives the software industry a bad name. A lot companies does this kind of wrong methodologies these day. They took advantage on end-users by making complicated end-user documentation and make the end-users who doesn’t really understand the documentation drop a call on the help centers and ask for a technical assistance. Or sometimes, they do trainings on how to use the software. And all of it has certain amount of charges. In short, they earn a lot of money in a wrong and corrupt way....

Words: 306 - Pages: 2

Agile Methodology

...to Agile methodology in Tata Steel ------------------------------------------------- ------------------------------------------------- Agile software development Agile software development is a group of software development methods in which solutions evolve through collaboration between self-organizing,[1] cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.[2] The Manifesto for Agile Software Development,[3] also known as the Agile Manifesto, was first proclaimed in 2001, The Agile Manifesto[edit] In February 2001, 17 software developers (see below) met at the Snowbird resort in Utah to discuss lightweight development methods. Individuals and interactions over Processes and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan Agile principles[edit] The Agile Manifesto is based on 12 principles:[14] 1. Customer satisfaction by early and continuous delivery of useful software 2. Welcome changing requirements, even late in development 3. Working software is delivered frequently (weeks rather than months) 4. Close, daily cooperation between business people and developers 5. Projects are built around motivated individuals, who should be trusted 6. Face-to-face conversation is the best form of communication (co-location) 7. Working software is......

Words: 419 - Pages: 2

Quality Assurance

...Chapter 8 Quality Assurance and Quality Control 8 QUALITY ASSURANCE AND QUALITY CONTROL IPCC Good Practice Guidance and Uncertainty Management in National Greenhouse Gas Inventories 8.1 Quality Assurance and Quality Control Chapter 8 CO-CHAIRS, EDITORS AND EXPERTS Co-Chairs of the Expert Meeting on Cross-sectoral Methodologies f or Uncertainty Estimation and Inventory Quality Taka Hiraishi (Japan) and Buruhani Nyenzi (Tanzania) REVIEW EDITORS Carlos M Lòpez Cabrera (Cuba) and Leo A Meyer (Netherlands) Expert Group: Quality Assurance and Quality Control (QA/QC) CO-CHAIRS Kay Abel (Australia) and Michael Gillenwater (USA) AUTHOR OF BACKGROUND PAPER Joe Mangino (USA) CONTRIBUTORS Sal Emmanuel (IPCC-NGGIP/TSU), Jean-Pierre Fontelle (France), Michael Gytarsky (Russia), Art Jaques (Canada), Magezi-Akiiki (Uganda), and Joe Mangino (USA) 8.2 IPCC Good Practice Guidance and Uncertainty Management in National Greenhouse Gas Inventories Chapter 8 Quality Assurance and Quality Control Contents 8 QUALITY ASSURANCE AND QUALITY CONTROL 8.1 INTRODUCTION.................................................................................................................................8.4 8.2 PRACTICAL CONSIDERATIONS IN DEVELOPING QA/QC SYSTEMS ......................................8.5 8.3 ELEMENTS OF A QA/QC SYSTEM .................................................................................................. 8.6 8.4 INVENTORY AGENCY...

Words: 9065 - Pages: 37

Quality Methodology

...For the past twenty years many quality improvement methodologies have been used, including international standardization 9000, Zero Effect, Six Sigma, Lean, Total Quality Management, Work-Out, Balanced Scorecard, Baldridge, Business Process Re-engineering, and Plan-Do-Check-Act. Team Orange initially discussed using Total Quality Management, also called TQM, as a methodology for success as it involves customers and stakeholders as well as requesting input from all employees as a means to constantly improve quality. However, given the fast pace of this project, TQM ultimately was rejected because it lacks structure and a means to measure outcomes (Antony, 2009). Six Sigma was discussed nest, and eventually selected this methodology for its project, based on the consensus that Six Sigma will support assurance to stakeholders concerning the quality of implementing a Cloud based infrastructure including the associated software as a service and content delivery network into the NewwDeal information technology portfolio. Six Sigma tools and practices will also support the timely delivery of the project, create value for its stakeholders, and promote continuous improvement (Antony, 2009). The rationale for the decision is further described in the paragraphs below. According to Fehlmann (2004): Applying Six Sigma to software development makes software projects transparent to both management and customers. Transparency requires an important cultural change. As a......

Words: 929 - Pages: 4