Entrepreneurship, Entry and Exit in Creative Industries: an explorative Survey

Series: Creative Industries in Vienna: Development, Dynamics and Potential

Models and metrics for software management and engineering

This paper attempts to characterize and present a state of the art view of several quantitative models and metrics of the software life cycle. These models and metrics can be used to aid in managing and engineering software projects. They deal with various aspects of the software process and product, including resources allocation and estimation, changes and errors, size, complexity and reliability. Some indication is given of the extent to which the various models have been used and the success they have achieved

Formal software measurements for object-oriented business models.

This paper presents a set of metrics and pseudo-metrics for the measurement of conceptual distances in M.E.R.O.D.E. business models. The measures are developed and validated using measure and measurement theory. It is argued that this metrics set constitutes a strong formal basis for the further assessment and prediction of relevant internal and external attributes of object-oriented specifications.Keywords: object type, business model, conceptual distance, measure theory, measurement theory, metric, pseudo-metric, scale type, measure validation.Measurement; Model; Models; Software;

Costs, Benefits and Value Distribution – Ingredients for Successful Cross-Organizational ES Business Cases

This paper introduces my PhD research project on developing guidelines for creating successful business cases for Enterprise System implementations in network settings. Three important aspects that were found to be important in such business cases are: the costs, benefits and the value distribution within a network. Each of the three aspects is addressed in this paper and the relationships between them are pointed out. A research model is presented showing how all three aspects contribute to the main goal of defining successful business case guidelines

Annotated bibliography of software engineering laboratory literature

An annotated bibliography is presented of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. The bibliography was updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials were grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. Subject and author indexes further classify these documents by specific topic and individual author

Survey instrument for measuring level of preparedness amongst healthcare personnel in radiation emergency

Drills and exercises are globally practiced to investigate the level of preparedness towards disaster events. However, these activities are rarely conducted because they require substantial investment, specifically to budget and time. A self-reported survey may serve as an alternative approach, although it may not be as effective as drills and exercises. As part of the survey development process, this article discusses preliminary validation of a survey instrument to measure the level of preparedness towards radiation emergency amongst healthcare personnel. Prior to this validation process, extensive literature reviews pointed out that the instrument consists of three constructs of preparedness, namely readiness, willingness, and ability. A total of seven subject matter experts were invited to judge the contents for verification purposes. Randolph Kappa analysis was then conducted to analyse their judgment to allow irrelevant items to be filtered from the rest prior to any improvements. Initially, the survey instrument consisted of 69 items; however, the analysis omitted 16 of them. The following values for each preparedness construct were: Readiness (0.77), Willingness (0.70), and Ability (0.73). These findings indicate that contents of the instrument are valid. Further analysis should be fulfilled to complete validation process to ensure its practicality prior to using it as an evaluation tool

Software component testing : a standard and the effectiveness of techniques

This portfolio comprises two projects linked by the theme of software component testing, which is also often referred to as module or unit testing. One project covers its standardisation, while the other considers the analysis and evaluation of the application of selected testing techniques to an existing avionics system. The evaluation is based on empirical data obtained from fault reports relating to the avionics system. The standardisation project is based on the development of the BC BSI Software Component Testing Standard and the BCS/BSI Glossary of terms used in software testing, which are both included in the portfolio. The papers included for this project consider both those issues concerned with the adopted development process and the resolution of technical matters concerning the definition of the testing techniques and their associated measures. The test effectiveness project documents a retrospective analysis of an operational avionics system to determine the relative effectiveness of several software component testing techniques. The methodology differs from that used in other test effectiveness experiments in that it considers every possible set of inputs that are required to satisfy a testing technique rather than arbitrarily chosen values from within this set. The three papers present the experimental methodology used, intermediate results from a failure analysis of the studied system, and the test effectiveness results for ten testing techniques, definitions for which were taken from the BCS BSI Software Component Testing Standard. The creation of the two standards has filled a gap in both the national and international software testing standards arenas. Their production required an in-depth knowledge of software component testing techniques, the identification and use of a development process, and the negotiation of the standardisation process at a national level. The knowledge gained during this process has been disseminated by the author in the papers included as part of this portfolio. The investigation of test effectiveness has introduced a new methodology for determining the test effectiveness of software component testing techniques by means of a retrospective analysis and so provided a new set of data that can be added to the body of empirical data on software component testing effectiveness