Change search
Link to record
Permanent link

Direct link
BETA
Khurum, Mahvish
Publications (6 of 6) Show all publications
Petersen, K., Khurum, M. & Angelis, L. (2014). Reasons for bottlenecks in very large-scale system of systems development. Information and Software Technology, 56(10), 1403-1420
Open this publication in new window or tab >>Reasons for bottlenecks in very large-scale system of systems development
2014 (English)In: Information and Software Technology, ISSN 0950-5849, E-ISSN 1873-6025, Vol. 56, no 10, p. 1403-1420Article in journal (Refereed) Published
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.

Place, publisher, year, edition, pages
Elsevier, 2014
Keywords
System of systems development, Bottlenecks, Case study
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-6587 (URN)10.1016/j.infsof.2014.05.004 (DOI)000340850700015 ()oai:bth.se:forskinfoB3C9112308A9503CC1257D6D00383E30 (Local ID)oai:bth.se:forskinfoB3C9112308A9503CC1257D6D00383E30 (Archive number)oai:bth.se:forskinfoB3C9112308A9503CC1257D6D00383E30 (OAI)
Available from: 2014-10-10 Created: 2014-10-10 Last updated: 2018-01-11Bibliographically approved
Khurum, M., Gorschek, T. & Wilson, M. (2013). The software value map—an exhaustive collection of value aspects for the development of software intensive products. Journal of Software Maintenance and Evolution: Research and Practice, 25(7), 711-741
Open this publication in new window or tab >>The software value map—an exhaustive collection of value aspects for the development of software intensive products
2013 (English)In: 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) Published
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.

Place, publisher, year, edition, pages
Wiley, 2013
Keywords
value-based software engineering, decision-support, software value, software value analysis, software value map, requirements engineering, technology and software product management, product customization, software engineering management, value taxonomy
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-6801 (URN)10.1002/smr.1560 (DOI)000326241300003 ()oai:bth.se:forskinfo66300B94FA97AB14C1257ACF006CE6EE (Local ID)oai:bth.se:forskinfo66300B94FA97AB14C1257ACF006CE6EE (Archive number)oai:bth.se:forskinfo66300B94FA97AB14C1257ACF006CE6EE (OAI)
Available from: 2013-12-17 Created: 2012-12-09 Last updated: 2018-01-11Bibliographically approved
Penzenstadler, B., Khurum, M. & Petersen, K. (2013). Towards Incorporating Sustainability while Taking Software Product Management Decisions. In: : . Paper presented at International Workshop on Software Product Management (IWSPM 2013). Essen: University of Duisburg-Essen
Open this publication in new window or tab >>Towards Incorporating Sustainability while Taking Software Product Management Decisions
2013 (English)Conference paper, Published 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.

Place, publisher, year, edition, pages
Essen: University of Duisburg-Essen, 2013
Keywords
Sustainability, value-based software engineering, decision-making, software product management
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-6957 (URN)oai:bth.se:forskinfo88A08853A831110CC1257B950033475D (Local ID)oai:bth.se:forskinfo88A08853A831110CC1257B950033475D (Archive number)oai:bth.se:forskinfo88A08853A831110CC1257B950033475D (OAI)
Conference
International Workshop on Software Product Management (IWSPM 2013)
Available from: 2013-06-27 Created: 2013-06-25 Last updated: 2018-01-11Bibliographically approved
Moe, N., Barney, S., Aurum, A., Khurum, M., Wohlin, C., Barney, H., . . . Winata, M. (2012). Fostering and sustaining innovation in a Fast Growing Agile Company. In: Lecture Notes in Computer Science: . Paper presented at 13th International Conference on Product-Focused Software Process Improvement, PROFES (pp. 160-174). Madrid: Springer, 7343
Open this publication in new window or tab >>Fostering and sustaining innovation in a Fast Growing Agile Company
Show others...
2012 (English)In: Lecture Notes in Computer Science, Madrid: Springer , 2012, Vol. 7343, p. 160-174Conference paper, Published 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.

Place, publisher, year, edition, pages
Madrid: Springer, 2012
Keywords
20% Time, agile software development, case study, empirical, FedEx Day, innovation, scrum, XP
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-7062 (URN)10.1007/978-3-642-31063-8_13 (DOI)oai:bth.se:forskinfoC661A1CB1695B6B7C1257AC6004FAC36 (Local ID)9783642310621 (ISBN)oai:bth.se:forskinfoC661A1CB1695B6B7C1257AC6004FAC36 (Archive number)oai:bth.se:forskinfoC661A1CB1695B6B7C1257AC6004FAC36 (OAI)
Conference
13th International Conference on Product-Focused Software Process Improvement, PROFES
Available from: 2012-12-19 Created: 2012-11-30 Last updated: 2018-01-11Bibliographically approved
Barney, S., Khurum, M., Petersen, K., Unterkalmsteiner, M. & jabangwe, R. (2012). Improving Students With Rubric-Based Self-Assessment and Oral Feedback. IEEE Transactions on Education, 55(3), 319-325
Open this publication in new window or tab >>Improving Students With Rubric-Based Self-Assessment and Oral Feedback
Show others...
2012 (English)In: IEEE Transactions on Education, ISSN 0018-9359, Vol. 55, no 3, p. 319-325Article in journal (Refereed) Published
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.

Place, publisher, year, edition, pages
IEEE, 2012
Keywords
education rubrics, requirements engineering
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-7157 (URN)10.1109/TE.2011.2172981 (DOI)000307191400002 ()oai:bth.se:forskinfoACBB1E5F4B5ACEECC125797F0069C846 (Local ID)oai:bth.se:forskinfoACBB1E5F4B5ACEECC125797F0069C846 (Archive number)oai:bth.se:forskinfoACBB1E5F4B5ACEECC125797F0069C846 (OAI)
External cooperation:
Available from: 2012-11-28 Created: 2012-01-08 Last updated: 2018-01-11Bibliographically approved
Khurum, M., Uppalapati,, N. & Chowdary, R. (2012). Software Requirements Triage and Selection: State-of-the-Art and State-of-Practice. In: : . Paper presented at 19th Asian Pacific Software Engineering Conference (APSEC). Hong Kong: IEEE Computer Society
Open this publication in new window or tab >>Software Requirements Triage and Selection: State-of-the-Art and State-of-Practice
2012 (English)Conference paper, Published 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.

Place, publisher, year, edition, pages
Hong Kong: IEEE Computer Society, 2012
Keywords
software requirements triage
National Category
Software Engineering
Identifiers
urn:nbn:se:bth-7091 (URN)oai:bth.se:forskinfo5F4B326B04A84322C1257ACF006D4556 (Local ID)oai:bth.se:forskinfo5F4B326B04A84322C1257ACF006D4556 (Archive number)oai:bth.se:forskinfo5F4B326B04A84322C1257ACF006D4556 (OAI)
Conference
19th Asian Pacific Software Engineering Conference (APSEC)
Available from: 2012-12-12 Created: 2012-12-09 Last updated: 2018-01-11Bibliographically approved
Organisations

Search in DiVA

Show all publications