Handling non-functional requirements in information system architecture design

4th International Conference on Software Engineering Advances, ICSEA 2009, Includes SEDES 2009: Simposio para Estudantes de Doutoramento em Engenharia de Software

Volumn , Issue , 2009, Pages 59-64

  Tsadimas, Anargyros ^a   Nikolaidou, Mara ^a   Anagnostopoulos, Dimosthenis ^a  

^a HAROKOPIO UNIVERSITY   (Greece)

Author keywords

Enterprise information systems; Non functional requirements; Requirements engineering

Indexed keywords

ARCHITECTURE DESIGNS; COMPLEX TASK; DESIGN ISSUES; ENTERPRISE INFORMA-TION SYSTEMS; INFORMATION SYSTEM ARCHITECTURE; MODEL BASED APPROACH; MODELING LANGUAGES; NON-FUNCTIONAL REQUIREMENTS; SYSTEM ARCHITECTURES; SYSTEM COMPONENTS; SYSTEM DESIGN PROCESS;

COMPUTER SOFTWARE; DESIGN; LARGE SCALE SYSTEMS; LEGACY SYSTEMS; MANAGEMENT INFORMATION SYSTEMS; REQUIREMENTS ENGINEERING; SYSTEMS ANALYSIS;

INFORMATION SYSTEMS;

EID: 70749114804     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSEA.2009.18     Document Type: Conference Paper

References (18)

1. INCOSE. INCOSE Handbook SE Process Model, September 2003. http://g2sebok.incose.org/.
2. A. Aurum and C. Wohlin. Engineering and Managing Software Requirements. Springer, 2005.
3. E. R. Byrne. IEEE Standard 830: Recommended Practice for Software Requirements Specifications, 1998.
4. A. v. Lamsweerde. Goal-Oriented Requirements Engineering: A Guided Tour. In Fifth IEEE International Symposium on Requirements Engineering (RE'01), p 249, 2001.
5. J. Mylopoulos, L. Chung and B. Nixon. Representing and using nonfunctional requirements: A process-oriented approach. In IEEE Trans. Softw. Eng, 18(6):483-497, 1992
6. L. Zhu and I. Gorton. Uml profiles for design decisions and non-functional requirements. In SHARK-ADI '07, p 8, 2007. IEEE Computer Society.
7. M. Glinz. On non-functional Requirements. 15th IEEE International Requirements Engineering Conference, 2007.
8. C.-W. Ho, L. Williams, and B. Robinson. Examining the relationships between performance requirements and "not a problem" defect reports. In RE '08, p 135-144, 2008. IEEE Computer Society.
9. J. A. Estefan. Survey of Model-based Systems Engineering (MBSE) Methodologies. INCOSE MBSE Focus Group, May 2007.
10. M. Nikolaidou, A. Tsadimas, N. Alexopoulou, D. Anagnostopoulos. Employing Zachman Enterprise Architecture Framework to Systematically Perform Model-Based System Engineering Activities In HICSS-42, p 1-10, 2009.
11. O. M. G. Inc. Systems Modeling Language (SYSML) Specification. Version 1.0, September 2007.
12. S. Leist and G. Zellner. Evaluation of current architecture frameworks. In H. Haddad, ed, SAC, p 1546-1553. ACM, 2006.
13. M. Nikolaidou and N. Alexopoulou. Enterprise Information System Engineering: A Model-Based Approach Based on the Zachman Framework. In HICSS'08. IEEE Computer Society, 2008.
14. A. Fatolahi and F. Shams. An investigation into applying UML to the Zachman Framework. Information Systems Frontiers, 8(2):133-143, 2006.
15. C. M. Pereira and P. Sousa. A method to define an Enterprise Architecture using the Zachman Framework. In H. Haddad, A. Omicini, R. L. Wainwright, and L. M. Liebrock, editors, SAC, p 1366-1371. ACM, 2004.
16. OMG. UML Profile for Modeling, Quality of Service and Fault Tolerance Characteristics and Mechanisms, September 16, 2004, omg.org
17. MagicDraw UML. http://www.magicdraw.com/.
18. I. Ozkaya. Representing requirement relationships. In REV '06, p 3, 2006. IEEE Computer Society.