This paper gives an overview of the software maintenance process of Hitachi Software Engineering (HSK) Co., Ltd in Japan‐including its success and failure cases. It discusses HSK's software processes, issues, use of specific tools and techniques such as IMOZU diagrams, and approaches in solving problems. These include the requirement capturing process, reverse‐engineering techniques, environmental changes, change management, and project management. By discussing actual project experiences, we point to certain lessons and their implications for research in software maintenance. We also present the latest re‐engineering CASE tools, such as RE‐ENGINEERING and SEWB3, used at HSK.

No abstract

No abstract

Framework based software development becomes in focus recently to facilitate global level of reuse. However, frameworks are not always available for new application domains, which forces to develop both framework and its application at the same time.Concurrent development introduces several new problems such as where to partition the system into framework part and application extension, interface consistency between them, integration, organizations, how and when to provide extension capabilities in the framework, and so on.We designed the methodology, which addresses some of these issues, to achieve concurrent development of a framework and its application.Preliminary case study on the actual real project from our life insurance related software development was conducted. The study showed that our methodology was capable of handling some of the issues. Partitioning applications and synchronization of process still need more sophisticated approaches for more efficient development.