1 / 16

BY ANKITHA CHOWDARY GARAPATI

CASE FOR SOFTWARE. PROCESS AUTOMATION. BY ANKITHA CHOWDARY GARAPATI. WHAT IS CASE ?. Computer Aided Software Engineering is a technique to help with one or more phases of the software development cycle which involves analysis, design, implementation and maintenance of software .

shering
Download Presentation

BY ANKITHA CHOWDARY GARAPATI

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. CASE FOR SOFTWARE PROCESS AUTOMATION BY ANKITHA CHOWDARY GARAPATI

  2. WHAT IS CASE ? • Computer Aided Software Engineering is a technique to help with one or more phases of the software development cycle which involves analysis, design, implementation and maintenance of software . • CASE provides the engineer with the ability to automate the manual activities

  3. CASE Tools Integration Framework Portability Services Operating System Hardware Environment Architecture CASE BUILDING BLOCKS

  4. TAXONOMY OF CASE • Tools that are interactive in nature [CASE tools] and those that are not [Development tools]. • Tools that support activities early in the life cycle of a soft ware project [front-end CASE tools] and those that are used later in the life cycle [back-end CASE tools]. • Tools that are specific to a particular life-cycle step or domain [vertical CASE tools] and those that are common across a number of life-cycle steps or domains [horizontal CASE tools].

  5. Classification by function • Their role as instruments for managers or technical people • Their use in various steps of the software development process • The environment architecture i.e. hardware and software that supports the CASE tools • Origin • Cost

  6. Information Engineering Tools • Process Modeling And Management Tools • Project Planning Tools • Risk Analysis Tools: • Project Management Tools

  7. Requirements Tracing Tools • Metrics And Management Tools • Documentation Tools • Quality Assurance Tools • Database Management Tools • Software Configuration Management Tools

  8. Analysis and Design tools • PRO/SIM tools • Interface Design and development Tools • Programming Tools • Integration and Testing tools • Reengineering Tools

  9. CASE ENVIRONMENT • A CASE environment is a collection of CASE tools and other components together with an integration approach that supports most or all of the interactions that occur among the environment components, and between the users of the environment and the environment itself. • The CASE tools provide an environment that will help automate the software process.

  10. I-CASE INTEGRATED ENVIRONMENT • Benefits can be derived from individual CASE tools that address specific software engineering activities, but the real power of CASE can be achieved only through integration. • Integration demands standardized interfaces between tools, consistent representation of information, homogeneous mechanism for communication, and an effective approach to enable the I-CASE to move along various hardware platforms and operating systems.

  11. Foundation blocks Portability services Integration Framework CASE Tools ELEMENTS OF I-CASE

  12. Architectural Model for the integration Framework USER INTERFACE LAYER Interface Toolkit and Presentation Protocol Tools Management Services CASE TOOL TOOLS LAYER OBJECT MANAGEMENT LAYER Integration and configuration management services SHARED REPOSITORY LAYER CASE Database and access control functions

  13. The integrated CASE environment ( I-CASE) enables • Smooth transfer of information from one tool to another and from one software engineering step to the next. • Allow direct access to any tool contained in the environment. • A change to one item of information to be tracked to other related information items.

  14. Collect both management and technical metrics to improve the process and the product. • Reduction in the effort required to perform umbrella activities • Increase in project control through better planning, monitoring and communication. • Improved coordination and support effective communication.

  15. CASE REPOSITORY Two types of mechanisms have been used in CASE software to store design information: • A dictionary, which contains names and descriptions of data items, processes, etc. • A repository, which contains this dictionary information and a complete coded representation of plans, models and designs, with tools for cross-checking, correlation analysis and validation.

  16. Role of Repository in I-CASE The repository is the heart of CASE system It performs the following functions : • Data integrity • Information Sharing • Data-Tool Integration • Data-Date Integration • Document standardization

More Related