CoSIT 2017

More documents

Recommendations

Info

140 Computer Science & Information Technology (CS & IT) [18] J. Wang and H. Zhang, \Predicting defect numbers based on defect state transition models," in Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement, pp. 191{200, ACM, 2012. [19] N. E. Fenton and M. Neil, \A critique of software defect prediction models," Software Engineering, IEEE Transactions on, vol. 25, no. 5, pp. 675{689, 1999.
NEED FOR A SOFT DIMENSION Pradeep Waychal 1 and Luiz Fernando Capretz 2 1 College of Engineering, Innovation Center, Pune, India 2 Dept. of Electrical and Computer Engineering, Western University, London, Canada, ABSTRACT It is impossible to separate the human factors from software engineering expertise during software development, because software is developed by people and for people. The intangible nature of software has made it a difficult product to successfully create, and an examination of the many reasons for major software system failures show that the reasons for failures eventually come down to human issues. Software developers, immersed as they are in the technological aspect of the product, can quickly learn lessons from technological failures and readily come up with solutions to avoid them in the future, yet they do not learn lessons from human aspects in software engineering. Dealing with human errors is much more difficult for developers and often this aspect is overlooked in the evaluation process as developers move on to issues that they are more comfortable solving. A major reason for this oversight is that software psychology (the softer side) has not developed as extensively KEYWORDS Human Factors in Software Engineering, Human Aspects of Engineering, Engineering Accreditation 1. INTRODUCTION The 2004 version of ACM/IEEE Software Engineering Curriculum mentioned document suggests only 5 hours of studies for group dynamics, whereas the 2013 draft recommends 8 hours. This is clearly not enough for a topic of such crucial importance. Besides, there should be more venues to publish papers with results in this field; workshops and conference sessions can help to increase visibility on this area and to discern the connection between human factors (including the individual, social, cultural, and organizational aspects) and the process of software development. But educators and researchers willing to venture into this area should not face an arduous task if they try to convince their colleagues and software engineering "purists" of the importance of the subject. We need to realize that the human element is pivotal to the engineering of software, and it is worth studying and teaching the soft dimension. Human-Computer Interaction (HCI), a common course within computer science departments, may be the closest subject and great strides have been made by computing professionals in adopting a human viewpoint to improve user interfaces. Although HCI addresses different topics, as it focuses on people interacting with software, HCI designers have been able to add this new dimension to their design philosophy. Likewise, software engineers could benefit immensely if even the smallest insights of human factors could be incorporated into their way of thinking. My own experiences as a software engineering educator, manager, and practitioner who continually keep human factors in mind. A course on human factor in software engineering should focus on providing a practical overview of Dhinaharan Nagamalai et al. (Eds) : CoSIT, AIAPP, SIGL, CYBI, CRIS, SEC, DMA - 2017 pp. 141– 145, 2017. © CS & IT-CSCP 2017 DOI : 10.5121/csit.2017.70414
Page 2:
Computer Science & Information Tech
Page 5 and 6:
Volume Editors Dhinaharan Nagamalai
Page 7 and 8:
Organization General Chair Nataraja
Page 9 and 10:
Technically Sponsored by Computer S
Page 11 and 12:
Fourth International Conference on
Page 13 and 14:
UNSUPERVISED DETECTION OF VIOLENT C
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
INVESTIGATING BINARY STRING ENCODIN
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
USE OF ADAPTIVE COLOURED PETRI NETW
Page 31 and 32:
2.2. Extended Adaptive Decision Tab
Page 33 and 34:
Page 35 and 36:
4. METHODOLOGY Computer Science & I
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
A NOVEL ADAPTIVE - WAVELET BASED DE
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
HANDWRITTEN CHARACTER RECOGNITION U
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
DIVING PERFORMANCE ASSESSMENT BY ME
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
4.4. Barycentre identification Comp
Page 69 and 70:
Page 71 and 72:
IS AI IN JEOPARDY? THE NEED TO UNDE
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
ANKLE MUSCLE SYNERGIES FOR SMOOTH P
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
ADVANCED LSB TECHNIQUE FOR AUDIO ST
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
SECURING ONLINE ACCOUNTS VIA NEW HA
Page 101 and 102: Computer Science & Information Tech
Page 109 and 110: • Clark-Wilson Integrity Model Co
Page 117 and 118: NEW NON-COPRIME CONJUGATE-PAIR BINA
Page 125 and 126: TOWARDS A MULTI-FEATURE ENABLED APP
Page 129 and 130: 3.1. Architecture Computer Science
Page 139 and 140: ESTIMATING HANDLING TIME OF SOFTWAR
Page 151: Computer Science & Information Tech
Page 157 and 158: AUTHORS Computer Science & Informat
Page 159 and 160: THE ANNUAL REPORT ALGORITHM: RETRIE
Page 179 and 180: A STUDY ON THE MOTION CHANGE UNDER
Page 181 and 182: B) Experiment part Computer Science
Page 185 and 186: ADAPTIVE AUTOMATA FOR GRAMMAR BASED
Page 197 and 198: STORAGE GROWING FORECAST WITH BACUL
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209:
AUTHOR INDEX Abdullah A. Al-Shaher
show all

CoSIT 2017

Create successful ePaper yourself

Delete template?

Save as template?