Scribd Logo
Upload

Welcome to Scribd!

  • 43 views

    Case Tools

    Uploaded by

    Navneet Kaur Gill
    CASE tools were introduced in the 1970s to speed up the software development process through automation. CASE tools assist programmers throughout the software development lifecycle by automating tasks like project management, documentation generation, and testing. They can be categorized as vertical tools that support individual lifecycle phases, horizontal tools that support information transfer between phases, and integrated CASE tools that support the entire lifecycle. While CASE tools improved productivity and quality, their benefits were only realized for large projects due to high costs and learning curves.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd

    Case Tools

    Uploaded by

    Navneet Kaur Gill
    43 views21 pages
    CASE tools were introduced in the 1970s to speed up the software development process through automation. CASE tools assist programmers throughout the software development lifecycle by automating tasks like project management, documentation generation, and testing. They can be categorized as vertical tools that support individual lifecycle phases, horizontal tools that support information transfer between phases, and integrated CASE tools that support the entire lifecycle. While CASE tools improved productivity and quality, their benefits were only realized for large projects due to high costs and learning curves.

    Original Title

    se

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    CASE tools were introduced in the 1970s to speed up the software development process through automation. CASE tools assist programmers throughout the software development lifecycle by automating tasks like project management, documentation generation, and testing. They can be categorized as vertical tools that support individual lifecycle phases, horizontal tools that support information transfer between phases, and integrated CASE tools that support the entire lifecycle. While CASE tools improved productivity and quality, their benefits were only realized for large projects due to high costs and learning curves.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    43 views21 pages

    Case Tools

    Uploaded by

    Navneet Kaur Gill
    CASE tools were introduced in the 1970s to speed up the software development process through automation. CASE tools assist programmers throughout the software development lifecycle by automating tasks like project management, documentation generation, and testing. They can be categorized as vertical tools that support individual lifecycle phases, horizontal tools that support information transfer between phases, and integrated CASE tools that support the entire lifecycle. While CASE tools improved productivity and quality, their benefits were only realized for large projects due to high costs and learning curves.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    of 21

    CASE TOOLS

    To speed up the software system building process ,a new concept of


    designing software is introduced in the 1970s,called Computer
    Aided Software Engineering(CASE).This term CASE is also
    known as Computer Assisted Systems Engineering and Computer
    Automated Systems Engineering.
    Computer-assisted software engineering (CASE) tools are a set
    of programs and aids that assist analysts, software engineers,
    and programmers during all phases of the system development
    life cycle

    CASE tools are software programs that are designed to assist


    human programmers with the complexity of the processes and
    the artifacts of software engineering .They automate project
    management activities ,manage all work product produced
    throughout the process ,and assist engineers in their analysis,
    design , coding, and test work.
    HISTORICAL EVOLUTION OF CASE TOOLS
    Pre-1969:S/w development was out of control, because of operating
    systems development.
    1969-1971:Advantages of Top- down design , modularity were
    recognized, Pascal was introduced.
    1972-1973:Awareness of SDLC grows.
    1974-1975:Rise to systematic testing procedures, models of fault
    tolerance and total system reliability appeared.
    1976-1977:Requirement ,specification ,and design tools were
    developed.
    1978-1980:Increased use of automated s/w development tools.
    1980-1989:CASE and s/w engineering workstations increased in
    number. Automated tools began to appear.
    1990-present:Combinations of software engineering workstation, and
    automated techniques for software development gain widespread use
    in the software engineering industry.
    error checking and test case generators were included to
    validate software design.

    graphic tools integrated with data dictionary


    databases

    Early graphics packages were soon replaced by specialists


    packages which enabled editing, updating and printing
    multiple versions of a design.

    CASE tools allowed diagrams to be easily


    created and modified, improving the quality
    of software designs.

    introduction of graphical techniques and structured data


    flow diagrams.

    simple word processor


    Benefits of CASE Tools
    •Improved Productivity
    -provide automation & reduce the time consume

    •Better Documentation
    -documentation produced along the way

    •Reduced Lifetime Maintenance


    -system quality improves so net effort & maintenance cost reduce

    •Improved Accuracy
    -ongoing debugging & error checking for early defect removal

    •Opportunity to Non-programmers

    •Intangible Benefits
    -can be used to allow for greater user participation-lead to better
    acceptance of the new system.
    Limitations of CASE Tools
    •Cost
    -very costly
    -benefits of CASE tools are justifiable only in development of large
    systems
    •Learning Curve
    - programmer productivity may fall in initial phase of
    implementation ,because users need time to learn new technology
    •Tool mix
    - appropriate selection of tool mix to get cost advantage
    Phases in Development
    Vertical Tools

    Horizontal Tools

    Horizontal vs. Vertical Tools in the Software Development Process

    Classification of CASE Tools


    •Vertical CASE Tools
    •Horizontal CASE Tools
    Vertical tools
    -Provide support for certain activities within a single phase of the
    software lifecycle.
    -Two subcategories
    -First category
    •set of tools that are used within one phase of a lifecycle.
    •s/w such as compilers ,debuggers , and code analysis tools
    ,support the development phase of a lifecycle.
    •Imp so that development in each phase can be quick as possible.
    -Second category
    •Used in more than one phase ,but does not support moving from
    one phase to the next.
    •Include the graphics editors that support the design and analysis
    part of a lifecycle.
    -
    Horizontal tools

    -supports automated transfer of information b\w phases of lifecycle

    -include Project management ,Configuration management tools, and


    Integration services
    Types of CASE Tools

    •Upper Case Tools


    •Lower case tools
    •Cross Life Cycle tools
    •Integrated CASE (I-CASE)tools
    •Reverse Engineering tools
    Upper CASE tools
    Also known as Front-end CASE tools, meant for
    •System planning
    •System analysis and
    •General system design

    •Upper CASE Tool For Systems Planning


    -help analyst capture ,store , organize and analyze models of the
    business.
    EXAMPLE:knowledgeware’s ADW Planning Workbench
    •Upper CASE Tool For Systems Analysis and Design
    -hepl analyst better express users requirements ,propose design
    solution and analyze information for consistency,completeness and
    integrity.
    EXAMPLE:ADW Analysis ,Design and RAD Workbneches by
    knowledgeware
    Systems Architect by Popkin S\w
    Lower CASE Tools
    -also known as Back-end CASE tools ,meant for:
    •Detailed System design And implementation.
    •Systems support.
    •Lower CASE Tools for Systems design and Implementation.
    -help applications programmers and other system implementors
    improve their productivity & quality.
    -can be further subcategorized as:
    •Applications Programmer Workbenches
    -support coding , compiling, testing ,and debugging of applications
    program on an intelligent workstationc.
    EXAMPLE : Micro Focus Cobol/2 Workbench.
    •Component Generators
    -design of specialized information system components or problems ,
    then generate the special code required to implement those
    components.
    EXAMPLE : Bachman Database Adminstrator Workbench
    •Code Generators
    -generate code for applications programmers from analysis & design
    specifications , include
    •Writing programs
    •Identify errors in the design specification , and
    •Serve as direct interface to upper –case design tools.

    •Lower CASE tools for systems support


    •Help programmer to restructure existing or old program code to be
    more maintainable.
    •Reengineer programs to accommodate newer technology

    •
    •
    •Cross Life Cucle CASE Tools
    -also known as Integrated CASE(I-CASE) Tools
    -support entire life cycle
    Project Manager tools-help manager plan, schedule , report on &
    manage their projects and resources
    Process Manager tools-help in selecting appropriate kind of tool and
    use them accordingly.
    EXAMPLE: Hyperanalyst
    •Reverse Engineering Tools
    -build bridge from lower -Case tools to upper-CASE tools
    -help in analysis existing applications program and database code to
    create higher –level representation of the code
    CASE For Future
    CASE is the tool-bench ,holding saws and drills and hammers ;
    programming languages are the wood from which you carve the
    model.

    Following types of tools are available:


    � System requirements specification documentation tool
    � Data flow diagramming tool
    � System flow chart generation tool
    � Data dictionary creation
    � Formatting and checking structured English process logic
    � Decision table checking
    � Screen design for data inputting
    � Form design for outputs.
    � E-R diagramming
    � Data base normalization given the dependency information
    I. SYSTEM FLOWCHART AND ER-DIAGRAM GENERATION
    TOOL
    Name of the tool: SMARTDRAW
    II. DATA FLOW DIAGRAM TOOL
    Name of the tool: IBMS/DFD

    III. TOOL TO CONVERT DECISION TABLE TO


    STRUCTURED ENGLISH
    Name of the tool: COPE

    IV. SYSTEM REQUIREMENTS SPECIFICATION


    DOCUMENTATION TOOL
    Name of the tool: ARM

    V. A TOOL FOR SCREEN DESIGN AND DATA INPUTTING


    Name of the tool: Visual Basic

    VI A TOOL FOR DESIGNING AND MANIPULATING


    DECISION TABLES
    Name of the tool: Prologa V.5

    You might also like