1 / 14

Special Software Development Paradigms Today: HW #5 Next Class: Pressman 17; Demos?

Special Software Development Paradigms Today: HW #5 Next Class: Pressman 17; Demos?. Questions? / Team Status Reports / HW#4 Object-Oriented Paradigm Bio Break ( 5 minutes ) Cleanroom Paradigm. Status Reports – 11/01/01. Key OO Concepts.

kay-jensen
Download Presentation

Special Software Development Paradigms Today: HW #5 Next Class: Pressman 17; Demos?

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. Special Software Development ParadigmsToday: HW #5Next Class: Pressman 17; Demos? • Questions? / Team Status Reports / HW#4 • Object-Oriented Paradigm • Bio Break (5 minutes) • Cleanroom Paradigm

  2. Status Reports – 11/01/01

  3. Key OO Concepts • Data and code are packaged together in a capsule called an object. 2. Information and instructions are passed between objects in the form of messages. 3. Objects of a similar type are grouped together in classes. 4. Objects can inherit characteristics (data and procedures) from other objects in their class.

  4. Advantages of OO • Easy to re-use code • Easy to extend or maintain code • Results in clean, modular designs • Easier to spot design defects • Great for rapid prototyping

  5. Costs / Risks with OO • Time to learn • Time to program useful library of classes • Tough to keep track of al the classes

  6. Golden Rule of OO Select tools that have already defined most of the classes you will want.

  7. IBM’s Checklist for OO • Pilot project identified: new project, flexible schedule • OO programming team members identified • Available OO tools and methodologies researched • OO training complete • Class hierarchies of selected tool appropriate to project needs • Commitment for more design time up front obtained • Project planned to maximize code reuse • Rapid prototyping used to gain immediate feedback • Feedback and continuous improvement process in place

  8. Traditional Waterfall Quality often tested in Unit test, function test, system test Division of labor common Serial development of whole product Test cases to uncover coding errors Cleanroom Quality is designed in No unit test; first test is system test Whole team involvement Incremental development & certification Statistical usage testing Waterfall v. Cleanroom

  9. Source: Secrets of Software Quality, Kaplan, Clark, & Tang pg. 271

  10. Source: Secrets of Software Quality, Kaplan, Clark, & Tang pg. 277

  11. Three Key Cleanroom Concepts • Box structure specification (formal methods), allows… • Boxes encapsulate (aspects of) the system at a given level of abstraction • Black boxes represent external behavior of system • State boxes encapsulate state data and observations • Clear boxes have procedural design for state boxes • Correctness verification. • Certification refers to components that have undergone statistical usage testing.

  12. Advantages of Cleanroom • Zero defects possible • < 6 errors/KLoc v. 30-50 errors/KLoc at first test • Overall about 10X fewer error at first test • Interfaces between increments well-tested • MTTF (up to 20X) higher due to statistical usage testing

  13. Costs / Risks with Cleanroom • Expensive! (10 – 11 days of training) • Time consuming (box spec takes up to 2X as long as regular spec)

  14. IBM’s Checklist for Cleanroom • Purpose of Pilot project clear • Cleanroom literature selected • Pilot project selected • Management commitment and funding obtained • Experts available for consultation • Cleanroom team members identified and educated • Conference room scheduled for daily use • Product requirements understood and prioritized • System environment understood • Cleanroom specification written • Expected customer usage defined • Incremental development plan specified • Test plan specified • Verifiable designs for procedures and objects • Team reviews • Results measured and communicated • Team recognition • Feedback and continuous improvement process in place

More Related