Search

Software practitioners can make sub-optimal decisions concerning requirements during gathering, documenting, prioritizing, and implementing requirements as software features or architectural design decisions -- this is captured by the metaphor `Requirements Technical Debt (RTD).' In our prior work, we developed a conceptual model to understand the quantification of RTD and support its management. In this paper, we present our perspective and the vision to apply the lens of RTD to software requirements concerning veracity, i.e., requirements related to truth, trust, authenticity, and demonstrability in software-intensive systems. Our goal is to cultivate awareness of veracity as an important concern and eventually support the management of RTD for software requirements concerning veracity, what we term as `Veracity Debt,' through its quantification.

To effectively manage Technical Debt (TD), we need reliable means to quantify it. We conducted a Systematic Mapping Study (SMS) where we identified TD quantification approaches that focus on different aspects of TD. Some approaches base the quantification on the identification of smells, some quantify the Return on Investment (ROI) of refactoring, some compare an ideal state with the current state of a software in terms of the software quality, and some compare alternative development paths to reduce TD. It is unclear if these approaches are quantifying the same thing and if they support similar or different decisions regarding TD Management (TDM). This creates the problem of not being able to effectively compare and evaluate approaches. To solve this problem, we developed a novel conceptual model, the Technical Debt Quantification Model (TDQM), that captures the important concepts related to TD quantification and illustrates the relationships between them. TDQM can represent varied TD quantification approaches via a common uniform representation, the TDQM Approach Comparison Matrix, that allows performing useful comparisons and evaluations between approaches. This paper reports on the mapping study, the development of TDQM, and on applying TDQM to compare and evaluate TD quantification approaches.

There is a shortage of qualified people in the IT industry in the world. To address this shortage, transition programmes are being created that help people change to careers in IT. To provide useful programmes, we need to know if the current curriculum provides value to its graduates. Moreover, as the IT industry undergoes continuous change, we need to regularly review what the industry needs and update any existing programmes as appropriate. In this paper we present the results of a survey of graduates of one such programme, the PGCertInfoTech at University of Auckland, with the view to evaluating the currency of the existing programme and to gather data on which to base decisions on updating it. Our conclusion is that our programme is largely useful to graduates, but could be improved with the addition of material on continuous integration, and some adjustment to the time spent on testing, concurrency, and project management. Our results will be useful to any other institutions having, or considering to have, IT transition programmes.