University of Southern California Center for Software Engineering CSE USC Distributed Assessment of Risk Tool DART Jesal Bhuta

Slides:

Advertisements

Similar presentations

Planning Iterative Software Development Projects Raj Agrawal, PMP Unisys.

Advertisements

University of Southern California Center for Systems and Software Engineering Risk Calculation Case Studies CS 510 Software Engineering Supannika Koolmanojwong.

University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.

University of Southern California Center for Software Engineering C S E USC 02/16/05©USC-CSE1 LiGuo Huang Computer Science Department.

University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Ricardo Valerdi USC Center for Systems and Software.

Stepan Potiyenko ISS Sr.SW Developer.

Rational Unified Process

3/14/2006USC-CSE1 Ye Yang, Barry Boehm Center for Software Engineering University of Southern California COCOTS Risk Analyzer and Process Usage Annual.

University of Southern California Center for Software Engineering CSE USC 477 Class Project – HazMat (Hazardous materials) Spring 2003 Feb. 4.

University of Southern California Center for Software Engineering CSE USC MBASE Essentials Planning and control Milestone content Process models Life cycle.

OTS Integration Analysis using iStudio Jesal Bhuta, USC-CSE March 14, 2006.

University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.

University of Southern California Center for Software Engineering CSE USC 12/6/01©USC-CSE CeBASE: Opportunities to Collaborate Barry Boehm, USC-CSE Annual.

Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.

University of Southern California Center for Software Engineering CSE USC ©USC-CSE 10/23/01 1 COSYSMO Portion The COCOMO II Suite of Software Cost Estimation.

2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.

SERC Security Systems Engineering Initiative Dr. Clifford Neuman, Director USC Center for Computer Systems Security Information Sciences Institute University.

Process Synchronization Workshop Summary Report Jo Ann Lane University of Southern California Center for Software Engineering.

1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.

University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy

Business Data Communications & Networking

University of Southern California Center for Software Engineering CSE USC ©USC-CSE 3/11/2002 Empirical Methods for Benchmarking High Dependability The.

USC CSSE Top 10 Risk Items: People’s Choice Awards Barry Boehm, Jesal Bhuta USC Center for Systems & Software Engineering

University of Southern California Center for Software Engineering C S E USC Agile and Plan-Driven Methods Barry Boehm, USC USC-CSE Affiliates’ Workshop.

Job roles in I.T. By Jamie colclough. Software engineer Also known as application programmer, software architect, system programmer, system engineer.

University of Southern California Center for Software Engineering CSE USC Sep. 24, 2009 v01 ©USC-CSE CS 577a Software Engineering I Peer Review.

Software Project Management

Architecture Evaluation Evaluation Factors Evaluation by the designer Every time the designer makes a key design decision or completes a design milestone,

Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.

© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.

1 SAIV/CAIV/SCQAIV LiGuo Huang USC University of Southern California Center for Software Engineering CSE USC.

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE11 USC e-Services Software Engineering Projects.

Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA

University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.

CS 577b Software Engineering II -- Introduction

© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.

University of Southern California Center for Systems and Software Engineering 7/13/2012(c) USC-CSSE11 USC e-Services Software Engineering Projects.

University of Southern California Center for Systems and Software Engineering 10/25/2010(C) USC CSSE1 CS 577a Overall FCR Feedback [Updated/More]

March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.

Product Lifecycle Management PLM Program. Is based on the business strategy achieve product lifecycle goals and objectives with maximum return and minimal.

University of Southern California Center for Software Engineering CSE USC A Case for Anchor Point Milestones and Feasibility Rationales April 2005 Barry.

PRJ566 Project Planning & Management Software Architecture.

CSE 303 – Software Design and Architecture

University of Southern California Center for Software Engineering CSE USC SCRover Increment 3 and JPL’s DDP Tool USC-CSE Annual Research Review March 16,

Week 1 -Introduction IT2005 System Analysis & Design.

University of Southern California Center for Systems and Software Engineering COTS Selection Sergio Romulo Salazar April 28, 2010.

University of Southern California Center for Systems and Software Engineering 7/23/2010(c) USC-CSSE1 08/21/09 ©USC-CSSE1 USC e-Services Software.

University of Southern California Center for Systems and Software Engineering Aug. 26, 2010 © USC-CSE Page 1 A Winsor Brown CS 577a Lecture Fall.

University of Southern California Center for Systems and Software Engineering July 2008ICM & CP Workshop (c) USC CSSE1 Update to Initial CP Survey Results.

The ATAM method. The ATAM method (1/2) Architecture Tradeoff Analysis Method Requirements for complex software systems Modifiability Performance Security.

Documenting Software Architectures. Outline  Introduction  Uses of Architectural Documentation  Views  Choosing the Relevant Views  Documenting a.

University of Southern California Center for Systems and Software Engineering ICSM Stage II: Phases and Continuing Project Example Anandi Hira CS 510,

University of Southern California Center for Systems and Software Engineering RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong.

CS 577b: Software Engineering II

Chapter 24: Architecture Competence

Fundamentals of Information Systems, Sixth Edition

SNS College of Engineering Coimbatore

Lecture 17 ATAM Team Expertise

Project Management Process Overview

Risk Management Workshop

Distributed Assessment of Risk Tool DART

Introduction to Constructive COTS (COCOTS) Model and Tool

CS 577b Software Engineering II -- Introduction

IT2005 System Analysis & Design

CSE 498, Collaborative Design

MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS

Engine Part ID Part 1.

Engine Part ID Part 2.

Engine Part ID Part 2.

Presentation transcript:

University of Southern California Center for Software Engineering CSE USC Distributed Assessment of Risk Tool DART Jesal Bhuta

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE2 Outline Introduction to DART DART Demonstration

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE3 Outline Introduction to DART DART Demonstration

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE4 Risk Assessment Role in Each Life-Cycle Phase Evaluate Alternatives W.R.T Objectives ID Potential High-Risk Areas No Alternatives Satisfy Objectives Major Satisfaction Uncertainty Analyze Risk Items (DART - partially) Prioritize Risk Items (DART) Risk Management Plan (RMP) Objectives Cost Schedule Function Operation Support Reuse Alternatives Physical Architecture Logical Architecture COTS Software Reused Software Special Software Risk ID Checklist, Techniques Models, Analysis Aids Revised Objectives Subset of Alternatives Prioritized Risk Items

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE5 Need for DART – Spatial Distribution Developers - SAL IV&V - Downtown LA Project Manager - Home Architect - Leavy Client – Health Science Campus Tester – OHE 122 Risk assessment meeting

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE6 Need for Dart – Spatial and Temporal Distribution Client Testers Hardware Vendors Developers Architects Software Contractor

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE7 Need for DART Spatially and Temporally distributed stakeholders –Difficult for the stakeholders to get together to assess risks frequently Need a tool to maintain, and help prioritize risks periodically

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE8 DART Process

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE9 Dart Snapshot

University of Southern California Center for Software Engineering CSE USC 9/7/2005©USC-CSE10 Outline Introduction to DART DART Demonstration