Software Measurement Activities in Small and Medium Enterprises: an Empirical Assessment

An empirical study for evaluating the proper implementation of measurement/metric programs in software companies in one area of Turkey is presented. The research questions are discussed and validated with the help of senior software managers (more than 15 years’ experience) and then used for interviewing a variety of medium and small scale software companies in Ankara. Observations show that there is a common reluctance/lack of interest in utilizing measurements/metrics despite the fact that they are well known in the industry. A side product of this research is that internationally recognized standards such as ISO and CMMI are pursued if they are a part of project/job requirements; without these requirements, introducing those standards to the companies remains as a long-term target to increase quality

A DISCUSSION ON ASSURING SOFTWARE QUALITY IN SMALL AND MEDIUM SOFTWARE ENTERPRISES: AN EMPIRICAL INVESTIGATION

Under the studies of general core activities including software inspection, review and testing to achieve quality objectives in small-medium size enterprises (SMEs), the paper presents a contemporary view of such companies against quality measures. The results from a local empirical investigation of quality standards in the Turkish software industry are reported.Around 150 software companies have been approached from which 17 detailed feedback inform that in order to ensure software quality, standards including internationally recognized International Standards Organization (ISO) and Capability Maturity Model Integration (CMMI) are given credit. However the substantial workload and resources required to obtain them are also reported as serious; downscaled frameworks of such large models proposed in the literature are not well known by the SMEs either. The paper also discusses "work around" that bypasses such standards to ease delivery of products while keeping certificates as labels just to acquire new jobs for the business

Requirements engineering for computer integrated environments in construction

A Computer Integrated Environment (CIE) is the type of innovative integrated information system that helps to reduce fragmentation and enables the stakeholders to collaborate together in business. Researchers have observed that the concept of CIE has been the subject of research for many years but the uptake of this technology has been very limited because of the development of the technology and its effective implementation. Although CIE is very much valued by both industrialists and academics, the answers to the question of how to develop and how to implement it are still not clear. The industrialists and researchers conveyed that networking, collaboration, information sharing and communication will become popular and critical issues in the future, which can be managed through CIE systems. In order for successful development of the technology, successful delivery, and effective implementation of user and industry-oriented CIE systems, requirements engineering seems a key parameter. Therefore, through experiences and lessons learnt in various case studies of CIE systems developments, this book explains the development of a requirements engineering framework specific to the CIE system. The requirements engineering process that has been developed in the research is targeted at computer integrated environments with a particular interest in the construction industry as the implementation field. The key features of the requirements engineering framework are the following: (1) ready-to-use, (2) simple, (3) domain specific, (4) adaptable and (5) systematic, (6) integrated with the legacy systems. The method has three key constructs: i) techniques for requirements development, which includes the requirement elicitation, requirements analysis/modelling and requirements validation, ii) requirements documentation and iii) facilitating the requirements management. It focuses on system development methodologies for the human driven ICT solutions that provide communication, collaboration, information sharing and exchange through computer integrated environments for professionals situated in discrete locations but working in a multidisciplinary and interdisciplinary environment. The overview for each chapter of the book is as follows; Chapter 1 provides an overview by setting the scene and presents the issues involved in requirements engineering and CIE (Computer Integrated Environments). Furthermore, it makes an introduction to the necessity for requirements engineering for CIE system development, experiences and lessons learnt cumulatively from CIE systems developments that the authors have been involved in, and the process of the development of an ideal requirements engineering framework for CIE systems development, based on the experiences and lessons learnt from the multi-case studies. Chapter 2 aims at building up contextual knowledge to acquire a deeper understanding of the topic area. This includes a detailed definition of the requirements engineering discipline and the importance and principles of requirements engineering and its process. In addition, state of the art techniques and approaches, including contextual design approach, the use case modelling, and the agile requirements engineering processes, are explained to provide contextual knowledge and understanding about requirements engineering to the readers. After building contextual knowledge and understanding about requirements engineering in chapter 2, chapter 3 attempts to identify a scope and contextual knowledge and understanding about computer integrated environments and Building Information Modelling (BIM). In doing so, previous experiences of the authors about systems developments for computer integrated environments are explained in detail as the CIE/BIM case studies. In the light of contextual knowledge gained about requirements engineering in chapter 2, in order to realize the critical necessity of requirements engineering to combine technology, process and people issues in the right balance, chapter 4 will critically evaluate the requirements engineering activities of CIE systems developments that are explained in chapter 3. Furthermore, to support the necessity of requirements engineering for human centred CIE systems development, the findings from semi-structured interviews are shown in a concept map that is also explained in this chapter. In chapter 5, requirements engineering is investigated from different angles to pick up the key issues from discrete research studies and practice such as traceability through process and product modelling, goal-oriented requirements engineering, the essential and incidental complexities in requirements models, the measurability of quality requirements, the fundamentals of requirements engineering, identifying and involving the stakeholders, reconciling software requirements and system architectures and barriers to the industrial uptake of requirements engineering. In addition, a comprehensive research study measuring the success of requirements engineering processes through a set of evaluation criteria is introduced. Finally, the key issues and the criteria are comparatively analyzed and evaluated in order to match each other and confirm the validity of the criteria for the evaluation and assessment of the requirements engineering implementation in the CIE case study projects in chapter 7 and the key issues will be used in chapter 9 to support the CMM (Capability Maturity Model) for acceptance and wider implications of the requirements engineering framework to be proposed in chapter 8. Chapter 6 explains and particularly focuses on how the requirements engineering activities in the case study projects were handled by highlighting strengths and weaknesses. This will also include the experiences and lessons learnt from these system development practices. The findings from these developments will also be utilized to support the justification of the necessity of a requirements engineering framework for the CIE systems developments. In particular, the following are addressed. • common and shared understanding in requirements engineering efforts, • continuous improvement, • outputs of requirement engineering • reflections and the critical analysis of the requirements engineering approaches in these practices. The premise of chapter 7 is to evaluate and assess the requirements engineering approaches in the CIE case study developments from multiple viewpoints in order to find out the strengths and the weaknesses in these requirements engineering processes. This evaluation will be mainly based on the set of criteria developed by the researchers and developers in the requirements engineering community in order to measure the success rate of the requirements engineering techniques after their implementation in the various system development projects. This set of criteria has already been introduced in chapter 5. This critical assessment includes conducting a questionnaire based survey and descriptive statistical analysis. In chapter 8, the requirements engineering techniques tested in the CIE case study developments are composed and compiled into a requirements engineering process in the light of the strengths and the weaknesses identified in the previous chapter through benchmarking with a Capability Maturity Model (CMM) to ensure that it has the required level of maturity for implementation in the CIE systems developments. As a result of this chapter, a framework for a generic requirements engineering process for CIE systems development will be proposed. In chapter 9, the authors will discuss the acceptance and the wider implications of the proposed framework of requirements engineering process using the CMM from chapter 8 and the key issues from chapter 5. Chapter 10 is the concluding chapter and it summarizes the findings and brings the book to a close with recommendations for the implementation of the Proposed RE framework and also prescribes a guideline as a way forward for better implementation of requirements engineering for successful developments of the CIE systems in the future

Conversion to Organic Production Software (OrgPlan, OF0159)

This is the final report for Defra Project OF0159. The Organic Conversion Planner (OrgPlan) is a computer program for farmers and advisors reducing the time input necessary for planning a conversion to organic farming. Conversion planning can help to identify whether organic management is suited to the farm and potential problems during the conversion period itself. This involves an assessment of the current situation of the farm, based on which proposals for an organic 'target (endpoint)' can be developed. This includes proposed rotation(s), cropping and stocking plan for the specific farm situation and the proposals need to be tested for their technical and financial feasibility, including impact on forage supply, nutrient requirements and financial budgets. In a final step a more detailed strategy for getting from the current situation to the target situation needs to be worked out. On the basis of such a plan a farmers can make an informed choice about the feasibility of a conversion and planning can help to reduce the risk of conversion. General whole farm planning methods can be broadly split into budgeting and optimisation methods. The former uses input and output data from existing enterprises or standard data, whereas the latter uses mathematical models to determine the optimal choice of enterprises for a maximisation of a key indicator, e.g. profit. OrgPlan uses the budgeting approach, building on experience with mainly German speaking budgeting software for organic conversion. It overcomes a number of key limitations of spreadsheet based budgeting approaches in relation to access to standard enterprise data, additional support tools (e.g. rotation planner) and ease of use. The software is structured into three major sections: In Central Resources basic standard data and farm profiles are entered, viewed and adjusted, and rotations can be planned. Access is also provided to the advisory section, containing documents about organic production standards, organic managmenet notes and a software help file. It is also possible to access these from other sections of the software. In the Scenario Planning section new files for a scenario are created, where a scenario refers to a period of several years of a farm during conversion and/or under organic management. Cropping and livestock plans are generated and a first assessment of the scenario of key farm mangement indicators, nutrients and forage budgets is provided. After adding whole farm financial data the results are transferred into the Report Builder where profit and loss and cash-flow forecasts for the scenario can be generated. Reports can be viewed on screen, printed (HTML format) or exported for further analysis in other packages (spreadsheets). A key aim in developing the software was to reduce the time input needed for conversion planning. The software is windows based and follows the layout of the EMA software (developed by UH). It was programmed in Microsoft (MS) Visual Basic, using MS Access databases for the storage of data. It used results of several DEFRA funded research projects and has relevance to the Organic Conversion Information Service (OCIS). A series of nine basic steps are needed to use the software to plan conversion. These are: viewing and modifying standard enterprise data, viewing and modifying rotations, creating a farm profile, creating and planning a conversion scenario, getting first feedback on the scenario, adding whole farm financial data, planning new investment during the scenario period and viewing and printing reports and/or export data for further analysis in other packages. The basic planning tool has been released as part of the EMA 2002 software (EMA Plan). Because of the sensitive nature of the financial calculations that are the main feature of OrgPlan, further field testing of the programme in conjunction with the Organic Standard Data Collection is envisaged in the autumn of 2002 for with experienced Organic Farming Consultants

A Conceptual Framework for Definition of the Correlation Between Company Size Categories and the Proliferation of Business Information Systems in Hungary Download article

Based on a conceptual model, this paper aims to explore the background of the decision-making process leading to the introduction of business information systems among enterprises in Hungary. Together with presenting the problems arising in the course of the implementation of such systems, their usage patterns are also investigated. A strong correlation is established between the size of an enterprise, the scope of its business activities and the range of the business information systems it applies

Development of the Integrated Model of the Automotive Product Quality Assessment

Issues on building an integrated model of the automotive product quality assessment are studied herein basing on widely applicable methods and models of the quality assessment. A conceptual model of the automotive product quality system meeting customer requirements has been developed. Typical characteristics of modern industrial production are an increase in the production dynamism that determines the product properties; a continuous increase in the volume of information required for decision-making, an increased role of knowledge and high technologies implementing absolutely new scientific and technical ideas. To solve the problem of increasing the automotive product quality, a conceptual structural and hierarchical model is offered to ensure its quality as a closed system with feedback between the regulatory, manufacturing, and information modules, responsible for formation of the product quality at all stages of its life cycle. The three module model of the system of the industrial product quality assurance is considered to be universal and to give the opportunity to explore processes of any complexity while solving theoretical and practical problems of the quality assessment and prediction for products for various purposes, including automotive