The most risk-averse system with a security architecture including layers upon layers of defenses-in-depth can still be vulnerable to violations and compromises if the software that implements those layered defenses is not dependable, trustworthy, and survivable. The reality is this: software has l

These so-called Agile Methods are creating a buzz in the software development community, drawing their fair share of advocates and opponents. The purpose of this report is to address this interest and provide a comprehensive overview of the current State-of-the-Art, as well as State-of-the-Practice

The purpose of this revised State of the Art Report (SOAR) is to provide new insights into the details necessary to demonstrate from a business perspective the benefits of improved software management using software process improvement (SPI) techniques. SPI has received much attention in recent yea

We all understand the importance of data to manage any program, whether it is estimated data for planning purposes or actual data for monitoring project progress and performance.

There has been so much published about cloud computing in the last couple of years it would seem difficult to find new things to say about it. However, the model is changing so rapidly there is indeed plenty to say about it, and there will be for years to come. As you will read in "Cloud Comput

This is a bundle of all of the Journal of Software Technology PDF's we have online.

Tech Views by Dan Ferens, Co-Editor, Software tech News And Ellen Walker, Editor, Software Tech News Software quality is sometimes overlooked as a key objective in developing software; cost, schedule, and scope considerations prevail, and quality is treated as a “nice to have”,

-Future Challenges and Rewards for Software Engineers .... Dr. Barry Boehm, USC<br> -Addressing the Software Engineering Challenges Over the Years and Into the Future...............Dr. Kenneth Nidiffer, SEI<br> -Navy C4I Open Architecture Strategy ...............Mr. Chris Miller, NAVY

Metrics-based scheduling is about establishing realistic software development or maintenance schedules based on accurate estimates of software size and effort. The practice necessitates use of a minimum set of four metrics (namely, software size, effort, time/schedule and quality) coined by the Sof

The process of eliciting, documenting, organizing, and tracking changing requirements and communicating this information across the project team to ensure that iterative and unanticipated changes are maintained throughout the project lifecycle. Requirements management is premised on accepting se

Acquisition process improvement has been defined as the analysis of current software acquisition processes for deficiencies and implementing new/modified processes to correct those deficiencies [Eslinger, 1999]. The definition provided in Turner’s dissertation [Turner, 2002] incorporates the concep

Establishing quality targets (e.g. defects per Function Point) and then tracking defects against those targets in order to track progress during testing activities

The achievement of a demonstrable balance among driving requirements, architecturally significant design decisions, and the life-cycle plans before resources are committed for full-scale development Every software system has an architecture because every system has one or more components that are