RAAP: A Requirements Analysis and Assessment Process Framework for Component-Based System (Invited Paper)

Success of a Component Based System (CBS) depends heavily on the selection of the right components. In reality, components are usually designed for general purposes and finding the ideal ones is often very difficult. The CBS requirements process is hence more complicated than the conventional approach. In this paper, we present a Requirements Analysis and Assessment Process (RAAP) for CBS that can provide quantitative information and guidelines for stakeholders to evaluate the suitability of the components for a given set of requirements. Subsequently, they will be able to select the most appropriate components that best satisfy their needs, taking into consideration the risks involved and the conflicts that could arise as a result of selecting certain components earlier in the process. RAAP consists of three phases: (i) requirements characterization which elicits user requirements; (ii) top-down analysis which calculates the degree of satisfaction of a component and the amount of risks involved; and (iii) trade-off analysis which identifies and resolves the potential conflicts in requirements after certain components have been selected. We also present an application of RAAP to the Seven Eleven Japan system.

[1]  Axel van Lamsweerde,et al.  Handling Obstacles in Goal-Oriented Requirements Engineering , 2000, IEEE Trans. Software Eng..

[2]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[3]  Lawrence Chung,et al.  A knowledge-based COTS-aware requirements engineering approach , 2002, SEKE '02.

[4]  William N. Robinson,et al.  Supporting multi-perspective requirements engineering , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[5]  Grace A. Lewis,et al.  Building systems from commercial components , 2002, ICSE '02.

[6]  Norman E. Fenton,et al.  Software Metrics: A Rigorous Approach , 1991 .

[7]  Lowy,et al.  Programming .Net Components , 2003 .

[8]  W. Mendenhall,et al.  Statistics for engineering and the sciences , 1984 .

[9]  Mohammad Zulkernine,et al.  Intrusion detection aware component-based systems: A specification-based framework , 2007, J. Syst. Softw..

[10]  Gerald Kotonya,et al.  Viewpoints for Specifying Component-Based Systems , 2004, CBSE.

[11]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[12]  Carina Alves,et al.  COTS-Based Requirements Engineering , 2003, Component-Based Software Quality.

[13]  Barry W. Boehm,et al.  COTS-Based Systems Top 10 List , 2001, Computer.

[14]  Jun Han.  A comprehensive interface definition framework for software components , 1998, Proceedings 1998 Asia Pacific Software Engineering Conference (Cat. No.98EX240).

[15]  Jyrki Kontio,et al.  A COTS Selection Method and Experiences of Its Use , 1995 .

[16]  Barry W. Boehm,et al.  COTS Integration: Plug and Pray? , 1999, Computer.

[17]  Carina Frota Alves,et al.  Investigating Conflicts in Cots Decision-Making , 2003, Int. J. Softw. Eng. Knowl. Eng..

[18]  Colette Rolland,et al.  Requirements engineering for COTS based systems , 1999, Inf. Softw. Technol..

[19]  Sajjad Mahmood,et al.  A complexity measure for UML component-based system specification , 2008 .

[20]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .

[21]  Akira Ishikawa,et al.  The Success of 7-Eleven Japan: Discovering the Secrets of the World's Best-Run Convenience Chain Stores , 2002 .

[22]  Carina Alves,et al.  Requirements Negotiation for COTS-based Systems: Challenges and Open Issues , 2004 .

[23]  Victor R. Basili,et al.  Validation on an Approach for Improving Existing Measurement Frameworks , 2000, IEEE Trans. Software Eng..

[24]  Javam C. Machado,et al.  The prediction of faulty classes using object-oriented design metrics , 2001, J. Syst. Softw..

[25]  William N. Robinson,et al.  Managing Requirements Inconsistency with Development Goal Monitors , 1999, IEEE Trans. Software Eng..

[26]  Clemens A. Szyperski,et al.  Component software - beyond object-oriented programming , 2002 .

[27]  Pradeep Kumar Ray,et al.  Strategy-Oriented Alignment in Requirements Engineering: Linking Business Strategy to Requirements of e-Business Systems using the SOARE Approach , 2004, J. Res. Pract. Inf. Technol..

[28]  Ian Sommerville,et al.  Integrated requirements engineering: a tutorial , 2005, IEEE Software.

[29]  Neil A. M. Maiden,et al.  Acquiring COTS Software Selection Requirements , 1998, IEEE Softw..

[30]  Hareton K. N. Leung,et al.  On the efficiency of domain-based COTS product selection method , 2002, Inf. Softw. Technol..

[31]  Jonathan Lee,et al.  Structuring requirement specifications with goals , 2001, Inf. Softw. Technol..

[32]  Mario Piattini,et al.  Early detection of COTS component functional suitability , 2007, Inf. Softw. Technol..

[33]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[34]  Hany H. Ammar,et al.  Architectural-Level Risk Analysis Using UML , 2003, IEEE Trans. Software Eng..

[35]  Keith Phalp,et al.  B-SCP: A requirements analysis framework for validating strategic alignment of organizational IT based on strategy, context, and process , 2006, Inf. Softw. Technol..

[36]  Søren Lauesen.  COTS tenders and integration requirements , 2005, Requirements Engineering.

[37]  Jonathan Lee,et al.  Analyzing User Requirements by Use Cases: A Goal-Driven Approach , 1999, IEEE Softw..

[38]  하수철,et al.  [서평]「Component Software」 - Beyond Object-Oriented Programming - , 2000 .

[39]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[40]  Karl Cox,et al.  Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams , 2006, J. Syst. Softw..

[41]  Paul McMahon,et al.  Risk Management Guide for DoD Acquisition , 1998 .