--- title: "Classification and features of CASE tools" subject: "Software Engineering" chapter: 10 key: "semester_5/software_engineering:case-classification" source: https://www.bctengineer.com/q/semester_5/software_engineering/case-classification site: BCT Engineering --- # Classification and features of CASE tools Software Engineering · Chapter 10: Configuration Management - Asked in: 2070 Chaitra (old course), 4+6 marks - Video: [CASE tools and different CASE tools | | software engineering](https://www.youtube.com/watch?v=CV_x18FxtE8) — abhishek seth - Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14 - Page: https://www.bctengineer.com/q/semester_5/software_engineering/case-classification - Whole chapter: https://www.bctengineer.com/md/semester_5/software_engineering/chapter-10 ## Question How the CASE tools are classified? Discuss the importance and feature of CASE tools. ## Answer #### Classification of CASE tools **CASE (Computer Aided Software Engineering) tools** are software tools that support software process activities. They are classified in several ways. **1. By life-cycle phase** - **Upper CASE:** support early phases: requirements, analysis and design (UML and DFD modelling tools). - **Lower CASE:** support later phases: coding, testing, debugging and maintenance (compilers, test tools). - **Integrated CASE (I-CASE):** support the whole life cycle and share a common repository. ```text Requirements Analysis Design | Coding Testing Maint. <------- Upper CASE ---------> <----- Lower CASE ----> <---------------- Integrated CASE -------------------> (shared central repository) ``` **2. By level of process support** (Fuggetta, used by Sommerville) - **Tools:** support a single task, such as an editor or compiler. - **Workbenches:** support one process phase with several integrated tools, such as an analysis-and-design workbench. - **Environments:** support all or most of the software process using several integrated workbenches. **3. By function** (Pressman) | Category | Example | |---|---| | Project planning and management | MS Project, Jira | | Requirements tracing | IBM DOORS | | Analysis and design (modelling) | StarUML, Enterprise Architect | | Programming | Eclipse, VS Code | | Testing and test management | JUnit, Selenium | | Configuration management | Git, Subversion | | Documentation | Doxygen | | Re-engineering | Reverse engineering tools | **4. By who uses them / their scope** - **Technical tools** support engineering work (design, coding, testing). - **Management tools** support planning, estimation, tracking and configuration management. #### Importance of CASE tools - **Higher productivity:** routine tasks such as drawing diagrams, generating code and documents are automated. - **Better quality:** consistency checks and standards enforcement catch errors early. - **Consistent documentation:** documents are produced from the same models, so they stay up to date. - **Lower cost:** fewer defects and less rework reduce development and maintenance cost. - **Easier maintenance:** reverse engineering and a central repository help understand and change old systems. - **Better teamwork:** all members share the same project information. - **Standardization:** everyone follows the same notation and method. #### Features of CASE tools 1. **Diagramming:** create DFDs, ER diagrams, UML class, sequence and state diagrams. 2. **Central repository / data dictionary:** stores all models, data definitions and their relationships. 3. **Consistency and completeness checking:** detects undefined data, unconnected processes or mismatched interfaces. 4. **Code generation:** produces code skeletons or full code from design models. 5. **Reverse engineering:** builds design models from existing code. 6. **Documentation and report generation:** creates SRS, design documents and reports automatically. 7. **Prototyping and screen design:** builds user interface prototypes quickly. 8. **Version and configuration control:** keeps track of versions of models and code. 9. **Testing support:** generates and runs test cases and measures coverage. 10. **Project management support:** estimation, scheduling and progress tracking. **Example:** with StarUML a designer draws a class diagram, the tool checks it, generates Java class skeletons, and exports diagram documentation for the design report. ## Check yourself The answer's key points as multiple-choice questions, with the correct option and why. 1. What does Integrated CASE (I-CASE) provide? A. Support only for coding B. Support only for early phases C. Support for a single task such as an editor D. Support for the whole life cycle with a shared common repository Answer: D. I-CASE covers the entire life cycle and shares information through a common repository. (Key point: Classification by life-cycle phase) 2. Which ordering of the Fuggetta classification goes from narrowest to broadest support? A. Tools, workbenches, environments B. Environments, workbenches, tools C. Workbenches, tools, environments D. Tools, environments, workbenches Answer: A. Tools support a task, workbenches a phase, and environments most of the process. (Key point: Classification by process support) 3. Why do CASE tools keep documentation consistent? A. Documents are written manually by one person B. Documents are produced from the same models, so they stay up to date C. Documentation is never needed D. Documents are printed only at the end Answer: B. Generating documents from shared models keeps them consistent with the design. (Key point: Importance: consistent documentation) 4. Which pair describes two features of CASE tools? A. Hardware testing and cabling B. Compiling hardware and drawing circuits C. Consistency checking (e.g., undefined data) and reverse engineering of models from code D. Hiring staff and payroll Answer: C. CASE tools detect undefined data or unconnected processes and can build design models from existing code. (Key point: Consistency checking and reverse engineering) ## Related in Software Engineering - [CASE, CASE environment and CASE tools](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acase-environment) — Software Engineering, chapter 10 - [Benefits of CBSE; CASE code generation](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acbse-benefits-case) — Software Engineering, chapter 6 ## Related in other subjects - [Microprocessors in instrumentation systems (case study)](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Ambi-casestudy-statement) — Instrumentation II, chapter 1 - [Classification of circuit breakers](https://www.bctengineer.com/question.md?key=semester_6%2Fswitchgear_and_protection%3Acb-classification) — Switchgear and Protection, chapter 6 - [Cable classification and 3½ core construction](https://www.bctengineer.com/question.md?key=semester_6%2Findustrial_power_distribution_and_illumination%3Acable-classification-construction) — Industrial Power Distribution and Illumination, chapter 3 - [ERP use, features and functionality](https://www.bctengineer.com/question.md?key=semester_8%2Finformation_system%3Aerp-use-features-functionality) — Information System, chapter 3, asked 2×