You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact

Limiting Practices in Developing and Managing Software-Intensive Systems: A Comparative Study



Publication Type:

Conference/Workshop Paper


Portland International Conference on Management of Engineering and Technology




Within the automotive industry, up to 90 percent of all new features are dependent on electronics and software. Consequently, the amount of software and electronics in vehicles is rapidly increasing. The same trend has been observed in other domains, such as telecom, avionics, trains, and more. An important factor in dealing with this inherent complexity is the use of a system architecture. The architecture is typically an enabler for both efficiency and effectiveness in the development of software-intensive systems but not directly connected to the customer needs. For example, the architecture can increase the agility of upcoming product releases in order to cost effectively satisfy future customer needs. By combining two parallel multiple case studies, one focusing on the architects view, and the other one focusing on the managerial perspective, we have identified six limitations. Our results indicate that the focus is on customer requirements for the current product, on the expense of the internal requirements related to the development of the architecture and long-term profitability. Further, even if the early phases of development are identified as a success criterion, they are still not given enough attention.


author = {Peter Wallin and Stefan Cedergren and Stig Larsson and Jakob Axelsson},
title = {Limiting Practices in Developing and Managing Software-Intensive Systems: A Comparative Study},
month = {July},
year = {2010},
booktitle = {Portland International Conference on Management of Engineering and Technology},
publisher = {IEEE},
url = {}