Marjo Kauppinen

ORCID: 0000-0002-8794-6792
Publications
Citations
Views
---
Saved
---
About
Contact & Profiles
Research Areas
  • Software Engineering Techniques and Practices
  • Software Engineering Research
  • Advanced Software Engineering Methodologies
  • Information Technology Governance and Strategy
  • Open Source Software Innovations
  • Service and Product Innovation
  • Big Data and Business Intelligence
  • Ethics and Social Impacts of AI
  • Service-Oriented Architecture and Web Services
  • Software System Performance and Reliability
  • Explainable Artificial Intelligence (XAI)
  • Usability and User Interface Design
  • Business Strategy and Innovation
  • ERP Systems Implementation and Impact
  • Digital Platforms and Economics
  • Business Process Modeling and Analysis
  • Software Reliability and Analysis Research
  • Innovation and Socioeconomic Development
  • Innovative Approaches in Technology and Social Development
  • Product Development and Customization
  • Customer Service Quality and Loyalty
  • Technology Assessment and Management
  • Adversarial Robustness in Machine Learning
  • Technology Adoption and User Behaviour
  • Artificial Intelligence in Healthcare and Education

Aalto University
2015-2024

University of Helsinki
2009

Helsinki Institute for Information Technology
2009

Recent studies have highlighted transparency and explainability as important quality requirements of AI systems. However, there are still relatively few case that describe the current state defining these in practice. This study consisted two phases. The first goal our was to explore what ethical guidelines organizations defined for development transparent explainable systems then we investigated how can be In phase, analyzed 16 representing different industries public sector. Then,...

10.1016/j.infsof.2023.107197 article EN cc-by Information and Software Technology 2023-03-08

User involvement is the key concept in development of useful and usable systems has positive effects on system success user satisfaction. This paper reports results interviews a survey conducted to investigate role defining requirements projects. The involved 18 software practitioners working related projects 13 companies Finland. In addition, eight three were interviewed. By combining qualitative statistical analysis, we examine how users are influences analysis shows that, although it rare...

10.1109/re.2005.72 article EN 2005-01-01

It is critical to the success of a system that appropriate and representative users are involved in development work. However, process identifying selecting has not been focus research. In this paper, we describe relevant specifically for field studies. Characterization sampling discussed. addition, way describing user groups suggested. Finally, summarize results from seven case studies six different companies. The show developers tend underestimate diversity systematic helps identify...

10.1145/1028014.1028060 article EN 2004-10-23

Abstract In a company producing off‐the‐shelf software for mass markets, the future development steps of products cannot be negotiated with one or few customers. The decisions concerning priorities requirements must made within company, developer bearing all financial risks included. This means that finding right is important. However, prioritization recognized as difficult activity in product development. literature offers methods prioritization, but many authors report practices companies...

10.1002/spip.249 article EN Software Process Improvement and Practice 2006-01-01

An increasing number of organizations are interested in binding requirements and testing more closely together. Based on a series practitioner interviews conducted five Finnish organizations, this paper presents set good practices that can be applied to create stronger link between engineering testing. These include early tester participation particularly reviews, setting up traceability policies, taking feature requests from testers into account, linking personnel with requirement owners....

10.1109/re.2008.30 article EN 2008-09-01

The rise of agile software development methods has led to the abandonment many traditional practices especially in requirements engineering (RE). Agile RE is still a relatively new research area and growing use large projects forcing companies look for more formal RE. This paper describes experiences gained from case study project. goal this was explore how prototyping can solve challenges Our findings indicate that while help with some such as lack documentation, motivation work poor...

10.1109/re.2015.7320450 article EN 2015-08-01

Companies moving into the software product business and growing in size face new challenges that cannot be tackled completely with old practices. For example, future development steps of off-the-shelf products negotiated just one or a few customers any more. This means practitioners should able to take aspects such as their company's own strategy available market information more effectively account decision-making. However, usually company unit is so high level gap single requirements...

10.1109/re.2005.36 article EN 2005-01-01

Under today's fiercely competitive conditions, companies are seeking new means to develop innovative products that satisfy customer and user needs. In order understand how requirements engineering (RE) can support innovations, we observed RE activities in six Finnish companies. Our observations indicate play a vital role the development of products. We identified three main opportunities for innovations: 1) discovering hidden needs, 2) inventing product features these 3) supporting feature...

10.1109/re.2007.47 article EN 2007-10-01

Requirements engineering and testing offer two complementary views of system development, can, therefore, benefit from each other. This paper describes the lessons Metso learned jointly improving requirements processes. The goal process improvement was to increase quality R&D work. new processes were piloted in an project. usage removed risk doing double work, improved visibility project status effectiveness experiences pilot suggest that good results mainly due linking concurrently at...

10.1109/apsec.2009.62 article EN 2009-12-01

Introducing requirements engineering appears to involve a cultural change in organizations. Such requires that are defined and managed systematically, not only from technical point of view, but also the customers' users' points view. This paper describes experiences gained four Finnish organizations have started introduce their product development. The goal this study was evaluate which factors support, prevent, change. Linking business goals via user needs one key improvement actions...

10.1109/icre.2002.1048504 article EN 2003-06-25

Marketing experts emphasize that the creation of superior customer value is a key element for companies' success. Understanding how to create customers, however, not trivial in practice. The purpose this paper analyze role requirements engineering (RE) creation. describes experiences gained from six Finnish companies develop software-intensive products and services global markets. In practice, focus RE activities mainly on product features. Customer is, more than developing competitive set...

10.1109/re.2009.35 article EN 2009-08-01

Usability and requirements engineering both provide means for discovering, analyzing, fulfilling users' needs. In practice, it is difficult to manage control user-centered design system development processes separately. Based on a case study conducted in two software product companies, we have aimed understand the role of usability specialists (RE) process. Our findings indicate that still often seen as user interface instead more comprehensive characteristic product. Therefore, had...

10.1109/re.2009.37 article EN 2009-08-01

It is difficult to draw conclusions about the prudence of antibiotic use in different hospitals by directly comparing usage figures. We present a patient case-mix adjustment model rank while taking characteristics into account.Data on were collected during national healthcare-associated infection (HAI) prevalence survey 2005 Finland all 5 tertiary care, 15 secondary care and 10 (25% 40) other acute hospitals. The antibiotics was measured using use-days/100 patient-days 7day period patients...

10.1093/jac/dkr333 article EN Journal of Antimicrobial Chemotherapy 2011-08-16

Roadmapping has been recognized as a critical activity for combining business strategy with release planning. Furthermore, the marketing literature placed increasing emphasis on importance of understanding customers' processes and customer value. This paper presents an action research study roadmapping problems two software product companies. The key findings were that knowledge was fragmented across different functions companies neglected service development. To solve these problems,...

10.1109/re.2011.6051662 article EN 2011-08-01
Coming Soon ...