Determining the Suitability of COTS in Mission Critical Systems VT/NVC Feb. 15, 2002 Ronald J. Kohl Chief Systems Engineer Titan Systems Co.

Slides:



Advertisements
Similar presentations
S Y S T E M S E N G I N E E R I N G.
Advertisements

Robert D. Walla, Larry A. Hacker, Ph.D. Astrix Technology Group 1090 King Georges Post Rd Edison, NJ LIMS Selection In A Forensic Toxicology Laboratory.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
CSE 470 : Software Engineering The Software Process.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.
© Prentice Hall CHAPTER 10 Alternative Approach: Purchasing Systems.
Manage Quality
CS540 Software Design Lecture 1 1 Lecture 1: Introduction to Software Design Anita S. Malik Adapted from Budgen (2003) Chapters 1.
COTS Based Systems: Benefits, Potential Risks and Mitigation Techniques Ronald J. Kohl Chair, GEIA IT&I TC Titan Systems Co
1 Independent Verification and Validation Current Status, Challenges, and Research Opportunities Dan McCaugherty IV&V Program Manager Titan Systems Corporation.
1 Certification Chapter 14, Storey. 2 Topics  What is certification?  Various forms of certification  The process of system certification (the planning.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
Costs of Security in a COTS-Based Software System True Program Success TM Costs of Security in a COTS-Based Software System Arlene Minkiewicz, Chief Scientist.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Fundamentals of Information Systems, Second Edition
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Michael S. Zachowski, Robert D. Walla Astrix Technology Group 1090 King Georges Post Rd Edison, NJ A Successful Approach to a LIMS Upgrade In A Public.
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
1 Risks of using COTS in Information Technology Systems Symposium on Risk May 9, 2001 Ronald Kohl Titan Systems Co., AverStar Group
Configuration Management, Logistics, and Universal CM Issues Larry Bauer Boeing Commercial Airplanes NDIA Conference Miami March 4-5, 2005
S/W Project Management
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
CLEANROOM SOFTWARE ENGINEERING.
Dr. Ralph R. Young Director of Software Engineering Systems and Process Engineering Northrop Grumman Information Technology (703)
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Animating and.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Week 2 Seminar: Project Scope Management
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
Note Excerpts from Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R. Schach
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem.
1 FRENCH PROPOSAL FOR ESARR6 1 - BACKGROUND - 15/02/00 : Kick-off meeting, Presentation of the CAA/SRG input (SW01), Request from the chairman to comment.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Formal Methods in Software Engineering
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Chapter 11 Managing Application Development. Agenda Application management framework Application management issues Criteria for development approach Development.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
Definitions of GIS Works with geographic information Performs data input, management, manipulation/analysis, and output functions Composed of hardware,
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Software Requirements Specification Document (SRS)
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Open Source Software in Federal Acquisitons Acquiring Maximum Agility: Beyond Open Standards TCO and Best Value Revisited.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
1 Team Skill 4 Managing the scope Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and Information Technology Based.
Advanced Software Engineering Dr. Cheng
Chapter 11 Project Management.
Project Cost Management
Stacy Kowalczyk WIC Technical Hour 3/30/2005
Chapter 6: Database Project Management
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Milestone A to Milestone B Requirements Management Activities
Introduction to Software Engineering: Second Edition
Chapter 2 SW Process Models
Software Prototyping Animating and demonstrating system requirements.
Relationship between MRLs and AS6500
An Overview of Software Processes
An Overview of Software Processes
Project Management Chapter 11.
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
SOFTWARE DEVELOPMENT PLAN
Presentation transcript:

Determining the Suitability of COTS in Mission Critical Systems VT/NVC Feb. 15, 2002 Ronald J. Kohl Chief Systems Engineer Titan Systems Co.

Contents Definitions Why use COTS Risks with Using COTS What’s all the fuss with Mission Critical? Mitigation approaches Summary

Definitions Commercial Off The Shelf (COTS) Commercially available product acquired in ‘as is’ condition, perhaps with ‘tailoring’ capabilities Other Non-Developed Item (NDI) types MOTS (Modified Off The Shelf) GOTS (Government Off The Shelf) Reuse products shareware Open Source Custom Home grown or home maintained, control of source code and development team

What is ‘Mission Critical’? Everyone has a definition They’re all different, but similar Ron’s Defn: –Those parts of an enterprise or system which are essential to the success of that enterprise or system Could be Hardware, Software, Procedures or People!!!

So what’s different about Mission Critical Systems? Non-critical –meet functional rqmts –meet performance rqmts, often –be available, often –work correctly most of the time –maintainable –ease of recovery Mission Critical –meet all rqmts and nothing more –do so, all the time –be available, all the time –work correctly, always –quality of maintenance –rigorous recovery requirements

Potential Benefits of Using COTS Reduced development cost/schedule Reduced maintenance cost Product ‘improvements’ at no cost “Proven” product Wide user base to identify problems Wide user base to build shelf life Available skill base Industry investment in technology base

CHART 7 COTS Risks Product Volatility product features change when and to what the Vendor chooses No/little insight into product * Unknown product flaws Limited, poor, or no documentation No source code Unknown development processes or skills May not meet program requirements * Product features not as advertised (more or fewer) Product not suited for intended operational use Difficult to find human-life rated products Product lifetime may be less than program life

COTS Risks (con’t) Underestimated total program costs Integration costs, Verification costs and O&M costs Risk to maintenance Unpredictable vendor support and vendor stability Dependency on vendor to identify flaws that are applicable to program Vendor resistant to accepting/fixing externally identified flaws (requires “proof”) High probability of mods or ‘wrappers’ * Interfaces/protocol not standard with industry Unique operational environment Stringent program requirements/needs

Mitigation Techniques Gain Marketplace and vendor knowledge – shop early & often Gain product knowledge prior to baselining requirements - Learn all you can, as early as you can, however you can COTS standards for program Use of redundant vendors Early vendor involvement throughout the life cycle Product and/or Vendor certification *

Mitigation Techniques (con’t) Robust verification plan and environment * Early prototyping, allowing time for design/requirements changes Overall robust system that can withstand the unexpected Source code escrow * Up front systems engineering evaluations Product ‘insight’ requirements * Product simulators/models *

Summary: COTS Evaluation Guidelines Maturity of COTS marketplace in the domain Stable/quality vendors in this marketplace Quality products in this marketplace Similar usage of this COTS in related applications Certifiable for Critical Applications Insights into development products and processes Fidelity of product simulations/models Product Change/Maintenance Plans Quality of and alternatives for product support

Some additional heuristics Prioritize requirements Recognize the basement requirements from the roof requirements Recognize system elements that may be ‘volatile’, make final decisions as late as possible Establish acceptance criteria, early! Employ effective analytical methods

Some ‘open problems’ Complete description of the COTS-based systems development and operational life- cycle model Effective cost estimation algorithms More objective eval/selection criteria and methods Verification/validation methods