Software Business Education for Software Engineers: Towards an Integrated Curriculum

Kontio, Jyrki; Ahokas, Mikko; Pöyry, P; Warsta, Juhani; Mäkelä, Marko M.; Tyrväinen, Pasi

doi:10.1109/cseetw.2006.15

Cited by 5 publications

(2 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Value-based software engineering (VBSE) emphasizes that every decision and/or feature of a product does not have an equal value like in a value-neutral setting [2]. This requires making decisions that are better for overall value creation [8,9], and balancing shortterm and long-term value creation. To enable this, different perspectives and corresponding value constructs need to be considered together while making decisions for sustaining growth and maintaining the competitive advantage.…”

Section: Introductionmentioning

confidence: 99%

The software value map — an exhaustive collection of value aspects for the development of software intensive products

Khurum

Gorschek

Wilson

2012

J Software Evolu Process

101

View full text Add to dashboard Cite

SUMMARY In software intensive products such as cars or telecom systems, software has traditionally been associated with cost, and there has been no real perception of its value in relation to the entire product offering. However, because software is becoming a larger part of the main competitive advantage, driving innovation and product differentiation, hardware is becoming more standardized, thus the valuation of software is becoming critical. In existing literature, several value constructs and corresponding valuation/measurement solutions needed for making decisions about software product development are presented. However, the contributions are often isolated with respect to a certain perspective such as focusing on product's internal or external quality aspects only. Consequently, a complete view of value constructs relevant from different perspectives required for making decisions about software product development is missing. This paper presents a consolidated view of the software value concept utilizing the major perspectives and introduces a software value map. The created value map was evaluated through an industry case study through the development of impact evaluation patterns, which were subsequently used by professionals in industry, and experiences gathered. During industry evaluation, practitioners found substantial benefits of having a consolidated, vastly improved, and extended value aspect's view of software. Copyright © 2012 John Wiley & Sons, Ltd.

show abstract

Section: Introductionmentioning

confidence: 99%

The software value map — an exhaustive collection of value aspects for the development of software intensive products

Khurum

Gorschek

Wilson

2012

J Software Evolu Process

101

View full text Add to dashboard Cite

show abstract

“…In [33], suggests specific áreas of business competencies that should be integrated into the software engineering curriculum; other suggestion was showed.…”

Section: Introductionmentioning

confidence: 99%

Curricular design based in bodies of knowledge: Engineering education for the innovation and the industry

Quezada–Sarmiento

Enciso-Quispe

Garbajosa³

et al. 2016

2016 SAI Computing Conference (SAI)

View full text Add to dashboard Cite

Abstract-Bodies of Knowledge (BOK), contain the relevant knowledge for a disciplines as example Software Engineering (SE), System Information (SI), Information Technology (IT), Computer Science (CS), Medicine, Economics, and others áreas of knowledge. BOK describes relevant knowledge for a discipline, and will need show the consensus in the Knowledge Áreas (KA), and related disciplines. The development of this consensus is a prerequisite to the adoption of coherent skills development in the education context, and continuing professional programs both in public and prívate orgañiz ations.In this context a systematic mapping study (SMS), it was performed to evalúate quantity and types of primary studies in an área of interest. SMS will be used as the research method within this research. The research method proposed will allow to sort and classify the information referent to the topics of this research.This paper is an attempt to analyze existing proposals on BOK contents, structure, and make a proposal what the kind of contents it should have, and how it should be structured so that this consensus among all parties can be described and best achieved. In the same way the relevance, and useful of the BOK in the curricular design for the innovation, and the industry context is present.

show abstract

Software Startup Education: A Transition from Theory to Practice

Chanin

Sales

Prikladnicki

2020

Fundamentals of Software Startups

View full text Add to dashboard Cite

Software Business Education for Software Engineers: Towards an Integrated Curriculum

Cited by 5 publications

References 2 publications

The software value map — an exhaustive collection of value aspects for the development of software intensive products

The software value map — an exhaustive collection of value aspects for the development of software intensive products

Curricular design based in bodies of knowledge: Engineering education for the innovation and the industry

Software Startup Education: A Transition from Theory to Practice

Contact Info

Product

Resources

About