12 Building Theories in Software Engineering
331
Actor–
Scope of validity: The project was distributed with development at four sites in three countries. Some of the teams were also distributed with team members working at different sites. The teams were medium-sized (typically 8–10
people in each team, the team members mostly had good knowledge of the application domain, their educational background was typically at the level of an MSc, and most were newcomers to the use of UML
at the start of the project, but became quite proficient in UML during the project due to it’s size
Scope of interest: Projects with distributed teams
Software system–
Scope of validity: The system to be developed was large (approximately 1,000 requirements and 3–4 mill. lines of code, which was divided into approximately ten large subsystems.
The software was embedded, C and C+ were used as programming languages, the system was safety-critical and the development followed the requirements of the safety standard IEC61508. Some parts of the system were developed from scratch while others were based on legacy code of existing systems
Scope of interest: Large,
embedded, safety-critical system, possibly based on legacy code.
ActivityBoth scope of validity and scope of interest are create and “modify.”
Share with your friends: