-
B. Henderson-Sellers
[show abstract]
[hide abstract]
ABSTRACT: The use of a method to build software creates an organizational standard and guidance to help developers. Using such a process assists developers in avoiding any repetition of past mistakes and aids them in repeating successful strategies. Furthermore, it is agreed that methods for object-oriented/component-based development (OO/CBD) should have a strong process focus: two current processes - RUP (Rational Unified Process<sup>TM</sup>) and OPEN (Object-oriented Process, Environment and Notation) - illustrate the current state of the art. There is also a move towards process meta-models. In this context, OPF (OPEN Process Framework), which underpins OPEN, and proposals to the Object Management Group (OMG) are discussed, together with how a specific process can be created from such a meta-model
Software Methods and Tools, 2000. SMT 2000. Proceedings. International Conference on; 02/2000
-
[show abstract]
[hide abstract]
ABSTRACT: Second generation OO methods, with a few exceptions, contained no elements addressing process or project management. Third generation methods have been defined as those collaborative developments which also have a significant process element. Two examples are the rational unified process (RUP) and object-oriented process, environment and notation (OPEN). We examine RUP and OPEN from a project management viewpoint and evaluate whether either or both would meet acceptable standards in process support, project management guidelines and full lifecycle description for OO software development
Software Engineering Conference, 2000. APSEC 2000. Proceedings. Seventh Asia-Pacific; 02/2000
-
[show abstract]
[hide abstract]
ABSTRACT: Object-oriented methodologies and processes advise on how a
project team can use object technology to create a software-intensive
system. While they offer good advice on software development, they are
inadequate in terms of how the organization (or the project team) should
change its operational culture to one that uses object technology
effectively. In other words, while the process of software development
is spelled out with these new OO methodologies, what is needed is a
process to put this software development process into operation. We
describe how such a process can be created and utilized in engendering
change management from a traditional to an OO software development
culture
Software Engineering Conference, 2000. APSEC 2000. Proceedings. Seventh Asia-Pacific; 02/2000
-
B. Henderson-Sellers
Technology of Object-Oriented Languages and Systems, 1999. Proceedings of; 08/1999
-
[show abstract]
[hide abstract]
ABSTRACT: An in-depth analysis of the semantics of aggregation in object
modelling leads to the identification of the primary axioms of
whole-part; irreflexivity at the instance level; antisymmetry at both
instance and type level; and in which the aggregate object has one or
more emergent and resultant properties. Other aspects of aggregation are
either a natural consequence of these axioms or else are secondary. Each
secondary characteristic defines a partition and thus gives the modelled
aggregation relationship a specific flavour. We show that many of the
existing definitions of aggregation in object modelling are
ill-considered
Technology of Object-Oriented Languages and Systems, 1999. Proceedings of; 08/1999
-
B. Henderson-Sellers
[show abstract]
[hide abstract]
ABSTRACT: Good software engineering requires a process and a means by which
to measure both the success of this process and the quality of the
product. Software engineering metrics are thus a vital component to all
software development organizations aspiring to high quality. In this
paper, an integrated (management and technical) viewpoint is taken in
which product and process metrics are examined in the context of a
third-generation, full-lifecycle object-oriented (OO) process
Software Metrics Symposium, 1999. Proceedings. Sixth International; 02/1999
-
[show abstract]
[hide abstract]
ABSTRACT: The benefits of object metamodelling are the clear and precise
definition of a semantics for the modelling constructs in an object
modelling language. Although this work has already been done for OML and
UML, some problems remain concerning the Whole-Part relationship, also
called aggregation. This paper introduces a new style of object
metamodelling in order to build a general yet abstract metatype called
Whole-Part (Whole,Part). Subtypes are then defined according to the
possibility (or not) of mixing properties generally assigned to
aggregation in the literature. All the candidate properties are
partitioned into three disjoint sets: the set of primary features owned
by the Whole-Part (Whole,Part) metatype, the set of implied properties
resulting from the adoption of the primary properties, as well as the
set of secondary features. Several “flavours” of aggregation
are then constructed leading to reliable and consistent subtypes of the
Whole-Part relationship
Technology of Object-Oriented Languages and Systems, 1999. TOOLS 32. Proceedings; 02/1999
-
B. Henderson-Sellers
[show abstract]
[hide abstract]
ABSTRACT: Relationships in object oriented models are evaluated based on a
formal metamodelling approach. Various types of association and
aggregation are discussed in detail as well as other relationships such
as possession, containment and roles. Finally, recommendations on both
semantics and notation are made for a modelling language such as OML
Technology of Object-Oriented Languages and Systems, 1997. TOOLS 25, Proceedings; 12/1997
-
B. Henderson-Sellers
Technology of Object-Oriented Languages and Systems, 1997. TOOLS 25, Proceedings; 12/1997
-
B. Henderson-Sellers
IEEE Software 08/1997; 14(4):96-97. · 1.51 Impact Factor
-
B. Henderson-Sellers
[show abstract]
[hide abstract]
ABSTRACT: In an interesting paper, L.A. Laranjeira (see ibid., vol.6, no.5,
p.510-22, 1990) describes a first attempt to understand cost estimation
within an object oriented environment. While the presented approach
presents many interesting and useful ideas, it is, unfortunately, marred
by several mathematical errors pertaining to statistics, exponential
functions, and the nature of discrete vs. continuous data. These are
discussed here and more appropriate correct procedures outlined
IEEE Transactions on Software Engineering 05/1997; · 1.98 Impact Factor
-
[show abstract]
[hide abstract]
ABSTRACT: In the object-oriented (OO) field, methods for analysis and design
are a major area of interest. Many such methods have been proposed in
the past few years, leading to numerous requests for convergence or
unification. The authors describe such an effort. Theirs is not the only
ongoing attempt at unification, but it has already attracted
considerable interest. The aim of the Omega project, leading to the OPEN
(Object-oriented Process, Environment and Notation) methodology, is a
process model for system development across the full life cycle,
including reuse strategies and legacy systems. In addition, OPEN will
support human-computer interaction, concurrency, databases, distributed
systems, fuzzy logic, artificial intelligence and intelligent agents.
OPEN is a true third-generation methodology, incorporating many ideas
from other methodologies. These include BON, FOOM, Martin/Odell, MOSES,
OBA, OOram, RDD, ROOM, SOMA and Syntropy. Thus, OPEN is not just another
methodology. Rather than adding one more to the overall count of current
OO methodologies, the OPEN framework will significantly decrease the
number of available available methods by superseding MOSES, SOMA,
Martin/Odell and others
Computer 05/1996; · 1.47 Impact Factor
-
[show abstract]
[hide abstract]
ABSTRACT: Method engineering proposes the construction of methodologies by selecting method fragments from a repository and assembling
them in an appropriate way. However, the rules by which the “optimal” method fragments are chosen are not clear, and such
chores are usually done manually by an expert. This paper presents a goal analysis technique for the selection of the optimal
method fragments from a repository, using backward reasoning to obtain the set of fragments that satisfy the desired goals
with minimum effort. By using this technique, a methodologist can determine the goals that the organisation wants the methodology
to satisfy, and then, preferably, rely on automated tools for the selection of the optimal solution.
01/1970: pages 79-91;
-
[show abstract]
[hide abstract]
ABSTRACT: The Camle approach offers a methodological framework for the development of multi-agent systems. However, this approach does not provide
full coverage of the needs often found in information systems development, lacking, for example, an appropriate capability
for customization or links to infrastructural, non-engineering processes. By adopting a method engineering perspective, it
is possible to integrate the best parts of Camle into the OPEN repository so organizations can create and own customized variants of Camle as necessary.
01/1970: pages 55-64;
-
[show abstract]
[hide abstract]
ABSTRACT: Software development processes and methodologies to date have frequently been described purely textually. However, more recently, a number of metamodels have been constructed to both underpin and begin to formalize these methodologies. We have critically examined four of these: the Object Management Group's Software Process Engineering Metamodel (SPEM), the OPEN Process Framework (OPF), the OOSPICE metamodel for capability assessment and the LiveNet approach for computer-supported collaborative work (CSCW). Based on this analysis, a new, combined metamodel, named Standard Metamodel for Software Development Methodologies (SMSDM) has been constructed which supports not only process but also products and capability assessment in the contexts of both software development and CSCW. As a proof of concept we conclude with a partial example to show how the SMSDM metamodel (and by inference the other metamodels) are used in practice by creating a simple yet usable methodology.
Information and Software Technology.
-
[show abstract]
[hide abstract]
ABSTRACT: This paper outlines existing maturity models of project management and their underlying constructs. Organizations involved in software development in Sydney, Australia were interviewed about their project management practices and their responses analysed to determine whether different project managers used different levels of project management practices and whether the practices were in accordance with a process based maturity model. This did not seem to be the case, yet the data suggested that, as a possible alternative, a systems theory based approach might be more tenable. The overall conclusion, that a system theory based maturity model appears to be better correlated with organizational size and software development maturity than a process based maturity model, is briefly discussed and additional research is suggested that could investigate this novel conclusion further.
Software Engineering Conference, 2004. 11th Asia-Pacific;
-
[show abstract]
[hide abstract]
ABSTRACT: The Camle approach offers a methodological framework for the development of multi-agent systems. However, this approach does not provide full coverage of the needs often found in information systems development, lacking, for example, an appropriate capability for customization or links to infrastructural, non-engineering processes. By adopting a method engineering perspective, it is possible to integrate the best parts of Camle into the OPEN repository so organizations can create and own customized variants of Camle as necessary. Full Text at Springer, may require registration or fee
International Federation for Information Processing Digital Library; Intelligent Information Processing II;.
-
[show abstract]
[hide abstract]
ABSTRACT: In object models built according to popular object-oriented formalisms, the commonest relationship types (excluding inheritance) are the structural relationships of association and of whole-part (often called aggregation). This last type is well known to have no accurately prescribed semantics. Here, some of the aggregation semantics frequently presented in the literature and sometimes supported in current object-oriented modelling languages, especially UML, are analysed and criticised. Because of defects, the use of a modelling notation based on these aggregation semantics is dubious and limited. Moreover, many properties are candidates for characterising the whole-part relationship provided that no redundancy and no inconsistency exist between them. A framework known as cOlOr is then offered by means of a metamodel in which the Whole-Part metatype inherits from the Structural-Relationship metatype. Defining a specific aggregation semantics leads then, first, within cOlOr, to the creation of a subtype of the Whole-Part metatype. Next, the behaviour of this last type is extended and/or restricted in using a constraint-based approach. Such a process is developed particularly for considering Composition in UML and Aggregation in OML more formally, as well as for dealing with domain-dependent aggregation semantics. Since a non-negligible feature of cOlOr is the availability of a C++ library that implements the proposed metamodel, some implementation concerns are also briefly discussed.
Information and Software Technology.
-
[show abstract]
[hide abstract]
ABSTRACT: Human Factors, the so-called Soft Issues, play a vital role in highlighting the difference between success and failure for any project where people are involved, resistance to change, both at a personal and organizational level, being one such factor. In this paper, we report the findings of two empirical studies, using Action Research (AR), that were conducted over a period of two years at a mid-size publishing organization in Sydney to investigate the effect of various human behavioural patterns during the organizational transition to Object Technology (OT). This investigation was carried out to validate our theory that the appropriate planning and managing of the human factors during an organizational change may eliminate/mitigate people's natural resistance to change and increase the chance of success. Here we focus on the resistance factor. Observations show that human factors such as resistance to change contributed to the first project's relative failure whereas acceptance of change (managing resistance) contributed to the second project's success. These case studies support the argument that both careful planning and management of specific human factors can positively impact the entire organizational transition process.
-
[show abstract]
[hide abstract]
ABSTRACT: Despite the vast attention and wide acceptance of the newly engineered agile methods for software development, those methods are seldom linked to the goals of software process improvement (SPI), an approach that aims to provide support for significant improvement of both the quality of those methods as well as the resultant software products. In this paper, we propose an extension to agile methods by adding extra characteristics in order for agile methods to better support SPI. We explain how agile methods can gain those extra attributes through the application of a method engineering approach along with our new tool (4-DAT) that assists method engineers and managers in selecting the most appropriate method fragments for their needed agile methods. Finally, we summarize a number of industrial case studies carried out over several years in order to test and improve the efficiency of our theory of adding SPI to an agile methodological approach.
