A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Managing the development of large software systems: concepts and techniques
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Principles of information systems analysis and design
Principles of information systems analysis and design
Software risk management
Covert Flow Trees: A Visual Approach to Analyzing Covert Storage Channels
IEEE Transactions on Software Engineering
Cleanroom software engineering: technology and process
Cleanroom software engineering: technology and process
Survivability—a new technical and business perspective on security
Proceedings of the 1999 workshop on New security paradigms
Toward Zero-Defect Programming
Toward Zero-Defect Programming
Dealing with nonfunctional requirements in large software systems
Annals of Software Engineering
Survivable Network System Analysis: A Case Study
IEEE Software
Requirements Definition for Survivable Network Systems
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Five Reasons for Scenario-Based Design
HICSS '99 Proceedings of the Thirty-Second Annual Hawaii International Conference on System Sciences-Volume 3 - Volume 3
Systematic Generation of Stochastic Diversity as an Intrusion Barrier in Survivable Systems Software
HICSS '99 Proceedings of the Thirty-Second Annual Hawaii International Conference on System Sciences-Volume 3 - Volume 3
Towards the generation of efficient code from verified programs
Towards the generation of efficient code from verified programs
A Portal for Software Security
IEEE Security and Privacy
Insecure context switching: inoculating regular expressions for survivability
WOOT'08 Proceedings of the 2nd conference on USENIX Workshop on offensive technologies
| Hi-index | 0.00 |
The environment in which software projects are managed has evolved dramatically in recent years. This evolution has been driven by an extraordinary increase in network connectivity and extensive use of contractors for system development, raising issues of interoperability, security, ownership, and intellectual property rights. Project managers face the ongoing challenge of creating an orderly incremental development process, which often proceeds for years, in this complex environment. At the same time, the dependency of organizations, their suppliers, and their customers on complex, large-scale information systems is increasing at an astonishing rate, to the point that conduct of business operations is virtually impossible if these systems are compromised. As a result, survivability is receiving increasing attention as a key property of critical systems. Survivability is the capability of a system to fulfill its mission, in a timely manner, in the presence of attacks, failures, or accidents. Given the severe consequences of system failure, it is clear that many more organizations should be, and at present are not, concerned with survivability issues. However, when survivability is added to the project management equation, software life cycles can look rather different from the traditional life-cycle model. In this paper we discuss this changing software project management environment, the impact of system survivability, and life-cycle activities that are tailored to development and evolution of survivable systems. Achieving survivable systems requires that survivability be integrated into project life cycles, and not treated as an add-on property.