PAORE: Package oriented requirements elicitation

Proceedings - Asia-Pacific Software Engineering Conference, APSEC

Volumn 2003-January, Issue , 2003, Pages 17-26

  Kato, Junzo ^a   Nagata, Morio ^b   Yamamoto, Shuichiro ^c   Saeki, Motoshi ^d   Kaiya, Haruhiko ^e   Horai, Hisayuki ^f   Ohnishi, Atsushi ^g   Komiya, Seiichi ^h   Watahiki, Kenji ^d  

^a NIPPON SOKEN INC   (Japan)

^b KEIO UNIVERSITY   (Japan)

^c NTT DATA Corporation   (Japan)

^d TOKYO INSTITUTE OF TECHNOLOGY   (Japan)

^e SHINSHU UNIVERSITY   (Japan)

^f Celestar Lexico Sciences Inc   (Japan)

^g RITSUMEIKAN UNIVERSITY   (Japan)

^h SHIBAURA INSTITUTE OF TECHNOLOGY   (Japan)

Author keywords

Domain knowledge; Requirements elicitation; Software packages

Indexed keywords

REQUIREMENTS ENGINEERING; SALES; SOFTWARE PACKAGES; SPECIFICATIONS;

DOMAIN KNOWLEDGE; REQUIREMENTS ELICITATION; REQUIREMENTS EVOLUTION; SUB PROCESS; SUPPORTING SYSTEMS; WEB BASED;

SOFTWARE ENGINEERING;

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

References (13)

1. R. P. Diaz and G. Arango. Domain Analysis and Software Systems Modeling. IEEE Computer Society Press, 1991.
2. X. Franch and J. P. Carvallo. A Quality-Model-Based Approach for Describing and Evaluating Software Package. In Proc. of IEEE Joint International Conference on Requirements Engineering (RE 02), pages 104-111, 2002.
3. R. L. Glass. The Naturalness of object orientation beating a dead horse? IEEE Software, 2002 (May/June), 2002.
4. Junzo Kato et al. A Model for Navigating Interview Processes in Requirements Elicitation. In Proc. of APSEC 2001, pages 141-148, 2001.
5. K. Kang et al. Feature-Oriented Domain Analysis (FODA) Feasibility Study. Technical Report CMU/SEI-90-TR-21, ADA 235785), Pittsburgh, PA, 1990.
6. J. Kontio. OTSO: A Systematic Process for Reusable Software Component Selection. Technical Report CS-TR-3478, University of Maryland, College Park, MD, 1995.
7. A. Liu. Gathering Middleware Requirements. In Proc. of 15th International Conference on Information Networking (ICOIN'01), pages 81-86, 2001.
8. N. A. M. Maiden, C. Ncube, and A. Moore. Lessons Learned During Requirements Acquisition for COTS System. Communication of the ACM, 40(12):21-25, 1997.
9. M. Mosko, H. Jiang, A. Samanta, and L. Werner. COTS Software Acquisition Meta-Model. In Proc. of COTS Workshop, 2000.
10. C. Ncube and N. A. M. Maiden. Guiding Parallel Requirements Acquisition and COTS Software Selection. In Proc. of 4th International Symposium on Requirements Engineering (RE'99), pages 133-140, 1999.
11. M. Ochs, D. Pfahl, G. Chrobok-Diening, and B. Northhelfer-Kolb. A COTS Acquisition Process: Definition and Application Experience. In Proc. of ESCOM-SCOPE 2000, pages 335-343, 2000.
12. C. Rolland and N. Prakash. Matching ERP System Functionality to Customer Requirements. In Proc. of 5th IEEE International Symposium on Requirements Engineering (RE 01), pages 66-75, 2001.
13. H. Rubenstein and R. Waters. The Requirements Apprentice: Automated Assistance for Requirements Acquisition. IEEE Trans. on Software Engineering, 17(3):226-240, 1991.