Copyright © 2007 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Software Quality Assurance Plan
Unit 2. Software Lifecycle
Public March 4, 2013 Head SDLC & ITIL Development and Consulting Peer M. Künstler The Journey to Agile WM IT and UBS Switzerland IT.
More CMM Part Two : Details.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Alternate Software Development Methodologies
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
CS 325: Software Engineering April 7, 2015 Software Configuration Management Task Scheduling & Prioritization Reporting Project Progress Configuration.
Copyright © 2003 Software Quality Research Laboratory Software Production Essentials Seeing Past the Buzz Words.
Stepan Potiyenko ISS Sr.SW Developer.
Source Control in MATLAB A tool for tracking changes in software development projects. Stuart Nelis & Rachel Sheldon.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 2 Software Processes.
Experimental Facilities DivisionORNL - SNS June 22, 2004 SNS Update – Team Building Steve Miller June 22, 2004 DANSE Meeting at Caltech.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
Slide 1 Sterling Software Peter Sharer Sterling Software.
Software Configuration Management
CSSE 375 Software Construction and Evolution: Configuration Management
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Effective Methods for Software and Systems Integration
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Framework for Automated Builds Natalia Ratnikova CHEP’03.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Standard WBS Version 1.0 WBS2-3.pptPage 1 Standard Work Breakdown Structure Legend = Decomposes to lower level WBS elements 4.0 Implementation 4.0 Implementation.
CLEANROOM SOFTWARE ENGINEERING.
N By: Md Rezaul Huda Reza n
Software Configuration Management
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Dr. Ralph R. Young Director of Software Engineering Systems and Process Engineering Northrop Grumman Information Technology (703)
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Software System Engineering: A tutorial
EMI INFSO-RI EMI SA2 Report Quality Assurance Alberto Aimar (CERN) SA2 WP Leader.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
1 Configuration Management “The Cookbook Approach”
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Medium Size Software, Inc. SQA Plan: The Batch Processing Application.
1 Lecture 19 Configuration Management Software Engineering.
ETICS2 All Hands Meeting VEGA GmbH INFSOM-RI Uwe Mueller-Wilm Palermo, Oct ETICS Service Management Framework Business Objectives and “Best.
Lecture 1 Introduction to Software Engineering
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Creator: ACSession No: 16 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 (Software Quality) Configuration Management CSE300 Advanced.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Software Quality Assurance
Georgia Institute of Technology CS 4320 Fall 2003.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
1 COMPUTER SCIENCE DEPARTMENT COLORADO STATE UNIVERSITY 1/9/2008 SAXS Software.
OHT 15.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Templates The contribution of templates to software quality The organizational.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Engineering Lecture 8: Quality Assurance.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
Worldwide Print Tracking System (WPTS) Merge to Interplan 2.0 Abhisek Rath July 24, 2014.
Configuration Control (Aliases: change control, change management )
Configuration Management
Supporting quality devices
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Software Life Cycle “What happens in the ‘life’ of software”
Configuration Management
Joseph JaJa, Mike Smorul, and Sangchul Song
CS 325: Software Engineering
Quality management standards
Automated Testing and Integration with CI Tool
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering I
Presentation transcript:

Copyright © 2007 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee Department of Computer Science

Copyright © 2007 Software Quality Research Laboratory DANSE Software Quality Challenges New, large, distributed development team Wide range of software engineering experience Expectations comparable to industrial product line Reliable, intuitive operation for novice users Straightforward extensibility for power users Long term maintenance by SNS

Copyright © 2007 Software Quality Research Laboratory Software Process Objectives Produce reliable software for community use Implement functionality tailored to user needs and expectations Maximize resource commitment to scientific innovation and productivity Minimize resources required for rework and maintenance

Copyright © 2007 Software Quality Research Laboratory SQA Tasks Software Quality Engineering SNS Interface Requirements SNS Integration Plan Software Testing Plan

Copyright © 2007 Software Quality Research Laboratory Software Quality Engineering Software Engineering Process Definition DANSE Software Quality Assurance Guidelines DANSE SQA Quick Reference Software Engineering Workshops Tailored to subgroups Applying preferred methods to current tasks

Copyright © 2007 Software Quality Research Laboratory Process Summary Rigorous code specification derived from informal requirements Architecture Behavior Certification Independent Work Product Review Quantitative Testing Configuration management Centralized build/release control Comprehensive change tracking

Copyright © 2007 Software Quality Research Laboratory DANSE Development Process

Copyright © 2007 Software Quality Research Laboratory Primary Work Products

Copyright © 2007 Software Quality Research Laboratory Essential Process Elements

Copyright © 2007 Software Quality Research Laboratory Tool Support for Configuration and Change Management Subversion Source code and document version control Tag, branch, and merge support Handles binary files gracefully Trac Bug, issue, and milestone tracking Built-in Wiki Integrates with Subversion Automatic audit trail

Copyright © 2007 Software Quality Research Laboratory Software Engineering Workshops Objectives Demonstrate Software Engineering Best Practices Establish Uniformity of Practice Across Project 4 Workshops at Subgroup Sites Hands-on Application of DANSE Process Application to Current DANSE Tasks Key Benefits Establish an Engineering Approach to S/W Development Accelerated Staff Learning Curve and Acceptance Provided Early Focus and Momentum for Some Tasks

Copyright © 2007 Software Quality Research Laboratory SNS Interface/Integration Focus Data Reduction Archived Data Access DANSE Application Integration

Copyright © 2007 Software Quality Research Laboratory DANSE & SNS Data Reduction Current View

Copyright © 2007 Software Quality Research Laboratory DANSE & SNS Data Reduction Proposed Integration Strategy

Copyright © 2007 Software Quality Research Laboratory Year 2 Objectives Software Development Process Workshop follow-up Improve behavior specifications Improve peer review effectiveness Establish application testing practices Formalize release management

Copyright © 2007 Software Quality Research Laboratory Year 2 Objectives DANSE/SNS Interface/Integration Finalize Data Reduction Interface Define/document Data Archive Access Initial Application Integration Planning

Copyright © 2007 Software Quality Research Laboratory Overall SQA Perspective “Product” Innovation → Innovative Process Process Evolving to Fit DANSE Domain Compliance Improving with Understanding Key Quality Control Points SNS Interface Release Management Final Process an Important By-Product