Top Down Implementation Plan for system performance test software

The top down implementation plan used for the development of system performance test software during the Mark IV-A era is described. The plan is based upon the identification of the hierarchical relationship of the individual elements of the software design, the development of a sequence of functionally oriented demonstrable steps, the allocation of subroutines to the specific step where they are first required, and objective status reporting. The results are: determination of milestones, improved managerial visibility, better project control, and a successful software development

Respondent Perceived Threat During the Information Systems Requirements Determination Process: Understanding and Mitigation

Requirements determination is a critical driver in a successful software development process. Despite decades of research prescribing various software development methodologies, intended to aid in achieving an eventual convergence between the user’s mental models and an informationally equivalent representation that is codified within an information system, we can still attribute many of the deficiencies in software development projects to the improper or ineffective execution of the requirements determination process. This study draws on the user resistance, software development, and psychology literature to discuss how perceived threats by potential users and key respondents can result in sub-optimization of a proposed information system via reduction in the quality of their responses during the requirements gathering phase. A laboratory experiment was carried out to explore the sources and effects of various threat perceptions and the effectiveness of techniques intended to detect and mitigate such perceptions of threat. The results confirm that perception of threat does lead to a degradation in response quality, with perceived adaptability fully mediating the relationship. The findings on whether interviewer reassurance has a moderating effect on the relationship between threat and perceived adaptability had interesting results, which are discussed

Guidelines for creating a testing process for a software - case study of comparing testing of two different size of slot game projects

Nowadays an important part of software development life cycle is software testing. As software and systems become more complex and integrated with other software and systems the importance of software testing becomes critical part of a successful software development process. Testing itself has a little value but for the software the testing is necessary. Well planned software testing can make mediocre software a great one whereas poorly executed testing can even harm the final product. Thus, it is important that there is well designed testing process for a software project. As every software project differ from each other the testing process can also vary from project to project. There are multiple levels, types and techniques of testing that can implemented to a testing process made for a certain software project. Creating an efficient and functional testing process can be a difficult task. In the case study of the paper it is concluded that two similar software projects of different size have multiple differences but do not force of creating two different testing process as both use the same kind development life cycle and both software projects are the same type, slot games. The major difference for testing is that as a major software project, compared to a minor one, has more requirements it is important to consider them in testing strategy and planning but not in the testing process

The Real World Software Process

The industry-wide demand for rapid development in concert with greater process maturity has seen many software development firms adopt tightly structured iterative processes. While a number of commercial vendors offer suitable process infrastructure and tool support, the cost of licensing, configuration and staff training may be prohibitive for the small and medium size enterprises (SMEs) which dominate the Asia-Pacific software industry. This work addresses these problems through the introduction of the Real World Software Process (RWSP), a freely available, Web-based iterative scheme designed specifically for small teams and organisations. RWSP provides a detailed process description, high quality document templates - including code review and inspection guidelines - and the integrated tutorial support necessary for successful usage by inexperienced developers and teams. In particular it is intended that the process be readily usable by software houses which at present do not follow a formal process, and that the free RWSP process infrastructure should be a vehicle for improving industry standards

Non-Technical Individual Skills are Weakly Connected to the Maturity of Agile Practices

Context: Existing knowledge in agile software development suggests that individual competency (e.g. skills) is a critical success factor for agile projects. While assuming that technical skills are important for every kind of software development project, many researchers suggest that non-technical individual skills are especially important in agile software development. Objective: In this paper, we investigate whether non-technical individual skills can predict the use of agile practices. Method: Through creating a set of multiple linear regression models using a total of 113 participants from agile teams in six software development organizations from The Netherlands and Brazil, we analyzed the predictive power of non-technical individual skills in relation to agile practices. Results: The results show that there is surprisingly low power in using non-technical individual skills to predict (i.e. explain variance in) the mature use of agile practices in software development. Conclusions: Therefore, we conclude that looking at non-technical individual skills is not the optimal level of analysis when trying to understand, and explain, the mature use of agile practices in the software development context. We argue that it is more important to focus on the non-technical skills as a team-level capacity instead of assuring that all individuals possess such skills when understanding the use of the agile practices.Comment: 18 pages, 1 figur

Allocating control in agency problems with limited liability and sequential hidden actions

This paper discusses the optimal organization of sequential agency problems with contractible control actions under limited liability. In each of two stages, a risk-neutral agent can choose an unobservable effort level. A success in the first stage makes e.ort in the second stage more effective. Should one agent be in control in both stages (integration), or should different agents be in charge of the two actions (separation)? Both modes of organization can be explained on the basis of incentive considerations due to moral hazard, without resorting to commitment problems or ad hoc restrictions on the class of feasible contracts.

Quarterly Report (QR1)

In the first quarter of the project, the participants have successfully laid the foundations for creating a stable, comprehensive, open-source cloud platform. The project has put in place the tools and processes to quickly build and expand the StratusLab distribution. Through dialog with targeted communities and through the partners' experience it has developed the initial architecture of the StratusLab distribution. The initial releases have been validated on the project's cloud infrastructure and the project has put in place the mechanisms for disseminating release information once StratusLab makes its first public release

Model-Driven Instructional Engineering to Generate Adaptable Learning Materials

Please, cite this publication as: Dodero, J. M. & Díez, D. (2006). Model-Driven Instructional Engineering to Generate Adaptable Learning Materials. Proceedings of ICALT2006. July, Kerkrade, The Netherlands: IEEE. Retrieved July 30th, 2006, from http://dspace.learningnetworks.orgThe application of software engineering approaches to generate learning material adapted to a specific instructional purpose presents some issues: the use of different models, different abstraction levels, different contexts and development concerns. These can be overcome by a model-driven development approach that provides different levels of automation for instructional engineering.ProLearn Projec