Search results for "Software Development Process"
showing 10 items of 33 documents
Explaining Change Paths of Systems and Software Development Practices
2010
This chapter discusses how systems development practices are shaped. Based on interviews conducted in ten development organizations and previous literature, we identify eight types of change paths in systems development practices: emergence, adoption, idealization, formalization, abandonment, informalization, entropy, and disobedience. We argue that the eight change path types provide an integrated theoretical framework on the study of how systems development practices change in organizations, projects, and among individual developers in a given context. We discuss how this framework complements existing theories and concepts of the contemporary literature on systems development.
MetaEdit+ A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment
1996
Computer Aided Software Engineering (CASE) environments have spread at a lower pace than expected. One reason for this is the immaturity of existing environments in supporting development in-the-large and by-many and their inability to address the varying needs of the software developers. In this paper we report on the development of a next generation CASE environment called MetaEdit+. The environment seeks to overcome all the above deficiencies, but in particular pays attention to catering for the varying needs of the software developers. MetaEdit+ is a multi-method, multi-tool platform for both CASE and Computer Aided Method Engineering (CAME). As a CASE tool it establishes a versatile an…
The Place and Role of Security Patterns in Software Development Process
2006
Security is one of the key quality attributes for many contemporary software products. Designing, developing, and maintaining such software necessitates the use of a secure-software development process which specifies how achieving this quality goal can be supported throughout the development life-cycle. In addition to satisfying the explicitly-stated functional security requirements, such process is aimed at minimising the number of vulnerabilities in the design and the implementation of the software. The secure software development is a challenging task spanning various stages of the development process. This inherent difficulty may be to some extent alleviated by the use of the so-called…
A modest but practical software process modeling technique for software process improvement
2002
One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals. Copyright © 2002 John Wiley & Sons, Ltd.
OntoFrame
2009
A large number of strategies, approaches, meta models, techniques and procedures have been suggested to support method engineering (ME). Most of these artifacts, here called the ME artifacts, have been constructed, in an inductive manner, synthesizing ME practice and existing ISD methods without any theory-driven conceptual foundation. Also those ME artifacts which have some conceptual groundwork have been anchored on foundations that only partly cover ME. This chapter presents an ontological framework, called OntoFrame, which can be used as a coherent conceptual foundation for the construction, analysis and comparison of ME artifacts. Due to its largeness, the authors here describe its mod…
How to Comprehend Large and Complicated Systems
2002
The basic problem at early analysis stage of the development life cycle is how to quickly comprehend a large and complicated system. One of the ways to comprehend such a system is to build an object model, as it was suggested by the pioneers of object modelling approach such as J.Rumbaugh1 and J.Martin2. In up-to-date terminology it means building a UML class diagram. The authors have got convinced in their everyday practice on extreme efficiency of this type of modelling, though at the same time a significant experience for this job is also required. To make this job easier, a modelling methodology must be developed. The goal of this paper is, on the one hand, to give some methodological r…
Considerations for Using Domain-Specific Modeling in the Analysis Phase of Software Development Process
2002
Recent studies claim that domain-specific modeling may highly increase development productivity in specific well-defined domains. Domain-specific modeling is most often used only in the design phase of software development process, while general-purpose modeling techniques are used in the other phases. Integrating general-purpose modeling techniques with domain-specific modeling might be problematic, which is why in this paper we consider if it is feasible to extend domain-specific modeling to cover analysis phase activities in addition to design phase activities. Essentially, we discuss the different activities in analysis phase and consider whether or not domain-specific techniques can be…
Improving the Reuse Process is Based on Understanding the Business and the Products: Four Case Studies
2002
The reuse of software engineering assets has been proposed as the most promising alternative for improving productivity and software quality. The improvement of reuse requires understanding of suitable reuse strategies and the software process. In four industrial cases the reuse process is analyzed for the purpose of its improvement and remarkable differences between successful processes are found. Those differences are due to differences in the products and businesses of the analyzed companies. In some cases the product line approach fits the business very well and high level of reuse can be achieved by using it. In other cases the black-box approach to reuse has turned out to suit the bus…
Usability Work in Agile Systems Development Practice: A Systematic Review
2013
In this chapter we present the results of a systematic literature review of the recommendations in the existing research literature on usability work in agile systems development. The review contributes by summarizing the literature in light of seven claims about how to integrate usability work into an agile development project. By analyzing the claims we show how the previous literature provides grounds, warrants, backing, rebuttal, and qualification with regard to each of them. From this comprehensive overview of the literature we then discuss a research agenda with a particular focus on how situational factors for the claims must be researched and how this must encompass identified rebut…
Software Inspections in Practice: Six Case Studies
2006
Software inspections have been acknowledged as an important method in software engineering, but they are not well applied in practice. This paper discusses the current practices and the related problems based on six case studies in industrial settings. The analysis of inspection practices was organized according to ICMM, which is a model for systematically assessing and improving software inspection process maturity. The sample case organizations used inspections relatively regularly. The involved units are compared and the revealed practices, their characteristics, inspection problems and implications of the study discussed. The main problem areas were non-existent inspection training, lim…