III. REVERSE ENGINEERING WEB APPLICATIONS
Web applications are always developed without following
the software life cycle processes, the requirements are not
recorded, and the models are not designed. The developer
early enters the implementation phase. Then we do not expect
developer to present a proper model for testing purpose.
Subsequently such a model should be produced from artifact.
Reverse engineering processes are in fact a way to present the
abstract demonstrations of the implemented work. These
demonstrations provide useful information in a diverse level of
granularity. The pages are the coarse grained part of the
structure of web applications. Each page includes different
components which are split to activate and inactivate
components. The pages are divided into server pages and
client pages. The server pages are set up on the server and the
pages sent back to a client requests are client pages which are
categorized in two groups as static pages and dynamic pages.
Static pages are those that their contents are fixed and stored in
a persistent way and the dynamic pages are built on the fly and
their contents are dependent upon the inputs entered by users.
[9] Exploiting the structure of web applications could be done
in two ways: