OO software engineering has been a well-known
software engineering methodology for years; however,
there are still some issues remaining unsolved: the
engineers using imperative software engineering have
a large gap to stride across when adopting OO
software engineering; the software may have some
problems resulting from process issue; and a generic
mechanism for checking consistency of designs is
still lacking. A new methodology is represented to
provide a complete global view of OO software system,
which solves issues that are identified. It uses
requirements document and some analysis documents as
foundation because these three issues intersect in
the early analysis phase. Three case studies are also
represented to exemplify the results of applying the
proposed methodology on both OO software engineering
and imperative software engineering.
software engineering methodology for years; however,
there are still some issues remaining unsolved: the
engineers using imperative software engineering have
a large gap to stride across when adopting OO
software engineering; the software may have some
problems resulting from process issue; and a generic
mechanism for checking consistency of designs is
still lacking. A new methodology is represented to
provide a complete global view of OO software system,
which solves issues that are identified. It uses
requirements document and some analysis documents as
foundation because these three issues intersect in
the early analysis phase. Three case studies are also
represented to exemplify the results of applying the
proposed methodology on both OO software engineering
and imperative software engineering.