Summary of the 1st International Workshop on Hybrid Development Approaches in Software Systems Development

2018 ◽  
Vol 42 (4) ◽  
pp. 18-20 ◽  
Author(s):  
Marco Kuhrmann ◽  
Jürgen Münch ◽  
Paolo Tell ◽  
Philipp Diebold
Keyword(s):  
International Workshop ◽  
Systems Development ◽  
Software Systems ◽  
Hybrid Development

Evolution and Maintenance of Web Sites

2011 ◽  
pp. 255-271
Author(s):  
Rafael Capilla ◽  
Juan C. Duenas
Keyword(s):  
Web Sites ◽  
Systems Development ◽  
Product Line ◽  
Software Systems ◽  
Software Products ◽  
Software Companies ◽  
Software Engineers ◽  
The Common ◽  
Common Architecture ◽  
The Web

In this chapter we describe the product line models, and show how to apply them for developing and evolving Web products. A product line captures the common and variable aspects of software systems as key assets under a common architecture. Software companies are increasingly adopting this approach in order to accelerate the development of families of similar software products. In certain domains, such as the Web systems, development and maintenance operations are required more often. New techniques to engineer Web sites are needed in order to reduce the time to market for the Web products and to maintain the systems afterward. The authors believe that understanding the notion of lightweight product line and the role that the architecture plays will help software engineers in the construction of software products, and they will be able to manage the evolution effectively against future changes.

Influential Agile Software Parameters

2011 ◽  
pp. 1938-1943
Author(s):  
Subhas C. Misra ◽  
Vinod Kumar ◽  
Uma Kumar
Keyword(s):  
Project Management ◽  
Software Process ◽  
Systems Development ◽  
The Other ◽  
Software Systems ◽  
Software Projects ◽  
Optimal Cost ◽  
Management Processes ◽  
Agile Software ◽  
Refining Processes

Successful software systems development is a delicate balance among several distinct factors (Jalote, 2002) such as enabling people to grow professionally; documenting processes representing the gained experiences and knowledge of the organization members; using know how to apply the suitable processes to similar circumstances; and refining processes based on achieved experience. Software projects have two main dimensions: engineering and project management. The engineering dimension concerns the construction of a system, and focuses mainly on issues such as how to build a system. The project management dimension is in charge with properly planning and controlling the engineering activities to meet project goals for optimal cost, schedule, and quality. For a project, the engineering processes specify how to perform activities such as requirement specification, design, testing, and so on. The project management processes, on the other hand, specify how to set milestones, organize personnel, manage risks, monitor progress, and so on (Jalote, 2002). A software process may be defined as “a set of activities, methods, practices, and transformations that people use to develop and maintain software, and the associated products and artifacts.”1 This is pictorially depicted in Figure 1 (Donaldson & Siegel, 2000).

Toward an Integrative Model of Application-Software Security

2003 ◽  
pp. 157-163
Author(s):  
Vijay V. Raghavan
Keyword(s):  
Software Security ◽  
Social Engineering ◽  
Systems Development ◽  
System Level ◽  
Integrative Model ◽  
Software Systems ◽  
Execution Monitoring ◽  
Systems Security ◽  
Least Privilege ◽  
Implementation Stages

Populist approaches to studying information systems security include architectural, infrastructure-related and system-level security. This study focuses on software security implemented and monitored during systems development and implementation stages. Moving away from the past checklist methods of studying software security, this study provides a model that could be used in categorizing checklists into meaningful clusters. Many constructs, such as principle of least privilege, execution monitoring, social engineering and formalism and pragmatism in security implementations, are identified in the model. The identification of useful constructs to study can form the basis of evaluating security in software systems as well as provide guidelines of implementing security in new systems developed.

Sign in / Sign up

Export Citation Format

Share Document