Software security for small development teams: a case study

Authors:
Michael Kainerstorfer;Johannes Sametinger;Andreas Wiesauer
Affiliations:
Aumayr GmbH, Steyregg, Austria;Johannes Kepler University, Linz, Austria;Johannes Kepler University, Linz, Austria
Venue:
Proceedings of the 13th International Conference on Information Integration and Web-based Applications and Services
Year:
2011

Citing 8
Cited 0

Writing Secure Code

Writing Secure Code
Balancing Agility and Discipline: A Guide for the Perplexed

Balancing Agility and Discipline: A Guide for the Perplexed
Threat Modeling

Threat Modeling
Extreme Programming Explained: Embrace Change (2nd Edition)

Extreme Programming Explained: Embrace Change (2nd Edition)
The Security Development Lifecycle

The Security Development Lifecycle
Crystal clear a human-powered methodology for small teams

Crystal clear a human-powered methodology for small teams
Software Engineering

Software Engineering
Succeeding with Agile: Software Development Using Scrum

Succeeding with Agile: Software Development Using Scrum

Quantified Score

Hi-index	0.00

Visualization

Abstract

Microsoft is developing wide-spread software solutions like the Windows operating system and the Office suite. In order to improve security of their products, they have introduced the Microsoft Security Development Lifecycle (MS-SDL). Ample documentation about the MS-SDL is available, thus, allowing other companies to adopt the lifecycle as well. We were wondering whether an adoption of the lifecycle is possible and useful for real small development teams, e.g., for a single developing person. In order to find out, we have done a practical test, i.e., we have used the MS-SDL for the development of a small, but real-world software project. The findings will be presented in this paper.