1 / 11

CASE Tool Evolution

Computer-aided documentation Computer- aided diagramming Analysis and design tools. Automated code generation Linked design automation. Automated design analysis Automated central repository. Intelligent methodology drivers Reusable code libraries. 1987. 1980. 1984. 1990.

ranee
Download Presentation

CASE Tool Evolution

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. Computer-aided documentation Computer-aided diagramming Analysis and design tools Automated code generation Linked design automation Automated design analysis Automated central repository Intelligent methodology drivers Reusable code libraries 1987 1980 1984 1990 CASE Tool Evolution

  2. Process Modeling Tools Detailed Analysis Tools Transformation Tools Database/Application Design Tools Application Generation Tools CASE Tool Components Central Repository

  3. Central Repository Detailed Analysis Findings Project Documentation Logical Model Diagrams Data Element Specifications Form and Report Layouts Reusable Code Libraries General Project Information Program Source and Object Code CASE Tool Repository

  4. Management Deliberation Center Defense Systems Management College Fort Belvoir, VA Air Force Innovation Center Pentagon Washington, D.C. Glensidige Insurance Oslo, Norway Center for Performance Improvement Soza and Company, Ltd. Fairfax, VA Large-Scale JAD Environments

  5. Preliminary Investigation Requirement Planning RAD Life Cycle Analysis User Design Logical Design Physical Design Construction Implementation Maintenance Cutover Traditional SDLC SDLC versus RAD

  6. Requirements Planning User Design Construction Traditional SDLC 8 7 6 5 4 3 2 1 Cutover E f f o r t RAD Reduces Time 2 4 6 8 10 12 14 16 18 20 22 24 26 Project Months RAD Reduces Time

  7. Product Cost $ Effort (man years) Lines of Code Lotus 1-2-3 V 3.0 22,000,000 263 400,000 NASA Space Shuttle 1,200,000,000 22,096 25,600 2000 Lincoln Continental 2,800,000 37 93,500 Modern Automatic Teller Machine 13,200,000 150 780,000 IBM Retail Checkout Scanner 3,000,000 58 90,000 Comparative Software Development Costs

  8. ·Create development process standards ·Improve overall application quality ·Decrease design time and improve time to market ·Decrease required effort and time in application testing ·Encourage integration of development projects ·Improve effectiveness of project management activities ·Decrease required effort and time in application maintenance activities ·Promote organization-wide reusable program code ·Improve portability of applications across platforms and operating environments CASE Tool Adoption Objectives

  9. The Good News The Bad News • Development process productivity and quality increases are realizable • Portability of new systems to other platforms is greatly enhanced • Analyst skill set will improve due to greater understanding of the process • Time to delivery of new applications will decrease • Conformity to development standards will increase • CASE acquisition costs are extremely high • Training of analysts and administrators is costly and time-consuming • Most organizations do not have clear standards for application development • CASE tools can be viewed as a threat to job security • CASE tools do not have a great reputation due to early benefits not being realized Good and Bad News

  10. Identify all stakeholders and clarify executive goal. • Scope out the general requirements from each of the users' perspectives. • Reconcile each user's view of the product with the executive goal into one summary. • Define the interaction of the product with users, other products or systems, and the organization. • Concur on business justification, time box, and cost box for project. • Define the ways in which the users will interact or use the new product. Collect samples of desired inputs and outputs from users. Stick to business processes first, then drill down for data needed and known. • Prioritize the user interaction scenarios by collective user preference and risk. • Validate and review the user interaction scenarios. • Organize the interactions scenarios, constraints, assumptions, and other requirements into a rigorous Software Requirements Specification. • Design (with technical help) the screen and report layouts. Prototypes are handy for this. Common JAD Session Tasks

  11. Requirements Planning User Design Construction Cutover Primary Activity Model and prototype requirements Model and prototype design Complete application development Install application Data Conversion Define data requirements Plan and design data conversion Develop data conversion modules Implement conversion plan Testing Design application test plan Conduct user testing End-user Training Define training requirements Design training plan Produce training materials Conduct end-user training RAD Activities and Deliverables

More Related