Advanced topics in software engineering
Download as PPT, PDF1 like8,030 views
This document outlines the components and taxonomy of Computer-Aided Software Engineering (CASE) tools, which automate various software development activities to enhance productivity and quality while reducing costs. It details components such as case repositories, diagramming tools, analysis tools, and documentation generators, as well as different categories of CASE tools like project planning, risk analysis, and quality assurance tools. The comprehensive taxonomy serves to illustrate the diverse tools and their functionalities throughout the software development lifecycle.
Advanced topics in software engineering
- 1. Unit-10 Advanced Topics in Software Engineering
- 2. Intro CASE •A CASE (Computer Aided Software Engineering) tool is a generic term used to denote any form of automated support for software engineering. •A CASE tool means any tool used to automate some activity associated with software development. The primary reasons for using a CASE tool are: • To increase productivity • To help produce better quality software at lower cost
- 3. Components of CASE CASE repository Document Generator Design Generator Analysis tool Code Generator Drawing Tool Error-checking tool Security and Version Control Screen and Report Generator Prototyping Tool Database Generator
- 4. Components of CASE •CASE repository • Central component of any CASE tool • Also known as the information repository or data dictionary
- 5. Components of CASE •CASE repository • Centralized database • Allows easy sharing of information between tools and SDLC activities • Used to store graphical diagrams and prototype forms and reports during analysis and design workflows • Provides wealth of information to project manager and allows control over project • Facilitates reusability
- 6. Components of CASE •CASE repository acts as: • Information repository • Combines information about organization’s business information and application portfolio • Provides automated tools to manage and control access • Data dictionary • Used to manage and control access to information repository • Facilities for recording, storing and processing resources • Useful for cross-referencing
- 7. Components of CASE •Diagramming tools • Allow you to represent a system and its components visually • Allows higher level processes to be easily decomposed • Can examine processes or data models at high or low level
- 8. Components of CASE •Screen and report generators • Used to • Create, modify and test prototypes of computer displays and reports • Identify which data items to display or collect for each screen or report • Some tools have templates
- 9. Components of CASE •Analysis tools • Generate reports that help identify possible inconsistencies, redundancies and omissions • Generally focus on • diagram completeness and consistency • data structures and usage
- 10. Components of CASE •CASE documentation generator tools • Create standard reports based on contents of repository • Need textual descriptions of needs, solutions, trade- offs, diagrams of data and processes, prototype forms and reports, program specifications and user documentation • High-quality documentation leads to 80% reduction in system maintenance effort in comparison to average quality documentation
- 11. CASE integration •Tools • Support individual process tasks such as design consistency checking, text editing, etc. •Workbenches • Support a process phase such as specification or design, Normally include a number of integrated tools. •Environments • Support all or a substantial part of an entire software process. Normally include several integrated workbenches.
- 12. CASE Tools • Upper CASE • requirements • specification • planning • design • Lower CASE • implementation • integration • maintenance
- 13. CASE Tool Taxonomy - 1 • Business process engineering tools • represent business data objects, their relationships, and flow of the data objects between company business areas • Process modeling and management tools • represent key elements of processes and provide links to other tools that provide support to defined process activities • Project planning tools • used for cost and effort estimation, and project scheduling
- 14. CASE Tool Taxonomy - 2 •Risk analysis tools • help project managers build risk tables by providing detailed guidance in the identification and analysis of risks •Requirements tracing tools • provide systematic database-like approach to tracking requirement status beginning with specification
- 15. CASE Tool Taxonomy - 3 •Metrics and management tools • management oriented tools capture project specific metrics that provide an overall indication of productivity or quality, technically oriented metrics determine metrics that provide greater insight into the quality of design or code •Documentation tools • provide opportunities for improved productivity by reducing the amount of time needed to produce work products
- 16. CASE Tool Taxonomy - 4 •System software tools • network system software, object management services, distributed component support, and communications software •Quality assurance tools • metrics tools that audit source code to determine compliance with language standards or tools that extract metrics to project the quality of software being built
- 17. CASE Tool Taxonomy - 5 •Database management tools • RDMS and OODMS serve as the foundation for the establishment of the CASE repository •Software configuration management tools • uses the CASE repository to assist with all SCM tasks (identification, version control, change control, auditing, status accounting) •Analysis and design tools • enable the software engineer to create analysis and design models of the system to be built, perform consistency checking between models
- 18. CASE Tool Taxonomy - 6 •PRO/SIM tools • prototyping and simulation tools provide software engineers with ability to predict the behavior of real-time systems before they are built and the creation of interface mockups for customer review •Interface design and development tools • toolkits of interface components, often part environment with a GUI to allow rapid prototyping of user interface designs
- 19. CASE Tool Taxonomy - 7 •Prototyping tools • enable rapid definition of screen layouts, data design, and report generation •Programming tools • compilers, editors, debuggers, OO programming environments, fourth generation languages, graphical programming environments, applications generators, and database query generators •Web development tools • assist with the generation of web page text, graphics, forms, scripts, applets, etc.
- 20. CASE Tool Taxonomy - 8 •Integration and testing tools •data acquisition • get data for testing •static measurement • analyze source code without using test cases •dynamic measurement • analyze source code during execution •simulation • simulate function of hardware and external devices •test management •cross-functional tools
- 21. CASE Tool Taxonomy - 9 •Static analysis tools • code-based testing tools, specialized testing languages, requirements-based testing tools •Dynamic analysis tools • intrusive tools modify source code by inserting probes to check path coverage, assertions, or execution flow • non-intrusive tools use a separate hardware processor running in parallel with processor containing the program being tested
- 22. CASE Tool Taxonomy - 10 •Test management tools • coordinate regression testing, compare actual and expected output, conduct batch testing, and serve as generic test drivers •Client/server testing tools • exercise the GUI and network communications requirements for the client and server
- 23. CASE Tool Taxonomy - 11 •Reengineering tools •reverse engineering to specification tools • generate analysis and design models from source code, where used lists, and other design information •code restructuring and analysis tools • analyze program syntax, generate control flow graph, and automatically generates a structured program •on-line system reengineering tools • used to modify on-line DBMS
Editor's Notes
- #5: CASE repository Stores the diagrams and other project information Keeps track of how the diagrams fit together
- #8: Diagramming tools Allow you to draw DFDs, ERDs, use case diagrams, case diagrams Allows you to use stepwise refinement in building models (work from high level to low level)
- #10: Analysis tools Types of analyses depend on methodology used and features of CASE environment
- #11: Case documentation generator tools Provide a method of managing documentation Allow creation of master templates