100525003 軟工一 吳彥諄. * Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A.

Slides:



Advertisements
Similar presentations
Requirements Specification and Management
Advertisements

System Integration Verification and Validation
Software Testing 3 Damian Gordon.
Software Testing #IRL Agenda Why Software Testing Software Testing Principles – Exhaustive testing is impossible – Early Testing.
Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.
Analysis Concepts and Principles
1 Quality Assurance in Construction and Maintenance (Section 13.4 of Maintenance Text; Chapter 20 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman.
CS 325: Software Engineering March 26, 2015 Software Quality Assurance Software Metrics Defect Injection Software Quality Lifecycle Measuring Progress.
Non-Functional Requirements
Project Documentation and its use in Testing JTALKS.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
Introduction to Software Testing
Non-functional requirements
Software Quality SEII-Lecture 15
Software Project Management Fifth Edition
Requirements Elicitation. Requirement: a feature or constraint that the system must satisfy Requirements Elicitation: specification of the system that.
COURSE TITLE: 1 Software Quality Assurance. Course Aims Introduction to software quality assurance. Software testing terminology. Role and responsibility.
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
ConfidentialPA Testing Mobile Applications A Model for Mobile Testing.
THE ROLE OF PROCESS IN SOFTWARE QUALITY By K.KARTHIKEYAN.
S oftware Q uality A ssurance Part One Reviews and Inspections.
Sept - Dec w1d11 Beyond Accuracy: What Data Quality Means to Data Consumers CMPT 455/826 - Week 1, Day 1 (based on R.Y. Wang & D.M. Strong)
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
Based on D. Galin, and R. Patton.  According to D. Galin  Software quality assurance is:  A systematic, planned set of actions necessary to provide.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory 1 Overview of Requirements Engineering Section One Version:
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
Copyright © Jerzy R. Nawrocki ISO 9126 and Non-functional Requirements Requirements.
Software Quality Assurance SE Software Quality Assurance What is “quality”?
Requirements Engineering ments_analysis.
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
12.1 Introduction Checklists are used as a technique to give status information in a formalized manner about all aspects of the test process. This chapter.
Software Methods Mö/ slide 1 Methods and Techniques of Software Quality Management ICEL Quality Management Systems: Methods and Techniques of Software.
About Quality Pre paired By: Muhammad Azhar. Scope What is Quality Quality Attributes Conclusion on software Quality Quality Concepts Quality Costs.
Code Complete Steve McConnell. 20. The Software-Quality Landscape.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
Modelling Support for Quality of Service Eclipse ECESIS Project Modelling Support for Quality of Service Department for Cooperative and Trusted Systems.
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
Software Testing for Intelligent Robots Justin Peckner Maria Velasquez November 13, 2012.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
UKTMF 27 th January 2010 Non-Functional Testing1 Non-Functional Testing Non-Functional Testing Why is this so often done badly or not done at all? Can.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
CSE 303 – Software Design and Architecture
Requirements Engineering ments_analysis.
EMI INFSO-RI Software Quality Assurance in EMI Maria Alandes Pradillo (CERN) SA2.2 Task Leader.
Requirements Engineering
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Non Functional Testing. Contents Introduction – Security Testing Why Security Test ? Security Testing Basic Concepts Security requirements - Top 5 Non-Functional.
 System Requirement Specification and System Planning.
Lecture 15 Attribute Driven Design Again Topics ATAM – team expertise and experience needed Chapter 24 Next Time: June 22, 2016 CSCE 742 Software Architecture.
Lecture 15 Attribute Driven Design Again Topics ATAM – team expertise and experience needed Chapter 24 Next Time: June 22, 2016 CSCE 742 Software Architecture.
ISQB Software Testing Section Meeting 10 Dec 2012.
Chapter 2 Object-Oriented Paradigm Overview
Lecture 12 Attribute Driven Design Again
Software Quality Control and Quality Assurance: Introduction
Non-functional requirements as Gordian knot
Security SIG in MTS 05th November 2013 DEG/MTS RISK-BASED SECURITY TESTING Fraunhofer FOKUS.
Quality Exercise 2 Instructions
Quality Exercise 2 Instructions
مقدمه اي بر مهندسي نيازمنديها
UNIT II.
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Charakteristiky kvality
and Jose-Norberto Mazón University of Alicante
Software Quality Assurance Lecture 3
ISO/IEC Systems and software Quality Requirements and Evaluation
Tomaž Špeh SURS TF SERV, Luxembourg,
Presentation transcript:

軟工一 吳彥諄

* Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A

* Backlog focus on implementing functional backlogs in the Scrum. * A software project must be redesigned or it fails. * Caused by non-satisfaction of functional feature. * Caused by non-satisfaction of non-functional requirements called “Quality Attribute”

External and internal quality PortabilityMaintainability usability efficiency functionality reliability Adaptability installability co-Existence replaceability Portability compliance Analysability Change ability Stability Testability Maintainability compliance Understandabili ty Learnability Operability Attractiveness Usability compliance Time behavior Resource utilisation Efficiency compliance Suitability Accuracy Interoperability Security Functionality compliance Maturity Fault tolerance Recoverability Reliability compliance ISO 9126 Model for Quality Attribute

* ACRUM was designed based on the development process of the existing SCRUM * ACRUM Practice * AQUA Practice (Analysis of Quality Attributes) * RAM Practice (Requirement Association Matrix) * VAQ Practice (VAlidation of Quality attribute)

Phase 0: Preparation Introduction AQUA process Introduces the AQUA process to all project staff. Explains the rules that all the members must follow. Explains the objective of AQUA. Phase 1: Initial Analysis Present Business Driver Understand the core business driver. Customer must prepare an RFP or business context data. Gathering of Quality Attribute Members have to elicit the related quality attributes

Phase 2: Complete Analysis Elicit Quality Attribute Elicit the quality attribute individually. Refinement of Quality Attribute Check the duplicate items. Remove or modify the duplicate items. Writing Quality Attribute Scenarios Written down in detail using the scenario to reflect properly the quality attributes in the software architecture. Ex. “Data storing or backup operation should be complete within 3 seconds in a general environment.”

* RAM is the activity that maintains traceability through mapping between the functional requirements and the quality attributes.

* Three validation points in VAQ practice. * Whether or not there are functional backlog items that were mapped with the quality attribute is validated. * The achievement or non-achievement of the quality attribut. * The quality attribute will progress using the working software program. * If the quality attribute is not satisfied, function should be implemented again or a new strategy must be formulated to achieve the quality attribute.

Checking RAM table validation Checking Achievement or not validation Checking working program validation Produce new approach Checking Validation Field [Yes] [No]

* Project X and Y are commercial project of Samsung Electronics those develop defense code to protect errors of NAND Flash Device.

* Agile development methods are being recognized as popular and efficient approaches to development of software systems * ACRUM is embedded AQUA, RAM, and VAQ practice into SCRUM to achieve quality attributes in a system. * Architectural approach was suggested in the analysis phase. * architectural approaches were applied in the design phase, the software quality would have been improved

Q&A