1 / 6

Lesson 4: Selecting an OO CASE Tool

Lesson 4: Selecting an OO CASE Tool. Software Engineering II. Objectives. Understand the role of a tool or an environment (e.g., CASE tool) Learn how to choose the right tool for specific need Understand the tool selection process Learn the important factors for selecting CASE tools

steel-rivas
Download Presentation

Lesson 4: Selecting an OO CASE Tool

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. Lesson 4: Selecting an OO CASE Tool Software Engineering II

  2. Objectives • Understand the role of a tool or an environment (e.g., CASE tool) • Learn how to choose the right tool for specific need • Understand the tool selection process • Learn the important factors for selecting CASE tools • Learn how to evaluate tools • Explore lessons learned and Experiences

  3. CHOOSE RIGHT TOOL FOR SPECIFIC NEED

  4. CRITERIA FOR EVALUATING AND APPLYING OO TOOLS • Utility • Consistency checks between diagrams • Integrated data repository • Leveled abstractions of diagrams • Integration between diagrams and code (2-way) • Method specific rules enforced • Bidirectional diagram dependency automation • Decomposition of objects (nodes) • Decomposition of arcs • Automated documentation generation (templates) • Reverse engineering of diagrams from code • Read-only version available for customers • Extensibility • Interface to rules (individual enable, insert new) • Interface to repository • Flexibility • Simultaneous network access • Interface with desktop publishing • Usability • User interface design • Documentation • User support (Help line) • Tool performance (speed) • Completeness • Requirements Analysis support • Preliminary Design support • Detailed Design support • Coding support • Testing support

  5. Project Weight Legend 5 Critical, customer/method requirement 4 Consistently saves manual effort 3 Sometimes saves manual effort 2 May save effort someday 1 Nice to have, but not important 0 Not helpful EXAMPLE TOOL EVALUATION MATRIX Tool Performance Legend 5 Complete, automated implementation 4 Partially addressed, useful implementation 3 Partially addressed, clumsy implementation 2 Addressed only through workarounds 1 Manual effort required 0 Unaddressed

  6. SUMMARY • Instituting an OO method requires a culture change • Your method selection will impact virtually all of your management processes • A single method is insufficient for all applications • There are many published OO methods • Select methods before tools • CASE tools automate the method

More Related