Extracting high-level functional design from software requirements

Proceedings - Asia-Pacific Software Engineering Conference, APSEC

Volumn , Issue , 2009, Pages 35-42

  Sharma, Vibhu Saujanya ^a   Sarkar, Santonu ^a   Verma, Kunal ^b   Panayappan, Arun ^b   Kass, Alex ^b  

^a Accenture Services Pvt Ltd India   (India)

^b ACCENTURE   (United States)

Author keywords

Functional design; High level design; Requirements to design

Indexed keywords

CLASS DIAGRAMS; COARSE-GRAINED; CONSTRAINED NATURAL LANGUAGES; DESIGN ARTIFACTS; DESIGN ELEMENTS; FUNCTIONAL DESIGN; HIGH-LEVEL DESIGN; NATURAL LANGUAGES; SOFTWARE ARCHITECTS; SOFTWARE REQUIREMENTS; UML CLASS DIAGRAMS;

COMPUTER SOFTWARE; DESIGN; ENCODING (SYMBOLS); HEURISTIC METHODS; LINGUISTICS;

SOFTWARE DESIGN;

EID: 76349103256     PISSN: 15301362     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/APSEC.2009.63     Document Type: Conference Paper

References (15)

1. G. Booch, I. Jacobson, and J. Rambaugh, The Unified Modeling Language User Guide. Addison Wesley.
2. J. G. Hall, M. Jackson, R. C. Laney, B. Nuseibeh, and L. Rapanotti, "Relating software requirements and architectures using problem frames," in Proc.of the IEEE Joint International Conference on Requirements Engineering, 2002, pp. 137-144.
3. P. Grnbacher, A. Egyed, and N. Medvidovic, "Reconciling software requirements and architectures: The cbsp approach," in Fifth IEEE International Symposium on Requirements Engineering, 2001, pp. 202-211.
4. M. Brandozzi and D. Perry, "Transforming goal oriented requirement specifications into architectural prescriptions," in Proceedings of First International Workshop From Software Requirements to Architectures (STRAW01), 2001, pp. 54-61.
5. D. Liu, K. Subramaniam, A. Eberlein, and B. H. Far, "Natural language requirements analysis and class model generation using UCDA," in Lecture Notes in Computer Science. Springer-Verlag, 2004, pp. 295-304.
6. S. P. Overmyer, B. Lavoie, and O. Rambow, "Conceptual modeling through linguistic analysis using LIDA," in Proceedings of the 23rd International Conference on Software Engineering, 2001, pp. 401-410.
7. M. Ilieva and O. Ormandjieva, "Automatic transition of natural language software requirements specification into formal presentation," in Lecture Notes in Computer Science. Springer-Verlag, 2005, pp. 392-397.
8. P. Clements, F. Bachman, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architecture. Addison Wesley, September 2002.
9. "IEEE Recommended Practice for Architectural Description of Software-Intensive Systems," 2000.
10. P. Kruchten, "Architectural BlueprintsThe "4+1" View Model of Software Architecture," IEEE Software, vol. 12, no. 6, pp. 42-50, 1995.
11. K. Verma and A. Kass, "Requirements analysis tool: A tool for automatically analyzing software requirements documents," in ISWC '08: Proc of the 7th International Conf. on The Semantic Web, 2008, pp. 751-763.
12. P. Jain, K. Verma, A. Kass, and R. G. Vasquez, "Automated review of natural language requirements documents: generating useful warnings with user-extensible glossaries driving a simple state machine," in ISEC '09: Proc. 2nd Annual Conf. on India Software Engineering Conference. ACM, 2009, pp. 37-46.
13. "IEEE Recommended Practice for Software Requirements Specifications," 1998.
14. F. Budinsky, S. A. Brodsky, and E. Merks, Eclipse Modeling Framework. Pearson Education, 2003.
15. R. J. A. Buhr, "Use case maps as architectural entities for complex systems," IEEE Transactions on Software Engineering, vol. 24, no. 12, pp. 1131-1155, 1998.