1 / 24

Links in the Chain

Richard Conn Microsoft December 2003. Links in the Chain. Why Mature Systems Engineering is Needed. Motivation – Software-Intensive Systems Engineering. People have to work in teams to produce many kinds of products – one person cannot do it alone in most cases!.

presta
Download Presentation

Links in the Chain

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Richard Conn Microsoft December 2003 Links in the Chain Why Mature Systems Engineering is Needed

  2. Motivation – Software-Intensive Systems Engineering People have to work in teams to produce many kinds of products – one person cannot do it alone in most cases! More and more, systems are becoming software intensive, containing millions of lines of code!

  3. The Systems We Build • Business-Critical • Financial • Infrastructure • Mission-Critical • Business-Critical • Domain-Specific • Safety-Critical • Lives are at stake! More and more, failure is NOT an option!

  4. The Systems Engineering Job • Produce quality product • Contain costs • Complete on time actual actual plan plan Budget Schedule

  5. Capability Maturity Optimizing Level Probability Target Time/$/... Managed Level Probability Time/$/... Target Defined Level Probability Time/$/... Repeatable Level Target Probability Time/$/... Initial Level Target Probability Time/$/... Target

  6. DUSD(S&T) responsible forSoftware Intensive Systems - Mar 99 Established: Software Intensive Systems Directorate Software Intensive Systems Steering Group Defense Software Collaborators Software Intensive Systems

  7. SIS Strategy: Policy Collaboration Education and Training Science and Technology SIS activities are focusedon recent Defense Science Board Recommendations. DoD’s Software Intensive Systems Strategy

  8. Stress software process and past performance Institutionalize independent expert program reviews Improve software skills of acquisition and program management Collect, disseminate and employ best practices Restructure contract incentives Strengthen the technology base Defense Science Board Recommendations

  9. Established to provide a single model framework for engineering process improvement Incorporates critical engineering principles by integrating systems and software engineering Oct 99 - Compliance with maturity level 3 required for all DoD contractors Capability Maturity Model Integration (CMMI)

  10. Context • Maturity is about … • People • Following a disciplined process • To create software-intensive products

  11. People are … • Members of a Team • Assigned one or more leadership/management roles • Team Leader • Development Manager • Planning Manager • Quality/Process Manager • Support Manager • Each role has a set of specific responsibilities • These responsibilities vary from process to process • Recurring responsibilities, which are repeated in all processes, also exist

  12. The Process is … • A set of activities for producing a product or set of products • Processes may also contain other processes • Each process has at least – • An entry criteria • A set of activities or processes to follow • A set of products to be consumed • A set of products to be created or modified • An owner (who can change it), a controller (who runs it) • An exit criteria

  13. The Products are … • Software (in the context of Software Engineering) • Code (obviously) • Documents • Data • Hardware • Created by people • Used by people

  14. Real-World ProcessesIn-Class Exercise • Industrial-Strength Software-Intensive Systems Engineering • Academic-Strength Software Engineering • Paper and talk to be published and presented at SIGCSE 2004

  15. Context (Reprise) = optional People following a disciplined process to create software - intensive products

  16. Aircraft Requirements Sources Aero Corporate IEEE 12207 Process Guide SEI SW CMM Assessments • SPP/SDP • CoRE • ADARTs • SPARK • MC/DC Test • Template Based • Training • Metrics Aircraft SW Direction DOD STDS ISO 9001 FAA DO-178B Safety Critical Software Multiple Customers In Multiple Countries Software Products • Safe / Reliable • Low Risk • Maintainable • Modular • Reusable • Cost Effective • Mission-Critical

  17. Perspectives • Department of Defense • Outsourcing • Learning Federation • Microsoft

  18. Department of DefensePerspective • Undersecretary of Defense for Science and Technology Briefing (2001) • Department of Defense • The Road Ahead • DoD Directive 5000.1

  19. OutsourcingPerspective • Building Airplanes in the Sky • Adaptive Organizations • Statistics, Issues

  20. Learning FederationPerspective • What is the Learning Federation? • Roadmaps for the Future

  21. MicrosoftPerspective • Bill Gates – Microsoft Research Faculty Summit 2003

  22. New World Order • Software Engineering is entering universities around the world, becoming a necessary component of an education in computer science and information technology. • Universities such as MIT, Carnegie Mellon University, and Stanford have had software engineering programs • Computing Curriculum 2001 of the Association for Computing Machinery’s Special Interest Group in Computer Science Education contains Software Engineering Knowledge Units • Software Engineering program accreditation by the Accreditation Board for Engineering and Technology (ABET) began in the Fall of 2002 • Systems Engineering is coming! USC (TRW), UMR (Boeing), SPSU (Lockheed), UHCL (NASA) Our society depends on software for its day-to-day existence, and the failure of software systems is increasingly becoming intolerable.

  23. S&T Requires Strong Partnerships Link to the Warfighter Expanded Resource Base New Ideas, Knowledge Interagency Service Labs Universities Maximum NationalSecurity Payoff DARPA Industries International High Risk, High Payoff Coalition Capability Innovation, Transition

More Related