UMD MSWE 609 - Evolving a Process for Inspecting OO Designs (13 pages)

Previewing pages 1, 2, 3, 4 of 13 page document View the full content.
View Full Document

Evolving a Process for Inspecting OO Designs



Previewing pages 1, 2, 3, 4 of actual document.

View the full content.
View Full Document
View Full Document

Evolving a Process for Inspecting OO Designs

11 views


Pages:
13
School:
University of Maryland, College Park
Course:
Mswe 609 - A Quantitative Approach to Engineering Software
A Quantitative Approach to Engineering Software Documents

Unformatted text preview:

Detecting Defects in Object Oriented Designs Using Reading Techniques to Increase Software Quality Current Research Team Prof Victor R Basili Forrest Shull Ph D Guilherme H Travassos D Sc 1 Jeffrey Carver Graduate Research Assistant basili travassos carver cs umd edu fshull fc md umd edu This work is partially supported by UMIACS and by NSF grant CCR9706151 1 On leave from the Federal University of Rio de Janeiro COPPE Computer Science and System Engineering Department partially supported by CAPES Brazil UFRJ COPPE Department of Computer Science Experimental Software Engineering Group Fraunhofer Center Maryland Evolving a Process for Inspecting OO Designs Outline y Reading Techniques x Families of Reading Techniques y Reading Techniques for OO Design x First Experiment at UMCP Lessons Learned from the Initial Study y The Road Ahead x Observational Studies Lessons Learned from the Observational Studies y Open Questions DCS ESEG OO Reading Techniques UFRJ COPPE 1 Reading Techniques Why read Software practitioners are taught how to write but typically not how to read software documents Many software processes assume that practitioners know how to effectively find the information they need i e how to read such documents e g inspection process read a document to find defects UFRJ COPPE OO Reading Techniques DCS ESEG Reading Techniques Domain Knowledge General Requirements Other Domain incorrect fact For what to deal with complete Software omission consistent Artifacts unambiguous and inconsistency correct documents across the software process Software Artifacts ambiguity Requirements Documents Use cases Scenarios descriptions Design Diagrams Source Code Increasing Quality Quality DCS ESEG extraneous OO Reading Techniques UFRJ COPPE 2 Reading Techniques Why read looking for defects Defect Omission Incorrect Fact Inconsistency Ambiguity Extraneous Information General Description Necessary information about the system has been omitted from the software artifact Some



View Full Document

Access the best Study Guides, Lecture Notes and Practice Exams

Loading Unlocking...
Login

Join to view Evolving a Process for Inspecting OO Designs and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Evolving a Process for Inspecting OO Designs and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?