Software and systems engineering: conflict and consensus

Authors:
Rick Gibson
Affiliations:
American University
Venue:
Practicing software engineering in the 21st century
Year:
2003

Citing 6
Cited 0

The profession of IT: The IT schools movement

Communications of the ACM
CMMI distilled: a practical introduction to integrated process improvement

CMMI distilled: a practical introduction to integrated process improvement
What Knowledge Is Important to a Software Professional?

Computer
Software Engineering in the Academy

Computer
Software Engineering Programs Are Not Computer Science Programs

IEEE Software
Toward a unified systems engineering education

IEEE Transactions on Systems, Man, and Cybernetics, Part C: Applications and Reviews

Quantified Score

Hi-index	0.00

Visualization

Abstract

This chapter will identify the key aspects of software engineering and systems engineering in an effort to highlight areas of consensus and conflict to support current efforts by practitioners and academics in both disciplines in redefining their professions and bodies of knowledge.By using the Software Engineering Institute's Capability Maturity Model - Integrated (CMMISM) project, which combines best practices from the systems and software engineering disciplines it can be shown that significant point of agreement and consensus are evident. Nevertheless, valid objections to such integration remain as areas of conflict. This chapter will provide an opportunity for these two communities to resolve unnecessary differences in terminology and methodologies that are reflected in their different perspectives and entrenched in their organizational cultures.