6 resultados para Finkelstein
em Aston University Research Archive
Resumo:
Some researchers argue that the top team, rather than the CEO, is a better predictor of an organisation’s fate (Finkelstein & Hambrick, 1996; Knight et al., 1999). However, others suggest that the importance of the top management team (TMT) composition literature is exaggerated (West & Schwenk, 1996). This has stimulated a need for further research on TMTs. While the importance of TMT is well documented in the innovation literature, the organisational environment also plays a key role in determining organisational outcomes. Therefore, the inclusion of both TMT characteristics and organisational variables (climate and organisational learning) in this study provides a more holistic picture of innovation. The research methodologies employed includes (i) interviews with TMT members in 35 Irish software companies (ii) a survey completed by managerial respondents and core workers in these companies (iii) in-depth interviews with TMT members from five companies. Data were gathered in two phases, time 1 (1998-2000) and time 2 (2003). The TMT played an important part in fostering innovation. However, it was a group process, rather than team demography, that was most strongly associated with innovation. Task reflexivity was an important predictor of innovation time 1, time 2). Only one measure of TMT diversity was associated with innovation - tenure diversity -in time 2 only. Organisational context played an important role in determining innovation. This was positively associated with innovation - but with one dimension of organisational learning only. The ability to share information (access to information) was not associated with innovation but the motivation to share information was (perceiving the sharing of information to be valuable). Innovative climate was also associated with innovation. This study suggests that this will lead to innovative outcomes if employees perceive the organisation to support risk, experimentation and other innovative behaviours.
Resumo:
Requirements are sensitive to the context in which the system-to-be must operate. Where such context is well-understood and is static or evolves slowly, existing RE techniques can be made to work well. Increasingly, however, development projects are being challenged to build systems to operate in contexts that are volatile over short periods in ways that are imperfectly understood. Such systems need to be able to adapt to new environmental contexts dynamically, but the contextual uncertainty that demands this self-adaptive ability makes it hard to formulate, validate and manage their requirements. Different contexts may demand different requirements trade-offs. Unanticipated contexts may even lead to entirely new requirements. To help counter this uncertainty, we argue that requirements for self-adaptive systems should be run-time entities that can be reasoned over in order to understand the extent to which they are being satisfied and to support adaptation decisions that can take advantage of the systems' self-adaptive machinery. We take our inspiration from the fact that explicit, abstract representations of software architectures used to be considered design-time-only entities but computational reflection showed that architectural concerns could be represented at run-time too, helping systems to dynamically reconfigure themselves according to changing context. We propose to use analogous mechanisms to achieve requirements reflection. In this paper we discuss the ideas that support requirements reflection as a means to articulate some of the outstanding research challenges.
Resumo:
Computational reflection is a well-established technique that gives a program the ability to dynamically observe and possibly modify its behaviour. To date, however, reflection is mainly applied either to the software architecture or its implementation. We know of no approach that fully supports requirements reflection- that is, making requirements available as runtime objects. Although there is a body of literature on requirements monitoring, such work typically generates runtime artefacts from requirements and so the requirements themselves are not directly accessible at runtime. In this paper, we define requirements reflection and a set of research challenges. Requirements reflection is important because software systems of the future will be self-managing and will need to adapt continuously to changing environmental conditions. We argue requirements reflection can support such self-adaptive systems by making requirements first-class runtime entities, thus endowing software systems with the ability to reason about, understand, explain and modify requirements at runtime. © 2010 ACM.
Resumo:
The goal of this roadmap paper is to summarize the state-of-the-art and to identify critical challenges for the systematic software engineering of self-adaptive systems. The paper is partitioned into four parts, one for each of the identified essential views of self-adaptation: modelling dimensions, requirements, engineering, and assurances. For each view, we present the state-of-the-art and the challenges that our community must address. This roadmap paper is a result of the Dagstuhl Seminar 08031 on "Software Engineering for Self-Adaptive Systems," which took place in January 2008. © 2009 Springer Berlin Heidelberg.
Resumo:
The 2nd edition of the Workshop requirements@run.time was held at the 19th International Conference on Requirements Engineering (RE 2011) in the city of Trento, Italy on the 30th of August 2011. It was organized by Nelly Bencomo, Emmanuel Letier, Jon Whittle, Anthony Finkelstein, and Kris Welsh. This foreword presents a digest of the discussions and presentations that took place during the workshop. © 2011 IEEE.
Resumo:
The first edition of the Workshop requirements@run.time was held at the Eighteenth International Conference on Requirements Engineering (RE 2010) in the city of Sydney, NSW, Australia on the 28th of September 2010. It was organized by Pete Sawyer, Jon Whittle, Nelly Bencomo, Daniel Berry, and Anthony Finkelstein. This foreword presents a digest of the presentations and discussions that took place during the workshop. © 2010 IEEE.