Author, Subjects, Keywords

Cited Author

 

 
   » By Author or Editor
 » Browse Author by Alphabet
 » By Journal
 » By Subjects
 » Malaysian Journals
 » By Type
 » By Year
 » By Latest Additions
 
 
   » By Author
 » Top 20 Authors
 » Top 20 Article
 » Top Journal Cited
 » Top Article Cited
 » Journal Citation Statistics
 » Usage Since Sept 2007


 
 
 

Login | Create Account

Design of a Requirements Management Tool

Ameran Jaafar, and Raja N. Ainon, and Rodina Ahmad, (2004) Design of a Requirements Management Tool. In: Proceedings of the Joint Conference on Informatics and Research on Women in ICT (RWICT) 2004 , 28 - 30 July 2004 , Putra World Trade Center Kuala Lumpur, Malaysia.

Full text not available from this repository.

Affiliations

University of Malaya, Faculty of Computer Science & Information Technology

Abstract

The requirements engineering phase in a typical software development project involves the systematic process of eliciting, analyzing. formalizing and verifying requirements of the intended system. In this research, our aim is to develop a tool to improve the quality of system requirements specification by managing changes to the system requirements with specific reference to the software industry in Malaysia. We propose a model with enhanced features, albeit simpler than that currently available, and developed a prototype to manage the requirements phase that offers interfacing with tools normally used by requirements engineers such as word processors and Unified Modeling Language. This paper describes the design of the requirements management model which is based on the three selected known Executable Requirements Management model (USNAVAL, INCOSE and RUP).

Item Type:Conference or Workshop Item (Paper)
Keywords:Requirements Management, Requirements management tool. Software design, CASE Tool
Subjects:Q Science
ID Code:1184

[1] Jones, D.A., Hollenbach, F., Kar, P.C., Bell, M., Gasbeek, J.R. and Ellinger, R.S.", Interfacing Requirements Management Tools in Requirements Process - A first look", Proc. 7th Int Symposim ofthe INCOSE-Vol II, Aug 1997.

[2] Kruchten, P.,The Rational Unified Process. 2nd ed., Addison-Weslev. 2000.

[3] Henderson-Sellers, B., Due, R., Graham, I.M. and Collins, G.," Third generation OO Processes: a critique of RUP and OPEN from a project management perspective'*, APSEC 2000,2000, pp 428-435.

[4] Jones, D. A.," Executable requirements management model Interim Report", Proc. 8th Annual Int. Symposium of the INCOSE, Vol II, 1998

[5] us Naval," Requirements management guidebook", Avionics Software Engineering, 1998 http://sepo.spawar.naw.mil/sepo/RM.Guidebook

[6] Goodwin, S. and Nellon, J. System Level Automation Tools for Engineer (SLATE), Texas Instruments, 1999.

[7] Paulk, M.C. et al, "Key Practices of the Capability Maturity Model. Version 1.1", Tech. Report CMU/SEI-93-TR-25,Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, 1993

[8] Brodman, J.G. and Johnson, D.L., "What small business and small organizations say about CMM: experience", Proc. 16* Int Conference on Software Engineering, 1994

[9] Walker, R., Software Project Management - A Unified Framework, Addison-Wesley, 1999

[10] Woodruff, W., Requirements Management for Small Organizations, Rational Software Corporation, 1997.

[11] Leffingwell, D. and Widrig, D. Managing Software Requirements: A Unified Approach, Addison Wesley Professional 1999.

Repository Staff Only: item control page