A Negotiation Framework for Managing the Requirements Changes

1. Sikora, E., B. Tenberge n, K. Pohl. Industry Needs and Research Directions in Equirements Engineering for Embedded Systems [J]. - Requirements Engineering, Vol. 17, 2012, No 1, 57-78.10.1007/s00766-011-0144-xSearch in Google Scholar

2. Jin, Z., L. Liu, Y. Jin. Software Requirements Engineering: Principles and Methods [M]. Bei Jing, Science Press, 2008 (in Chinese).Search in Google Scholar

3. Hunter, A., B. Nuseibeh. Managing Inconsistent Specification: Reasoning, Analysis, and Action. - ACM Transactions on Software Engineering and Methodology, Vol. 7, 1998, No 4, 335-367.10.1145/292182.292187Search in Google Scholar

4. Alchourron, C., P. Gäardenfor s, D. Makinson. On the Logic of Theory Change: Partial Meeting Contraction and Revision Functions [J]. - Journal of Symbolic Logic, Vol. 50, 1985, No 2, 510-530.10.2307/2274239Search in Google Scholar

5. Garcez, A. S., A. Russ o, B. Nuseibeh, J. Kramer. An Analysis-Revision Cycle to Evolve Requirements Specifications [C]. - In: Proceedings of the 16th IEEE Conference on Automated Software Engineering (ASE’2001), Coronado, USA, 26-29 November 2001, 354-358.Search in Google Scholar

6. Garcez, A. S., A. Russ o, B. Nuseibeh, J. Kramer. Combining Abductive Reasoning and Inductive Learning to Evolve Requirements Specifications [J]. - IEEE Proceedings of Software, Vol. 150, 2003, No 1, 25-38.10.1049/ip-sen:20030207Search in Google Scholar

7. Boot h, R. A. Negotiation-Style Framework for Non-Prioritised Revision [C]. - In: Proceedings of the 8th Conference on Theoretical Aspects of Rationality and Knowledge (TARK’2001), Siena, Italy, 8-10 July 2001, 137-150.Search in Google Scholar

8. Ke-Dian, M., L. Weir u, J. Zh i, H. Ju n, D. Bell. Managing Software Requirements Changes Based on Negotiation-Style Revision [J]. - Journal of Computer Science and Technology, Vol. 26, 2011, No 5, 890-907.10.1007/s11390-011-0187-ySearch in Google Scholar

9. Mu, K., Z. Jin, R. Lu, Y. Peng. Handling Non-Canonical Software Requirements Based on Annotated Predicate Calculus [J]. - Knowledge and Information System, Vol. 11, 2007, No 1, 85-104.10.1007/s10115-006-0021-ySearch in Google Scholar

10. Mu, K., Z. Jin, R. Lu. Inconsistency-Based Strategy for Clarifying Vague Software Requirements [C]. - In: Proceedings of AI2005, LNCS3809, 2005, 39-48.10.1007/11589990_7Search in Google Scholar

11. Mu, K., W. Liu, Z. Ji n, R. Lu, A. Yu e, D. A. Bell. Handling Inconsistency in Distributed Software Requirements Specifications Based on Prioritized Merging [J]. - Fundam. Inform., Vol. 91, 2009, No 3-4, 631-670.10.3233/FI-2009-0062Search in Google Scholar

12. Mu, K., Z. Jin, R. Lu, W. Li u. Measuring Inconsistency in Requirements Specifications [C]. - In: Proceedings of ECSQARU’2005, LNAI3571, 2005, 440-451.10.1007/11518655_38Search in Google Scholar

13. Saaty, T. L. Modeling Unstructured Decision Problems - the Theory of Analytical Hierarchies [J]. - Mathematics and Computers in Simulation, Vol. 20, 1978, No 3, 147-158.10.1016/0378-4754(78)90064-2Search in Google Scholar

14. Pardee, W. J. To Satisfy and Delight Your Customer: How to Manage for Customer Value [M]. New York, Dorset House Publishing, 1996.Search in Google Scholar

15. Wiegers, K. E. Software Requirements [M]. 2nd Ed. Portland, Microsoft Press, USA, 2003.Search in Google Scholar

16. Davis, A. Just Enough Requirements Management: Where Software Development Meets Marking [M]. New York, Dorset House Publishing, 2005.Search in Google Scholar

17. Al-Khaldi, R. Inconsistency Management in Software Functional Requirements: A Machine Learning System [J]. LAP Lambert Academic Publishing, Germany, 2012.Search in Google Scholar

18. Bonoma, T. V. Case Research in Marketing: Opportunities, Problems, anda Process. - Journal of Marketing Research, Vol. 12, 1985, No 1, 199-208. 10.1177/002224378502200209Search in Google Scholar