Software Engineering CASEComputer Aided Software Engineering Tools Section

Software Engineering CASE(Computer Aided Software Engineering) Tools (Section II – Unit 7)

Will discuss on… • • What is CASE Tools? Concepts on CASE Tools Building Block of CASE Functioned Integrated CASE Environment Prepared By: Ashwin G. Raiyani

Learning Objective At the end of this chapter, students should be able to – – Explain the purpose of CASE tool. Explain the CASE building blocks. Explain the taxonomy of CASE tools. Explain what is I-CASE Prepared By: Ashwin G. Raiyani

What is CASE? • CASE tools helps software engineering in every activity associated with the software process • CASE tools are programs that automate or support one or more phases in a SW development life cycle. • Using CASE allows designers, code writers, testers, planners, and managers to share a common view of where a project stands at each stage of development Prepared By: Ashwin G. Raiyani

What is CASE? ( Continue. . ) 3 Primary characteristics • A collection of useful tools that will help in every step of building a product, • An organized layout that enables tools to be found quickly and used efficiently • A skilled worker who understands how to use the tools in an effective manner Prepared By: Ashwin G. Raiyani

Purpose of CASE tools • increase the speed of SW development activities • increase the SW productivity • improve the quality of the SW developed Prepared By: Ashwin G. Raiyani

CASE building block Prepared By: Ashwin G. Raiyani

• portability services = as a bridge between CASE tools + integration framework + environment architecture • integration framework = collection of specialized programs that enables individual CASE tools to : ü communicate with one another ü create a project data base ü exhibit the same look and feel to the SW engineer • integrated tools help project team develop, organize and control work products Prepared By: Ashwin G. Raiyani

CASE building blocks…cont. • Integration options are shown below : ·Used to assist in a particular SE activity (ex : analysis modeling) ·Does not directly communicate with other tools ·Not part of I-CASE environment Individual tool (point solution) 9

Integration options…Cont Data exchange ·Facilities for data exchange ·Produce output in standard format that compatible with other tools ·Or form a bridge between tools Tool bridges & partnerships 10

Integration options…cont Single source integration ·When a single CASE tools vendor integrates a number of different tools ·Sells as a package ·Addition of tools from other vendors is not easy

Integration options…Cont ·Each building blocks have been created ·Use IPSE standards to build tools that’ll be compatible with IPSE Integrated Project Support Environment 12

Taxonomy of CASE tools • CASE tools do not have to be part of an integrated environment to be useful to SW engineers but the impact on product quality will be greater if they are [pressman] • CASE tools can be classified by function, role, use in SE process, environment architecture, etc. 13

A Taxonomy of CASE Tools business systems planning project management support CASE Database analysis and design programming integration &testing prototyping/simulation tools re–engineering framework 14

Integrated CASE (I-CASE) environments • Integration = combination and closure • Combines a variety of different tools and a spectrum of information enables closure of communication among tools, between people and across the SW process • Tools are integrated SE information is available to each tool that needs it • Usage is integrated common look and feel is provided for all tools • Development philosophy is integrated standards SE approach 15

Benefits of I-CASE Smooth transfer of information from one tool to another and one SE step to the next Improve staff coordination Reduction in the effort required to perform umbrella activities Increase in project control

Challenges of I-CASE • Consistent representations of SE information • Standardized interfaces between tools • Homogeneous mechanism for communication between SW engineer and each tool • An effective approach that will enable I-CASE to move among various HW platforms and OS. 17

Integration Architecture User interface layer Interface tool kit Presentation protocol Tools mgt services CASE tool Tools layer Object mgt layer Integration services Configuration mgt services Shared repository layer CASE database Access control functions Architectural model for the integration framework[pressman] 18

CASE repository • REPOSITORY = a centralized database that contains all diagrams, forms & report definitions, data structure, data definitions, process flows & logic, and definitions of other organizational and system components • It provides a set of mechanisms and data structures that achieve data/tool and data/data integration 19

Thank You Prepared By: Ashwin G. Raiyani