Software Application Logging: Aspects to Consider by Implementing Knowledge Management

Standard workday today includes use of software applications that enable faster task processing and can do so for several tasks in parallel for us. Still, also the best applications can stop working or may not work correctly. For investigating such unintended malfunctioning of a software application, logging is very important. By examining application logs, software developers can find the cause and provide an update or patch with fixed bugs. On the other hand, logging can provide enormous amount of data that can flood the memory. That is why it is important not to log everything. The decision about logging (how to do logging of what data) is done during the software development phase. This paper describes research that has been focused on logging strategies in form of case studies of software development projects and in conclusion we give some guidelines for future decisions on logging for software development teams that may lead to logging improvement.

[1]  Lorenzo Alvisi,et al.  Message logging: pessimistic, optimistic, and causal , 1995, Proceedings of 15th International Conference on Distributed Computing Systems.

[2]  Raffael Marty,et al.  Cloud application logging for forensics , 2011, SAC.

[3]  Lorenzo Alvisi,et al.  Reasons for a pessimistic or optimistic message logging protocol in MPI uncoordinated failure, recovery , 2009, 2009 IEEE International Conference on Cluster Computing and Workshops.

[4]  Gunnar Peterson,et al.  How to Do Application Logging Right , 2010, IEEE Security & Privacy.

[5]  R. Krishnamoorthi,et al.  Identifying User Behavior by Analyzing Web Server Access Log File , 2009 .

[6]  Allen Cypher,et al.  EAGER: programming repetitive tasks by example , 1991, CHI.

[7]  Jesús Rodríguez López,et al.  Labor demand and ICT adoption in Spain , 2016 .

[8]  Israel Spiegler,et al.  Knowledge Management: A New Idea Or a Recycled Concept? , 2000, Commun. Assoc. Inf. Syst..

[9]  D. Jorgenson,et al.  The ICT revolution, world economic growth, and policy issues , 2016 .

[10]  Siobhán Clarke,et al.  Subject-oriented design: towards improved alignment of requirements, design, and code , 1999, OOPSLA '99.

[11]  Karen L. Myers,et al.  Question Asking to Inform Procedure Learning , 2008 .

[12]  N. Al‐Rodhan.  Information and Communications Technology (ICT) , 2011 .

[13]  Nayef R. F. Al-Rodhan.  The Politics of Emerging Strategic Technologies , 2011 .

[14]  P. Weill,et al.  Management by Maxim: How Business and IT Managers Can Create IT Infrastructures , 1997 .

[15]  Colin Potts,et al.  Invented requirements and imagined customers: requirements engineering for off-the-shelf software , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[16]  Aristeidis Samitas,et al.  The effects of ICT* on output per worker , 2016 .

[17]  Luba Cherbakov,et al.  Impact of service orientation at the business level , 2005, IBM Syst. J..

[18]  Satish Narayanasamy,et al.  Automatic logging of operating system effects to guide application-level architecture simulation , 2006, SIGMETRICS '06/Performance '06.

[19]  Ilkka Tuomi,et al.  Data is more than knowledge: implications of the reversed knowledge hierarchy for knowledge management and organizational memory , 1999, Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences. 1999. HICSS-32. Abstracts and CD-ROM of Full Papers.