Abstract
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.
| Original language | English (US) |
|---|---|
| Pages (from-to) | 333-375 |
| Number of pages | 43 |
| Journal | Journal of Software Maintenance |
| Volume | 7 |
| Issue number | 5 |
| DOIs | |
| State | Published - 1995 |
| Externally published | Yes |
Keywords
- IMOZU diagram
- Japan
- PAD chart
- change management
- documentation
- maintenance projects
- potato diagram
- requirements
ASJC Scopus subject areas
- General Computer Science
Fingerprint
Dive into the research topics of 'Software maintenance—an industrial experience'. Together they form a unique fingerprint.Cite this
- APA
- Standard
- Harvard
- Vancouver
- Author
- BIBTEX
- RIS