Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.

Slides:



Advertisements
Similar presentations
CASE tools Upper CASE tools: support for the analysis and design Lower CASE tools: support for construction and maintenance 1980s… Nowadays… Integrated.
Advertisements

Systems Development Environment
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Dr Gordon Russell, Napier University Unit Data Dictionary 1 Data Dictionary Unit 5.3.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
11.1 Lecture 11 CASE tools IMS Systems Design and Implementation.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Requirements Analysis 5. 1 CASE b505.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis CASE Computer.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Lecture 13 Revision IMS Systems Analysis and Design.
IMS Information Systems Development Practices
9.1 Quality and productivity issues in information systems development: CASE tools and prototyping IMS Information Systems Development Practices.
Fundamentals of Information Systems, Second Edition
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Galin, SQA from theory to implementation © Pearson Education Limited Chapter 13 CASE Tools and their Effect on Software Quality.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Introduction to Systems Analysis and Design Trisha Cummings.
Chapter 2: Approaches to System Development
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
Everyone has heard the old saying about the shoemaker's children: The shoemaker is so busy making shoes for others that his children don't have shoes of.
Section 11 : Normalisation
The Systems Development Methodologies. Objectives  Describe the information Systems Development Life Cycle (SDLC)  Explain prototyping  Explain Rapid.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Content The system development life cycle
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Fundamentals of Information Systems, Second Edition 1 Systems Development.
ANKITHA CHOWDARY GARAPATI
Database Administration
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Chapter 5: Software Re-Engineering Omar Meqdadi SE 3860 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
CSC480 Software Engineering Lecture 10 September 25, 2002.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
Source Mastering UML with Rational Rose 2002 Information System Engineering Introduction to UML.
NURHALIMA 1. Identify the trade-offs when using CASE Describe organizational forces for and against adoption of CASE tools Describe the role of CASE tools.
Online School Management System Supervisor Name: Ashraful Islam Juwel Lecturer of Asian University of Bangladesh Submitted By: Bikash Chandra SutrodhorID.
CASE Tools and their Effect on Software Quality
CASE (Computer-Aided Software Engineering) Tools
Appendix 2 Automated Tools for Systems Development
Software Project Configuration Management
Chapter 1 The Systems Development Environment
Modern Systems Analysis and Design Third Edition
Computer Aided Software Engineering (CASE)
Modern Systems Analysis and Design Third Edition
Business System Development
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Tools of Software Development
Chapter 4 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Information Systems Development (ISD) Systems Development Life Cycle
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ

Supplement 02CASE Tools2 Learning Aims Objective 1 –to understand the importance of CASE tools and techniques Aims –What is CASE?

Supplement 02CASE Tools3 What is CASE? “Computer Aided Software Engineering (CASE) are the software tools that provide automated support for some portion of the systems development process” (Hoffer,1999) Abstraction based methodology based on diagrams (pictures) CASE can be used to model any system All future lectures will be devoted to learning this modelling technique

Supplement 02CASE Tools4 Why use CASE TEAM – share system development tasks –Size of development team –Size and scope of project –Skill & experience of the team …. Documentation used to communication. STRUCTURED METHODOLOGIES –used to document all systems to a universally accepted defined standards Documentation standards – use the same tools Speak the same language - use the same tools Structured Methodology tool of interest : –Computer Aided Software Engineering Tools & Techniques (CASE)

Supplement 02CASE Tools5 Integrated CASE Tools Support activities occurring across several phases of the systems development lifecycle Integrated CASE provide tools to create diagrams, forms & report definitions facilities for analysis, reporting and code generation shares and integrates data across and between tools Rely on common terminology, notation and system development methods Use a common repository to allow data to be shared between tools and SDLC activities

Supplement 02CASE Tools6 Organisational use of CASE Depending on the CASE tool, the following system development activities may be covered: project identification and selection project initiation and planning analysis design implementation maintenance

Supplement 02CASE Tools7 Organisational use of CASE Objectives of CASE improve quality of developed systems increase speed of systems development improve testing process through automatic checking integrate development activities (common methods) improve documentation (quality and completeness) standardise the development process simplify program maintenance promote reusability of modules & documentation improve software portability across environments

Supplement 02CASE Tools8 CASE Tool Components Vary depending on which CASE tool is considered but in general will include: diagramming facilities means of describing/defining functional and data objects means of identifying relationships between system components central repository of system information error checking facilities (syntax errors)

Supplement 02CASE Tools9 CASE Tool Components consistency and completeness checks user interface generators database specification code generators project management aids documentation generators May also provide features for group working, version control, interfacing facilities and security features

Supplement 02CASE Tools10 CASE Diagramming Tools Diagramming facilities include: checks for syntactic correctness consistency & completeness checks navigation to linked diagrams data dictionary support layering of system components traceability of requirements report generation system simulation/performance analysis (models)

Supplement 02CASE Tools11 CASE Repository A repository is a centralised database containing all models (diagrams), data dictionary entries, form & report definitions and system & organisational information Holds complete information to develop a system from initiation to maintenance Supports team IS development

Supplement 02CASE Tools12 CASE Repository CASE Repository Diagrams Documentation Forms and Reports Project Information Source and Object Code Standard Libraries Analysis & Testing Results

Supplement 02CASE Tools13 CASE Analysis Tools Help handle the complexities of building large complex systems Analyse items stored in the repository for consistency & completeness includes diagrams, data, process flows and reports e.g. all classes in a sequence diagram are present in the class diagram and messages are consistent Analysis tools often may be customised

Supplement 02CASE Tools14 CASE Documentation Generators Create reports based on the Repository’s contents technical & user documents in standard formats Benefits: helps manage large amounts of documentation generated during Systems Development Lifecycle reduces “retrospective” documenting of system high quality documentation reduces maintenance costs/effort

Supplement 02CASE Tools15 CASE Code Generators Automatic generation of program and database definition code from information stored in the Repository Produce source code (not compiled) allows generation for several environments –standard programming language conventions –compiled on different platforms with different operating systems

Supplement 02CASE Tools16 CASE Code Generators e.g. the IBM Rational Rose suite includes tools which:IBM Rational Rose – generate class definitions, in C++, Visual Basic, Java etc.; – generate ER model, SQL schema (e.g. Oracle8), CORBA IDL and Web Publisher; – reverse engineer from many of these; – trace requirements from model to code; model integrator / check model – guide the development process. e.g. the ASCENT suite developed at UoTASCENT

Supplement 02CASE Tools17 Benefits of using CASE Tools Automation of tedious tasks Syntax/completeness checks ensure consistency Amending/updating achieved far more easily documentation can be kept up-to-date beneficial effect on maintenance More rapid development more feasible to develop & evaluate alternative designs an aid to prototyping

Supplement 02CASE Tools18 Benefits of using CASE Tools Capture of system data for reuse particularly important for OO development May guide the use of a methodology Clearer communication with users Continuity of development with changing staff Standardised quality assurance/test procedures Improvements in system quality Reduction in defects increases morale

Supplement 02CASE Tools19 Role of CASE in Software Quality Assurance CASE can help with: – adherence to standards, – integrity of documentation, – centrally held data dictionary, – fast capture of requirements, – quick modification to designs, – trace requirements from model to code, – guide the development process, – easy, consistent code-generation. All important in maintaining quality

Supplement 02CASE Tools20 Limitations of CASE Limited flexibility in documentation –standards may not suit organisation or project needs Development approach limited to fit capabilities of the CASE tool –may not adhere to industry or organisational standards Training and experience required

Supplement 02CASE Tools21 Limitations of CASE Front loaded cost of installation of CASE tool & training –benefits may outweigh initial costs Incomplete coverage of syntax/ consistency checks Limited intelligence - no checks on overall quality or correctness

Supplement 02CASE Tools22 SAD using Case Tools Systems Analysis –“What” the proposed system must do –Construct Analysis Specification document Systems Design –“How” the proposed system will achieve this –Construct Design Specification document Documentation Standards –Emphasis on CASE tools documentation –And not PROJECT documentation !!!!!!!!!

Supplement 02CASE Tools23 CASE Diagramming Tools Systems Development uses diagrams to represent various system components and their relationships –Context Diagram supported by text –Event List supported by text –Data Flow Fragments supported by text –Top-Level Data Flow Diagram supported by text –Low-Level Data Flow Diagrams supported by text

Supplement 02CASE Tools24 All future lectures will be devoted to learning CASE Tools & Techniques –Context Diagram supported by text –Event List supported by text –Data Flow Fragments supported by text –Top-Level Data Flow Diagram supported by text –Low-Level Data Flow Diagrams supported by text –Data Dictionary Data Description –Structures & Elements –Starting point is DATA STORES& DATA FLOW Data Store Descriptions Data Flow Descriptions Process Descriptions –NORMALISATION Database Tables derived from Data Store Descriptions

Supplement 02CASE Tools25 Summary Importance of CASE tools & techniques to model systems Case Documentation requirements & standards CASE TOOLS - ONLINE