Steven Bleistein | The University of New South Wales (original) (raw)
Uploads
Papers by Steven Bleistein
Rapid Organizational Change
Rapid Organizational Change, 2017
karl.cox, vladimir.tosic, steven.bleistein
Rapid Organizational Change, 2017
Rapid Organizational Change, 2017
Rapid Organizational Change, 2017
Rapid Organizational Change, 2017
Management Development Review, 1997
Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a soc... more Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a socialist society. But all are becoming more common in the People’s Republic of China. Explains why.
Management Development Review, 1997
Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a soc... more Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a socialist society. But all are becoming more common in the People’s Republic of China. Explains why.
Rapid Organizational Change, 2017
AbstractAs a means of contributing to the achievement of business advantage for companies engagin... more AbstractAs a means of contributing to the achievement of business advantage for companies engaging in ebusiness, we propose a requirements engineering framework that incorporates a business strategy dimension. We employ Jackson’s Problem Frames approach, goal modeling, and business process modeling (BPM) to achieve this. Jackson’s context diagrams, used to represent business model context, are integrated with goal models to describe the requirements of the business strategy. We leverage the paradigm of projection in both approaches as a means of simultaneously decomposing both the requirement and context parts, from an abstract business level to concrete system requirements. Our approach maintains traceability to high-level business objectives via contribution relationship links in the goal model. We integrate use of role activity diagrams to describe business processes in detail where needed. The feasibility of our approach is shown by a well-known case study taken from the literature. 1
B-SCP: a requirements analysis framework for validating
As a means of contributing to the achievement of business advantage for companies engaging in e-b... more As a means of contributing to the achievement of business advantage for companies engaging in e-business, we propose a requirements engineering approach that incorporates a business strategy dimension. We employ both goal modeling and Jackson's Problem Frames approach to achieve this. Jackson's context diagrams, used to represent the business model context, are integrated with goal-models to describe the complete business strategy. We leverage the paradigm of projection in both approaches while maintaining traceability to high-level business objectives as a means of simultaneously decomposing both the optative and indicative parts of the requirements problem, from an abstract business level to concrete system requirements. We integrate use of role activity diagrams to describe business processes in detail where needed.
As a means of contributing to the achievement of business advantage for companies engaging in e-b... more As a means of contributing to the achievement of business advantage for companies engaging in e-business, we propose a requirements engineering approach that incorporates a business strategy dimension. We employ both goal modeling and Jackson's Problem Frames approach to achieve this. Jackson's context diagrams, used to represent the business model context, are integrated with goal-models to describe the complete business strategy. We leverage the paradigm of projection in both approaches while maintaining traceability to high-level business objectives as a means of simultaneously decomposing both the optative and indicative parts of the requirements problem, from an abstract business level to concrete system requirements. We integrate use of role activity diagrams to describe business processes in detail where needed.
It is no longer possible to consider IT separate from the business organization it supports, and ... more It is no longer possible to consider IT separate from the business organization it supports, and hence requirements engineering should address the business needs of an organization. Business needs can be described through IT alignment with business strategy, including alignment, explicit value analysis of IT, integrated market analysis and product development, as well other types of analysis of business processes, organisational infrastructures, business goals and objectives. Though it is recognised that requirements engineering (RE) is a natural bridge that connects the business world and the IT world, much of RE research continues to be solution-oriented and avoids addressing the hard, real-world business problems that confront business practitioners every day. This trend, if continued unchecked, threatens to ultimately make requirements engineering research of little relevance or importance to industry. As such, the goal of this workshop is to provide a specific forum for researc...
Ingénierie des systèmes d'information, 2009
ABSTRACT ABSTRACT. While research on project failure tends to supply lists of risk and failure fa... more ABSTRACT ABSTRACT. While research on project failure tends to supply lists of risk and failure factors, and negative business effects, the objective of this research is to identify specific factors behind failure and who is to blame. We analyze practitioners’ perspectives on 57 development and management factors for projects they considered failures across 70 failed projects. Results show that all projects reviewed suffered 6 to 48 failure factors. While no single set of factors is identified, nearly all projects suffered from organizational factors outside the project manager’s control. We conclude with suggestions to minimize the most common ones. RÉSUMÉ : Tandis que la recherche sur l’échec de projets logiciels tend à fournir des listes de facteurs de risque et d’erreurs, et des effets négatifs sur l’activité des organisations, l’objectif de ces travaux de recherche est d’identifier les facteurs sous-jacents spécifiques et les éléments responsables. Nous analysons le point de vue des spécialistes sur 57 facteurs de développement et de gestion pour des projets qu’ils ont considérés comme des échecs parmi 70 projets infructueux. Les résultats montrent que les projets considérés sont critiques sur 6 à 48 facteurs d’échec. Bien qu’un unique ensemble de facteurs ne soit pas identifié, il s’agit en majorité de facteurs organisationnels hors du contrôle du chef de projet. Nous concluons par des suggestions sur la manière de réduire les plus fréquents. KEYWORDS: software project failure, software project management, failure factors, project risk. MOTS-CLÉS : échec de projet logiciel, gestion de projet logiciel, facteurs d’échec, risque des projets.
dpnm.postech.ac.kr
This paper is intended to identify issues in design methodology of sophisticated self-managing sy... more This paper is intended to identify issues in design methodology of sophisticated self-managing systems. Whereas self-managing systems are intended to achieve increasingly sophisticated business-level objectives, current agentoriented design methodologies begin requirements gathering and analysis at much lower levels. This leaves a hazardous gap in the system analysis phase of selfmanaging system design. This paper proposes desiderata for design methodology that include requirements gathering from high-level abstract business goals. It proposes structured and systematic means of decomposing and mapping high-level business objectives down to the finer requirements necessary to agent-oriented methodologies. It explores the possibility of applying experience gained from goaloriented software engineering techniques as well as methodologies in integrated management of networks and services. Finally, this paper proposes an evolving high-level notation of design patterns to model self-managing systems in an integrated way.
Business-ICT alignment is the problem of matching ICTservices with the requirements of the busine... more Business-ICT alignment is the problem of matching ICTservices with the requirements of the business. In businesses of any significant size, business-ICT alignment is a hard problem, which is currently not solved completely. With the advent of networked constellations of enterprises, the problem gets a new dimension, because in such a network, there is not a single point of authority for making decisions about ICT support to solve conflicts in requirements these various enterprises may have. Network constellations exist when different businesses decide to cooperate by means of ICT networks, but they also exist in large corporations, which often consist of nearly independent business units, and thus have no single point of authority anymore. In this position paper we discuss the need for several solution techniques to address the problem of business-ICT alignment in networked constellations. Such techniques include: • RE techniques to describe networked value constellations requesting and offering ICT services as economic value. These techniques should allow reasoning about the matching of business needs with available ICT services in the constellation. • RE techniques to design a networked ICT architecture that supports ICT services required by the business, taking the value offered by those services, and the costs incurred by the architecture, into account. • Models of decision processes about ICT services and their architecture, and maturity models of those processes. The techniques and methods will be developed and validated using case studies and action research.
Rapid Organizational Change
Rapid Organizational Change, 2017
karl.cox, vladimir.tosic, steven.bleistein
Rapid Organizational Change, 2017
Rapid Organizational Change, 2017
Rapid Organizational Change, 2017
Rapid Organizational Change, 2017
Management Development Review, 1997
Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a soc... more Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a socialist society. But all are becoming more common in the People’s Republic of China. Explains why.
Management Development Review, 1997
Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a soc... more Short‐term contracts, redundancies and unemployment insurance hardly sound like features of a socialist society. But all are becoming more common in the People’s Republic of China. Explains why.
Rapid Organizational Change, 2017
AbstractAs a means of contributing to the achievement of business advantage for companies engagin... more AbstractAs a means of contributing to the achievement of business advantage for companies engaging in ebusiness, we propose a requirements engineering framework that incorporates a business strategy dimension. We employ Jackson’s Problem Frames approach, goal modeling, and business process modeling (BPM) to achieve this. Jackson’s context diagrams, used to represent business model context, are integrated with goal models to describe the requirements of the business strategy. We leverage the paradigm of projection in both approaches as a means of simultaneously decomposing both the requirement and context parts, from an abstract business level to concrete system requirements. Our approach maintains traceability to high-level business objectives via contribution relationship links in the goal model. We integrate use of role activity diagrams to describe business processes in detail where needed. The feasibility of our approach is shown by a well-known case study taken from the literature. 1
B-SCP: a requirements analysis framework for validating
As a means of contributing to the achievement of business advantage for companies engaging in e-b... more As a means of contributing to the achievement of business advantage for companies engaging in e-business, we propose a requirements engineering approach that incorporates a business strategy dimension. We employ both goal modeling and Jackson's Problem Frames approach to achieve this. Jackson's context diagrams, used to represent the business model context, are integrated with goal-models to describe the complete business strategy. We leverage the paradigm of projection in both approaches while maintaining traceability to high-level business objectives as a means of simultaneously decomposing both the optative and indicative parts of the requirements problem, from an abstract business level to concrete system requirements. We integrate use of role activity diagrams to describe business processes in detail where needed.
As a means of contributing to the achievement of business advantage for companies engaging in e-b... more As a means of contributing to the achievement of business advantage for companies engaging in e-business, we propose a requirements engineering approach that incorporates a business strategy dimension. We employ both goal modeling and Jackson's Problem Frames approach to achieve this. Jackson's context diagrams, used to represent the business model context, are integrated with goal-models to describe the complete business strategy. We leverage the paradigm of projection in both approaches while maintaining traceability to high-level business objectives as a means of simultaneously decomposing both the optative and indicative parts of the requirements problem, from an abstract business level to concrete system requirements. We integrate use of role activity diagrams to describe business processes in detail where needed.
It is no longer possible to consider IT separate from the business organization it supports, and ... more It is no longer possible to consider IT separate from the business organization it supports, and hence requirements engineering should address the business needs of an organization. Business needs can be described through IT alignment with business strategy, including alignment, explicit value analysis of IT, integrated market analysis and product development, as well other types of analysis of business processes, organisational infrastructures, business goals and objectives. Though it is recognised that requirements engineering (RE) is a natural bridge that connects the business world and the IT world, much of RE research continues to be solution-oriented and avoids addressing the hard, real-world business problems that confront business practitioners every day. This trend, if continued unchecked, threatens to ultimately make requirements engineering research of little relevance or importance to industry. As such, the goal of this workshop is to provide a specific forum for researc...
Ingénierie des systèmes d'information, 2009
ABSTRACT ABSTRACT. While research on project failure tends to supply lists of risk and failure fa... more ABSTRACT ABSTRACT. While research on project failure tends to supply lists of risk and failure factors, and negative business effects, the objective of this research is to identify specific factors behind failure and who is to blame. We analyze practitioners’ perspectives on 57 development and management factors for projects they considered failures across 70 failed projects. Results show that all projects reviewed suffered 6 to 48 failure factors. While no single set of factors is identified, nearly all projects suffered from organizational factors outside the project manager’s control. We conclude with suggestions to minimize the most common ones. RÉSUMÉ : Tandis que la recherche sur l’échec de projets logiciels tend à fournir des listes de facteurs de risque et d’erreurs, et des effets négatifs sur l’activité des organisations, l’objectif de ces travaux de recherche est d’identifier les facteurs sous-jacents spécifiques et les éléments responsables. Nous analysons le point de vue des spécialistes sur 57 facteurs de développement et de gestion pour des projets qu’ils ont considérés comme des échecs parmi 70 projets infructueux. Les résultats montrent que les projets considérés sont critiques sur 6 à 48 facteurs d’échec. Bien qu’un unique ensemble de facteurs ne soit pas identifié, il s’agit en majorité de facteurs organisationnels hors du contrôle du chef de projet. Nous concluons par des suggestions sur la manière de réduire les plus fréquents. KEYWORDS: software project failure, software project management, failure factors, project risk. MOTS-CLÉS : échec de projet logiciel, gestion de projet logiciel, facteurs d’échec, risque des projets.
dpnm.postech.ac.kr
This paper is intended to identify issues in design methodology of sophisticated self-managing sy... more This paper is intended to identify issues in design methodology of sophisticated self-managing systems. Whereas self-managing systems are intended to achieve increasingly sophisticated business-level objectives, current agentoriented design methodologies begin requirements gathering and analysis at much lower levels. This leaves a hazardous gap in the system analysis phase of selfmanaging system design. This paper proposes desiderata for design methodology that include requirements gathering from high-level abstract business goals. It proposes structured and systematic means of decomposing and mapping high-level business objectives down to the finer requirements necessary to agent-oriented methodologies. It explores the possibility of applying experience gained from goaloriented software engineering techniques as well as methodologies in integrated management of networks and services. Finally, this paper proposes an evolving high-level notation of design patterns to model self-managing systems in an integrated way.
Business-ICT alignment is the problem of matching ICTservices with the requirements of the busine... more Business-ICT alignment is the problem of matching ICTservices with the requirements of the business. In businesses of any significant size, business-ICT alignment is a hard problem, which is currently not solved completely. With the advent of networked constellations of enterprises, the problem gets a new dimension, because in such a network, there is not a single point of authority for making decisions about ICT support to solve conflicts in requirements these various enterprises may have. Network constellations exist when different businesses decide to cooperate by means of ICT networks, but they also exist in large corporations, which often consist of nearly independent business units, and thus have no single point of authority anymore. In this position paper we discuss the need for several solution techniques to address the problem of business-ICT alignment in networked constellations. Such techniques include: • RE techniques to describe networked value constellations requesting and offering ICT services as economic value. These techniques should allow reasoning about the matching of business needs with available ICT services in the constellation. • RE techniques to design a networked ICT architecture that supports ICT services required by the business, taking the value offered by those services, and the costs incurred by the architecture, into account. • Models of decision processes about ICT services and their architecture, and maturity models of those processes. The techniques and methods will be developed and validated using case studies and action research.