Search

Your search keyword '"Johnson, Pontus"' showing total 39 results
Start Over Author "Johnson, Pontus" Publisher ieee
39 results on '"Johnson, Pontus"'

7. Modeling and Prediction of Monetary and Non-monetary Business Values

Author

Välja, Margus, Österlind, Magnus, Iacob, Maria Eugenia, van Sinderen, Marten J., Johnson, Pontus, Gasevic, D, Hatala, M., Motahari Nezhad, H.R., and Reichert, M.U.

Subjects
Service (business), Customer retention, EWI-23831, Computer science, media_common.quotation_subject, E3value, Business value, Business model, Business models, IR-88272, Management, Profitability analysis, Microeconomics, Utility, METIS-300083, Value (economics), Production (economics), Quality (business), Customer to customer, SCS-Services, media_common
Abstract

In existing business model frameworks little attention is paid to a thorough understanding of the perceived customer value of a business’ offering as compared to competing offers. In this paper, we propose to use utility theory in combination with e3value models to address this issue. An actor's joint utility function specifies how much value the actor attaches to a given product or service's different qualities. Competing value offerings map to different points on the customer utility function, since they provide certain quantities of each quality. Since the customer can be expected to exhibit a utility maximizing behavior, his/her choices between offerings can be predicted. Thus, given the proposed utility extension, it becomes possible to quantitatively reason about the relative customer value of an offering compared to those of the competition. This, in turn, allows the optimization of price, the key ingredient in any business model.

Published
2013
Full Text
View/download PDF

8. Search-Based Design of Large Software Systems-of-Systems

Author

Lagerström, Robert, Johnson, Pontus, Ekstedt, Mathias, Lagerström, Robert, Johnson, Pontus, and Ekstedt, Mathias

Abstract

This work in progress paper presents the foundation for an Automatic Designer of large software systems-of-systems. The core formalism for the Automatic Designer is UML. The Automatic Designer extends UML with a fitness function, which uses analysis of non-functional requirements, utility theory, and stakeholder requirements, as the basis for its design suggestions. This extension logic is formalized using an OCL-based Predictive, Probabilistic Architecture Modeling Framework (called P2AMF). A set of manipulation operators is used on the UML model in order to modify it. Then, from a component library (with OTS products), new components will be introduced to the design. Using operators, a search algorithm will look for an optimal solution., QC 20191009

Published
2015
Full Text
View/download PDF

9. Exploring theory of cognition for general theory of software engineering : Predicting the effort of programming language comprehension

Author

Johnson, Pontus, Ekstedt, Mathias, Johnson, Pontus, and Ekstedt, Mathias

Abstract

In recent years, there has been significant interest in general theories of software engineering. In this article, we explore the utility of a theory of cognition, ACT-R, as a component of such a general theory. The ACT-R theory was instantiated to predict the effort of programming language comprehension for two cases: (i) a C program, and (ii) the corresponding Assembly program. An experiment was then conducted to generate empirical data on the two comprehension tasks. The theoretical predictions were compared to the empirical results. The theoretical model predicted that the effort of understanding the considered program in C is 37% of the effort of understanding a comparable program written in Assembly. The experiment generated 33% as the corresponding percentage number. The concordance between theoretical model and experimental data was surprisingly high, encouraging further investigations into the utility of cognitive theories in software engineering., QC 20160517

Published
2015
Full Text
View/download PDF

37. Re-founding software engineering -- SEMAT at the age of three (keynote abstract).

Author

Jacobson, Ivar, Spence, Ian, Johnson, Pontus, and Kajko-Mattsson, Mira

Abstract

Software engineering is gravely hampered by immature practices. Specific problems include: The prevalence of fads more typical of the fashion industry than an engineering discipline; a huge number of methods and method variants, with differences little understood and artificially magnified; the lack of credible experimental evaluation and validation; and the split between industry practice and academic research. At the root of the problems we lack a sound, widely accepted theoretical basis. A prime example of such a basis is Maxwell’s equations in electrical engineering. It is difficult to fathom what electrical engineering would be today without those four concise equations. They are a great example to the statement “There is nothing so practical as a good theory”. In software engineering we have nothing similar, and there is widespread doubt whether it is needed. This talk will argue for the need of a basic theory in software engineering, a theory identifying its pure essence, its common ground or its kernel. The Semat (Software Engineering Methods and Theory) community addresses this huge challenge. It supports a process to refound software engineering based on a kernel of widely-agreed elements, extensible for specific uses, addressing both technology and people issues. This kernel represents the essence of software engineering. This talk promises to make you see the light in the tunnel. [ABSTRACT FROM PUBLISHER]

Published
2012
Full Text
View/download PDF

39. Where's the Theory for Software Engineering?

Author

Johnson, Pontus, Ekstedt, Mathias, and Jacobson, Ivar

Subjects
*SOFTWARE engineering, *THEORY, *INFORMATION technology, *ENGINEERING & society, *PARADIGMS (Social sciences), *PHILOSOPHY
Abstract

Darwin's theory of natural selection, Maxwell's equations, the theory of demand and supply; almost all established academic disciplines place great emphasis on what their core theory is. This is not, however, the case in software engineering. What is the reason behind the software engineering community's apparent indifference to a concept that is so important to so many others? [ABSTRACT FROM PUBLISHER]

Published
2012
Full Text
View/download PDF

Catalog

Books, media, physical & digital resources
See catalog results