Security requirements in Software Requirements Engineering
 |
International Journal of Computer & Organization Trends (IJCOT) |  |
| © 2012 by IJCOT Journal | ||
| Volume-2 Issue-5 |
||
| Year of Publication : 2012 | ||
| Authors : Mahizharuvi,Dr.K.Alagarsamy |
Citation
Mahizharuvi,Dr.K.Alagarsamy "Security requirements in Software Requirements Engineering". International Journal of Computer & organization Trends (IJCOT), V2(5):18-24 Sep - Oct 2012, ISSN 2249-2593, www.ijcotjournal.org. Published by Seventh Sense Research Group.
Abstract
In the last few decades, software projects have encountered major difficulties. Most software engineering projects tend to be late and over budget. Several of the causes of these failures are related to requirements engineering issues such as requirements creep, poorly documented requirements, requirements that were impossible to satisfy, and requirements that failed to meet the needs of the user. Good requirements management practices help improve customer satisfaction, lower the system development costs, and increase the chance of having successful project which in turn give rise to security issue or vulnerable to hackers. Requirements metrics, when incorporated in requirements management, assist in analyzing the quality of requirements and identifying the reasons for software reengineering.
References
[1] N. R. Mead, E. Hough, and T. Stehney, Security Quality Requirements Engineering(SQUARE) Methodology, Software Engineering Institute, Carnegie MellonUniv., Pittsburgh,PA,Tech.Rep.CMU/SEI-2005- TR-009,2005. http://www.sei.cmu.edu/publications/docum ents/05.reports/05tr009.html
[2] AnalystPro Software Development,Requirements Management (2000).Retrieved from the World Wide Web http://www.analysttool.com/requirements.htm.
[3] Waterfall model,‖ Wikipedia. http://en.wikipedia.org/wiki/Waterfall_Model
[4] B. Boehm, ― A Spiral Model of Software Development and Enhancement,‖ IEEE Computer, vol. 21, no. 5, pp. 61-72, May 1988.
[5] P. Kruchten, the Rational Unified Process: An Introduction, 3rd ed. Boston: Addison-Wesley, 2003.
[6] Rational Software, ―Rational Unified Process: Best Practices for Software Development Teams,‖ Rational Software, White Paper TP026B, Rev 11/01, 2001. http://www.ibm.com/developerworks/rational/library/content/03July/1000/1251/1251_best practices_TP026B.pdf
[7] S. W. Ambler, ―A Manager’s Introduction to Rational Unified Process, 2005. http://www.ambysoft.com/downloads/managersIntroToRUP.pdf
[8] Principles behind the Agile Manifesto,‖2001.http://agilemanifesto.org/principles.html
[9] Asbrand D. (1998). IT Metrics For Success, Information Week Online, News in Review issue of August 17, 1998.
[10] ASEA Report (1994). Analysis of Automated Requirements Management Capabilities developed in support of Advanced System Engineering Automation (ASEA), CSC-2.7 Requirements/Design Manager (Contract N0. F30602-93-C0123), Prepared for Rome Laboratory, Air Force Materiel Command C3CB 525 Brooks Rd. Griffiss AFB, NY 13441 by Software Productivity Solutions, Inc. 122 4th Avenue Indalantic, FL. 32903.
[11] Bahill, A.T. and Dean, F.(1999). Discovering system requirements, Chapter 4 in the Handbook of Systems Engineering and Management, A.P. Sage and W.B. Rouse (Eds), John Wiley & Sons, 175-220.