Alexander Kofman - Academia.edu (original) (raw)
Papers by Alexander Kofman
2009 31st International Conference on Software Engineering - Companion Volume, 2009
ABSTRACT IBM software development governor is a novel tool that supports specification and enactm... more ABSTRACT IBM software development governor is a novel tool that supports specification and enactment of governance in software development environments. It enables specifying key decision points and policies throughout the life-cycle of development artifacts and automating these specifications in rational team concert-a collaborative software development and delivery environment. In this paper we describe the concepts on which software development governor is built and present the tool and its architecture.
2009 ICSE Workshop on Software Development Governance, 2009
ABSTRACT At its essence software development governance is about guiding the development organiza... more ABSTRACT At its essence software development governance is about guiding the development organization so that it produces value that aligns with the needs of the business. As software development platforms mature they provide increasingly sophisticated capabilities for process measurement and guidance. These new capabilities in turn offer an excellent opportunity for governance tools to help guide the development. In this paper we discuss a model of the development organization that includes: roles, responsibilities, decisions, rights, artifacts and their lifecycles. We show how this model can be elicited and deployed as part of a governance solution to guide the development organization and provide a description of a prototype we have built to automate this process. We conclude with a discussion and important directions for future work in the area.
Does the Rational Jazz ® platform provide adequate services to facilitate the creation of researc... more Does the Rational Jazz ® platform provide adequate services to facilitate the creation of research prototypes in an end-to-end, full lifecycle domain like software development governance? Jazz is a platform for seamlessly integrating development activities, artifacts, and teams throughout the software lifecycle. The Software Development Governance group-whose vision is to help businesses and IT organizations understand and increase the delivered value of software while managing the risk-has been using Jazz to implement research prototypes that promote developer communications, management of decision rights and decision points during software development processes, and the scheduling of software projects. We also used Rational Team Concert ® (RTC)-an Eclipse-based development platform built on Jazz-to aid our own globally distributed development efforts. This paper describes our experiences extending and using Jazz and RTC. It also provides some recommendations for other researchers considering extending the Jazz platform.
ABSTRACT Teams differ in the way they define roles and responsibilities and in the level of forma... more ABSTRACT Teams differ in the way they define roles and responsibilities and in the level of formalism by which they establish and communicate these definitions. Responsibilities are not always clearly defined, and there is often confusion or mismatch between the individual's perspectives of a role and the expectations of that role by other team members. This lack of shared understanding can lead to issues in performance and lack of accountability. We review the notion of role specification as part of software development governance and present an approach for specifying responsibilities in terms of decisions to be made during the life cycle of software development artifacts. We present evaluation data from software teams as they redefine their roles and shape their responsibilities. We further present a tool for governance specification based on this approach, which can ensure that these specifications are adhered to in the software development platform. We conclude by describing a methodology for how the tool and approach can be implemented to help software development teams understand and evolve the appropriate governance for their needs.
Service-Oriented …, Jan 1, 2010
Business processes must become agile, respond to changes in the business environment in a timely ... more Business processes must become agile, respond to changes in the business environment in a timely manner and quickly adapt themselves to new conditions. Event-Driven Business Process Management (ED-BPM) is an enhancement of Business Process Management (BPM) by concepts of Service Oriented Architecture (SOA) and Complex Event Processing (CEP). The most important enhancement is the integration of services accessible via the Internet that fire events into global event clouds. The events can be processed by event processing platforms for aggregating the information into higher value complex business events. These events can be modeled in a business process execution language within a process driven Business Process Management System (BPMS) to trigger changes in control flow of a process or start other services. A reference model and a reference architecture for ED-BPM are presented, based on the NEXOF Reference Architecture. A taxonomy for classifying changes to process flow is proposed. Enhancements have to be applied to the existing standards in the BPM field, including both the design-time and the runtime. A scenario from the banking domain illustrates the main concepts and principles.
2009 31st International Conference on Software Engineering - Companion Volume, 2009
ABSTRACT IBM software development governor is a novel tool that supports specification and enactm... more ABSTRACT IBM software development governor is a novel tool that supports specification and enactment of governance in software development environments. It enables specifying key decision points and policies throughout the life-cycle of development artifacts and automating these specifications in rational team concert-a collaborative software development and delivery environment. In this paper we describe the concepts on which software development governor is built and present the tool and its architecture.
2009 ICSE Workshop on Software Development Governance, 2009
ABSTRACT At its essence software development governance is about guiding the development organiza... more ABSTRACT At its essence software development governance is about guiding the development organization so that it produces value that aligns with the needs of the business. As software development platforms mature they provide increasingly sophisticated capabilities for process measurement and guidance. These new capabilities in turn offer an excellent opportunity for governance tools to help guide the development. In this paper we discuss a model of the development organization that includes: roles, responsibilities, decisions, rights, artifacts and their lifecycles. We show how this model can be elicited and deployed as part of a governance solution to guide the development organization and provide a description of a prototype we have built to automate this process. We conclude with a discussion and important directions for future work in the area.
Does the Rational Jazz ® platform provide adequate services to facilitate the creation of researc... more Does the Rational Jazz ® platform provide adequate services to facilitate the creation of research prototypes in an end-to-end, full lifecycle domain like software development governance? Jazz is a platform for seamlessly integrating development activities, artifacts, and teams throughout the software lifecycle. The Software Development Governance group-whose vision is to help businesses and IT organizations understand and increase the delivered value of software while managing the risk-has been using Jazz to implement research prototypes that promote developer communications, management of decision rights and decision points during software development processes, and the scheduling of software projects. We also used Rational Team Concert ® (RTC)-an Eclipse-based development platform built on Jazz-to aid our own globally distributed development efforts. This paper describes our experiences extending and using Jazz and RTC. It also provides some recommendations for other researchers considering extending the Jazz platform.
ABSTRACT Teams differ in the way they define roles and responsibilities and in the level of forma... more ABSTRACT Teams differ in the way they define roles and responsibilities and in the level of formalism by which they establish and communicate these definitions. Responsibilities are not always clearly defined, and there is often confusion or mismatch between the individual's perspectives of a role and the expectations of that role by other team members. This lack of shared understanding can lead to issues in performance and lack of accountability. We review the notion of role specification as part of software development governance and present an approach for specifying responsibilities in terms of decisions to be made during the life cycle of software development artifacts. We present evaluation data from software teams as they redefine their roles and shape their responsibilities. We further present a tool for governance specification based on this approach, which can ensure that these specifications are adhered to in the software development platform. We conclude by describing a methodology for how the tool and approach can be implemented to help software development teams understand and evolve the appropriate governance for their needs.
Service-Oriented …, Jan 1, 2010
Business processes must become agile, respond to changes in the business environment in a timely ... more Business processes must become agile, respond to changes in the business environment in a timely manner and quickly adapt themselves to new conditions. Event-Driven Business Process Management (ED-BPM) is an enhancement of Business Process Management (BPM) by concepts of Service Oriented Architecture (SOA) and Complex Event Processing (CEP). The most important enhancement is the integration of services accessible via the Internet that fire events into global event clouds. The events can be processed by event processing platforms for aggregating the information into higher value complex business events. These events can be modeled in a business process execution language within a process driven Business Process Management System (BPMS) to trigger changes in control flow of a process or start other services. A reference model and a reference architecture for ED-BPM are presented, based on the NEXOF Reference Architecture. A taxonomy for classifying changes to process flow is proposed. Enhancements have to be applied to the existing standards in the BPM field, including both the design-time and the runtime. A scenario from the banking domain illustrates the main concepts and principles.