Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "100525003 軟工一 吳彥諄. * Scrum overview * What happened to the software * What is the quality attribute * ACRUM * Q&A."— Presentation transcript:

1 100525003 軟工一 吳彥諄

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

3

4 * 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”

5 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

6

7 * 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)

8 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

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

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

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

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

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

14 * 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

15 Q&A


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

Similar presentations


Ads by Google