Paweł Janczarek

Bio: Paweł Janczarek is an academic researcher from Warsaw University of Technology. The author has contributed to research in topics: Software construction & Software project management. The author has an hindex of 3, co-authored 4 publications receiving 31 citations.

Investigating software testing and maintenance reports: Case study

Abstract: Context Although many papers have been published on software development and defect prediction techniques, problem reports in real projects quite often differ from those described in the literature. Hence, there is still a need for deeper exploration of case studies from industry. Objective The aim of this study is to present the impact of fine-grained problem reports on improving evaluation of testing and maintenance processes. It is targeted at projects involving several releases and complex schemes of problem handling. This is based on our experience gained while monitoring several commercial projects. Method Extracting certain features from detailed problem reports, we derive various measures and present analysis models which characterize and visualize the effectiveness of testing and problem resolution processes. The considered reports describe types of problems (e.g. defects), their locations in project versions and software modules, ways of their resolution, etc. The performed analysis is related to eleven projects developed in the same company. This study is an exploratory research with some explanatory features. Moreover, having identified some drawbacks, we present extensions of problem reports and their analysis which have been verified in another industrial case study project. Results Fine-grained (accurate) problem handling reports provide a wider scope of possible measures to assess the relevant development processes. This is helpful in controlling single projects (local perspective) as well as in managing these processes in the whole company (global perspective). Conclusion Detailed problem handling reports extend the space and quality of statistical analysis, they provide significant enhancement in evaluation and refinement of software development processes as well as in reliability prediction.

Analysing problem handling schemes in software projects

Abstract: Context Although many papers have been published on software development and maintenance processes, there is still a need for deeper exploration of software repositories related to real projects to evaluate these processes. Objective The aim of this study is to present and evaluate different schemes of handling problems (bugs) during software development and maintenance. It is based on exploring information comprised in various software repositories. Method Having analysed the contents of software repositories we have introduced a graph model describing problem handling processes and a scheme of analysing the effectiveness of these processes. This analysis is targeted at structural, throughput and timing aspects. The presented methodology has been verified on real data comprised in open source and commercial projects. Moreover, having identified some drawbacks and anomalies, we point out possible improvements in problem reports and their management. Results Detailed software repositories provide a wider scope of possible measures to assess the relevant problem handling processes. This is helpful in controlling single projects (local perspective) as well as in managing these processes in the whole company (global perspective). Conclusion Detailed problem handling reports extend the space and quality of statistical analysis, the presented graph model with proposed metrics provides a useful tool to evaluate and refine problem resolution schemes.

Monitoring Software Development and Usage

Abstract: This paper presents the methodology of monitoring software testing and debugging processes during system development and usage. We concentrate on control metrics related to these problems and consider two development models related to practical projects. Basing on the collected data we show the usefulness of the presented approach to control software quality, the effectiveness of development and maintenance processes. We also outline possible improvements in monitoring schemes. Streszczenie. Artykul przedstawia metodyke monitorowania procesow testowania i korekcji bledow w fazie rozwijania i eksploatacji oprogramowania. Praca koncertuje sie na miarach opisujących te procesy w odniesieniu do dwu modeli wytwarzania oprogramowania wykorzystywanych we wdrozonych projektach. Bazując na zebranych danych przedstawiono uzytecznośc opracowanego podejścia w kontrolowaniu jakości oprogramowania oraz efektywności procesow jego wytwarzania i utrzymania. Wskazano rowniez mozliwości poprawienia efektywności procesow monitorowania. (Monitorowanie rozwijania i eksploatacji oprogramowania).

Managing Complex Software Projects

Abstract: In the paper we present our experience with develop ment and maintenance of complex software systems. In particular, we concen trate on monitoring related development, testing and debugging processes. We ha v analyzed the contents of collected reports (provided by different tools) cov ering many projects and defined several metrics and statistics helpful in managing complex projects and achieving high quality software. Moreover, we have identified lacking data which could improve these processes.

Strategies to Manage Enterprise Information Technology Projects

Abstract: Strategies to Manage Enterprise Information Technology Projects by

Software Reliability for Agile Testing

Abstract: It is known that quantitative measures for the reliability of software systems can be derived from software reliability models, and, as such, support the product development process. Over the past four decades, research activities in this area have been performed. As a result, many software reliability models have been proposed. It was shown that, once these models reach a certain level of convergence, it can enable the developer to release the software and stop software testing accordingly. Criteria to determine the optimal testing time include the number of remaining errors, failure rate, reliability requirements, or total system cost. In this paper, we present our results in predicting the reliability of software for agile testing environments. We seek to model this way of working by extending the Jelinski-Moranda model to a "stack" of feature-specific models, assuming that the bugs are labeled with the features they belong to. In order to demonstrate the extended model, two use cases are presented. The questions to be answered in these two cases are: how many software bugs remain in the software and should one decide to stop testing the software?.

Analysing problem handling schemes in software projects

Abstract: Context Although many papers have been published on software development and maintenance processes, there is still a need for deeper exploration of software repositories related to real projects to evaluate these processes. Objective The aim of this study is to present and evaluate different schemes of handling problems (bugs) during software development and maintenance. It is based on exploring information comprised in various software repositories. Method Having analysed the contents of software repositories we have introduced a graph model describing problem handling processes and a scheme of analysing the effectiveness of these processes. This analysis is targeted at structural, throughput and timing aspects. The presented methodology has been verified on real data comprised in open source and commercial projects. Moreover, having identified some drawbacks and anomalies, we point out possible improvements in problem reports and their management. Results Detailed software repositories provide a wider scope of possible measures to assess the relevant problem handling processes. This is helpful in controlling single projects (local perspective) as well as in managing these processes in the whole company (global perspective). Conclusion Detailed problem handling reports extend the space and quality of statistical analysis, the presented graph model with proposed metrics provides a useful tool to evaluate and refine problem resolution schemes.

Exploring the software repositories of embedded systems: An industrial experience

Abstract: Context Tracing reports for software repositories have attracted many researchers. Most of them have focused on defect analysis and development processes in relation to open source programs. There exists a gap between open source and industrial software projects, which, in particular, relates to different schemes for creating software repositories and development schemes. This is especially true for embedded systems that gain large markets and become more complex. Objective The aim is to explore the software repositories of industrial embedded systems and derive characteristic features in order to evaluate quality and identify problems to do with development processes. Method In this paper we have proposed a novel approach to software repository analysis based on the fine grained exploration of issue tracking and code control repositories. In particular, we distinguish the various activities of project actors (e.g. creating new functions, correcting defects, improving performance, modifying tests) and analyse them in a context, not only of a single project, but also a set of correlated projects that have been developed in the company. These issues have been neglected in the literature. These analyses needed new holistic schemes for repository exploration, including various statistical metrics, text mining, and machine learning techniques. Results In exploring selected industrial projects we have identified that only 40–75% of issues relate to defects; the issue reports and commit descriptions included here comprise a lot of data that has been disregarded in the literature. These data allow us to trace diverse types of code changes and identify imperfections in software repositories. Conclusion We show that fine grained repository analysis gives a broader and more complete view of project development, which may lead to its improvement.