Software Business Education for Software Engineers: Towards an Integrated Curriculum
19 Apr 2006-pp 5-5
TL;DR: This paper suggests specific areas of business competencies that should be integrated into the software engineering curriculum and compares these topics with software business curricula in three Finnish universities.
Abstract: All software is developed to create value to its stakeholders. Software engineering decisions and business value are closely linked with each other: technical decisions may have a profound impact on the business potential of software. Yet, software engineering education usually does not provide students with sufficient knowledge on business-related issues. We believe that the general business education is too abstract and unfocused to address the specific characteristics of software business. This paper suggests specific areas of business competencies that should be integrated into the software engineering curriculum. In addition, we compare these topics with software business curricula in three Finnish universities.
Citations
More filters
TL;DR: Shapiro and Varian as mentioned in this paper reviewed the book "Information Rules: A Strategic Guide to the Network Economy" by Carl Shapiro and Hal R. Varian and found that it is a good book to read.
Abstract: The article reviews the book “Information Rules: A Strategic Guide to the Network Economy,” by Carl Shapiro and Hal R. Varian.
1,029 citations
01 Jan 2005
TL;DR: An enhancement to the role played case approach was developed with the aim of increasing the proportion of students who are able to apply a deep learning approach and the further use of phenomenographic techniques in information systems education (ISE) research is recommended.
Abstract: Information systems development needs to be taught using an expe-Chris Cope riential approach. This is difficult when introductory classes are large and the stu-Pat Horan dents have no knowledge of the complex social and business environments in which Department of Information Technology information systems are developed. This paper presents a teaching approach called aLa Trobe University, BendiO'o role played case as an experiential tool for large classes of introductory IS students. Bendigo, 3550 o These cases involve students behaving as systems analysts confronting an actor who Australia role plays a cli~nt from a real business organ~sation envi:~nment. .The role played C.Cope@bendigo.latrobe.edu.au case approach IS compared and contrasted WIth the tradluonal wrItten case approach Horan@ironabark.bendigo.latrobe.edu.au and is shown to have significant advantages, particularly in allowing direct interaction between the student and the complex personal and social environments associated with information systems development. A phenomenographic research technique was used to investigate the students' perceptions of the learning context associated with a role played case. It is considered highly desirable to provide a learning context in which students attempt to understand the material being presented and relate the new material to the rest of the curriculum. This is known as a deep learning approach and is associated in the phenomenographic view of learning with conceptually significant learning. The investigation showed that a majority of students perceived the learning context associated with the role played case as requiring a deep learning approach. As a result of the investigation an enhancement to the role played case approach was developed with the aim of increasing the proportion of students who are able to apply a deep learning approach. Finally, the paper recommends the further use of phenomenographic techniques in information systems education (ISE) research. INTRODUCTION The need to teach information systems (IS) development using an experiential approach is well documented in the literature. A number of teaching methods have been reported which assist students to achieve the knowledge, skills and awareness of complex business environments they will need in industry. One such method is to include a real-world or simulated long term project in the curriculum [I] [2] [3]. This method is not suited to an introductory IS subject, however, because: the theory of systems analysis and design needs to be taught before any long term project can be considered.; the organisation and supervision of projects is resource intensive and beyond the capabilities of most IS …
91 citations
TL;DR: A consolidated view of the software value concept utilizing the major perspectives is presented and a software value map is introduced that was evaluated through an industry case study through the development of impact evaluation patterns.
Abstract: 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.
77 citations
Cites background from "Software Business Education for Sof..."
...This requires making decisions that are better for overall value creation [8, 9], and balancing shortterm and long-term value creation....
[...]
13 Jul 2016
TL;DR: 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.
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 areas of knowledge. BOK describes relevant knowledge for a discipline, and will need show the consensus in the Knowledge Areas (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 private organizations. In this context a systematic mapping study (SMS), it was performed to evaluate quantity and types of primary studies in an area 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.
34 citations
Cites background from "Software Business Education for Sof..."
...In [33], suggests specific areas of business competencies that should be integrated into the software engineering curriculum; other suggestion was showed....
[...]
01 Jan 2020
TL;DR: In this chapter, six groups of theories that are already used by practical entrepreneurs and their advisors are explained including the ongoing research around them, the connections among these theories, and how they can be applied in a real case study are explained.
Abstract: In recent years, there has been an explosion of interest in entrepreneurship from both practical entrepreneurs and researchers. While theories are helpful for explaining business-driven activities in a startup, they are also valid in reasoning for the practical activities occurring in the entrepreneurial context. We believe that startups would benefit from the awareness of these entrepreneurial theories and the understanding of how they can be connected to decision-making in both business and engineering perspectives. In particular, we want to focus on theories that are already used by practical entrepreneurs and their advisors. As an example, we have studied the Scandinavian entrepreneurial ecosystem. We selected six groups of theories that might be particularly relevant for the startup population, namely (1) core competence and resource-based view, (2) effectuation, (3) the fulfillment of entrepreneurial opportunities, (4) bricolage, (5) business model innovation, and (6) lean startup. In this chapter, we explain these theories including the ongoing research around them, the connections among these theories, and how they can be applied in a real case study.
22 citations
References
More filters
Book•
01 Jan 1999TL;DR: Information Rules will help business leaders and policy makers - from executives in the entertainment, publishing, hardware, and software industries to lawyers, finance professionals, and writers -- make intelligent decisions about their information assets.
Abstract: From the Publisher:
Information Goods -- from movies and music to software code and stock quotes - have supplanted industrial goods as the key drivers of world markets. Confronted by this New Economy, many instinctively react by searching for a corresponding New Economics to guide their business decisions. Executives charged with rolling out cutting-edge software products or on-line versions of their magazines are tempted to abandon the classic lessons of economics, and rely instead on an ever changing roster of trends, buzzwords, and analogies that promise to guide strategy in the information age. Not so fast, say authors Carl Shapiro and Hal R. Varian. In Information Rules they warn managers, "Ignore basic economic principles at your own risk. Technology changes. Economic laws do not." Understanding these laws and their relevance to information goods is critical when fashioning today's successful competitive strategies. Information Rules introduces and explains the economic concepts needed to navigate the evolving network economy. Information Rules will help business leaders and policy makers - from executives in the entertainment, publishing, hardware, and software industries to lawyers, finance professionals, and writers -- make intelligent decisions about their information assets.
4,977 citations
Proceedings Article•
01 Jan 1986
TL;DR: This article shall try to show why there is no single development, in either technology or management technique, that by itself promises even one order-of-magnitude improvement in productivity, in reliability, in simplicity.
3,107 citations
"Software Business Education for Sof..." refers background in this paper
...More specifically, the complexity of software [4] makes it difficult to understand the value implications of engineering decisions; the conformity characteristic of software makes engineering of software more reactive and less stable, increasing the uncertainty in value estimates of software; the…...
[...]
TL;DR: In this article, the authors examine both the nature of the software problem and the properties of the bullets proposed, and show that there is no single development, in either technology or in management technique, that by itself promises even one order-of-magnitude improvement in productivity, in reliability, in simplicity.
Abstract: But, as we look to the horizon of a decade hence, we see no silver bullet. There is no single development, in either technology or in management technique, that by itself promises even one order-of-magnitude improvement in productivity, in reliability, in simplicity. In this article, I shall try to show why, by examining both the nature of the software problem and the properties of the bullets proposed.
2,794 citations
Book•
01 Jan 1989TL;DR: This work describes the development of a Software Maturity Framework and the Principles of Software Process Change, and describes the management of this framework.
Abstract: Foreword. Preface. I. SOFTWARE PROCESS MATURITY. A Software Maturity Framework. The Principles of Software Process Change. Software Process Assessment. The Initial Process. II. THE REPEATABLE PROCESS. Managing Software Organizations. The Project Plan. Software Configuration Management-Part 1: Software Quality Assurance. III. THE DEFINED PROCESS. Software Standards. Software Inspections. Software Testing. Software Configuration Management (Continued). Defining the Software Process. The Software Engineering Process Group IV. THE MANAGED PROCESS. Data Gathering and Analysis. Managing Software Quality. V. THE OPTIMIZING PROCESS. Defect Prevention. Automating The Software Process. Contracting for Software. Conclusion. Appendices. Index. 0201180952T04062001
2,469 citations
Additional excerpts
...Software development is also closely tied to the people, organization, and processes utilized to develop software [6]....
[...]
TL;DR: Shapiro and Varian as mentioned in this paper reviewed the book "Information Rules: A Strategic Guide to the Network Economy" by Carl Shapiro and Hal R. Varian and found that it is a good book to read.
Abstract: The article reviews the book “Information Rules: A Strategic Guide to the Network Economy,” by Carl Shapiro and Hal R. Varian.
1,029 citations
"Software Business Education for Sof..." refers background in this paper
...…makes it difficult to explicate and understand the characteristics of software and, hence, their implications on value; software is a digital good [9] and, consequently, the ease of copying, transfer, and durability influence many aspects of value; as software is an experience good [7], its…...
[...]