The suitability of PRINCE2 for engineering infrastructure

The view that PRINCE2 was not suitable for application to infrastructure was identified in a study done for a separate purpose, namely, to examine project governance and methodology, which is not reported in this paper. It was asserted by several participants in interviews conducted with a sample of experienced practitioners across a range of industries and disciplines. This paper follows up on those comments by conducting an examination of PRINCE2 from an engineering infrastructure perspective to investigate the validity of this assertion. It takes a deductive, definitional approach to determine if there are any features in it that would cause difficulty for engineering infrastructure use. Seventeen features were examined, and 15 were found to have difficulty in application to the project management of engineering infrastructure. The remaining two found inconsistencies that were unlikely to cause too much difficulty. The features causing difficulty include non-generic terminology for the terms project, lifecycle and stage, using a product rather than a project-based process, use of an iterative product delivery process unsuited to predictive projects, use of a delivery process for all project phases, assumption of a board governance model with inappropriate accountabilities, lack of clarity around the use of the project plan, and absence of a lifecycle appropriate for engineering infrastructure, with PRINCE2 effectively self-declaring its need for a higher-level project lifecycle/ methodology from somewhere else. The paper concludes that PRINCE2 is quite poorly suited to managing engineering infrastructure projects and identifies that some of the reasons for this are likely to also cause difficulty for many ICT projects as well

<i>Trace++</i>: A Traceability Approach for Agile Software Engineering

Agile methodologies have been introduced as an alternative to traditional software engineering methodologies. However, despite the advantages of using agile methodologies, the transition between traditional and agile methodologies is not an easy task. There are several problems associated with the use of agile methodologies. Examples of these problems are related to (i) lack of metrics to measure the amount of rework that occurs per sprint, (ii) interruption of a project after several iterations, (iii) changes in the requirements, (iv) lack of documentation, and (v) lack of management control. In this paper we present Trace++, a traceability technique that extends traditional traceability relationships with extra information in order to support the transition between traditional and agile software development. The use of Trace++ has been evaluated in two real projects of different software development companies to measure the benefits of using Trace++ to support agile software development

A Product Line Systems Engineering Process for Variability Identification and Reduction

Software Product Line Engineering has attracted attention in the last two decades due to its promising capabilities to reduce costs and time to market through reuse of requirements and components. In practice, developing system level product lines in a large-scale company is not an easy task as there may be thousands of variants and multiple disciplines involved. The manual reuse of legacy system models at domain engineering to build reusable system libraries and configurations of variants to derive target products can be infeasible. To tackle this challenge, a Product Line Systems Engineering process is proposed. Specifically, the process extends research in the System Orthogonal Variability Model to support hierarchical variability modeling with formal definitions; utilizes Systems Engineering concepts and legacy system models to build the hierarchy for the variability model and to identify essential relations between variants; and finally, analyzes the identified relations to reduce the number of variation points. The process, which is automated by computational algorithms, is demonstrated through an illustrative example on generalized Rolls-Royce aircraft engine control systems. To evaluate the effectiveness of the process in the reduction of variation points, it is further applied to case studies in different engineering domains at different levels of complexity. Subject to system model availability, reduction of 14% to 40% in the number of variation points are demonstrated in the case studies.Comment: 12 pages, 6 figures, 2 tables; submitted to the IEEE Systems Journal on 3rd June 201

Linking design and manufacturing domains via web-based and enterprise integration technologies

The manufacturing industry faces many challenges such as reducing time-to-market and cutting costs. In order to meet these increasing demands, effective methods are need to support the early product development stages by bridging the gap of communicating early design ideas and the evaluation of manufacturing performance. This paper introduces methods of linking design and manufacturing domains using disparate technologies. The combined technologies include knowledge management supporting for product lifecycle management (PLM) systems, enterprise resource planning (ERP) systems, aggregate process planning systems, workflow management and data exchange formats. A case study has been used to demonstrate the use of these technologies, illustrated by adding manufacturing knowledge to generate alternative early process plan which are in turn used by an ERP system to obtain and optimise a rough-cut capacity plan

Managing design variety, process variety and engineering change: a case study of two capital good firms

Many capital good firms deliver products that are not strictly one-off, but instead share a certain degree of similarity with other deliveries. In the delivery of the product, they aim to balance stability and variety in their product design and processes. The issue of engineering change plays an important in how they manage to do so. Our aim is to gain more understanding into how capital good firms manage engineering change, design variety and process variety, and into the role of the product delivery strategies they thereby use. Product delivery strategies are defined as the type of engineering work that is done independent of an order and the specification freedom the customer has in the remaining part of the design. Based on the within-case and cross-case analysis of two capital good firms several mechanisms for managing engineering change, design variety and process variety are distilled. It was found that there exist different ways of (1) managing generic design information, (2) isolating large engineering changes, (3) managing process variety, (4) designing and executing engineering change processes. Together with different product delivery strategies these mechanisms can be placed within an archetypes framework of engineering change management. On one side of the spectrum capital good firms operate according to open product delivery strategies, have some practices in place to investigate design reuse potential, isolate discontinuous engineering changes into the first deliveries of the product, employ ‘probe and learn’ process management principles in order to allow evolving insights to be accurately executed and have informal engineering change processes. On the other side of the spectrum capital good firms operate according to a closed product delivery strategy, focus on prevention of engineering changes based on design standards, need no isolation mechanisms for discontinuous engineering changes, have formal process management practices in place and make use of closed and formal engineering change procedures. The framework should help managers to (1) analyze existing configurations of product delivery strategies, product and process designs and engineering change management and (2) reconfigure any of these elements according to a ‘misfit’ derived from the framework. Since this is one of the few in-depth empirical studies into engineering change management in the capital good sector, our work adds to the understanding on the various ways in which engineering change can be dealt with

Effect of waste plaster of Paris on physical and mechanical properties of ceramic pottery body

Over the years, millions tonnes of waste plaster of Paris (POP) were generated and disposed in landfills or most of the time was dumped directly into the environment without any treatments, makes it as one of the environmental issues. Therefore, a new alternative is required to convert the wastes POP into useful materials and marketable to minimize the environmental impact. In the early stage, this study focused on the characterization of the raw material used through particle size analysis, thermal analysis, and identification of its purity. Then, the slip casting technique and standard American Society for Test and Materials (ASTM) was respectively used to fabricate and characterize all of the pottery samples. In the second stage, the ceramic pottery body was fabricated using different composition of waste POP, started from 0 wt.% until 12 wt.%. The samples obtained were analysed through viscosity test and its green body was observed. The results showed that the samples with compositions of 0 to 10 wt.% of waste POP were the only samples that can be used in this study. The analysis on the effects of particle sizes ranging from 25 to 73 μm and sintering temperatures ranging from 950 to 1050 °C on the physical and mechanical properties of the fabricated ceramic pottery body, respectively, were then determined in the third and fourth stage of this study. The physical properties were reported in terms of shrinkage, porosity, and density values; whereas, the mechanical properties were reported in terms of the value of modulus of rupture (MOR). The result showed that a dense and a high strength of ceramic pottery can be produced by using a finer size of particle of 25 μm and at a high sintering temperature of 1050 °C, based on the low porosity value, the high density value, MOR and also the controllable value of shrinkage. Therefore, it can be concluded that the waste POP can be successfully used as a filler to enhance the properties of ceramic pottery body

European Information System for Organic Markets (EISFOM QLK5-2002-02400): WP 2: “Data collection and processing systems (DCPS) for the conventional markets” and WP 3: “Data collection and processing systems for organic markets” = Deliverable D2

European markets for organic products are developing fast. In Europe, as other parts of the world, more and more farm land is being converted to organic production. In order to adjust production and consumption levels, detailed market information is needed, especially where decisions with a long-term impact need to be taken, for example on converting specific land or livestock enterprises requiring high levels of investment in glasshouses, housing, processing facilities etc. Since public subsidies (regional / national / European) are heavily involved in these investments, valid, accurate and up-to-date information is essential not only for farmers and growers, but also for policy-makers, consultants, processing industry etc. EU-research projects such as OFCAP (FAIR3-CT96-1794) and OMIaRD (QLK5-2000-01124) have shown that regional or national data gathering takes place in many countries, but often only very basic data are reported, such as certified organic holdings, land areas and livestock numbers. Important market data, e.g. the amount of production, consumption, international trade or producer and consumer prices, do not exist in most European countries. In some European countries there are only rough estimates of the levels of production and consumption. There is no standardization and data are seldom comparable. Furthermore, detailed information on specific commodities is missing. Hence, investment decisions are taken under conditions of great uncertainty. Likewise, if politicians want to support organic agriculture, they do not know whether it would be better to support production or consumption or to address problems in the marketing channel. The EU concerted action EISfOM (QLK5-2002-02400) (European Information System for Organic Markets) is attempting to take the first steps in solving these problems. The aim of this concerted action is to build up a framework for reporting valid and reliable data for relevant production and market sectors of the European organic sector in order to meet the needs of policy-makers, farmers, processors, wholesalers and other actors involved in organic markets. In order to reach this aim, this action was split into several workpackages. This report describes the approach and results of workpackages 2 and 3. In this first chapter the objective and general approach of these work packages are described. Chapters 2 and 3 provide an overview of international statistics and data collection systems within the food supply chain at the public and the private level. Chapter 4 describes national statistics and data collection systems within the food supply chain. In Chapter 5, an analysis and appraisal is made of the results with regard to organic data collection and processing systems (DCPSs) and their integration into existing common DCPSs. Chapter 6 draws several general conclusions. Two substantial annexes complete the report, one with the country reports on the situation of data collection and processing in all investigated countries and the other with the first and the second stage questionnaires covering the different data collection levels

UK and EU policy for approval of pesticides suitable for organic systems: Implications for Wales

This study was commissioned by the Welsh Assembly Government (WAG) to review the pesticide approval system in the UK and Europe as far as it affects the use of substances and techniques for crop protection by organic producers in Wales. WAG considers it important that the UK pesticide approval system does not present unnecessary barriers to the development of organic production in Wales. Key Recommendations and scope for further work · WAG should work with the Pesticides Safety Directorate to ensure that the development of pesticide regulatory policy at both National and European level takes full account of the needs of both conventional and organic agriculture and horticulture in the UK. · There is scope for WAG to support the development of a National Pesticide Policy so that regulatory and commercial barriers impeding the development of organic pesticides are minimised. Not only could greater availability of ‘organic pesticides’ have a significant impact on organic production in Wales but there could be important implications for conventional horticulture systems and the use of alternatives to conventional pesticides. · One important regulatory barrier to the registration of ‘organic pesticides’ is the MRL requirement(s) for their approval and this needs to be resolved. Suitable analytical techniques are required to determine firstly whether these substances result in residues, and secondly to identify the breakdown and residue pathways. So far, this issue has not received the attention of any EU Member State. · According to the proposed framework for the 4th Stage Review of EU Pesticides Directive 91/414, notifiers are required to produce a dossier, at their own expense, covering characterisation, human toxicity, ecotoxicity efficacy and other relevant data. The Review includes specific provision for companies notifying the same substance to submit a shared dossier. This will help those businesses (many of which are relatively small companies) to save on the high cost of producing the dossiers. It will also aid the Commission since it will reduce the number of dossiers that have to be considered, and ensure that all the available data is included. WAG should encourage and support the production of collective dossiers; although as yet there is no indication of how this will be done in practice, and further details from the Commission are awaited. · This study has concluded that access to a wider range of ‘organically acceptable pesticides’ would not have a dramatic impact on organic production in Wales. However, in developing an integrated organic policy, WAG should continue to address the pesticides issue. Some of the methods of pest & disease control in organic systems are either physical or multi-cellular e.g. micro-organisms used as biocontrol agents. WAG agri environment policy may provide a vehicle to promote these techniques much more actively. Further, it is important to recognise that while Wales alone is too small to have a major impact on commercial and regulatory pressures, WAG can have an impact by working pro-actively with others to make progress. · There are no published EU or national Member State criteria that can be used to evaluate the acceptability of pesticide substances for organic production. Identifying such criteria and promoting their acceptance at EU level and nationally would allow more active substances to be made available. WAG should work with PSD and others to identify appropriate criteria. · The specific provisions of Article 7 in Annex 2(b) of the Organic Regulation (2092/91) place potential barriers to the adoption of organically acceptable substances for crop protection. There are a number of potentially useful substances currently not included in the Organic Regulation e.g. potassium bicarbonate. WAG should work with PSD and others to identify such substances and support the production of appropriate dossiers. WAG could also encourage further dialogue between the organic sector and Defra to identify amendments in the Organic Regulations to facilitate the inclusion of new pesticides. · Organic pest and disease management is not just a question of inputs but it also relies crucially on advice and extension through initiatives such as Farming Connect and the work of Organic Centre Wales. Long-term commitment to supporting on going advice and extension activities is vital to promote and disseminate best practice in Welsh agriculture and horticulture. · Organic horticulture, vegetable and fruit production systems are particularly sensitive to pest and disease management. Successful control of pests, diseases (and weeds) in these sectors can be critical to the business, and is not assured even when all husbandry and management methods have been effectively applied. Consequently, the use of organically acceptable crop protection methods resulting from future developments (e.g. biopesticides, biological control agents) could have an important role in pest and disease management in these sectors. Both organic and conventional producers in Wales could benefit from having these options available to them and WAG could encourage the adoption of these approaches through appropriate Technology Transfer activities. · The way in which such substances will be regulated at a European level in future is evolving as the review of the Pesticide Directive 91/414 EEC enters the 4th Stage. This stage of the review includes (amongst others) those substances permitted for use in organic production. The guidance documents for the evaluation of applications on plant protection products made from plants or plant extracts and from chemical substances are currently at the draft stage. The response of the Pesticide Safety Directorate and Defra to these developments is not yet clear but this provides an excellent opportunity for WAG to have an input at an early stage in the review process

Incorporating Agile with MDA Case Study: Online Polling System

Nowadays agile software development is used in greater extend but for small organizations only, whereas MDA is suitable for large organizations but yet not standardized. In this paper the pros and cons of Model Driven Architecture (MDA) and Extreme programming have been discussed. As both of them have some limitations and cannot be used in both large scale and small scale organizations a new architecture has been proposed. In this model it is tried to opt the advantages and important values to overcome the limitations of both the software development procedures. In support to the proposed architecture the implementation of it on Online Polling System has been discussed and all the phases of software development have been explained.Comment: 14 pages,1 Figure,1 Tabl