Software Engineering Timeline: major areas of interest and multidisciplinary trends

Ingeniería del software. EvolucionSociety today cannot run without software and by extension, without Software Engineering. Since this discipline emerged in 1968, practitioners have learned valuable lessons that have contributed to current practices. Some have become outdated but many are still relevant and widely used. From the personal and incomplete perspective of the authors, this paper not only reviews the major milestones and areas of interest in the Software Engineering timeline helping software engineers to appreciate the state of things, but also tries to give some insights into the trends that this complex engineering will see in the near future

KEMNAD: A Knowledge Engineering Methodology for Negotiating Agent Development

Automated negotiation is widely applied in various domains. However, the development of such systems is a complex knowledge and software engineering task. So, a methodology there will be helpful. Unfortunately, none of existing methodologies can offer sufficient, detailed support for such system development. To remove this limitation, this paper develops a new methodology made up of: (1) a generic framework (architectural pattern) for the main task, and (2) a library of modular and reusable design pattern (templates) of subtasks. Thus, it is much easier to build a negotiating agent by assembling these standardised components rather than reinventing the wheel each time. Moreover, since these patterns are identified from a wide variety of existing negotiating agents(especially high impact ones), they can also improve the quality of the final systems developed. In addition, our methodology reveals what types of domain knowledge need to be input into the negotiating agents. This in turn provides a basis for developing techniques to acquire the domain knowledge from human users. This is important because negotiation agents act faithfully on the behalf of their human users and thus the relevant domain knowledge must be acquired from the human users. Finally, our methodology is validated with one high impact system

Uncovering the impact of organisational culture types on the willingness to share knowledge between projects

Current literature has established that organisational culture influences knowledge management efforts; however, it is only recently that research on project management has focused its interest on organisational culture in the context of knowledge sharing and some preliminary studies have been conducted. In response, this paper adds a significant contribution by providing rich empirical evidence of the relationships between culture and the willingness to share knowledge, demonstrating which cultural values are more and which are less likely to improve inter-project knowledge sharing behaviours. The use of interviews and the Organisational Culture Assessment Instrument (OCAI) (Cameron & Quinn, 2005) in the cross-case examination of culture in four participating cases has resulted in rich empirical contributions. Furthermore, this paper adds to the project management literature by introducing the Competing Values Framework (CVF) of Cameron and Quinn (2005) to evaluate knowledge sharing in the inter-project context