Change search
Refine search result
1 - 6 of 6
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Rows per page
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sort
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
Select
The maximal number of hits you can export is 250. When you want to export more records please use the Create feeds function.
  • 1.
    Barney, Sebastian
    et al.
    Blekinge Institute of Technology, School of Computing.
    Khurum, Mahvish
    Blekinge Institute of Technology, School of Computing.
    Petersen, Kai
    Blekinge Institute of Technology, School of Computing.
    Unterkalmsteiner, Michael
    Blekinge Institute of Technology, School of Computing.
    jabangwe, Ronald
    Blekinge Institute of Technology, School of Computing.
    Improving Students With Rubric-Based Self-Assessment and Oral Feedback2012In: IEEE Transactions on Education, ISSN 0018-9359, Vol. 55, no 3, p. 319-325Article in journal (Refereed)
    Abstract [en]

    Rubrics and oral feedback are approaches to help students improve performance and meet learning outcomes. However, their effect on the actual improvement achieved is inconclusive. This paper evaluates the effect of rubrics and oral feedback on student learning outcomes. An experiment was conducted in a software engineering course on requirements engineering, using the two approaches in course assignments. Both approaches led to statistically significant improvements, though no material improvement (i.e., a change by more than one grade) was achieved. The rubrics led to a significant decrease in the number of complaints and questions regarding grades.

  • 2.
    Khurum, Mahvish
    et al.
    Blekinge Institute of Technology, School of Computing.
    Gorschek, Tony
    Blekinge Institute of Technology, School of Computing.
    Wilson, Magnus
    The software value map—an exhaustive collection of value aspects for the development of software intensive products2013In: Journal of Software Maintenance and Evolution: Research and Practice, ISSN 1532-060X, E-ISSN 1532-0618, Vol. 25, no 7, p. 711-741Article in journal (Refereed)
    Abstract [en]

    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.

  • 3.
    Khurum, Mahvish
    et al.
    Blekinge Institute of Technology, School of Computing.
    Uppalapati,, Niroopa
    Chowdary, Ramya
    Software Requirements Triage and Selection: State-of-the-Art and State-of-Practice2012Conference paper (Refereed)
    Abstract [en]

    Software requirement triage and selection in market- driven requirements engineering is a crucial activity for the success of a project, product and company. This paper presents state-of-the- art and state-of-practice in requirements triage and selection through systematic literature review and an industrial survey. Industry practitioner can read solutions that have been proposed in literature and most applicable challenges and factors considered today and factors to be considered ideally to address the challenges, which have been collected through the survey. For researchers, the results show which challenges still needs to be addressed.

  • 4. Moe, NilsBrede
    et al.
    Barney, Sebastian
    Blekinge Institute of Technology, School of Computing.
    Aurum, Aybüe
    Khurum, Mahvish
    Blekinge Institute of Technology, School of Computing.
    Wohlin, Claes
    Blekinge Institute of Technology, School of Computing.
    Barney, Hamish
    Gorschek, Tony
    Blekinge Institute of Technology, School of Computing.
    Winata, Martha
    Fostering and sustaining innovation in a Fast Growing Agile Company2012In: Lecture Notes in Computer Science, Madrid: Springer , 2012, Vol. 7343, p. 160-174Conference paper (Refereed)
    Abstract [en]

    Sustaining innovation in a fast growing software development company is difficult. As organisations grow, peoples' focus often changes from the big picture of the product being developed to the specific role they fill. This paper presents two complementary approaches that were successfully used to support continued developer-driven innovation in a rapidly growing Australian agile software development company. The method "FedEx TM Day" gives developers one day to showcase a proof of concept they believe should be part of the product, while the method "20% Time" allows more ambitious projects to be undertaken. Given the right setting and management support, the two approaches can support and improve bottom-up innovation in organizations.

  • 5. Penzenstadler, Birgit
    et al.
    Khurum, Mahvish
    Blekinge Institute of Technology, School of Computing.
    Petersen, Kai
    Blekinge Institute of Technology, School of Computing.
    Towards Incorporating Sustainability while Taking Software Product Management Decisions2013Conference paper (Refereed)
    Abstract [en]

    Software product managers are missing guidelines on how to incorporate di erent dimensions of sustainability in software product management and requirements selection decision-making. This is a challenge because considering sustainability perspective while selecting requirements has become a major objective for software product development companies; however, it is unclear how to support it during complex product management decision-making. In this paper, we identify the value aspects related to sustainability for software requirements selection. An exemplary dialogue between a consultant and a product manager illustrates how the proposed approach can be used while taking product management and requirements selection decisions. Our contribution provides software product managers with guidance on how toincorporate value aspects related to sustainability while taking software product management and requirements selection decisions.

  • 6.
    Petersen, Kai
    et al.
    Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
    Khurum, Mahvish
    Blekinge Institute of Technology, Faculty of Computing, Department of Software Engineering.
    Angelis, Lefteris
    Reasons for bottlenecks in very large-scale system of systems development2014In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 56, no 10, p. 1403-1420Article in journal (Refereed)
    Abstract [en]

    Context: System of systems (SOS) is a set or arrangement of systems that results when independent and useful systems are to be incorporated into a larger system that delivers unique capabilities. Our investigation showed that the development life cycle (i.e. the activities transforming requirements into design, code, test cases, and releases) in SoS is more prone to bottlenecks in comparison to single systems. Objective: The objective of the research is to identify reasons for bottlenecks in SoS, prioritize their significance according to their effect on bottlenecks, and compare them with respect to different roles and different perspectives, i.e. SoS view (concerned with integration of systems), and systems view (concerned with system development and delivery). Method: The research method used is a case study at Ericsson AB. Results: Results show that the most significant reasons for bottlenecks are related to requirements engineering. All the different roles agree on the significance of requirements related factors. However, there are also disagreements between the roles, in particular with respect to quality related reasons. Quality related hinders are primarily observed and highly prioritized by quality assurance responsibles. Furthermore, SoS view and system view perceive different hinders, and prioritize them differently. Conclusion: We conclude that solutions for requirements engineering in SoS context are needed, quality awareness in the organization has to be achieved end to end, and views between SoS and system view need to be aligned to avoid sub optimization in improvements.

1 - 6 of 6
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf