Popkin Software: Software Quality Assurance November 2004 Mariya Shapran
Content Table 1. Popkin Software 1. who we are 2. what we do 2. Our Development Life Cycle 1. 2. 3. 4. what, when, why, who and where. . Quality Assurance vs. Quality Control Quality assurance as part of the product development lifecycle Standards 3. Test Life Cycle 1. 2. 3. 4. 5. SA Metamodel IDEF 0/Black Box/White Box Test Approaches Best practices Test Approaches Merging industry standards into our test methodology 4. Defects Life Cycle 1. Critical path 2. Non-critical path 5. Questions and Answers 2 www. popkin. com
Popkin Software The Enterprise Architecture Company
Popkin Software Overview • The Enterprise Architecture Company • Founded in 1986 • Leading Provider of Enterprise Architecture Tools – Flagship Product is System Architect® • Vision: – We develop, globally market, sell, and support a diverse but integrated set of Enterprise Architecture, Business Analysis, and Systems Design tools. – Our tools enable clients to visualize, analyze, implement, and communicate their Enterprise Architecture. This enables clients to maximize the efficiency of their organization and improve their strategic decision making capabilities. • World Wide Presence: – Corporate Headquarters in New York City – European Headquarters in United Kingdom – Other Major Offices in Washington DC and The Netherlands • Distributors throughout the World 4 www. popkin. com
Company Overview • Products: – System Architect® – Flagship Product – System Architect Do. DAF – i. RMA™ – SA Information Web Publisher™ – SA Compare™ – SA Simulator™ – Training – Consulting • Users: – More than 80, 000 users and 40, 000 licenses at 7, 000 sites worldwide • User groups in the US, UK, and Australia 5 www. popkin. com
Partial List of Clients • • • • IBM Lockheed Martin Publix Paychex Mc. Graw Hill Scholastic CSC JPMorgan. Chase Virgin Mobile Du. Pont Corporation Borders Vodafone JB Hunt Siemens 6 • • • • British Airways Samsung Verizon AT&T Glaxo-Smithkline MCI Worldcom Bell Canada Time Warner Telecom BT Ericsson Nokia T-Mobile Telia Sonera www. popkin. com • Department of Defense • US Air Force • Department of Treasury • Department of Agriculture • Veterans Administration • GSA • Department of Homeland Security • Intelligence Agencies
System Architect
System Architect • Leading Enterprise Architecture Tool on Market • Integrated Support for Modeling Disciplines: – Business Modeling • Latest Standards: BPMN, BPEL 4 WS, etc • Simulation of Process Models – UML for Systems Modeling • Synchronization with code such as Java, VB. NET, C++, etc – Relational Data Modeling • Implement/Reverse Engineer DBMS’s such as Oracle, DB 2, and SQL Server – XML Design – Network Modeling – Communicate Models by Publishing to Websites – Repository based with Networking support 8 www. popkin. com
System Architect V 10 Framework Manager Business Modeling • Enterprise Direction • Processes (BPMN) • Organization • Functions • Technology Infra • IDEF 0/IDEF 3 • Simulation (IDEF 3, Data Modeling UML Analyze Business: SA Guidebooks Design Applications: Structured Methods Design Databases: • Use Cases • Object Interactions • Classes • Components • State Machines • Java • VB. NET Analyze Legacy Systems: • ERD Model • Gane/Sarson • Physical Model • IDEF 1 X • DB Synchronize™ • SQL Server • Oracle 8, 9 i BPMN, Process Charts) • Ward/Mellor • Yourdon/De. Marco • SSADM Shared Definitions XML Design XML Schemas: • DTDs • Biz. Talk • Instance Docs • Test Data • UML Integration • Data Modeling Integration Explorer Diagram SA Compare Repository Microsoft SQL Server Customizable Repository Metamodel Reporting/Publishing SA Info Web Pub XML 9 MS Office HTML Browsing XML SVG Interfaces OLE HTML Automation www. popkin. com CSV Matrices XML HTML MS Office XML
System Architect V 10 Role-Based Access Control Functions Users Encyclopedias NT Authorization Catalog Repository Customizable Repository Metamodel Configuration Management SA Compare 10 Backup Reporting www. popkin. com Merge/Extract
Popkin’s View of Standards IDEF Catalyst BPMN Vendordriven Entity Relationships UML BPEL 4 WS FEA Frameworks 11 www. popkin. com
Enterprise Architecture HTML/Web Automated Reports on Information in Repository Information XSLT Publisher Enterprise view of data 16+ years of enterprise architecture and modeling ICAMS System Architect Multiple Method View of Information Methods E/R Data BPM 12 SA Repository XML UML Frameworks www. popkin. com Industry Standards BPMN XML Schema Entity / Relation UML Frameworks C 4 ISR Do. DAF
Evolution of System Architect First Windows. Based Modeling Tool Introduced ‘ 88 Structured Analysis and Design ‘ 97 ‘ 98 ‘ 99 Objectoriented Multiple Methods 13 C 4 ISR Framework Support TOGAF Support UML Support ‘ 96 Data Modeling Business Process Modeling (IDEF) ‘ 00 ‘ 01 Simulation, XML Support Zachman Framework Support www. popkin. com ’ 02 ‘ 03 SQL Server As Underlying Repository
Product Development Life Cycle Management Team Project Proposal Commercial Release Business Team Business Requirements Acceptance Definition Test Development Team Test Cycle Technical Design & Audit Program Code Unit Test Integration Specification Fix Bugs Test System Deployment Quality Control Team Test Regression Test Build Test Cases Review Test Cases Execute Test Quality Review Cases Performance & Multi-user Test 14 www. popkin. com
Quality Assurance vs. Quality Control • Quality Assurance • Quality Control What’s the difference? 15 www. popkin. com
Quality Assurance: - System Development Methodologies Estimation Processes System Maintenance Processes Requirements Definition Processes Testing Processes and Standards Measurement Programs to evaluate processes Processes gap analysis Concerned with all of the products that will ever will be produced by a process 16 www. popkin. com
Quality Control - Relates and concern with a specific product or service; - Verifies whether specific attributes are in, or are not in a specific product or service; - Identifies defects for the primary purpose of correcting defects; 17 www. popkin. com
Test Life Cycle QA Test Plan Management Team Project Proposal Commercial Release Business Team Business Acceptance Test Requirements Definition Development Team Test Cycle Technical Design & Audit Program Specification Code Unit Test Integration Test Quality Control Team Fix Bugs System Deployment Test Regression Test Build Test Cases Review Test Cases Execute Test Cases Quality Review Performance & Multi-user Test 18 www. popkin. com
Quality Factors Correctness Extend to which a program satisfies its specifications and fulfills the user’s mission objectives Reliability Extend to which a program can be expected to perform its intended function with required precision Efficiency The amount of computing resources and code required by a program to perform a function Integrity Extend to which access to software or data by unauthorized persons can be controlled Usability Effort required to learn, operate, prepare input, and interpret output of a program Maintainability Effort required to locate and fix an error in an operational program Testability Effort required to test a program to ensure that it performs its intended function Flexibility Effort required to modify an operation program Reusability Extend to which program can be used in other applications – related to the packaging and scope of the functions that programs perform Interoperability Effort required to couple one system with another 19 www. popkin. com
The System Architect Metamodel 20 www. popkin. com
IDEF 0 – Integration Definition for Function Modeling 21 www. popkin. com
Black Box Test Approach 22 www. popkin. com
White Box Test Approach 23 www. popkin. com
Test Approach • Black Box Approach – – – – • Boundary Value Analysis (internal code) Regression Testing (Test Partner and Loadgen) Data Integrity Testing (Internal Tools) Stress (Volume) Testing (Loadgen) Backup and Recoverability (Internal Tools) Functional Testing (Test Partner and Manual Testing) Security Testing Configuration/Compatibility Testing (VMWare images) User Acceptance Testing (End Users) Benchmark Testing (Loadgen) Operational Readiness Testing (Loadgen and Test Partner) Usability Testing (End Users/508 Compliance Guidelines) Alpha/Beta Testing (Loadgen) White Box Approach – Memory Usage (Bounce. Checker) – General Resource Usage – Error Handling • Gray Box Approach – Combination of Black Box and White Box Approach 24 www. popkin. com
Boundary Value Analysis Example: Problem: Need to understand what will take place at the boundaries of the behavior for each component. Example: Field Name for the Diagram is required to accept unique name for the diagram consistent of alpha-numeric characters up to 105 characters (with exception for special characters) Boundary Value Analysis: Absence of the name = rejected Special Characters = rejected (this is on the boundary) null = rejected 2 alpha 5 numeric characters = accepted All alpha characters = accepted All numeric characters= accepted 106 characters = rejected 25 www. popkin. com
Best Practices • • • Peer Reviews Defined Requirements Standards Defined Quality Standards Constant improvements to Quality Processes Implementation of Automation Testing into Regression and Performance Test Phases 26 www. popkin. com
Merging Industry Standards into our Test Methodology • 508 Compliance – 508 Compliance Checklist • Methodologies: IDEF 0, IDEF 1, IDEF 3 – IDEF 0/IDEF 1/IDEF 3 Compliance Checklist • IEEE Standards – Used as guideline in defining of Quality Assurance Processes • ISO Standards – Used as guideline in defining of Quality Assurance Processes 27 www. popkin. com
508 Compliance Check List • • • • Menu items have a unique, functioning access key. Shortcut or popup menu items have a unique, functioning access key. Dialog controls have a unique, functioning access key. Dialogs can be closed by pressing the ESC key. Shortcut or popup menus can be opened via the keyboard. Most keyboards have what's called an application key. Pressing this key displays the shortcut menu for the selected object. Drag and drop functionality can also be executed via the keyboard. Dialogs have a logical and consistent tab order (left to right and top to bottom). Color alone should not be used to indicate different states. For example, in access control red and green colored arrows were used to represent checked in and checked out items. The tabs on a tabbed control can be navigated by pressing CTRL+TAB. Tree controls can be navigated by pressing the arrow keys. Interfaces containing multiple windows and/or frames allow for focus to be shifted via the keyboard. Focus is always placed on the most recently opened or accessed window. The application’s active window should display a visual focus indicator at all times so that users can anticipate the effects of their keystrokes. The application can read, use, and preserve system-wide user interface (UI) settings when displaying customized controls or window content. The system-wide settings adopted by a user enhance the product’s accessibility; the application should use them where possible, and not disable or disregard them. An example of a system-wide setting is the Tool. Tip size. The application does not convey information exclusively by sound. If sound is the default method for conveying information, the application should provide other options to express this information. 28 www. popkin. com
IEEE Software Engineering Standards 610. 12. 1990 IEEE Standard Glossary of Software Engineering Terminology 730. 1998 IEEE Standard for Software Quality Assurance Plans 730. 1 – 1995 IEEE Guide for Software Quality Assurance Plans (ANSI) 828 – 1998 IEEE Standard for Software Configuration Management Plans 829 – 1998 IEEE Standard for Software Test Documentation 830 – 1998 IEEE Recommended Practice for Software Requirements Specifications 1008 – 1987 (R 1993) IEEE Standard for Software Unit Testing (ANSI) 1012 – 1998 IEEE Standard for Software Verification and Validation 1012 a - 1998 IEEE Standard for Software Verification and Validation – Supplement to 10121998. Content Map to IEEE 12207. 1 1028 – 1997 IEEE Standard for Software Reviews 1058 – 1998 IEEE Standard for Software Project Management Plans 1058. 1 – 1987 (R 1993) IEEE Standard for Software Project Management Plans (ANSI) 29 www. popkin. com
Defect Life Cycle 30 www. popkin. com
Glossary • Organizations: – ARTS – Retail Tech Standards with Industry Data Model • www. nrf-arts. org – BPMI – Business Process Management Standards body • www. bpmi. org – DAMA – Data Management Association • www. dama. org – DSDM – Dynamic Systems Development Method • www. dsdm. org – NASCIO – National Association of State Chief Information Officers • www. nascio. org – OMG – Object and XMI Tech Standards Body • www. omg. org – Supply Chain Management standards with SCM data model • www. supply-chain. org – Telecoms Tech Standards with Industry Process Mode • www. tmforum. org – The Open Group • www. opengroup. org 31 www. popkin. com
Glossary • FEA – Federal Enterprise Architecture • • • BPMN – • XML Metadata Interchange Do. DAF – • Unified Modeling Language, an object-oriented design language XMI – • Business Process Execution Language for Web Services UML – • Entity Relation BPEL 4 WS – • Object Role Modeling E/R – • Integrated Definition Language, a systems modeling technique using a specific graphical structure ORM – • Business Process Modeling Notation IDEF – • BRM - Business Reference Model SRM - System Component Reference Model PRM - Performance Reference Model DRM - Data Reference Model TRM - Technical Reference Model Department of Defense Architecture Framework C 4 ISR – 32 Command, Control, Communications, Computers, Intel-ligence, Surveillance, and Reconnaissance Architecture Framework www. popkin. com
POPKIN SOFTWARE Popkin Software 2 Rector Street New York, NY 10006 Tel: (646) 346. 8578 Fax: (646) 346. 8501 33 www. popkin. com
Скачать презентацию Popkin Software Software Quality Assurance November 2004 Mariya
7be9eb0d20b1cc758a1160cda01178ac.ppt