ISBN : 978-81-963532-2-3 (E-Book) ExternalInterface The CASE tool should allow exchange of information for reusability of design. The informationwhich istobeexported by the CASEtoolshouldbe preferably inASCII formatand supportopenarchitecture.Similarly,thedatadictionary shouldprovideaprogramminginterfacetoaccess information. It is required for integration of custom utilities, building new techniques, orpopulatingthe datadictionary. ReverseEngineering The CASE tool should support generation of structure charts and data dictionaries from theexisting source codes. It should populate the data dictionary from the source code. If the tool isused for re-engineering information systems, it should contain conversion tool from indexedsequentialfilestructure,hierarchicalandnetworkdatabasetorelational databasesystems. DataDictionaryInterface The data dictionary interface should provide view and update access to the entities and relationsstored in it. It should have print facility to obtain hard copy of the viewed screens. It shouldprovide analysis reports like cross-referencing, impact analysis, etc. Ideally, it should support aquerylanguageto view its contents. Second-generationCASEtool An important feature of the second-generation CASE tool is the direct support of any adaptedmethodology. This would necessitate the function of a CASE administrator organization who cantailor the CASE tool to a particular methodology. In addition, the second-generation CASE toolshavefollowingfeatures: Intelligent diagramming support- The fact that diagramming techniques are useful forsystemanalysisanddesigniswellestablished.ThefutureCASEtoolswouldprovidehelpto aestheticallyandautomaticallylayout thediagrams. IntegrationwithimplementationenvironmentTheCASEtoolsshouldprovideintegrationbetween design and implementation. Data dictionary standards- The user should be allowed to integrate many developmenttools into one environment. It is highly unlikely that any one vendor will be able todeliveratotalsolution.Moreover,apreferredtoolwouldrequiretuningupforaparticular system. Thus the user would act as a system integrator. This is possibly only ifsomestandard ondata dictionaryemerges. Customization support- The user should be allowed to define new types of objects andconnections. This facility may be used to build some special methodologies. Ideally itshould be possible to specify the rules of a methodology to a rule engine for carrying outthenecessaryconsistencychecks. 207 Software Engineering Keerthana P, Manasa KN, Ganga D Bengal
213 Publizr Home