Exploring the Concept of Method Rationale

2011 ◽  
pp. 63-78 ◽  
Author(s):  
Pär J. Aerfalk ◽  
Brian Fitzgerald
Keyword(s):  
Software Development ◽  
Systems Development ◽  
Analytic Tool ◽  
Research Areas ◽  
Development Processes ◽  
Development Methods ◽  
Different Levels

Systems development methods are used to express and communicate knowledge about systems and software development processes, that is, methods encapsulate knowledge. Since methods encapsulate knowledge, they also encapsulate rationale. Rationale can, in this context, be understood as the reasons and arguments for particular method prescriptions. In this chapter, we show how the combination of two different aspects of method rationale can be used to shed some light on the communication and apprehension of methods in systems development, particularly in the context of tailoring of methods to suit particular development situations. This is done by clarifying how method rationale is present at three different levels of method existence. By mapping existing research on methods onto this model, we conclude the chapter by pointing at some research areas that deserve attention and where method rationale could be used as an important analytic tool.

An Analysis of Process Characteristics for Developing Scientific Software

2011 ◽  
Vol 23 (4) ◽  
pp. 64-79 ◽  
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Differentiated Process Support for Large Software Projects

2009 ◽  
pp. 1-20
Author(s):  
Alf Inge Wang ◽  
Carl-Fredrik Sørensen
Keyword(s):  
Software Development ◽  
Software Projects ◽  
Individual Group ◽  
Development Organization ◽  
Process Support ◽  
Development Processes ◽  
Large Software ◽  
Organizational Levels ◽  
Different Levels ◽  
Project Level

This chapter presents a framework for differentiated process support in large software projects. Process support can be differentiated in different levels based on the size of the development organization and the need for coordination across different levels of the organization. We have defined four main perspectives: individual, group, team, and project level, where the framework consider essential issues when planning and executing the software development processes in organizations with different levels of management. Further, a guideline is provided that suggests what is required of process support in the various organizational levels.

Differentiated Process Support for Large Software Projects

2009 ◽  
pp. 2359-2378
Author(s):  
Alf Inge Wang ◽  
Carl-Fredrik Sørensen
Keyword(s):  
Software Development ◽  
Software Projects ◽  
Individual Group ◽  
Development Organization ◽  
Process Support ◽  
Development Processes ◽  
Large Software ◽  
Organizational Levels ◽  
Different Levels ◽  
Project Level

This chapter presents a framework for differentiated process support in large software projects. Process support can be differentiated in different levels based on the size of the development organization and the need for coordination across different levels of the organization. We have defined four main perspectives: individual, group, team, and project level, where the framework consider essential issues when planning and executing the software development processes in organizations with different levels of management. Further, a guideline is provided that suggests what is required of process support in the various organizational levels.

Business Action and Information Modeling - The Task of the New Millennium

2011 ◽  
pp. 110-136 ◽  
Author(s):  
Par J. Agerfalk ◽  
Goran Goldkuhl
Keyword(s):  
Business Processes ◽  
Action Theory ◽  
Systems Development ◽  
Information Modeling ◽  
Important Research ◽  
Research Areas ◽  
Business Analysis ◽  
Development Methods ◽  
Business Framework ◽  
New Millennium

In this chapter, we discuss the importance of considering the action character of information when modeling information in business processes. The Language Action Perspective (LAP) is described and proposed as the perspective of choice for information modeling – now and for the future. It is emphasized that two of the most important research areas in the new millennium are to further develop LAP and to operationalize it into systems development methods. Furthermore, the generic business framework of Business Action Theory (BAT) and the requirements engineering method VIBA/SIMM (Versatile Information and Business Analysis according to the Situation adaptable work and Information Modelling Method), as representatives of LAP, are both described and positioned within LAP. This positioning is achieved by elaborating different LAP approaches and their relationships to BAT and VIBA/SIMM.

An Analysis of Process Characteristics for Developing Scientific Software

2012 ◽  
pp. 347-363
Author(s):  
Diane Kelly
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Professional Training ◽  
Scientific Software ◽  
Development Environment ◽  
Engineering Development ◽  
Process Characteristics ◽  
Development Processes ◽  
Development Methods ◽  
Software Development Methods

The development of scientific software is usually carried out by a scientist who has little professional training as a software developer. Concerns exist that such development produces low-quality products, leading to low-quality science. These concerns have led to recommendations and the imposition of software engineering development processes and standards on the scientists. This paper utilizes different frameworks to investigate and map characteristics of the scientific software development environment to the assumptions made in plan-driven software development methods and agile software development methods. This mapping exposes a mismatch between the needs and goals of scientific software development and the assumptions and goals of well-known software engineering development processes.

Agile Knowledge Management

2011 ◽  
pp. 112-117 ◽  
Author(s):  
Meira Levy ◽  
Orit Hazzan
Keyword(s):  
Knowledge Management ◽  
Software Development ◽  
Agile Software Development ◽  
Organizational Processes ◽  
Team Members ◽  
Cultural Infrastructure ◽  
Development Processes ◽  
Agile Software ◽  
Development Methods ◽  
Common Barriers

This article is based on the assumption that Knowledge Management (KM) is a vital part of any project. Based on this working assumption, the purpose of this article is to introduce the term Agile Knowledge Management (AKM) by illustrating how the Agile Software Development (ASD) approach is suitable for the introduction of KM processes. The ASD approach emerged over the past decade in response to the unique problems that characterize software development processes (Highsmith, 2002). In general, ASD emphasizes customer needs, communication among team members, short releases and heavy testing throughout the entire development process. These ideas are implemented quite variedly by the different ASD development methods. Knowledge Management (KM) and Agile Software Development (ASD) are two organizational processes that face common barriers when introduced and applied. This article suggests that because the field of KM presents a less disciplined approach compared with ASD, it is logical that KM practitioners should learn how ASD has coped with very similar barriers. We further illustrate how it is but natural to emphasize the concept of Agile Knowledge Management (AKM) in order to improve KM processes, because ASD already encompasses the organizational and cultural infrastructure needed for KM. The pairing of KM and ASD is not new; a connection between the two concepts has been acknowledged by various researchers. For related discussions, see, for example, Dove (1999) and Holz, Melnik and Schaaf (2003). This connection, however, is not surprising because both disciplines deal with organizational culture and change management. In what follows, we further highlight the connection between the two fields. First, we show that the two processes, KM and ASD, face the same barriers when introduced into an organization. We also include some suggestions for coping with such barriers. Second, we highlight the way in which KM is already embedded into ASD processes. Thus, in order to improve KM in such processes, it should be made more explicit. Accordingly, we introduce an agile KM manifesto.

A Systematic Review and Catalog of Security Metric during the Secure Software Development Life Cycle

2020 ◽  
Vol 13 ◽  
Author(s):  
Sampada G.C ◽  
Tende Ivo Sake ◽  
Amrita
Keyword(s):  
Systematic Review ◽  
Life Cycle ◽  
Software Development ◽  
Software Security ◽  
Security Assessment ◽  
Security Metrics ◽  
Development Life Cycle ◽  
Development Processes ◽  
Secure Software Development ◽  
Software Development Life Cycle

Background: With the advancement in the field of software development, software poses threats and risks to customers’ data and privacy. Most of these threats are persistent because security is mostly considered as a feature or a non-functional requirement, not taken into account during the software development life cycle (SDLC). Introduction: In order to evaluate the security performance of a software system, it is necessary to integrate the security metrics during the SDLC. The appropriate security metrics adopted for each phase of SDLC aids in defining the security goals and objectives of the software as well as quantify the security in the software. Methods: This paper presents systematic review and catalog of security metrics that can be adopted during the distinguishable phases of SDLC, security metrics for vulnerability and risk assessment reported in the literature for secure development of software. The practices of these metrics enable software security experts to improve the security characteristics of the software being developed. The critical analysis of security metrics of each phase and their comparison are also discussed. Results: Security metrics obtained during the development processes help to improve the confidentiality, integrity, and availability of software. Hence, it is imperative to consider security during the development of the software, which can be done with the use of software security metrics. Conclusion: This paper reviews the various security metrics that are meditated in the copious phases during the progression of the SDLC in order to provide researchers and practitioners with substantial knowledge for adaptation and further security assessment.

scholarly journals Factors to be Considered When to Design Software Development Plan

2012 ◽  
Vol 6-7 ◽  
pp. 3-8
Author(s):  
Yu Gao ◽  
Xiang Zhong Feng
Keyword(s):  
Software Development ◽  
Development Plan ◽  
Team Development ◽  
Difficulty Level ◽  
Design Work ◽  
Study Results ◽  
Design Software ◽  
Development Risks ◽  
Development Methods ◽  
Main Factor

It is an important prerequisite to ensure the success of software development that designing a reasonable and suitable software development plan. In the past, when discussing the design of the software development plan, people focus limited to a specific development tasks, so the lack of universality. In order to guide design work of software development plan, starting from the perspective of software engineering, the main factor to be considered has been studied when designing software development plan. These factors are: the type and size of the software, the experience of use for reference to predecessors, difficulty level to obtain users' needs, development techniques and tools, situation of development team, development risks, the software development methods that can be chosen. This study results can improve the rationality and applicability of the software development plan.

Sign in / Sign up

Export Citation Format

Share Document