A critical problem in software development is the monitoring, control and improvement in the proc... more A critical problem in software development is the monitoring, control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge differences between 'actual' and 'official' processes: ''the actual process is what you do, with all its omissions, mistakes, and oversights. The official process is what the book, i.e., a quality manual, says you are supposed to do'' (Humphrey in A discipline for software engineering. Addison-Wesley, New York, 1995). Software developers lack support to identify, analyze and better understand their processes. Consequently, process improvements are often not based on an in-depth understanding of the 'actual' processes, but on organization-wide improvement programs or ad hoc initiatives of individual developers. In this paper, we show that, based on particular data from software development projects, the underlying software development processes can be extracted and that automatically more realistic process models can be constructed. This is called software process mining (Rubin et al. in Process mining framework for software processes. Software process dynamics and agility. Springer Berlin, Heidelberg, 2007). The goal of process mining is to better understand the development processes, to compare constructed process models with the 'official' guidelines and procedures in quality manuals and, subsequently, to improve development processes. This paper reports on process mining case studies in a large industrial company in The Netherlands. The subject of the process mining is a particular process: the change control board (CCB) process. The results of process mining are fed back to practice in order to subsequently improve the CCB process.
Proceedings of the 10th International Workshop on Software Technology and Engineering Practice, 2002
... Defect Prevention ✎ Quality Management ✎ Process Change Management ... the process is impleme... more ... Defect Prevention ✎ Quality Management ✎ Process Change Management ... the process is implemented as planned and satisfies the relevant policies, requirements, standards, and ... This section addresses some practical guidelines regarding the application of the model in day-to ...
Systematic software process improvement based on multiple software process improvement approaches... more Systematic software process improvement based on multiple software process improvement approaches is getting more and more emphasised. Despite a systematic improvement requires mapping of quality approaches to organizational processes and data shall be stored in a well-designed manner, storing multimodel results is not yet addressed in detail in the current literature. In this report we present a data model for multimodel software process improvement which allows storing multimodel results in a maintainable way.
Many of quality approaches are described in hundreds of textual pages (see CMMI, SPICE, Enterpris... more Many of quality approaches are described in hundreds of textual pages (see CMMI, SPICE, Enterprise SPICE, ITIL among others). Manual processing of information consumes plenty of resources. In this report we present the complexity analysis of CMMIone well known and widely process improvement framework. The complexity analysis can provide a quick overview on the coupledness of the elements of quality approaches by an automated analysis of the cross-references in quality approaches. The result of the analysis could accelerate the understanding the quality approach and help in setting the starting points of improvement.
Identification and specification of software quality is an important aspect of software developme... more Identification and specification of software quality is an important aspect of software development. Although there exist standards for the definition of software quality still there is a lack of operational methods that support the process of identification and specification. The process of quality requirement specification contains multiple aspects of a multi-criteria decision process. This paper stresses the importance of decision support in the process of identifying and specifying software quality. The application of Multi-Criteria Decision Analysis (MCDA) theory and the Analytical Hierarchy Process (AHP) is suggested to support the decision process. The new method is applied in a real life project at CAMS-Force Vision, the software development unit of the Royal Marine and the Defense Organisation in The Netherlands. The paper presents results and experiences from the case study.
Many researchers and practitioners have recognised that the perception of 'r... more Many researchers and practitioners have recognised that the perception of 'reliability' is largely influenced by personal view and application context. Depending on personal goals, interests and background, the interpretation of the reliability concept is different per individual. ...
Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004), 2004
We present a quantitative method for scenariodriven value, risk, and cost analysis when proposing... more We present a quantitative method for scenariodriven value, risk, and cost analysis when proposing new system architectures for innovation projects. The method helps to articulate the relative benefits and/or disadvantages of the proposed set of scenarios in the early architecting phases of a new system. It provides the arguments on which to base an informed decision to select the final architectural scenarios for further consideration in the design. In this paper we present a case study in which we applied the proposed method.
Reference architectures provide major guidelines for the structure of a class of information syst... more Reference architectures provide major guidelines for the structure of a class of information systems. Because of their fundamental role, reference architectures have to be of high quality. Before accepting a reference architecture, it has to go through a rigorous evaluation process. A number of methods exist for the evaluation of software architectures. In this paper, we analyze the main differences between concrete software architectures and reference architectures. We discuss the effects of these differences on the evaluation of reference architectures and show that existing methods cannot be directly applied for the evaluation of reference architectures. For the evaluation of a reference architecture for e-contracting systems, we used the Architecture Tradeoff Analysis Method with a number of adaptations and extensions. We present our approach and share our experiences from this evaluation process. Based on the analysis and our experiences gained, we present our vision for a method for the evaluation of reference architectures.
Proceedings of the 17th International Conference on Enterprise Information Systems, 2015
Offering a PSS that is based on co-creating value with customer, starts with understanding custom... more Offering a PSS that is based on co-creating value with customer, starts with understanding customer needs. Customer understanding is realized through the process of managing customer knowledge across a PSS value network. In this respect, customer knowledge management (CKM) is seen as a core business capability. We extend the notion of CKM capability to a PSS value network, defining it as a value network CKM (VN-CKM) capability. We also look at the supportive IT capability, which we define as the value network social customer relationship management (VN-SCRM) capability. At operational level VN-CKM and VN-SCRM capabilities are reflected in the execution of business processes and information systems. To achieve BIA, a linkage is required between the VN-CKM capability and the VN-SCRM capability and between its accompanying business processes and systems. If in the process of VN-CKM, activities such as creation, storage/retrieve, transfer, and usage of customer knowledge are enabled by VN-SCRM systems across a network, the established BIA will support the functioning of the PSS. In this study we discuss the role of a VN-SCRM capability and identify requirement components of accompanying systems in relation to a VN-CKM capability and accompanying processes, in order to foster BIA at a network level.
IFIP Advances in Information and Communication Technology, 2014
Offering customer-centric value through dynamic and networked capabilities is a strategic need in... more Offering customer-centric value through dynamic and networked capabilities is a strategic need in the current business environment. This strategic need can be met by a Service-Oriented Demand-Supply Chain (SODSC) concept. Various direct and indirect notions in different contexts have been developed about SODSC concept. However, the lack of integration between these notions can easily lead to confusion. This paper aims to counter this confusion by providing a framework for structuring various related notions and explaining them through illustrative cases. Based on a cybernetic system approach, the serviceoriented value, partnership and control aspects of SODSC have been investigated respectively. On the basis of a distinction between demand and supply chain perspectives, two distinct dimensions of service orientation have been explored in each of the aspects. The resulting integrated framework, visualized by three related two-dimensional matrices and illustrated by real cases, offers the possibility to characterize and analyze the various SODSC notions.
A critical problem in software development is the monitoring, control and improvement in the proc... more A critical problem in software development is the monitoring, control and improvement in the processes of software developers. Software processes are often not explicitly modeled, and manuals to support the development work contain abstract guidelines and procedures. Consequently, there are huge differences between 'actual' and 'official' processes: ''the actual process is what you do, with all its omissions, mistakes, and oversights. The official process is what the book, i.e., a quality manual, says you are supposed to do'' (Humphrey in A discipline for software engineering. Addison-Wesley, New York, 1995). Software developers lack support to identify, analyze and better understand their processes. Consequently, process improvements are often not based on an in-depth understanding of the 'actual' processes, but on organization-wide improvement programs or ad hoc initiatives of individual developers. In this paper, we show that, based on particular data from software development projects, the underlying software development processes can be extracted and that automatically more realistic process models can be constructed. This is called software process mining (Rubin et al. in Process mining framework for software processes. Software process dynamics and agility. Springer Berlin, Heidelberg, 2007). The goal of process mining is to better understand the development processes, to compare constructed process models with the 'official' guidelines and procedures in quality manuals and, subsequently, to improve development processes. This paper reports on process mining case studies in a large industrial company in The Netherlands. The subject of the process mining is a particular process: the change control board (CCB) process. The results of process mining are fed back to practice in order to subsequently improve the CCB process.
Proceedings of the 10th International Workshop on Software Technology and Engineering Practice, 2002
... Defect Prevention ✎ Quality Management ✎ Process Change Management ... the process is impleme... more ... Defect Prevention ✎ Quality Management ✎ Process Change Management ... the process is implemented as planned and satisfies the relevant policies, requirements, standards, and ... This section addresses some practical guidelines regarding the application of the model in day-to ...
Systematic software process improvement based on multiple software process improvement approaches... more Systematic software process improvement based on multiple software process improvement approaches is getting more and more emphasised. Despite a systematic improvement requires mapping of quality approaches to organizational processes and data shall be stored in a well-designed manner, storing multimodel results is not yet addressed in detail in the current literature. In this report we present a data model for multimodel software process improvement which allows storing multimodel results in a maintainable way.
Many of quality approaches are described in hundreds of textual pages (see CMMI, SPICE, Enterpris... more Many of quality approaches are described in hundreds of textual pages (see CMMI, SPICE, Enterprise SPICE, ITIL among others). Manual processing of information consumes plenty of resources. In this report we present the complexity analysis of CMMIone well known and widely process improvement framework. The complexity analysis can provide a quick overview on the coupledness of the elements of quality approaches by an automated analysis of the cross-references in quality approaches. The result of the analysis could accelerate the understanding the quality approach and help in setting the starting points of improvement.
Identification and specification of software quality is an important aspect of software developme... more Identification and specification of software quality is an important aspect of software development. Although there exist standards for the definition of software quality still there is a lack of operational methods that support the process of identification and specification. The process of quality requirement specification contains multiple aspects of a multi-criteria decision process. This paper stresses the importance of decision support in the process of identifying and specifying software quality. The application of Multi-Criteria Decision Analysis (MCDA) theory and the Analytical Hierarchy Process (AHP) is suggested to support the decision process. The new method is applied in a real life project at CAMS-Force Vision, the software development unit of the Royal Marine and the Defense Organisation in The Netherlands. The paper presents results and experiences from the case study.
Many researchers and practitioners have recognised that the perception of 'r... more Many researchers and practitioners have recognised that the perception of 'reliability' is largely influenced by personal view and application context. Depending on personal goals, interests and background, the interpretation of the reliability concept is different per individual. ...
Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004), 2004
We present a quantitative method for scenariodriven value, risk, and cost analysis when proposing... more We present a quantitative method for scenariodriven value, risk, and cost analysis when proposing new system architectures for innovation projects. The method helps to articulate the relative benefits and/or disadvantages of the proposed set of scenarios in the early architecting phases of a new system. It provides the arguments on which to base an informed decision to select the final architectural scenarios for further consideration in the design. In this paper we present a case study in which we applied the proposed method.
Reference architectures provide major guidelines for the structure of a class of information syst... more Reference architectures provide major guidelines for the structure of a class of information systems. Because of their fundamental role, reference architectures have to be of high quality. Before accepting a reference architecture, it has to go through a rigorous evaluation process. A number of methods exist for the evaluation of software architectures. In this paper, we analyze the main differences between concrete software architectures and reference architectures. We discuss the effects of these differences on the evaluation of reference architectures and show that existing methods cannot be directly applied for the evaluation of reference architectures. For the evaluation of a reference architecture for e-contracting systems, we used the Architecture Tradeoff Analysis Method with a number of adaptations and extensions. We present our approach and share our experiences from this evaluation process. Based on the analysis and our experiences gained, we present our vision for a method for the evaluation of reference architectures.
Proceedings of the 17th International Conference on Enterprise Information Systems, 2015
Offering a PSS that is based on co-creating value with customer, starts with understanding custom... more Offering a PSS that is based on co-creating value with customer, starts with understanding customer needs. Customer understanding is realized through the process of managing customer knowledge across a PSS value network. In this respect, customer knowledge management (CKM) is seen as a core business capability. We extend the notion of CKM capability to a PSS value network, defining it as a value network CKM (VN-CKM) capability. We also look at the supportive IT capability, which we define as the value network social customer relationship management (VN-SCRM) capability. At operational level VN-CKM and VN-SCRM capabilities are reflected in the execution of business processes and information systems. To achieve BIA, a linkage is required between the VN-CKM capability and the VN-SCRM capability and between its accompanying business processes and systems. If in the process of VN-CKM, activities such as creation, storage/retrieve, transfer, and usage of customer knowledge are enabled by VN-SCRM systems across a network, the established BIA will support the functioning of the PSS. In this study we discuss the role of a VN-SCRM capability and identify requirement components of accompanying systems in relation to a VN-CKM capability and accompanying processes, in order to foster BIA at a network level.
IFIP Advances in Information and Communication Technology, 2014
Offering customer-centric value through dynamic and networked capabilities is a strategic need in... more Offering customer-centric value through dynamic and networked capabilities is a strategic need in the current business environment. This strategic need can be met by a Service-Oriented Demand-Supply Chain (SODSC) concept. Various direct and indirect notions in different contexts have been developed about SODSC concept. However, the lack of integration between these notions can easily lead to confusion. This paper aims to counter this confusion by providing a framework for structuring various related notions and explaining them through illustrative cases. Based on a cybernetic system approach, the serviceoriented value, partnership and control aspects of SODSC have been investigated respectively. On the basis of a distinction between demand and supply chain perspectives, two distinct dimensions of service orientation have been explored in each of the aspects. The resulting integrated framework, visualized by three related two-dimensional matrices and illustrated by real cases, offers the possibility to characterize and analyze the various SODSC notions.
Uploads
Papers by Jjm Trienekens