Requirements Analysis and Traceability at CIM Level ()
Abstract
Poernomo suggested an approach for requirement analysis within the CIM level of the MDA framework. His approach combined MEASUR, goal and object oriented analysis, and developed a new methodology that can be integrated within the CIM level of the MDA. This paper adds requirement traceability capabilities to the method developed by Poernomo and applies the extended method on a case study based on a high profile international law firm.
Share and Cite:
M. Yamin, V. Zuna and M. Bugami, "Requirements Analysis and Traceability at CIM Level,"
Journal of Software Engineering and Applications, Vol. 3 No. 9, 2010, pp. 845-851. doi:
10.4236/jsea.2010.39098.
Conflicts of Interest
The authors declare no conflicts of interest.
References
|
[1]
|
M. Roper, “Software Testing,” ACM Computing Surveys, Vol. 23, 1994, p. 103.
|
|
[2]
|
R. Wieringa, “A Survey of Structured and Object-Oriented
Software,” 1998. http://portal.acm.org/citation.cfm
|
|
[3]
|
V. Schlag, Patrick Certification Magazine, Vol. 8, No. 9, September 2006, pp. 30-35.
|
|
[4]
|
“OMG, MDA Guide Version 1.0.1,” 2000. http://www. omg.org/docs/omg/03-06-01.pdf
|
|
[5]
|
I. Poernomo, G. Tsaramirsis and V. Zuna, “A Methodol-ogy for Requirements Analysis at CIM Level,” 2008. http://ftp.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-376/paper2.pdf
|
|
[6]
|
V. Castro, J. M. V. Mesa, E. Herrmann and E. Marcos, “From Real Computational Independent Models to Information System Models: An MDE Approach,” Proceedings of the 4th International Workshop on Model- Driven Web Engineering, Tolouse, 2008.
|
|
[7]
|
O. Gotel and A. Finkelstein, “An Analysis of the Requirements Traceability Problem,” Proceedings of 1st International Conference on Requirements Engineering, Vol. 11, 1994, pp 94-101.
|
|
[8]
|
A. Salter and L. Kecheng, “Using Semantic Analysis and Norm Analysis to Model Organizations,” Proceedings of ICEIS, Vol. 3, 2002
|
|
[9]
|
T. Philip, G. Schwabe and E. Wende, “Early Warning Signs of Failures in Offshore Software Development Projects,” Management Services, Vol. 51 No. 3, 2007, pp. 38-43.
|