Software Engineering | Characteristics of CASE Tools
Prerequisite – CASE (Computer power-assisted software package Engineering), Benefits of CASE
Hardware and environmental requirements:
In most cases, it’s the prevailing hardware that might place constraints upon the CASE tool choice. Thus, rather than process hardware necessities for a CASE tool, the task at hand becomes to suit in associate degree optimum configuration of the CASE tool within the existing hardware capabilities. Therefore, it is often emphasized on choosing the foremost optimum CASE tool configuration for a given hardware configuration.
The heterogeneous network is one instance of distributed surroundings and this will be chosen for illustration because it is a lot of in style because of its machine freelance options. The CASE tool implementation in the heterogeneous network makes use of the client-server paradigm. The multiple purchasers WHO run totally different modules access knowledge wordbook through this server. the info wordbook server could support one or a lot of comes. although it’s doable to run several servers for various comes however distributed implementation of information wordbook isn’t common.
The toolset is integrated through the info wordbook that supports multiple cores, multiple users operating at the same time and permission to share data between users and comes. the info wordbook provides consistent read of all project entities, e.g. a knowledge record definition and its entity-relationship diagram be consistent. The server ought to depict the per-project logical read of the info wordbook. this suggests that it ought to permit back up/restore, copy, cleansing a part of the info wordbook, etc.
The tool ought to work satisfactorily for optimum doable variety of users operating at the same time. The tool ought to support multi-windowing surroundings for the users. this is often vital to modify the users to work out quite one diagram at a time. It additionally facilitates navigation and change from one half to the opposite.
Documentation support:
The deliverable documents should be organized diagrammatically and may be able to incorporate text and diagrams from the central repository. This helps in manufacturing up-to-date documentation. The CASE tool ought to integrate with one or a lot of the commercially obtainable publication packages. It ought to be doable to export text, graphics, tables, knowledge wordbook reports to the DTP package in commonplace forms like PostScript
Project management support:
The CASE tool ought to support assembling, storing, and analyzing data on the computer code project’s progress like the calculable task length, regular and actual task begin, completion date, dates, and results of the reviews, etc.
External interface:
The CASE tool ought to permit the exchange of data for the reusability of style. the data that is to be exported by the CASE tool ought to be ideally in American Standard Code for Information Interchange format and support open design. Similarly, {the data|the info|the data} wordbook ought to give a programming interface to access information. it’s needed for integration of custom utilities, building new techniques, or populating the info wordbook.
Reverse engineering:
The CASE tool ought to support the generation of structure charts and knowledge dictionaries from the prevailing supply codes. It ought to populate the info wordbook from the ASCII text file. If the tool is employed for re-engineering data systems, it ought to contain conversion tool from indexed consecutive file structure, graded and network database to computer database systems.
Data dictionary interface:
The data wordbook interface ought to give read and update access to the entities and relations hold on in it. It ought to have the print facility to get the textual matter of the viewed screens. It ought to give analysis reports like cross-referencing, impact analysis, etc. Ideally, it ought to support a question language to look at its contents.
Please Login to comment...