Architecting software systems is a knowledgeintensive activity. It requires significant knowledge about architecting in general, but also about domains and technologies. Such knowledge should be managed systematically to make it available throughout the whole software development cycle (e.g. to facilitate maintenance). Architectural knowledge management (AKM) literature covers organizations in ...

Time is an essential measure of performance in software development because time delays tend to fall directly to the bottom line. To address this issue, this research seeks to distinguish time-based software development practices: those managerial actions that result in faster development speed and higher productivity. This study is based upon a survey of software management practices in Wester...

Software project development includes a number of activities that result in a delivered product (software). As software becomes more and more expensive to develop, project management has been recognised as a difficult task in practice. There are a lot of unpredictable factors existing in the software development cycle that have become contributing factors to this problem. This paper gives an ov...

This paper describes an ongoing empirical investigation into software project schedule behaviour at a leading, international software development organisation. Due to the complexity of the phenomena being observed and the diversity and volume of empirical evidence being collected, a framework is proposed. The framework both facilitates the organisation of single and multiple sources of evidence...

Software tools play an important role in the software development process. Some tools are used by users taking on one specific role, in very specific activities and to process documents of a specific type (e.g., a compiler). Other tools are used by users in multiple roles, during many activities and for processing documents of multiple types (e.g., a configuration management system). Inserting ...

Limiting the focus of risk analysis to quantifiable factors and using a narrow understanding of the scope of a software project are major contributors to significant software failures. A Software Development Impact Statement (SoDIS) process is presented which extends the concept of software risk in three ways; --it moves beyond the limited approach of schedule, budget, and function, --it adds q...

Software development is a complex, knowledgeintensive, and innovative process that frequently takes place in an extremely competitive and highly uncertain environment. For a long time, software developers have used traditional-structured approaches that are more disciplined and focus on coordinated actions to ensure the software goals are met. Recently, this traditional way of software developm...

There have been many studies and examples in the literature separately demonstrating the benefits of Agile software development and Software Configuration Management process to software development organizations. There is, however, a general misconception that these two practice domains cannot coexist in a single environment without compromising the values of each other, and there is little rep...

Risk is not always avoidable, but it is controllable. The aim of this paper is to present new techniques which use the stepwise regression analysis to model and evaluate the risks in planning software development and reducing risk with software process improvement. Top ten software risk factors in planning software development phase and thirty control factors were presented to respondents. This...

Software development is a complex activity. It is involved with different scenarios and risks which must be managed through a systematic approach to Software Risk Management (SRM). The best software process depends on the project’s particularities. Situational Method Engineering (SME) focuses on building project specific method/process according to the situation at hand. This paper proposes an ...