Search results for "development process"
showing 10 items of 50 documents
Special education without teaching assistants? : The development process for students with autism
2020
Many children may need the help of another person to attend school. It is common for children with disabilities to receive help from a teaching assistant at school. Assistants are provided in many countries as a legal right and are often publicly funded. It is also widely assumed that having teaching assistants in the class is an effective and cost-efficient way to support students with disabilities. In this study, the research task was to monitor and document the development process carried out by the teacher, with the aim of making visible the development of a more dynamic classroom interaction. The focus in this development process was the teacher’s idea of minimizing the conta…
An Information Systems Design Product Theory for Software Project Estimation and Measurement Systems
2009
There is relatively little research on software Project Estimation and Measurement Systems (PEMS). Commercial PEMS vary in functionality and effective- ness. Their intended users thus do not know what to ex- pect from PEMS and how to evaluate them. This paper creates an information system design product theory for the class of PEMS that prescribes the meta-requirements, the meta-design, and applicable theories for all products within the class. Meta-requirements and the meta-design are derived from the project estimation and measurement literature, experiences obtained during more than ten years of empirical work in Finnish Software Measurement Association, and a commercially available PEMS.
A Proposal for Modelling Usability in a Holistic MDD Method
2014
Holistic methods for Model-Driven Development (MDD) aim to model all the system features in a conceptual model. This conceptual model is the input for a model compiler that can generate software systems by means of automatic transformations. However, in general, MDD methods focus on modelling the structure and functionality of systems, relegating the interaction and usability features to manual implementations at the last steps of the software development process. Some usability features are strongly related to the functionality of the system and their inclusion is not so easy. In order to facilitate the inclusion of functional usability features from the first steps of the development proc…
Low Degree of Separation Does Not Guarantee Easy Coordination
2012
In the times of increased global competition, software companies are forced to search for more effective development practices and often team up with onshore and offshore partners to develop faster and better products. In this paper we empirically explore a highly distributed onshore development project with a complex coordination structure. Our findings demonstrate that onshore development projects are not protected from coordination and communication challenges and task allocation complexities. Previously reported qualitative findings regarding organizational problems in this paper are supplemented with quantitative measurements of the true coordination delays and additional analysis of c…
Comprehensive System for Systematic Case-Driven Software Reuse
2010
Reuse of software artifacts (blueprints and code) is normally associated with organising a systematic reuse framework most often constructed for a specific problem domain. In this paper we present a system (language, tool, reuse process) where software reuse is based on building and retrieving of so-called software cases (large compound artifacts) that can be reused between domains. The system is opportunistic in that software cases result from usual (non-reuse oriented) activities where also semantic information is added. This information is used to support regular development but may serve later to retrieve software cases. Having this common semantic basis, we can organise a systematic cr…
Software Business in the Telecommunications Sector
2012
Operations and Business Support Systems (OSS/BSS) software of Communication Service Providers (CSP's) can be developed internally within the CSP or acquired from a Software Vendor. The software industry lifecycle model hypothesizes that software development is internal in the beginning of the industry's lifecycle, and that the share of external products increases when it matures. Empirical evidence shows signs of the OSS/BSS software industry approaching maturity. Current and future developments of the industry include the possibilities of utilizing the Software-as-a-Service (SaaS) model and Open Source software (OSSw). Both have gained increasing interest by the CSP's. However, the relativ…
Learning and organizational change in SPI initiatives
2009
Explaining how organizations chance has been a central and enduring quest of management scholars and many other disciplines. In order to be successful change requires not only a new process or technology but also the engagement and participation of the people involved. In this vein the change process results in new behavior and is routinized in practical daily business life of the company. Change management provides a framework for managing the human side of these changes. In this article we present a literature review on the change management in the context of Software Process Improvement. The tra- ditional view of learning, as a “lessons learned” or post-mortem reporting activity is often…
Requirements Engineering and Process Modelling in Software Quality Management— Towards a Generic Process Metamodel
2004
This paper examines the concept of Quality in Software Engineering, its different contexts and its different meanings to various people. It begins with a commentary on quality issues for systems development and various stakeholders' involvement. It revisits aspects and concepts of systems development methods and highlights the relevance of quality issues to the choice of a process model. A summarised review of some families of methods is presented, where their application domain, lifecycle coverage, strengths and weaknesses are considered. Under the new development era the requirements of software development change; the role of methods and stakeholders change, too. The paper refers to the …
Smart Technologies in Software Life Cycle
2007
In software life cycle models traditionally the main attention is being paid to the software development, including requirement gathering (specification), design, implementation and testing. Less research is devoted to the system maintenance and operation despite the fact that these aspects take up the main part of the duration of a successful system. In the paper smart technologies are being analysed - architectural designs and software components which using meta information on system and its usage conditions are able to solve efficiently the problems of maintenance and usage: data quality and performance monitoring, software flexibility and testability, context dependant user interface. …
The Personal Software Process, Experiences from Denmark
2003
Software process improvement (SPI) research and practice is transforming from the traditional large-scale assessment based improvement initiatives into smaller sized, tailored initiatives where the emphasis is set on the development personnel and their personal abilities. The personal software process (PSPSM) is a method for improving the personal capabilities of a single software engineer. This paper contributes to the body of knowledge within this area by reporting experiences from Denmark. The results indicate an improvement in the effort estimation skills and a significant increase in the resulting product quality in terms of reduced total defect density. The data shows that with relati…