CFP last date
20 January 2025
Reseach Article

Proactive Detection of Higher- Order Software Code Conflict’s System

by Godswill U. Nwamuruamu, Laeticia N. Onyejegbu
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 179 - Number 35
Year of Publication: 2018
Authors: Godswill U. Nwamuruamu, Laeticia N. Onyejegbu
10.5120/ijca2018916776

Godswill U. Nwamuruamu, Laeticia N. Onyejegbu . Proactive Detection of Higher- Order Software Code Conflict’s System. International Journal of Computer Applications. 179, 35 ( Apr 2018), 1-5. DOI=10.5120/ijca2018916776

@article{ 10.5120/ijca2018916776,
author = { Godswill U. Nwamuruamu, Laeticia N. Onyejegbu },
title = { Proactive Detection of Higher- Order Software Code Conflict’s System },
journal = { International Journal of Computer Applications },
issue_date = { Apr 2018 },
volume = { 179 },
number = { 35 },
month = { Apr },
year = { 2018 },
issn = { 0975-8887 },
pages = { 1-5 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume179/number35/29223-2018916776/ },
doi = { 10.5120/ijca2018916776 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-07T00:59:18.644505+05:30
%A Godswill U. Nwamuruamu
%A Laeticia N. Onyejegbu
%T Proactive Detection of Higher- Order Software Code Conflict’s System
%J International Journal of Computer Applications
%@ 0975-8887
%V 179
%N 35
%P 1-5
%D 2018
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Collaborative development can be hampered when conflicts arise because developers have inconsistent copies of a shared project. We present an approach to help developers identify and resolve conflicts early, before those conflicts become severe and before relevant changes fade away in the developers' memories. A proactive high-order conflict detector helps programmers in a collaborative environment to detect conflicts and resolve same early to avoid malfunction of the software after deployment. With this, system conflicts are detected on time during design and resolved before they become more difficult to handle or before the code becomes too voluminous to debug. Using Java as a design tool the system was developed to detect code errors earlier and faster than already existing systems. The result obtained shows that the system resolves and detects conflicts early enough to avoid damage to the design in record time. The system designed uses less memory space with highly effective software activity which maximizes the host system resources. The methodology adopted for this design is the object oriented approach which gives a lot of avenues for conflict resolution and encourages code flexibility.

References
  1. Gilb, T., “(1998): Evolutionary Development. ACM. Software Engineering, (1), 17-23.
  2. Highsmith, J. A. (2002). Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. New York: Dorset House. 1(1), 5-8.
  3. Nwachukwu, E.O. and Eke, B.O.(2008). Critical Analysis of Software Development Strategies. Journal of Science and Technology. 7(4), 1-7
  4. Wloka J., B. Ryder, F. Tip, and X. Ren, (2009) “Safe-Commit Analysis to Facilitate Team Software Development,” in Proceedings of the 31st International Conference on Software Engineering (ICSE) IEEE Computer Society. (7),507–517
  5. Brun, R. Holmes, M. D. Ernst, and D. Notkin (2011): “Crystal: Precise and Unobtrusive Conflict Warnings,” in Proceedings of the 8th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering (ESEC/FSE). ACM, (12), 444–447.
  6. Algert, N.E., and Watson, K. (2002): Conflict management: introductions for individuals and organizations. Bryan, TX: (97)775-870
  7. Labib, C., Hasanein, E., And Hegazy, O., (2009).Early Development Of Graphical User Interface (GUI) In Agile Methodologies. Journal Of Computation Methods In Sciences And Engineering. (9), 239-249.
  8. Leffingwell, D. (2007). Scaling Software Agility: Best Practices for Large Enterprises. Boston: Addison-Wesley. 37 (12), 26–34.
  9. Guntamukala, V., Wen, H. J and Tarn, J.M. (2006).An empirical study of selecting software development life cycle models. Human systems management. 25(1), 265-278.
  10. Walia, Khalid Shergil, (2014): ”Impact of interpersonal conflict on requirements”, A Research Review”, University of westernontario , 1(2), 10-19.
  11. Royce, W.W. (1970). Managing the Development Of Large Software Systems: Concept And Techniques, Proceeding WESCON. (2), 23-55
  12. Madnick, Stuart Elliot (1968) Multi-processor software lockout Proceedings of the 1968 23rd ACM national conference, (1), 19 – 24.
Index Terms

Computer Science
Information Sciences

Keywords

Proactive Conflicts FLAME Conflict detection Software model high- order.