DEN Student Roles In Detail

Slides:



Advertisements
Similar presentations
Verification and Validation
Advertisements

By Veronika Movagharianpour and Adam Brakel. Software Developers face challenges:  Producing high-quality software  with low-defect levels  while doing.
© Copyright 2010 Hitachi Consulting Hitachi Consulting Hindsite Overview & Demo 1.
CS 3500 SE - 1 Software Engineering: It’s Much More Than Programming! Sources: “Software Engineering: A Practitioner’s Approach - Fourth Edition” Pressman,
Thammanoon Kawinfruangfukul CSSE MS, ID:
Stepan Potiyenko ISS Sr.SW Developer.
1 SWE Introduction to Software Engineering Lecture 3 Introduction to Software Engineering.
University of Southern California Center for Systems and Software Engineering USC CSSE Research Overview Barry Boehm Sue Koolmanojwong Jo Ann Lane Nupul.
2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.
Software Project Planning CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 12, 2002.
SE 555 Software Requirements & Specification Requirements Validation.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
Software Quality Assurance For Software Engineering && Architecture and Design.
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
SQA Architecture Software Quality.
Verification and Validation
“80% of software projects fail”  Standish Report (1995) Standish Report 16.2% completed on-time and on-budget with all features and functions as initially.
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
SQA Architecture Software Quality By: MSMZ.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
N By: Md Rezaul Huda Reza n
Software Quality Assurance Activities
PPMT CE-408T Engr. Faisal ur Rehman CED N-W.F.P UET P.
Teaching material for a course in Software Project Management & Software Engineering – part II.
Software Quality Assurance Lecture #2 By: Faraz Ahmed.
Kick-off Meeting Kick-off Meeting Presented By:.  Project/s overview and Scope  Project Organization Structure  Client Overview  Project Profitability.
Lecture 31 Introduction to System Development Life Cycle - Part 2.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
Note Excerpts from Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R. Schach
Process Improvement. Improving the Test Process In the Software V&V course, Prof. Uwe asked the question: How to improve the Testing Process?
Formal Methods in Software Engineering
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
University of Southern California Center for Systems and Software Engineering 577 process CSCI 577a Software Engineering I Supannika Koolmanojwong Mobasser.
University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE CSCI577B 2010 Light Weight Sw Engg for Off-the-Books.
Test Manager’s Role Best Practice By Gabriel Rodriguez.
University of Southern California Center for Systems and Software Engineering 577a Critique Summary Barry Boehm CSCI 577b January 22, 2010.
Project Management Inspections and Reviews 1 February.
Project Management and Risk Workshop
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
CSCE 240 – Intro to Software Engineering Lecture 2.
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
PI2134 Software Engineering IT Telkom.  Software definition  Characteristic of software  Software myths  Software Engineering definition  Generic.
This chapter is extracted from Sommerville’s slides. Textbook chapter 22 1 Chapter 8 Validation and Verification 1.
Software Engineering 2 Term Project by: Feras Batarseh Nestor Rivera.
DevCOP: A Software Certificate Management System for Eclipse Mark Sherriff and Laurie Williams North Carolina State University ISSRE ’06 November 10, 2006.
Week # 4 Quality Assurance Software Quality Engineering 1.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
Supplier Management Can’t live with them, Can’t live without them!
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Fall 2010 Software Planning Guidelines.
What is a Functional Spec?  Defines what the functionality will be NOT how it will be implemented  Describes features of the software product product's.
Software Quality Assurance
CSC 480 Software Engineering
USC e-Services Software Engineering Projects
Client Introductions to CS577a
The Systems Engineering Context
Software Engineering and Best Practices
USC e-Services Software Engineering Projects
Software What Is Software?
Verification and Validation
ICM_Sw Essentials for CS510
Software Quality Assurance
Quality Management, Peer Review, & Architecture Review Board
Software Verification, Validation, and Acceptance Testing
Comparison between each special case
Architecture Review Boards Remote Student Specifics
HHS Child Welfare National IT Managers' Meeting
Testing and Inspection Present and Future
Presentation transcript:

DEN Student Roles In Detail Supannika Koolmanojwong CS577

Outline Instructional ICSM-Sw Context and More Realities CS577 "System" Engineer CS577 Quality Management overview CS577 Systems Requirements Management Overview CS577 Quality Focal Point The shared IIV&V Role for DEN (remote students) What it is & how it works Principles behind it How it’s distinct from other project participation @USC CSSE

Software Engineering of Large Systems Not enough time to do a "large" system, but Real client Real deliverables Teach and Use "best practices": techniques, tools and ... WinWin; IICSM-Sw (nee MBASE); Risk Driven; COCOMO II OO Analysis and Design Quality Management (QM) Peer Reviews and other QM early assessment techniques Configuration Management (CM) Integrated Independent Verification and Validation (IIV&V) EPG for IICSM-Sw … Projects run & documented like "Medium Systems" projects Evolving: IICSM-Sw, IIV&V, QM, DEN Student responsibilities … @USC CSSE

Quality Dilemma Early Defect Detection is very cost effective You make "Defects" as you do your work, but you don't know what to do until we tell you Most effective way to identify potential defects is a Fagan Inspection; but Don't have time to train you well in the method Fagan's Inspections take time (early in Life Cycle) [which is made up later]; CS577 doesn't have the time Solution IIV&V (PEER review) Simple Role-based Peer Review for critical artifacts @USC CSSE

More Reliabilities CS577a is a four unit course => 12 hours/week Early in semester: more explicit learning, less doing Late in semester: more doing (~ 80% of time), less learning Schedule (not budget for staff) is the independent variable [a client can't offer more $'s for more staff] Milestones are based on a fixed schedule dictated by academic/pedagogical constraints @USC CSSE

IIV&V role – for DEN-remote students ONLY! IIV&V role – project "quality" & DEN learning enhancer Not totally "Independent": More "Integrated" IV&V => IIV&V Originally "independent" meant no direct contact Integrated IV&V permits working closely, but independently IIV&V requires DEMANDING corrections for tacit knowledge Project results can be improved as a result of YOUR efforts You learn by doing and interacting with a real project and real client @USC CSSE