Costing Secure Systems Workshop Report

Slides:



Advertisements
Similar presentations
Cost as a Business Driver 1 John Brown C Eng MIEE mr_ Software Cost Estimation.
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
BAM! Business Analysis Methodologies. Change-driven or Plan-driven?
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Printed by CONIPMO (Constructive Infrastructure Protection Model): ACCURATELY ESTIMATING HOW MUCH IT WILL COST TO SET UP NETWORK.
W5HH Principle As applied to Software Projects
FAA Information Technology- Information Systems Security R&D Workshop June 2015© USC-CSE Extending COCOMO II to Estimate the Cost of Developing.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
COSYSMO: Constructive Systems Engineering Cost Model Ricardo Valerdi USC CSE Workshop October 25, 2001.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5.
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.
May 11, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #5 Tuesday, May 11, 2004.
10/25/2005USC-CSE1 Ye Yang, Barry Boehm USC-CSE COCOTS Risk Analyzer COCOMO II Forum, Oct. 25 th, 2005 Betsy Clark Software Metrics, Inc.
Ch8: Management of Software Engineering. 1 Management of software engineering  Traditional engineering practice is to define a project around the product.
Welcome and Overview: COCOMO / SCM #20 Forum and Workshops Barry Boehm, USC-CSE October 25, 2005.
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.
Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
Expert COSYSMO Update Raymond Madachy USC-CSSE Annual Research Review March 17, 2009.
COCOMO II Database Brad Clark Center for Software Engineering Annual Research Review March 11, 2002.
April 13, 2004CS WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 – 7 pm Instructor: Diane Kramer.
University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
University of Southern California Center for Software Engineering CSE USC 10/8/00©USC-CSE1 Expediting Technology Transfer via Affiliate Programs and Focused.
N A managed approach to planning and controlling the implementation of complex application software. n A flexible tool kit, designed to support the Project.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Introduction to Software Development 1. Outline The code-compile-debug process for writing a program The software development process 2.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Background Management Council (MC) was briefed on approach in early Feb 2003 and approved it Agreed that every Service Group (SG) will participate in.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
University of Southern California Center for Systems and Software Engineering Vu Nguyen, Barry Boehm USC-CSSE ARR, May 1, 2014 COCOMO II Cost Driver Trends.
University of Southern California Center for Systems and Software Engineering COCOMO Suite Toolset Ray Madachy, NPS Winsor Brown, USC.
SFWR ENG 3KO4 Slide 1 Management of Software Engineering Chapter 8: Fundamentals of Software Engineering C. Ghezzi, M. Jazayeri, D. Mandrioli.
Intro. to Software Engineering 1CSCI 3333 Data Structures.
Overview of COCOMO Reporter:Hui Zhang
The B uff. The Buffs Outline 1. Summary of last presentation 2. Current iteration and Progress 3. Plan for next iteration.
PDS4 Project Report PDS MC F2F University of Maryland Dan Crichton March 27,
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
1 Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5 LiGuo Huang Computer Science and Engineering Southern Methodist University.
A LOOK AT AMENDMENTS TO ISO/IEC (1999) Presented at NCSLI Conference Washington DC August 11, 2005 by Roxanne Robinson.
TK2023 Object-Oriented Software Engineering
Sample Fit-Gap Kick-off
Appendix B Agile Methodologies
Lecture 3 Prescriptive Process Models
COCOMO III Workshop Summary
Testing Process Roman Yagodka ISS Test Leader.
USC e-Services Software Engineering Projects
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Enterprise Algorithm Change Process
USC e-Services Software Engineering Projects
2006 Annual Research Review & Executive Forum
COCOMO II Security Extension Workshop Report
SLOC and Size Reporting
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
COSYSMO: Constructive Systems Engineering Cost Model
Costing Secure Systems Workshop
Core Capability Drive-Through Workshop
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6
Multi-Build Software Cost Estimation Using COINCOMO
Working Group Meeting Report
University of Southern California Center for Software Engineering
Appendix B Agile Methodologies
COSYSMO: Constructive Systems Engineering Cost Model
Center for Software and Systems Engineering,
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Software Development In Agile
Presentation transcript:

Costing Secure Systems Workshop Report Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Costing Secure Systems Workshop Report Edward Colbert Danni Wu {ecolbert, danwu}@cse.usc.edu 21st International Forum on COCOMO & Software Cost Modeling © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

In Case You Aren’t Sure That Security Is Important © 2002-6 USC-CSE 19 November 2018

Workshop Participants Ed Colbert, USC, Moderator (ecolbert@usc.edur) Danni Wu, Scribe (danwu@usc.edu) Don Reifer, Reifer Inc. (dreifer@earthlink.net) Martha Leonette (Martha.J.Leonettee@FAA.org) Anca-Jiliana Stoica (anca@dsv.su.se) Rita Creel (rc@sei.usc.edu) Ron Owens (Ronal.L.Owens@aero.org) Barry Boehm (boehm@usc.edu) © 2002-6 USC-CSE 19 November 2018

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Goal Of Workshop Review Research Draft model for early costing of system security Extensions to COCOMO II for development of secure software systems (“COSECMO”) Gather expert opinion Invite Data MetaH provides semantics & supporting tools UML provides graphic front-end © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Workshop Agenda Introduction Review Early Estimation Model Review COCOMO Security Extension ("COSECMO") Delphi © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Outline Project Schedule Early Estimation Model COCOMO Security Extension ("COSECMO") To Do © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Cost Model for System Security Increment 1 (Feb – July ’04) Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Cost Model for System Security Increment 1 (Feb – July ’04) Task Element Activities 1. Develop Early Estimation Model Prototype model 2. Sources of Cost Identify, define, scope sources of cost Relate sources of cost to FAA WBS Recommend type of CER for each 3. Secure Product Taxonomy Identify, define, scope product elements 4. COCOMO II Security Extensions Refine model form and data definitions 5. COCOTS Security Extensions Explore security aspects in COCOTS data collection © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Cost Model for System Security Increment 2 (Aug ’04 – Mar ’06) Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Cost Model for System Security Increment 2 (Aug ’04 – Mar ’06) Task Element Activities 1. Develop Early Estimation Model Experimental use & refinement 2. Sources of Cost Prioritize sources of cost needing CER’s Refine, prototype, experiment with top-priority CER’s Relate to scope of COCOMO II security extensions 3. Secure Product Taxonomy Experimental use, feedback, and refinement 4. COCOMO II Security Extensions Refine, scope, form, definitions based on results of Tasks 1-3 Experimentally apply to pilot projects, obtain usage feedback 5. COCOTS Security Extensions Develop initial scope, form, definitions based on results of Tasks 1-4 © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Cost Model for System Security Increment 3 (Mar ’06 – Feb ’07) Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 We are in middle of inc. Cost Model for System Security Increment 3 (Mar ’06 – Feb ’07) Task Element Activities 1. Develop Early Estimation Model Evolution; integration with other models 2. Sources of Cost Refine sources of cost, CER’s based on usage feedback Integrate with other models Address lower-priority CER’s as appropriate 3. Secure Product Taxonomy Monitor evolution 4. COCOMO II Security Extensions Baseline model definitions Collect project data Develop initially calibrated model; experiment and refine © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Cost Model for System Security Increment 4 (Apr ’07 – Mar ’08) Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Cost Model for System Security Increment 4 (Apr ’07 – Mar ’08) Task Element Activities 1. Develop Early Estimation Model Evolution Integration with other models 2. Sources of Cost Refine sources of cost, CER’s based on usage feedback Integrate with other models 3. Secure Product Taxonomy Monitor evolution 4. COCOMO II Security Extensions Collect project data Develop initially calibrated model Experiment & refine © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Outline Project Schedule Early Estimation Model COCOMO Security Extension (“COSECMO") Data Mining To Do © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Formula for Cost of System & Security Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Formula for Cost of System & Security Ctotal = CInitial/Mission Analysis + CInvestment Analysis + CSystem Engineering + CDev & Imp + CSys of Sys Integration + CInstall/Deployment + CO&M + CDisposal CDev & Imp = CDesign & Build HW + CDesign & Build SW + CPurchased Services + CCOTS-Sys + CEnv-Mods-design + CBus-Proc-Re-engineering Ctotal (Security) = Ctotal (with security) – Ctotal (without security) COTSYS  Commercial of the Shelf Systems O&M  operation & maintenance Env-Mods-Design  Design of Modifications to environment that needs to be implemented during installation/deployment (e.g. add steal-re-enforced cement barriers) Bus-Process Re-engineering  Re-engineering/Design of business processes that needs to be implemented during installation/deployment, operation & maintenance, or disposal C = Cost © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 5th Prototype Tool Screenshot#4 Advance Estimate — Cost Item by Parametric Models © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Outline Project Schedule Early Estimation Model COCOMO Security Extension (“COSECMO") Data Mining To Do © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Effect Of Security On COCOMO II Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Effect Of Security On COCOMO II Source lines of code (SLOC’s) increased Implementation of Security Functional Requirements (SFR’s) Effort to produce code increased by Security Assurance Requirements (SAR’s) A few Security Functional Requirements (SFR’S) Effort for “outer phases” of life–cycle (e.g. Inception, Transition) increased by Additional documents Additional activities e.g. definition of security roles, certification © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Effect Of Security Functional Requirements On SLOC’s & Computed Effort (cont.) Computation of total effort PMtotal = PMTSF + PMapplication + PMCertification/Validation/Accreditation TSF often developed at higher level of security © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

New Security Driver (SECU) (cont.) Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 New Security Driver (SECU) (cont.) 6 COCOMO levels ≈ 7 CC EAL’s (or equivalent activity) Treating EAL 1 as Nominal & EAL 2 as Nominal+50 (or High-50 ) Tailoring/Modification/Addition of SAR’s handled by increasing/decreasing base level Rating Level Estimated Scale Value Rating Scale (Refer to Supplement for details) Nominal (NOM) 0.00 No security requirements of added protection High (HI) 1.0 Informal security requirements, methodically tested and checked Very High (VH) 1.5 Methodically designed, tested and checked Extra High (XH) 2.0 Semi-formally designed and tested Super High (XXH) 5.0 Semi-formally verified designed and tested Ultra High (XXXH) 10.0 Formally verified designed and tested © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 COSECMO Estimation Trends Effort for Different Size Projects at Assurance Levels Plot of projects where only SECU & effort increasing drivers Efforts seem a little low based on values from Orange Book projects © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 COSECMO Estimation Trends Effort by Assurance Levels for Different Size Projects Plot of projects where only SECU & effort increasing drivers Efforts seem a little low based on values from Orange Book projects © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Barry’s Advice Follow KISS principle Keep It Simple, Stupid Or as Einstein said “Keep it as simple as possible, but no simpler” © 2002-6 USC-CSE 19 November 2018

Proposed Changes to COSECMO Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Proposed Changes to COSECMO Reviewing decision to make SECU driver a scale factor Calibration issues Reduce model complexity by Eliminating guide for other drivers & Re-integrate effect into SECU Discuss with customer simple ways to estimate Certification, Validation, Accreditation Eliminate “Validation” Define as percent of development cost? © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Outline Project Schedule Early Estimation Model COCOMO Security Extension (“COSECMO") Data Mining To Do © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 To Do Refine costing prototypes Get more feedback from security community Refine models Refine Delphi Collect & analyze data We need data! Write papers & Ph.D. thesis (theses?) © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE

Next Costing Secure Systems Workshop Costing Secure Systems Update, USC-CSE 20th Annual COCOMO/SCF Forum 11/19/2018 Next Costing Secure Systems Workshop Date: 14 February 2007 Time: 8AM –5PM Location: USC’s CSSE Part of CSSE’s Annual Research Review & Executive Forum See csse.usc.edu & click on Events Cost: Workshop is free © 2002-6 USC-CSE 19 November 2018 © 2002-6 USC-CSE