Software Inspection Improves Quality of Software Product

Quality Software development is needful requirement in each of the software discipline. Software Inspections, Review plays very important role to maintain quality of the software. Customer satisfaction after deliver software fulfill by this concept

The Alignment Between Business Objectives Clarity and Software Objectives

This paper aims to highlight a very important concept and plays a key role in the success of software development, which is the alignment between business objectives and software objectives. In this research we refer to most of the literature that dealt with this subject. The researcher designed a questionnaire and conducted field interviews with software project managers. This study concluded with a set of recommendations and found that the alignment between business objectives and software goals plays a prominent role in software development and has a positive impact on the success of the software. Keywords: business objective, software objective, software development, alignment DOI: 10.7176/CEIS/10-2-04 Publication date:March 31st 201

Launch processing system concept to reality

The Launch Processing System represents Kennedy Space Center's role in providing a major integrated hardware and software system for the test, checkout and launch of a new space vehicle. Past programs considered the active flight vehicle to ground interfaces as part of the flight systems and therefore the related ground system was provided by the Development Center. The major steps taken to transform the Launch Processing System from a concept to reality with the successful launches of the Shuttle Programs Space Transportation System are addressed

THE AWARENESS NETWORK OF MONITORING AND DISPLAYING ACTIONS OF SOCIAL NETWORKS

The concept of awareness plays a pivotal role in research in Computer-Supported Cooperative Work. Recently, Software Engineering researchers interested in the collaborative nature of software development have explored the implications of this concept in the design of software development tools. A critical aspect of awareness is the associated coordinative work practices of displaying and monitoring actions. This aspect concerns how colleagues monitor one another’s actions to understand how these actions impact their own work and how they display their actions in such a way that others can easily monitor them while doing their own work. we focus on an additional aspect of awareness: the identification of the social actors who should be monitored and the actors to whom their actions should be displayed. We address this aspect by presenting software developers’ work practices based on ethnographic data from three different software development teams. In addition, we illustrate how these work practices are influenced by different factors, including the organizational setting, the age of the project, and the software architecture. We discuss how our results are relevant for both CSCW and Software Engineering researchers

The Case for Kairos: The Importance of Moment and Manner in Software Engineering Communication

Students preparing for software engineering careers need to be proficient in the mechanics of communication and experienced in the basic communication genres common to the profession. We argue, however, that this is not enough: students must also be prepared for the inventive, in-the-moment nature of real project communication. Choosing the right moment and manner for inventive discourse is the essence of kairos, a long-standing concept in the field of rhetoric. We find similarities between the concept of kairos and the role of communication in agile software development methods. We argue for the need to address kairos in software engineering education. We present an approach, based on the concept of cognitive apprenticeship, that we have used in a team software project course with successful results. Finally, we pose two important challenges: how to evaluate kairotic awareness across a student\u27s academic career and beyond, and how to make software engineering instructors feel comfortable covering communication topics

Position paper: Runtime Model for Role-based Software Systems

In the increasingly dynamic realities of today's software systems, it is no longer feasible to always expect human developers to react to changing environments and changing conditions immediately. Instead, software systems need to be self-aware and autonomously adapt their behavior according to their experiences gathered from their environment. Current research provides role-based modeling as a promising approach to handle the adaptivity and self-awareness within a software system. There are established role-based systems e.g., for application development, persistence, and so on. However, these are isolated approaches using the role-based model on their specific layer and mapping to existing non-role-based layers. We present a global runtime model covering the whole stack of a software system to maintain a global view of the current system state and model the interdependencies between the layers. This facilitates building holistic role-based software systems using the role concept on every single layer to exploit its full potential, particularly adaptivity and self-awareness

Classifying and evaluating architecture design methods

The concept of software architecture has gained a wide popularity and is generally considered to play a fundamental role in coping with the inherent difficulties of the development of large-scale and complex software systems. This document first gives a definition of architectures. Second, a meta-model for architecture design methods is presented. This model is used for classifying and evaluating various architecture design approaches. The document concludes with the description of the identified problems

Sprat: Hierarchies of Domain-Specific Languages for Marine Ecosystem Simulation Engineering

Scientific software is becoming more complex and its development nowadays is often an interdisciplinary process in which usually scientists - most of them without training in software engineering - implement the software themselves. To help them achieve a good code quality, we propose to employ a process called Sprat based on the concept of hierarchies of domain-specific languages (DSLs). In such a hierarchy, every DSL constitutes an implementation platform for the DSL directly above it. Each role in the development process (i.e., a scientist from a specific discipline) implements a layer of the software in a DSL belonging to the hierarchy. Therefore, the scientists only deal with abstractions they are familiar with from their respective domain and a clear separation of components is attained. To evaluate the Sprat approach, we present its application to the development of the Sprat simulation - a marine ecosystem model for long-term fish stock prediction

Software Product Line Engineering: Future Research Directions

The recent trend of switching from single software product development tolines of software products in the software industry has made the software product line concept viable and widely accepted methodology in the future. Some of the potential benefits of this approach include cost reduction, improvement in quality and a decrease in product development time. Many organizations that deal in wide areas of operation, from consumer electronics, telecommunications, and avionics to information technology, are using software product lines practice because it deals with effective utilization ofsoftware assets and provides numerous benefits. Software product line engineering is an inter-disciplinary concept. It spans over the dimensions of business, architecture, process and organization. The business dimension of software product lines deals with managing a strong coordination between product line engineering and the business aspects of product line. Software product line architecture is regarded as one of the crucial piece of entity in software product lines. All the resulting products share thiscommon architecture. The organizational theories, behavior and management play critical role in the process of institutionalization of software product line engineering in an organization. The objective of this chapter is to discuss the state of the art of software product line engineering from the perspectives of business, architecture, organizational management and software engineering process. This work also highlights and discusses the future research directions in this area thus providing an opportunity to researchers and practitioners to better understand the future trends and requirements