Publication | Closed Access
Coping with changes: Causes, findings, and strategies
206
Citations
5
References
2000
Year
EngineeringGerman IndustrySoftware SystemsSoftware EngineeringMental HealthPsychologySystem Of Systems EngineeringSuccessful SystemsChange Management (Itsm)ManagementSystems EngineeringSystem CharacteristicPublic HealthNew Product DevelopmentCoping BehaviorBehavioral SciencesProduct LifecycleSoftware Development ProcessDesignApplied Social PsychologyLifecycle ModelSocial StressBehavior Change (Individual)Psychosocial ResearchSoftware EvolutionBusiness OperationsBehavior ChangeLife CycleSystem Software
Changes are inherent to engineering successful systems, making their management a critical practice in product development. The study aims to uncover the problems, rationales, and goals of changes during a system’s life cycle and proposes making late changes cost‑efficient by embedding changeability into system architectures. An exploratory case study in German industry, illustrated by an example of preventing and front‑loading changes, provides the methodological basis. The authors identify causes and reasons for changes, describe five coping strategies and methods, and conclude that while prevention and front‑loading are preferred, changes remain essential for competitiveness. © 2000 John Wiley & Sons, Inc.; Syst Eng 3: 169–179, 2000.
There is no engineering of successful systems without any changes; they are the rule and not the exception in product development. To uncover the problems, rationales and goals associated with changes during the life cycle of a system, an exploratory case study in German industry was conducted. Causes and reasons for changes are described, as well as five strategies to cope with changes and the related methods. One example will show how to successfully prevent and front-load changes. Though the preferred strategies to cope with changes are prevention and front-loading, it is concluded that, in today's dynamic business environments, changes are necessary to stay competitive. Therefore, it is proposed to make late changes cost-efficient by implementing changeability within system architectures. Managing changes has to be understood as a major practice for developing successful systems. © 2000 John Wiley & Sons, Inc. Syst Eng 3: 169–179, 2000
| Year | Citations | |
|---|---|---|
Page 1
Page 1