Since 2006 we have worked closely with software engineering industry to create efficient and effective measurement processes. Since then we have succeeded in creating a framework for measurement systems based on the standard ISO/IEC 15939:2007. The framework is used at a number of units of Ericsson and is described in the following publications:
Staron, Miroslaw; Meding, Wilhelm; Nilsson, Christer: A framework for developing measurement systems and its industrial evaluation. Information and Software Technology, 51 (April) pp. 721-737 - this paper describes a set of simple technology solutions which we use for automation of our measurement systems.
Pandazo, Kosta; Shollo, Arisa; Staron, Miroslaw; Meding, Wilhelm: Presenting Software Metrics Indicators - A Case Study. Proceedings of the 20th International Conference on Software Product and Process Measurement (MENSURA), 20 (1) - if you look for information about how we communicate our results for stakeholders, please do take a look at this paper.
Staron, Miroslaw; Meding, Wilhelm: A Modeling Language for Specifying and Visualizing Measurement Systems for Software Metr ics. Tampere University of Technology research report, Nordic workhop on MDE, 2009 (5) pp. 300-315 - if you look for the methods which we use to be efficient when developing measurement systems, here is the paper you should read.
Staron, Miroslaw; Meding, Wilhelm: Ensuring Reliability of Information Provided by Measurement Systems. Software Process and Product Measurement, pp. 1-16 - if you want to know how we make our measurement system self-diagnose themselves, here is our work on information quality.
Staron, Miroslaw; Meding, Wilhelm: Using Models to Develop Measurement Systems: A Method and Its Industrial Use. International Conferences IWSM 2009 and Mensura 2009, 5891/2009 pp. 212-226 - if you are interested in the process which we follow in order to create measurement systems, please take a look here.
Staron, M. ; Meding, W. ; Karlsson, G. et al. (2010). Developing measurement systems: an industrial case study. Journal of Software Maintenance and Evolution: Research and Practice. Wiley - is another paper which describes our processes.
... and in a number of other papers available here
Predictions were the first aspect of our work at Ericsson and after a number of trials we could develop predictions that are about 90% accurate (for large software projects). The predictions are described in the following publications:
Staron, Miroslaw; Meding, W.; Soderqvist, B.: A method for forecasting defect backlog in large streamline software development projects and its industrial evaluation. Information and Software Technology, 52 (10) pp. 1069-1079 - this is the most recent paper describing the algorithms mentioned above. It is mainly for practitioners, but researchers can learn quite a big deal of it too.
Staron, Miroslaw; Meding, Wilhelm: Defect Inflow Prediction in Large Software Projects. e-Informatica Software Engineering Journal, 4 (1) pp. 1-23 - describes how we can predict both the short and the long term defect inflow in large projects. However, this is not a work in the context of Agile Software Development.
Staron, Miroslaw; Meding, Wilhelm: Predicting Weekly Defect Inflow in Large Software Projects based on Project Planning and Test Status. Information and Software Technology, 50 (7-8) pp. 782-796 - this, however, is a paper for practitioners describing how to predict defect inflow using statics.
Staron, Miroslaw; Meding, Wilhelm: Predicting Monthly Defect Inflow in Large Software Projects – An Industrial Case Study. Industry Track Proceedings of the 27 International Symposium on Software Reliability Engineering, pp. 23-30.
Staron, Miroslaw; Meding, Wilhelm: Short-term defect inflow prediction in large software project - an initial evaluation. International Conference on Empirical Assessment in Software Engineering (EASE), 2007 (1) pp. 18-27.
In short, we use simple algorithms and qualitative data (empirical relationships) to predict defect inflow and defect backlog in large LEAN and Agile software projects. The algorithm and the associated measurement system is used in a number of units of Ericsson and has proved itself to be a very good decision support tool.
Some of my previous works on software quality are related to the workshop of software quality at MODELS:
2nd Workshop on Quality in Modeling. Miroslaw Staron [editor(s)].
Pareto, Lars; Lange, Christian; Mohagheghi, Parastoo; Dehlen, Vegard; Staron, Miroslaw; Bohours, Cédric; Weil, Frank; Bastarrica, Cecilia; Rivas, Sebastián; Rossel, Pedro; Kuzniarz, Ludwik: Towards a Unified Quality Model for Models- A Working Session at the 2nd workshop on Quality in Modeling. ISBN/ISSN: ISSN: 1654-4870
Kuzniarz, L.; Staron, Miroslaw: Inconsistencies in Student Designs. International workshop on Consistency Problems in UML, UML 2004, Lisbon - this paper showed itself to be rather inspirational with a number of citations. It shows how one makes simple yet very destructive mistakes in modelling; was valid in 2004 and still is in 2010 (IMHO)
... and in a number of other papers available here
Models are in the cornerstone of almost all engineering disciplines as they allow reasoning about things in a simplified way. Some of my work related to that are described in the following papers:
Staron, Miroslaw; Kuzniarz, Ludwik; Wohlin, Claes: Empirical assessment of using stereotypes to improve comprehension of UML models: A set of experiments. Journal of Systems and Software, 79 (5) pp. 727-742.
Staron, Miroslaw: Adopting MDD in Industry - A Case Study at Two Companies. ACM/IEEE 9th International Conference on Model Driven Engineering Languages and Systems, 4199 (1) pp. 57-72.
Staron, Miroslaw: Sizing Stereotypes and Profiles in UML. Model Size Metrics Workshop at MODELS, 2007 (1)
Staron, Miroslaw; Kuzniarz, Ludwik: Properties of Stereotypes from the Perspective of Their Role in Designs. 8th International Conference on Model Driven Engineering Languages and Systems (formerly "UML"), Lecture Notes in Computer Science , pp. 201-215
Staron, Miroslaw; Kuzniarz, Ludwik; Wallin, Ludwik: A Case Study on Industrial MDA Realization - Determinants of Effectiveness. Nordic Journal of Computing, 11 (3) pp. 254-278.
... and in a number of other papers available here
Experimentation used to be my favourite research method in the past (still is if I have the opportunity to do it), so I managed to make a few reflections on the process of experimentation, which is described in the following papers.
Staron, Miroslaw: Using Experiments in Software Engineering as an Auxiliary Tool for Teaching ? A Qualitative Evaluation from the Perspective of Students? Learn-ing Process. 27th International Conference on Software Engineering (ICSE), 2007 (1)
Staron, Miroslaw: Using Students as Subjects in Experiments – A Quantitative Analysis of the Influence of Experimentation on Students’ Learning Process . 20th Conference on Software Engineering Education and Training, 2007 (1) pp. 221-228. ISBN/ISSN: 0-7695-2893
Staron, Miroslaw: Using Experiments in Software Engineering as an Auxiliary Tool for Teaching ? A Perspective of Students? Learning Process. 6th Conference on Software Engineering Research and Practice in Sweden, pp. 29-38. ISBN/ISSN: 91-7264-198-3
... and in a number of other papers available here
In order to produce useful research results we work based according the interactive and collaborative research approach.
Our research is interactive since we work closely with companies, solving the current problems in short time.
Our reserach is collaborative since we work together with practitioners, we work on-site of the company and we listen to the needs of our industrial partners.