SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "L773:1865 1348 OR L773:1865 1356 OR L773:9783319186115 srt2:(2010-2014)"

Sökning: L773:1865 1348 OR L773:1865 1356 OR L773:9783319186115 > (2010-2014)

  • Resultat 1-30 av 30
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Atem de Carvalho, Rogerio, et al. (författare)
  • Towards more flexible enterprise information systems
  • 2012
  • Ingår i: Enterprise Information Systems of the Future : Lecture Notes in Business Information Processing, vol 139 - Lecture Notes in Business Information Processing, vol 139. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642366109 - 9783642366116 ; , s. 157-164
  • Konferensbidrag (refereegranskat)abstract
    • The aim of this paper is to present the software development techniques used to build the EIS Patterns development framework, which is a testbed for a series of techniques that aim at giving more flexibility to EIS in general. Some of these techniques are customizations or extensions of practices created by the agile software development movement, while others represent new proposals. This paper also aims at helping promoting more discussion around the EIS development questions, since most of research papers in EIS area focus on deployment, IT, or business related issues, leaving the discussion on development techniques ill-treated.
  •  
2.
  • Backlund, Emil, 1988, et al. (författare)
  • Automated User Interaction Analysis for Workflow-Based Web Portals
  • 2014
  • Ingår i: Software Business. - Cham : Springer. ; 182, s. 148-162
  • Konferensbidrag (refereegranskat)abstract
    • Success in the software market requires constant improvement of the software. These improvements however have to directly align with the needs of the users of the software. A recent trend in software engineering is to collect post-deployment data about how users use a software system. We report in this paper about a case study with an industrial partner in which (1) we identified which data has to be collected for a web-based portal system, (2) implemented the data collection, and (3) performed an experiment comparing the collected data with answers of the test subjects in a survey.
  •  
3.
  • Bosch, Jan, 1967 (författare)
  • Building products as innovation experiment systems
  • 2012
  • Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642307454 ; 114, s. 27-39
  • Konferensbidrag (refereegranskat)abstract
    • Traditional software development focuses on specifying and freezing requirements early in the, typically yearly, product development lifecycle. The requirements are defined based on product management's best understanding. The adoption of SaaS and cloud computing has shown a different approach to managing requirements, adding frequent and rigorous experimentation to the development process with the intent of minimizing R&D investment between customer proof points. This offers several benefits including increased customer satisfaction, improved and quantified business goals and the transformation to a continuous rather than waterfall development process. In this paper, we present our learnings from studying software companies applying an innovation experiment system approach to product development. The approach is illustrated with three cases from Intuit, the case study company.
  •  
4.
  • Bosch, Jan, 1967, et al. (författare)
  • ESAO: A holistic Ecosystem-Driven Analysis Model
  • 2014
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. - 9783319087375 ; 182, s. 179-193
  • Konferensbidrag (refereegranskat)abstract
    • The growing importance of software ecosystems and open innovation requires that companies become more intentional about aligning their internal strategy, architecture and organizing efforts with the ecosystem that the company is part of. Few models exist that facilitate analysis and improvement of this alignment. In this paper, we present the ESAO model and describe its six main components. Organizations and researchers can use the model to analyze the alignment between the different parts of their business, technologies and ways of working, internally and in the ecosystem. The model is illustrated and validated through the use of three case studies.
  •  
5.
  • Bosch, Jan, 1967, et al. (författare)
  • The Early Stage Software Startup Development Model: A Framework for Operationalizing Lean Principles in Software Startups
  • 2013
  • Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. ; 167, s. 1-15
  • Konferensbidrag (refereegranskat)abstract
    • Software startups are more popular than ever and growing in numbers. They operate under conditions of extreme uncertainty and face many challenges. Often, agile development practices and lean principles are suggested as ways to increase the odds of succeeding as a startup, as they both advocate close customer collaboration and short feedback cycles focusing on delivering direct customer value. However, based on an interview study we see that despite guidance and support in terms of well-known and documented development methods, practitioners find it difficult to implement and apply these in practice. To explore this further, and to propose operational support for software startup companies, this study aims at investigating (1) what are the typical challenges when finding a product idea worth scaling, and (2) what solution would serve to address these challenges. To this end, we propose the ‘Early Stage Software Startup Development Model’ (ESSSDM). The model extends already existing lean principles, but offers novel support for practitioners for investigating multiple product ideas in parallel, for determining when to move forward with a product idea, and for deciding when to abandon a product idea. The model was evaluated in a software startup project, as well as with industry professionals within the software startup domain.
  •  
6.
  • Eklund, Ulrik, 1967, et al. (författare)
  • Applying Agile Development in Mass-Produced Embedded Systems
  • 2012
  • Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642303494 ; 111, s. 31-46
  • Konferensbidrag (refereegranskat)abstract
    • The paper presents a method to manage critical interactions to manage when introducing agile software development in mass-produced embedded systems. The method consists of a context model together with a set of measures, and is validated by empirical evidence from three cases.From an industrial perspective, the paper provides a prescription on how to implement agile software development outside the typical domains for agile, in this case for mass-produced products with embedded software governed by a stage-gate process for mechanics and hardware.From a research perspective, the paper provides an analysis of the software development cycle for products with embedded software, especially where product development as a whole is driven by a plan-driven process. The main contribution is a method for introducing agile in areas where by necessity the full R&D process cannot be agile.
  •  
7.
  • Eklund, Ulrik, 1967, et al. (författare)
  • Introducing Software Ecosystems for Mass-Produced Embedded Systems
  • 2012
  • Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642307461 ; 114, s. 248-254
  • Konferensbidrag (refereegranskat)abstract
    • Embedded systems are today predominantly developed with an integration-centric approach. The paper identifies the need to remove full-scale integration and process synchronisation of involved development teams. The paper presents software ecosystem as an alternative approach to develop embedded software and identifies a set of key activities for how an original equipment manufacturer can introduce an ecosystem.An example of a software ecosystem is presented for the carindustry together a case which implemented some of the ecosystem platform properties.
  •  
8.
  • Haftor, Darek M., et al. (författare)
  • A Review of Information Logistics Research Publications
  • 2011. - 1
  • Ingår i: Business Information Systems Workshops. - Berlin, Heidelberg : Springer. - 1865-1348 .- 1865-1356. - 9783642253690 - 9783642253706 ; , s. 244-255
  • Konferensbidrag (refereegranskat)abstract
    • ‘Information Logistics’ has presented itself as an intellectual and professional domain addressing the question of timely providence of the right information. A question that emerges then is: What is Information Logistics? To answer this question, a comprehensive review of research publications was conducted, where ‘Information Logistics’ was featured in the publication title. A detailed analysis of the content of these publications identified eleven different research directions, where five are currently active, all in Europe. Among various findings, the results show that these research directions have been pursued independently of each other, addressing different kinds of research questions and contexts, utilising different research approaches, and therefore generating a variety of unrelated research results. All the reviewed research here shows that there are numerous unmet empirical needs in our human and social affairs, as well as a need for intra-disciplinary developments, which calls for a joint mobilisation of the research efforts.
  •  
9.
  • Hartmann, H., et al. (författare)
  • Orchestrate your platform: Architectural challenges for different types of ecosystems for mobile devices
  • 2014
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. - 9783319087375 ; 182, s. 163-178
  • Konferensbidrag (refereegranskat)abstract
    • The introduction of smartphones and tablets has led to a fast growing industry in which most firms have started an ecosystem-centric approach. In this paper three types of ecosystems are identified: Vertically integrated hardware/ software platforms, closed source software platforms and open source software platforms. These ecosystems differ in the scope of the platform, i.e. covering both hardware and software, and the technology design, i.e. whether the software can be altered by the complementors. In this paper the challenges for each type of ecosystems are identified from an architectural point of view. Platform leaders can use our analysis to orchestrate their platform by proactively addressing the challenges that we identify and properly evolving the scope and technology design of their platforms.
  •  
10.
  • Koch, Christian, 1958, et al. (författare)
  • Information Standards Enabling or Constraining Innovative Hospital Facilities? -A Scandinavian Case
  • 2014
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. ; 194, s. 347-361
  • Konferensbidrag (refereegranskat)abstract
    • The losses from suboptimal interoperability in IT supported design, production, and operation of health care facilities are tantamount. In these years new built of hospitals in Scandinavia could be realized in a more efficient and innovative way if using information standards. This paper inquires into whether computerized information standards enable or constrain innovation in public procurement of buildings. In architectural and engineering design of public buildings the project based product development tends be done in constellations of firms in interorganisational contracting, which do not provide stability or room for innovation. A large hospital project was investigated through interviews, documents and observations. The effects of implementing building information standards are both inter- and intraorganisational. The building client claims to have saved money, through better structured building component data that gave considerable positive effects during tendering. The IT-suppliers develop IT-tools, and the AEC companies can commence develop services preparing for new markets.
  •  
11.
  • Martini, Antonio, 1982, et al. (författare)
  • Improving Businesses Success by Managing Interactions among Agile Teams in Large Organizations
  • 2013
  • Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642393358 ; 150, s. 60-72
  • Konferensbidrag (refereegranskat)abstract
    • To achieve successful business, large software companies employ Agile Software Development to be fast and responsive in addressing customer needs. However, a large number of small, independent and fast teams suffer from excessive inter-team interactions, which may lead to paralysis. In this paper we provide a framework to understand how such interactions affect business goals dependent on speed. We detect factors causing observable interaction effects that generate speed waste. By combining data and literature, we provide recommendations to manage such factors, complementing current Agile practices so that they can be adapted in large software organizations.
  •  
12.
  • Martini, Antonio, 1982 (författare)
  • Managing Speed in Companies Developing Large-Scale Embedded Systems
  • 2013
  • Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642393365 ; 150, s. 231-232
  • Konferensbidrag (refereegranskat)abstract
    • An open issue is how to reach quickness and responsiveness in addressing customer needs within large-scale embedded system product development, where the processes are bound to the physical product development. Speed is a key quality that needs particular attention. We are developing a framework to understand what kinds of speed are important, what factors are determining them, what are the visible effects and what is possible to improve in order to reach speed related business goals.
  •  
13.
  • Mellegård, Niklas, 1971, et al. (författare)
  • Distribution of Effort Among Software Development Artefacts: An Initial Case Study
  • 2010
  • Ingår i: Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1356 .- 1865-1348. - 9783642130502 ; 50, s. 234-246
  • Konferensbidrag (refereegranskat)abstract
    • Model-driven development aims at increasing productivity by raising the abstraction level of software specifications and introducing automated transformations for replacing lower level specifications. To assess benefits of replacing a legacy development process with a model-driven approach, one needs to establish a baseline of the current process with respect to the effort invested in the development artefacts. In this paper we report on an initial case study in which we investigate the main artefacts in the analysis and design phase with respect to required effort and perceived importance. We studied a non-model driven development of software based automotive functionality and our initial results show that a few artefacts receive the majority of effort, and that the artefacts that receive the most effort are not the most important ones. The initial results indicate that the distribution of effort between models and other artefacts is similar to that of model-driven projects in spite of the project being perceived and characterized as code-centric.
  •  
14.
  • Nilsson, Agneta, 1968, et al. (författare)
  • Visualizing Testing Activities to Support Continuous Integration: A Multiple Case Study
  • 2014
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. ; 179, s. 171-186
  • Konferensbidrag (refereegranskat)abstract
    • While efficient testing arrangements are the key for software companies that are striving for continuous integration, most companies struggle with arranging these highly complex and interconnected testing activities. There is often a lack of an adequate overview of companies’ end-to-end testing activities, which tend to lead to problems such as double work, slow feedback loops, too many issues found during post-development, disconnected organizations, and unpredictable release schedules. We report from a multiple-case study in which we explore current testing arrangements at five different software development sites. The outcome of the study is a visualization technique of the testing activities involved from unit and component level to product and release level that support the identification of improvement areas. This model for visualizing the end-to-end testing activities for a system has been used to visualize these five cases and has been validated empirically.
  •  
15.
  • Olsson Holmström, Helena, et al. (författare)
  • Post-deployment Data Collection in Software-Intensive Embedded Products
  • 2013
  • Ingår i: Software Business. - Berlin, Heidelberg : Springer. - 9783642393358 - 9783642393365 ; 150, s. 79-89
  • Konferensbidrag (refereegranskat)abstract
    • To stay competitive, software development companies need to constantly evolve their software development practices. Companies that succeed in shortening customer feedback loops, minimizing the time between customer proof points and learn from customer usage data will be able to accelerate innovation and improve the accuracy of their development investments. While contemporary research reports on a number of well-established techniques for actively involving customers before and during development, there is less evidence on how to successfully use post-deployment customer data as input to the development process. As a result, companies invest significantly in development efforts without having an accurate way of continuously validating whether the functionality they develop is of direct value to customers once the product is taken into use. In this paper, we explore techniques for involving customers and for collecting customer data in pre-development, during development and in the post-deployment phase of software development. We do so by studying three software development companies involved in large-scale development of embedded software. We present an inventory of the techniques they use for collecting customer feedback and we outline the key opportunities for more effective development and evolution based on post-deployment data collection.
  •  
16.
  • Olsson Holmström, Helena, et al. (författare)
  • Towards Agile And Beyond : An empirical account on the challenges involved when advancing software development practices
  • 2014
  • Ingår i: XP 2014: Agile Processes in Software Engineering and Extreme Programming. - Cham : Springer. ; 179, s. 327-335
  • Konferensbidrag (refereegranskat)abstract
    • During the last decade, the vast majority of software companies have adopted agile development practices. Now companies are looking to move beyond agile and further advance their practices. In this paper, we report on the experiences of a company in the embedded systems domain that is adopting agile practices with the intention to move beyond agile and towards continuous deployment of software. Based on case study research involving group interviews and a web-based survey, we identify challenges in relation to (1) the adoption of agile practices, (2) testing practices, (3) continuous deployment, and (4) customer validation.
  •  
17.
  • Olsson Holmström, Helena, et al. (författare)
  • Towards Data-Driven Product Development : A Multiple Case Study on Post-Deployment Data Usage in Software-Intensive Embedded Systems
  • 2013
  • Ingår i: LESS 2013: Lean Enterprise Software and Systems. - Berlin, Heidelberg : Springer. ; , s. 152-164, s. 152-164
  • Konferensbidrag (refereegranskat)abstract
    • Today, products within telecommunication, transportation, consumer electronics, home automation, security etc. involve an increasing amount of software. As a result, organizations that have a tradition within hardware development are transforming to become software-intensive organizations. This implies products where software constitutes the majority of functionality, costs, future investments, and potential. While this shift poses a number of challenges, it brings with it opportunities as well. One of these opportunities is to collect product data in order to learn about product use, to inform product management decisions, and for improving already deployed products. In this paper, we focus on the opportunity to use post-deployment data, i.e. data that is generated while products are used, as a basis for product improvement and new product development. We do so by studying three software development companies involved in large-scale development of embedded software. In our study, we highlight limitations in post-deployment data usage and we conclude that post-deployment data remains an untapped resource for most companies. The contribution of the paper is two-fold. First, we present key opportunities for more effective product development based on post-deployment data usage. Second, we propose a framework for organizations interested in advancing their use of post-deployment product data.
  •  
18.
  • Sekitoleko, Nelson, et al. (författare)
  • Technical Dependency Challenges in Large-Scale Agile Software Development
  • 2014
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. - 9783319068619 ; 179, s. 46-61, s. 46-61
  • Konferensbidrag (refereegranskat)abstract
    • This qualitative study investigates challenges associated with technical dependencies and their communication.Such challenges frequently occur when agile practices are scaled to large-scale software development. The use of thematic analysis on semi-structured interviews revealed five challenges: planning, task prioritization, information exchange, code quality, and integration. More importantly, these challenges interact with one another and can lead to a domino effect or vicious circle. If an organization struggles with one challenge, it is likely that the other challenges become problematic as well. This situation can have a significant impact on process and product quality. Our recommendations focus on improving planning and knowledge sharing (with practices such as scrum-of-scrums, continuous integration, open space technology) to break the vicious circle, and to reestablish effective communication across teams, which will then enable large-scale companies to achieve the benefits of large-scale agility.
  •  
19.
  • Olsson, Helena Holmström, et al. (författare)
  • 2014
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. ; 182, s. 16-26
  • Konferensbidrag (refereegranskat)abstract
    • Most companies today experience a situation in which they are part of a complex business ecosystem of stakeholders that influence business outcomes. Especially for companies transitioning from selling products to becoming systems, solutions and services providers, this is causing a significant shift in their business strategies and relationships. Instead of focusing on internal processes, companies need to strategically position themselves in a dynamic network of actors to accelerate synergies and value co-creation. However, while this shift in business strategy is inevitable, it is not without challenges. An understanding for how to align internal, as well as external processes is critical, as well as a careful assessment on how to establish strategic partnerships in a dynamic network of interests. Based on on-going research, this paper outlines the emerging challenges that most software development companies face when adopting an ecosystem-driven approach, and the different mitigation strategies to manage these.
  •  
20.
  • Andersson, Bo (författare)
  • Mobile Computing from a Developer's Perspective: A 10-Year Review, 1999-2008
  • 2010
  • Ingår i: Perspectives in Business Informatics Research. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1348. - 9783642161001 - 9783642161018 ; 64, s. 220-233
  • Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
    • This review has examined research in mobile computing from a developer's perspective. The review was underpinned by the assumption that mobile computing has accentuated factors compared to stationary computing that ought to be managed to harness the possibilities of mobile computing. Applying a developer's perspective rendered a certain interest in design-oriented research, i.e. prescriptive research. Articles were categorised in three dimensions; the first dimension was developmental factors accentuated by mobile computing. The second dimension regarded the approach, if it was descriptive or prescriptive. The third dimension regarded the organisational settings, if the user were a member of the mobile workforce or not. The purpose of this study was to identify areas of inquiry in mobile computing from a design-oriented perspective. The findings revealed that research among accentuated factors of mobility is unevenly distributed and that research on the mobile workforce is under-represented. However, design-oriented research has a reasonable representation in the set of publications. The under-representation of research concerning the mobile workforce ought to have relevance for business informatics research. In conjunction with these findings some thoughts on future research areas are presented.
  •  
21.
  • Johansson, Björn, et al. (författare)
  • Deployment of Open Source ERPs: What Knowledge Does It Require?
  • 2012
  • Ingår i: Lecture Notes in Business Information Processing - Re-conceptualizing Enterprise Information Systems. - 1865-1348. - 9783642288265 ; 105, s. 75-91
  • Bokkapitel (refereegranskat)abstract
    • Abstract in UndeterminedEnterprise resource planning (ERP) systems are rapidly becoming a de facto standard in business activity. While large and medium-sized companies have the luxury to afford proprietary ERP solutions, small companies are struggling with resource poverty which maybe makes them consider available open source ERP products which are free from licensing fee. However, there is little knowledge available on open source ERP adoption in small companies. In order to spread some light on the first phase of ERP adoption, an experiment on open source ERP deployment was conducted. The experiment aimed at investigating what knowledge is required to successfully deploy open source ERP systems. The experiment was based on a research framework, the Technology Acceptance Model 2 (TAM2), and considered usability testing and user training and education factors. The factors of Perceived Ease of Use (PEOU) and Perceived Usefulness (PU) were used to determine the ease of deployment process, and the usefulness of the open source ERP deployed in relation to the made effort. The findings suggest that user with advanced computer skills perceive open source ERP deployment process as easy, and the deployed open source ERP was seen as being useful to organizations business activities.
  •  
22.
  •  
23.
  • Johansson, Björn, et al. (författare)
  • Feedback in the ERP Value-Chain: What Influence Has Thoughts about Competitive Advantage
  • 2013
  • Ingår i: Enterprise Information Systems of the Future: 6th IFIP WG 8.9 Working Conference, CONFENIS 2012, Ghent, Belgium, September 19-21, 2012, Revised Selected Papers. - 1865-1348. - 9783642366109 ; 139, s. 134-148
  • Bokkapitel (refereegranskat)abstract
    • Different opinions about whether an organization gains a competitiveadvantage (CA) from an enterprise resource planning (ERP) system exist. However, this paper describes another angle of the much reported competitive advantage discussion. The basic question in the paper concerns how thoughts about receiving competitive advantage from customizing ERPs influences feedback in ERP development. ERP development is described as having three stakeholders: an ERP vendor, an ERP partner or re-seller, and the ERP end-user or client. The question asked is: What influence has thoughts about receiving competitive advantage on the feedback related to requirements in ERPdevelopment? From a set of theoretical propositions eight scenarios are proposed. These scenarios are then illustrated from interviews with stakeholders in ERP development. From an initial research, evidence for six of these eight scenarios was uncovered. The main conclusion is that thoughts about competitive advantage seem to influence the feedback, but not really in the way that was initial assumed. Instead of, as was assumed, having a restrict view of providing feedback stakeholders seems to be more interested in having a working feedback loop in the ERP value-chain making the parties in a specific value-chain more interested in competing with other parties in other ERP valuechains.
  •  
24.
  •  
25.
  • Lindholm, Christin, et al. (författare)
  • A Case Study on Software Risk Analysis in Medical Device Development
  • 2012
  • Ingår i: Software Quality. Process Automation in Software Development/Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1348. - 9783642272127 ; 94, s. 143-158
  • Konferensbidrag (refereegranskat)abstract
    • Software failures in medical devices can lead to catastrophic situations. Therefore is it crucial to handle software related risks when developing medical devices. This paper presents the experiences gained from an ongoing case study with a medical device development organisation. This part of the study focuses on the two first steps of the risk management process, i.e. risk identification and risk analysis. The research is conducted as action research, with the aim of analysing and giving input to the organisation’s introduction of a software risk management process. The risk identification activities focus on user risks based on scenarios describing the expected use of the medical device in its target environment. Challenging problems have been found in the risk management process with respect to definition of the system boundary and system context, the use of scenarios as input to the risk identification and estimation of detectability used during risk assessment.
  •  
26.
  • Paulsson, Wipawee, et al. (författare)
  • Understanding the ERP system use in budgeting
  • 2013
  • Ingår i: Enterprise Information Systems of the Future : 6th IFIP WG 8.9 Working Conference, CONFENIS 2012, Ghent, Belgium, September 19-21, 2012, Revised Selected Papers - 6th IFIP WG 8.9 Working Conference, CONFENIS 2012, Ghent, Belgium, September 19-21, 2012, Revised Selected Papers. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1348. - 9783642366116 ; 139, s. 106-121
  • Konferensbidrag (refereegranskat)abstract
    • This paper investigates the enterprise resource planning (ERP) system use in budgeting in order to explain how and why ERP system are used or not used in budgeting practices. Budgeting is considered as a social phenomenon which requires flexibility for decision-making and integration for management controls. The analysis at the activity levels, guided by the concept of ‘conflict’ in structuration theory (ST), suggests that ERP systems impede flexibility in decision-making. However, the systems have the potential to facilitate integration in management controls. The analysis at the structural level, guided by the concept of ‘contradiction’ in ST, concludes that the ERP systems are not widely used in budgeting. This is because the systems support the integration function alone while budgeting assumes both roles. This paper offers the ERP system non-use explanation from an ulitarian perspective. Additionally, it calls for solutions to improve ERP use especially for the integration function.
  •  
27.
  • Staron, Miroslaw, 1977, et al. (författare)
  • Improving Completeness of Measurement Systems for Monitoring Software Development Workflows
  • 2013
  • Ingår i: Lecture Notes in Business Information Processing. - 1865-1348. - 9783642357015 ; 133, s. 230-243
  • Konferensbidrag (refereegranskat)abstract
    • Monitoring and controlling of software projects executed according to Lean or Agile software development requires, in principle, continuous measurement and use of indicators to monitor development areas and/or identify problem areas. Indicators are specific kind of measures with associated analysis models and decision criteria (ISO/IEC 15939). Indicating/highlighting problems in processes, is often used in Lean SW development and despite obvious benefits there are also dangers with improper use of indicators – using inadequate indicators can mislead the stakeholders towards sub-optimizations/erroneous decisions. In this paper we present a method for assessing completeness of information provided by measurement systems (i.e. both measures and indicators). The method is a variation of value stream mapping modeling with an application in a software development organization in the telecom domain. We also show the use of this method at one of the units of Ericsson where it was applied to provide stakeholders with an early warning system about upcoming problems with software quality.
  •  
28.
  • Wnuk, Krzysztof, et al. (författare)
  • Engineering Open Innovation – a Framework for Fostering Open Innovation
  • 2013
  • Ingår i: Software Business. From Physical Products to Software Services and Solutions/Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1348. - 9783642393358 ; 150, s. 48-59
  • Konferensbidrag (refereegranskat)abstract
    • Open innovation is an emerging innovation paradigm that can greatly accelerate technical knowledge innovation in software companies. The increasing importance and density of software in today’s products and services puts extensive pressure on excelling the discovery, description and execution of innovation. Despite that, software engineering literature lacks methods, tools and frameworks for full exploitation of technological advantages that open innovation can bring. This paper proposes a software engineering framework, designed to foster open inno- vation by designing and tailoring appropriate software engineering meth- ods and tools. Furthermore, this paper discusses the methodological and process dimensions and outlines challenge areas that should be reviewed when transitioning to software engineering driven open innovation.
  •  
29.
  • Wnuk, Krzysztof, et al. (författare)
  • Evaluating the Governance Model of Hardware-Dependent Software Ecosystems – A Case Study of the Axis Ecosystem
  • 2014
  • Ingår i: Lecture Notes in Business Information Processing. - 1865-1348. ; 182, s. 212-226
  • Konferensbidrag (refereegranskat)abstract
    • Ecosystem governance becomes gradually more relevant for a set of companies or actors characterized by symbiotic relations evolved on the top of a technological platform, i.e. a software ecosystem. In this study, we focus on the governance of a hardware-dependent software ecosystem. More specifically, we evaluate the governance model applied by Axis, a network video and surveillance camera producer, that is the platform owner and orchestrator of the Application Development Partner (ADP) software ecosystem. We conduct an exploratory case study col- lecting data from observations and interviews and apply the governance model for prevention and improvement of the software ecosystem health proposed by Jansen and Cusumano. Our results reveal that although the governance actions do not address the majority of their governance model, the ADP ecosystem is considered a growing ecosystem provid- ing opportunities for its actors. This can be explained by the fact that Axis, as the orchestrator and the platform owner, does not address the productivity and robustness of the ecosystem adequately, but has a net- work of vendors and resellers to support it and some of the governance activities (e.g. communication) are achieved by non-formal means. The current governance model does not take into consideration.
  •  
30.
  • Wnuk, Krzysztof, et al. (författare)
  • Requirements Scoping Visualization for Project Management
  • 2011
  • Ingår i: Software Business. - 1865-1348. ; 80, s. 168-180
  • Konferensbidrag (refereegranskat)abstract
    • Determining requirements process efficiency, and measuring the corresponding monetary impacts, is a challenging but necessary aspect of project management. In this paper, we perform an independent analysis of scoping decisions from a large industrial project with the goal of providing visualizations that facilitate investigations of process efficiency, agility, and the effects of scoping decisions. The visualizations proposed in this paper can be used to analyze scoping dynamics and support process management decisions on a quantitative rather than a qualitative basis.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-30 av 30
Typ av publikation
konferensbidrag (26)
bokkapitel (4)
Typ av innehåll
refereegranskat (29)
övrigt vetenskapligt/konstnärligt (1)
Författare/redaktör
Bosch, Jan, 1967 (13)
Johansson, Björn (5)
Olsson Holmström, He ... (4)
Poels, Geert (3)
Wnuk, Krzysztof (3)
Staron, Miroslaw, 19 ... (2)
visa fler...
Martini, Antonio, 19 ... (2)
Runeson, Per (2)
Eklund, Ulrik, 1967 (2)
Olsson, Helena Holms ... (2)
Hartmann, H. (1)
Höst, Martin (1)
Chaudron, Michel, 19 ... (1)
Berger, Christian, 1 ... (1)
Tichy, Matthias, 197 ... (1)
Meding, Wilhelm (1)
Knauss, Eric, 1977 (1)
Andersson, Bo (1)
Sandberg, Anna (1)
Atem de Carvalho, Ro ... (1)
Nilsson, Agneta, 196 ... (1)
Olsson Holmström, He ... (1)
Backlund, Emil, 1988 (1)
Bolle, Mikael, 1985 (1)
Koch, Christian, 195 ... (1)
Bosch, Petra, 1971 (1)
Mirijamdotter, Anita (1)
Biffl, Stefan (1)
Winkler, Dietmar (1)
Björk, Jens (1)
Ljungblad, Jens (1)
Holmén Notander, Jes ... (1)
Pareto, Lars, 1966 (1)
Callele, David (1)
Chaudhry, Sohail (1)
Lindholm, Christin (1)
Evbota, Felix (1)
Kajtazi, Miranda (1)
Kotlarsky, Julia (1)
Haftor, Darek M. (1)
Møller, Charles (1)
Koroliov, Vadim (1)
Kobylinski, A (1)
Sobczak, A (1)
Oshri, Ilan (1)
Willcocks, LeslieP (1)
Jacobsen, Kim (1)
Moum, Anita (1)
Margaria, T. (1)
Manikas, Konstantino ... (1)
visa färre...
Lärosäte
Chalmers tekniska högskola (17)
Lunds universitet (11)
Göteborgs universitet (7)
Malmö universitet (5)
Linnéuniversitetet (2)
Stockholms universitet (1)
Språk
Engelska (30)
Forskningsämne (UKÄ/SCB)
Naturvetenskap (23)
Samhällsvetenskap (8)
Teknik (3)

År

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy