CS560: Formal Modelling and Implementation of Systems (Term II) Lecture: CASE A. O Riordan, 2009.

Transcription

1 CS560: Formal Modelling and Implementation of Systems (Term II) Lecture: CASE A. O Riordan, 2009.

2 Software Engineering Tools Project Planning and Management tools Requirements tools Risk Analysis tools Development and Testing tools Integrated Development Environments (IDEs) Configuration management tools Data Modelling tools User Interface Generators Report Generators Refactoring/ Reengineering tools Modelling (Unified Modelling Language) tools

3 Computer-Aided Software Engineering Computer tool to assist developers with modelling and documentation Sometimes can generate parts of system implementation Benefits Help standardization of notations and diagrams Help communication between development team members Automatically check the quality of models Reduction of time and effort Enhance reuse of models But Limitations in flexibility Syntactic correctness does NOT mean compliance with requirements Costs associated with the use of the tool

4 CASE tool Classification In the mid-1980s a number of separate tools became prominent for analysis and design (for Entity Relationship diagrams, Data Flow Diagrams, and Program Design). This often entailed manual conversion of the output of one tool to provide the input of another. Need for CASE tool integration. Tools can be classified according to their specific function or according to process activities that are supported UpperCASE (front-end tools, e.g. planning, design) versus LowerCASE (back-end tools, e.g. development) Horizontal integration - tools connected at the same stage of the software development lifecycle (SDLC). Vertical integration - tools connected at different stages of the SDLC.

5 Documentation Legacy of analysis and design decisions - offer traceability back to requirements. Documentation should be allowed to evolve together with the product releases What? requirements, analysis, design, implementation end user manual(s) planning/management reports, etc. A traceability matrix can match design elements with requirements.

6 Degree of Support Many CASE tools simply act as repositories of models and documets. They do not assist in the creative part of modelling. Some CASE tools attempt to provide more assistance, ranging from simple prompts through to syntax/model checking. Ways to use CASE: As independent toolkits to be utilized in a way decided by development team. As part of a method(-ology)

7 Architecture of a CASE tool Report Generation Requirements Spec. Tools Code Generation Methods (e.g. UML) Tools Model Checking Dictionary Import./Fxport Schema Generation

8 Data Repository/Dictionary Manage and control access to the information repository Contains all data definitions for all models Entries have a standard definition format Support Cross referencing Single definition for a data item is established and used Enable model import/export (XMI XML Model Interchange Format)

9 Advanced Features Support for architectures, patterns and frameworks Support for development process and methods, e.g. RUP Code generation, Reengineering Tools Model Checking Support for Metrics Support for Team development Version Control Import/Export Facilities Backup and Recovery

10 UML-supported CASE tools Proprietary Rational Software Architect (IBM) - Eclipse-based UML 2.0 tool Together (Borland): UML modelling tool, integrated with Eclipse Poseidon for UML (Gentleware) - commercial version of ArgoUML Objecteering (Softeam) Open Source StarUML - mostly written in Delphi ArgoUML - Java-based EclipseUML - uses Eclipse Modeling Framework (EMF)

11 ArgoUML Simple and easy to use Available for free and can be used in commercial settings Gentleware sell a commercial CASE tool based on ArgoUML Open-source (BSD license) Based on the UML 1.4 specification Written in Java Uses the open file formats XMI (XML Metadata Interchange format) for model information Uses PGML (Precision Graphics Markup Language) for graph information storage Supports Forward Engineering (Java code-generation)

12 Limitations of ArgoUML While it is easy to learn and use it is limited Lacks some of the advanced features of commercial tools Version control; team support; refactoring No support for UML 2 No support for sequence diagrams Alternative: StarUML - Windows tool that supports most of UML 2

13 Titlebar ArgoUML Screenshot Toolbar Menubar Editing pane Explorer pane Details pane To do pane

14 Together Features Commercial tool from Borland (acquired TogetherSoft 2003) Integrates Java IDE with a UML modelling tool Works as a set of Eclipse plugins (Eclipse 3.4) Support for UML 2, Design Patterns Model differencing and Model merging Supports Audits and metrics Support fro XMI Code generators for Java 6, C++, CORBA IDL, and C# (new) Forward and reverse engineering for leading DBMS Teamwork: Share diagrams and models HTML documentation generation

15 Together Screenshot