Abstract

Many software organizations today are confronted with challenge of building secure software systems. Traditional software engineering principles place little emphasis on security. These principles tend to tread security as one of a long list of quality factors that are expected from all professionally developed software. As software systems of today have a wide reach, security has become a more important factor than ever in the history of software engineering can no longer be treated as Separate Island. There is an imperative necessity to incorporative security into software engineering. Incorporating security into software engineering necessitates modification of existing software engineering principles, as these have to be tailored to take into account the security aspect. All phases of software engineering are likely to be impacted. In this paper we tried a novel security mechanism in system development life cycle.

References

1. Mead, N.R., Viswanathan, V., Padmanabhan, D., and Raveendran, A., Incorporating Security Quality Requirements Engineering (SQUARE) into Standard Life-Cycle Models. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2008.
2. Ambler, S. W. A Manager’s Introduction to Rational Unified Process, 2005.
3. Kruchten, P. The Rational Unified Process: An Introduction, 3rd ed. Boston, MA: Addison- Wesley, 2003.
4. Mead, N. R., E. Hough, and T. Stehney. Security Quality Requirements Engineering (SQUARE) Methodology. Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2005.
5. Rational Unified Process: Best Practices for Software Development Teams. Rational Software White Paper TP026B, Rev 11/01,2001.

Download PDF
Back