Articulation of stakeholders requirements for complex e-government systems development

Requirements analysis focuses on stakeholders concerns and their influence towards e-government systems. Some characteristics of stakeholders concerns clearly show the complexity and conflicts. This imposes a number of questions in the requirements analysis, such as how are they relevant to stakeholders? What are their needs? How conflicts among the different stakeholders can be resolved? And what coherent requirements can be methodologically produced? This paper describes the problem articulation method in organizational semiotics which can be used to conduct such complex requirements analysis. The outcomes of the analysis enable e-government systems development and management to meet userspsila needs. A case study of Yantai Citizen Card is chosen to illustrate a process of analysing stakeholders in the lifecycle of requirements analysis.

A framework for assessing continuing professional development activities for satisfying pharmacy revalidation requirements

The United Kingdom’s pharmacy regulator contemplated using continuing professional development (CPD) in pharmacy revalidation in 2009, simultaneously asking pharmacy professionals to demonstrate the value of their CPD by showing its relevance and impact. The idea of linking new CPD requirements with revalidation was yet to be explored. Our aim was to develop and validate a framework to guide pharmacy professionals to select CPD activities that are relevant to their work and to produce a score sheet that would make it possible to quantify the impact and relevance of CPD. METHODS: We adapted an existing risk matrix, producing a CPD framework consisting of relevance and impact matrices. Concepts underpinning the framework were refined through feedback from five pharmacist teacher-practitioners. We then asked seven pharmacists to rate the relevance of the framework’s individual elements on a 4-point scale to determine content validity. We explored views about the framework through focus groups with six and interviews with 17 participants who had used it formally in a study. RESULTS: The framework’s content validity index was 0.91. Feedback about the framework related to three themes of penetrability of the framework, usefulness to completion of CPD, and advancement of CPD records for the purpose of revalidation. DISCUSSION: The framework can help professionals better select CPD activities prospectively, and makes assessment of CPD more objective by allowing quantification, which could be helpful for revalidation. We believe the framework could potentially help other health professionals with better management of their CPD irrespective of their field of practice.

Involving users in expert system development

The ultimate criterion of success for interactive expert systems is that they will be used, and used to effect, by individuals other than the system developers. A key ingredient of success in most systems is involving users in the specification and development of systems as they are being built. However, until recently, system designers have paid little attention to ascertaining user needs and to developing systems with corresponding functionality and appropriate interfaces to match those requirements. Although the situation is beginning to change, many developers do not know how to go about involving users, or else tackle the problem in an inadequate way. This paper discusses the need for user involvement and considers why many developers are still not involving users in an optimal way. It looks at the different ways in which users can be involved in the development process and describes how to select appropriate techniques and methods for studying users. Finally, it discusses some of the problems inherent in involving users in expert system development, and recommends an approach which incorporates both ethnographic analysis and formal user testing.

Goal sketching: towards agile requirements engineering

This paper describes a technique that can be used as part of a simple and practical agile method for requirements engineering. The technique can be used together with Agile Programming to develop software in internet time. We illustrate the technique and introduce lazy refinement, responsibility composition and context sketching. Goal sketching has been used in a number of real-world development projects, one of which is described here.

A data collection case study supporting requirements oriented prediction and management in software developments

Consider the statement "this project should cost X and has risk of Y". Such statements are used daily in industry as the basis for making decisions. The work reported here is part of a study aimed at providing a rational and pragmatic basis for such statements. Of particular interest are predictions made in the requirements and early phases of projects. A preliminary model has been constructed using Bayesian Belief Networks and in support of this, a programme to collect and study data during the execution of various software development projects commenced in May 2002. The data collection programme is undertaken under the constraints of a commercial industrial regime of multiple concurrent small to medium scale software development projects. Guided by pragmatism, the work is predicated on the use of data that can be collected readily by project managers; including expert judgements, effort, elapsed times and metrics collected within each project.

A lightweight technique for assessing risks in requirements analysis

A simple and practical technique for assessing the risks, that is, the potential for error, and consequent loss, in software system development, acquired during a requirements engineering phase is described. The technique uses a goal-based requirements analysis as a framework to identify and rate a set of key issues in order to arrive at estimates of the feasibility and adequacy of the requirements. The technique is illustrated and how it has been applied to a real systems development project is shown. How problems in this project could have been identified earlier is shown, thereby avoiding costly additional work and unhappy users.

Factors affecting biological control effectiveness of Pasteuria penetrans in Meloidogyne javanica and the bacterial development in the nematode body

The invasion and infectivity of Meloidogyne javanica juveniles (J2) encumbered with spore of Pasteuria Penetrans were influenced by the temperature and the time J2 were in the soil before exposure to roots. The percentage of infected females decreased as the time juveniles spent in soil increased. When spore encumbered J2 were maintained at 30 degrees C the decrease in infection was greater than that at 18 degrees C. The thermal time requirements and the base temperature for P. penetrans development were estimated. The rate of development followed an exponential curve between 21 and 36 degrees C and the base temperature for development was estimated by extrapolation to be 18.5 degrees C. The effect of integrating a nematode resistant tomato cultivar with the biocontrol agent P. penetrans also was investigated. The ability of the biocontrol agent to reduce numbers of root-knot nematodes was dependent on the densities of the nematode and P. penetrans spores in the soil.

The business case development process in the delivery of NHS infrastructure

There is a lack of knowledge base in relation to experiences gained and lessons learnt from previously executed National Health Service (NHS) infrastructure projects in the UK. This is in part a feature of one-off construction projects, which typify healthcare infrastructure, and in part due to the absence of a suitable method for conveying such information. The complexity of infrastructure delivery process in the NHS makes the construction of healthcare buildings a formidable task. This is particularly the case for the NHS trusts who have little or no experience of construction projects. To facilitate understanding a most important aspect of the delivery process, which is the preparation of a capital investment proposal; steps taken in developing the business case for an NHS healthcare facility are examined. The context for such examination is provided by the planning process of a healthcare project, studied retrospectively. The process is analysed using a social science based method called ‘building stories’, developed at the University of California-Berkeley. By applying this method, stories or narratives are constructed around the data captured on the case study. The findings indicate that the business case process may be used to justify, rather than identify, trusts’ requirements. The study is useful for UK public sector clients as well as consultants and professionals who aim to participate in the delivery of healthcare infrastructure projects in the UK.

A lightweight technique for assessing risks in requirements analysis

A simple and practical technique for assessing the risks, that is, the potential for error, and consequent loss, in software system development, acquired during a requirements engineering phase is described. The technique uses a goal-based requirements analysis as a framework to identify and rate a set of key issues in order to arrive at estimates of the feasibility and adequacy of the requirements. The technique is illustrated and how it has been applied to a real systems development project is shown. How problems in this project could have been identified earlier is shown, thereby avoiding costly additional work and unhappy users.

Design and development of a haptic dental training system - hapTEL

This paper presents a novel design of a virtual dental training system (hapTEL) using haptic technology. The system allows dental students to learn and practice procedures such as dental drilling, caries removal and cavity preparation for tooth restoration. This paper focuses on the hardware design, development and evaluation aspects in relation to the dental training and educational requirements. Detailed discussions on how the system offers dental students a natural operational position are documented. An innovative design of measuring and connecting the dental tools to the haptic device is also shown. Evaluation of the impact on teaching and learning is discussed.

Goal sketching: an agile approach to clarifying requirements

This paper describes a technique that can be used as part of a simple and practical agile method for requirements engineering. It is based on disciplined goal-responsibility modelling but eschews formality in favour of a set of practicality objectives. The technique can be used together with Agile Programming to develop software in internet time. We illustrate the technique and introduce lazy refinement, responsibility composition and context sketching. Goal sketching has been used in a number of real-world development.

A method for assessing confidence in requirements analysis

Context: During development managers, analysts and designers often need to know whether enough requirements analysis work has been done and whether or not it is safe to proceed to the design stage. Objective: This paper describes a new, simple and practical method for assessing our confidence in a set of requirements. Method: We identified 4 confidence factors and used a goal oriented framework with a simple ordinal scale to develop a method for assessing confidence. We illustrate the method and show how it has been applied to a real systems development project. Results: We show how assessing confidence in the requirements could have revealed problems in this project earlier and so saved both time and money. Conclusion: Our meta-level assessment of requirements provides a practical and pragmatic method that can prove useful to managers, analysts and designers who need to know when sufficient requirements analysis has been performed.

An investigation of the role of business analysts in IS development

Business analysis has developed since the early 1990s as an IS discipline that is concerned with understanding business problems, defining requirements and evaluating relevant solutions. However, this discipline has had limited recognition within the academic community and little research has been conducted into the practices and standards employed by business analysts. This paper reports on a study into business analysis that considered the activities conducted and the outcomes experienced on IS projects. Senior business analysts were interviewed in order to gain insights into the business analyst role and the techniques and approaches applied when conducting this work. The Context, Content, Process, Outcomes framework was adopted as a basis for developing the interview questions. The data collected was analysed using the template analysis technique and the template was based upon this framework. Additional themes concerning aspects of business analysis that may contribute to IS success emerged during data analysis. These included the key business analysis activities and the skills business analysts require to perform these activities. The organisational attitude was also identified as a key factor in enabling the use and contribution of business analysis.