1 / 11

RE-ENGINEERING AND DOMAIN ANALYSIS

RE-ENGINEERING AND DOMAIN ANALYSIS. BY- NISHANTH TIRUVAIPATI. INTRODUCTION. Necessity of Re-Engineering. Purpose of Re-Engineering: --Documentation --Maintenance --Re-Use. Problems in Re-Engineering --Changes in original program.

renee-donaldson
Download Presentation

RE-ENGINEERING AND DOMAIN ANALYSIS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RE-ENGINEERINGANDDOMAIN ANALYSIS BY- NISHANTH TIRUVAIPATI

  2. INTRODUCTION • Necessity of Re-Engineering. • Purpose of Re-Engineering: --Documentation --Maintenance --Re-Use

  3. Problems in Re-Engineering --Changes in original program. --Program intended for a specific purpose only. --There are many programs running simultaneously. --Not all problems are expressed with Code

  4. DOMAIN ANALYSIS • Domain Analysis is the “Problem Area”. • Areas into which Domains can be divided: --relations between Objects. --Solutions and their approximations --Store of Data and Knowledge about the program. • Characteristics: --Vocabulary --Architectural approach --Common assumptions

  5. Domain Analysis: --Identify objects, operators & relationships Domain Representation: --Represents results in systematic order The exact from of representation and the extent of its formality are important for both the Software Engineer and Re-Engineer.

  6. Relationship to Re-Engineering • Domain descriptions represent expected constructs to look out in the code. • Since all the issues can’t be looked into domain analysis establishes expectations to be confirmed in the program. • Domain analysis are related to each other and are organized in prototyping order that may be related to program.

  7. Approaches to Domain Modeling • Algebraic: --its semantic represented in equations, combination of operations preformed and data items of type. Denotational: --Languages like VDM and Z are used. --represent data in equations using sets, lists, tuples and maps.

  8. Issues • Methodology --Can domain analysis help? --Where should we start? --The method should be illustrative and expansive as the code grows. • Representation --Who do we represent domain information? --how do we represent several domains?

  9. --How much formality should reach domain represent • Tools --What kind of tools are required, Browser type tools? CASE tools? New approach? --Tools need to have validity check of representation of complex domains.

  10. Research • Current work --Use of CASE tool in Interactive Environment Development Software through Pictures (StP) --Use of Object Oriented frame work to record understand.

  11. Conclusion • We can obtain maximum leverage in reuse by using highest possible level of abstraction and domain knowledge. • Hence we can consider domain model as a efficient approach for Re-engineering.

More Related