A Method of Software Requirement Optimization and Selection Based on AGORA Extended Model

Abstract:

With the widely used of software technology, how to build a trusted software system has become a hot topic in the academic field. However, to the multi-channel and multi-option of the realization for software systems, how to optimization and selection the requirement has become an important issue. Based on the AGORA extended model, this paper proposes a requirement optimization and selection method with some indicators, such as development costs, correctness and consistency.

• Periodical: Advanced Materials Research (Volumes 271-273)
• Pages: 1124-1129
• DOI: https://doi.org/10.4028/www.scientific.net/AMR.271-273.1124
• Online since: July 2011
• Authors: Ya Luo, Yang Li
• Keywords: AGORA, Software Requirement, TOPSIS, Trusted Attribute

References

[1] Liveira A. Telling Stories About System Use: Capturing Collective Tacit Knowledge for System Maintenance[C]. Boston: Proceedings of the International Conference on Software Engineering and Knowledge Engineering, 2007, 337–342.

[2] Sutcliffe A. The domain theory for requirement engineering[J]. IEEE Trans on Soft Eng, 1998, 24(3): 174-195.

[3] Maiden N. Requirements Critiquing Using Domain Abstractions[C]. Los Alamitos, CA: IEEE Computer Society Press, 1994, 184-193.

[4] Lano R. Structured Approach for Pperational Concept Formulation[C]. Los Alamitos CA: IEEE Computer Society Press, 1990, 48-57.

[5] Zhi Jin, Ruqian Lu. Automatically multi-paradigm requirements modeling and analyzing: An ontology-based approach[J]. Science in China 2003, 33(4): 297-312 (in chinese).

DOI: 10.1360/02yf0093

[6] Howes N. On Using the Users Manual as the Requirements Specification[C]. Los Alamitos CA: IEEE Computer Society Press, 1990, 164-169.

[7] Kans M. An approach for determining the requirements of computerized maintenance management systems[J]. Computers in Industry , 2008, 59(3): 32–40.

DOI: 10.1016/j.compind.2007.06.003

[8] Hull E, Jackson K, Dick J. Requirements Engineering[M]. Springer, (2005).

[9] Nilsson V, Fagerstro B. Managing stakeholder requirements in a product modelling system[J]. Computers in Industry, 2006, 57(2): 167–177.

DOI: 10.1016/j.compind.2005.06.003

[10] Shen H, Wall B, Zaremba M , et al. Integration of business modeling methods for enterprise information system analysis and user requirements gathering[J]. Computers in Industry, 2004, 54(4): 307–323.

DOI: 10.1016/j.compind.2003.07.009

[11] Sommerville I. Software Engineering[M], Boston: Addison-Wesley, (2006).

[12] Glinz M. Statecharts for Requirements Specification—as Simple as Possible, as Rich as Needed[C]. Orlando: Proceedings of the ICSE Workshop on Scenarios and State Machines Models, Algorithms, and Tools, (2002).

[13] Anton A, Potts C. A representational framework for scenarios of system use[J]. Requirements Engineering Journal, 1998(3): 219–241.

[14] Breitman K, Leite J, Berry D. Supporting scenario evolution[J]. Requirements Engineering, 2005(10): 112–131.

DOI: 10.1007/s00766-004-0199-z

[15] Machado R, Borges M, Guerlain S, Gomes J. An Observation Model for the Collaborative Analysis of Real Workplaces[C]. Melbourne Australia: Proceedings of the International Conference on Computer Supported Cooperative Work in Design, 2007: 292–297.

DOI: 10.1109/cscwd.2007.4281450

[16] Nuseibeh B, Easterbrook S. Requirements Engineering: aA Roadmap[C]. Limerick Ireland: Proceedings of the Conference on the Future of Software Engineering, 2000: 35-46.

DOI: 10.1145/336512.336523

[17] Antunes P, Ramirez J, Respicio A. Addressing the conflicting dimension of groupware: a case study in software requirements validation[J]. Computing and Informatics, 2006, 25(5): 523–546.