An Analysis Of The Recommended Knowledge For The Software Project Management Discipline

According to the PMBOK (Project Management Body of Knowledge), project management is “the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements” [1]. Project Management has proven to be one of the most important disciplines at the moment of determining the success of any project [2][3][4]. Given that many of the activities covered by this discipline can be said that are “horizontal” for any kind of domain, the importance of acknowledge the concepts and practices becomes even more obvious. The specific case of the projects that fall in the domain of Software Engineering are not the exception about the great influence of Project Management for their success. The critical role that this discipline plays in the industry has come to numbers. A report by McKinsey & Co [4] shows that the establishment of programs for the teaching of critical skills of project management can improve the performance of the project in time and costs. As an example of the above, the reports exposes: “One defense organization used these programs to train several waves of project managers and leaders who together administered a portfolio of more than 1,000 capital projects ranging in Project management size from $100,000 to$500 million. Managers who successfully completed the training were able to cut costs on most projects by between 20 and 35 percent. Over time, the organization expects savings of about 15 percent of its entire baseline spending”. In a white paper by the PMI (Project Management Institute) about the value of project management [5], it is stated that: “Leading organizations across sectors and geographic borders have been steadily embracing project management as a way to control spending and improve project results”. According to the research made by the PMI for the paper, after the economical crisis “Executives discovered that adhering to project management methods and strategies reduced risks, cut costs and improved success rates—all vital to surviving the economic crisis”. In every elite company, a proper execution of the project management discipline has become a must. Several members of the software industry have putted effort into achieving ways of assuring high quality results from projects; many standards, best practices, methodologies and other resources have been produced by experts from different fields of expertise. In the industry and the academic community, there is a continuous research on how to teach better software engineering together with project management [4][6]. For the general practices of Project Management the PMI produced a guide of the required knowledge that any project manager should have in their toolbox to lead any kind of project, this guide is called the PMBOK. On the side of best practices 10 and required knowledge for the Software Engineering discipline, the IEEE (Institute of Electrical and Electronics Engineers) developed the SWEBOK (Software Engineering Body of Knowledge) in collaboration with software industry experts and academic researchers, introducing into the guide many of the needed knowledge for a 5-year expertise software engineer [7]. The SWEBOK also covers management from the perspective of a software project. This thesis is developed to provide guidance to practitioners and members of the academic community about project management applied to software engineering. The way used in this thesis to get useful information for practitioners is to take an industry-approved guide for software engineering professionals such as the SWEBOK, and compare the content to what is found in the PMBOK. After comparing the contents of the SWEBOK and the PMBOK, what is found missing in the SWEBOK is used to give recommendations on how to enrich project management skills for a software engineering professional. Recommendations for members of the academic community on the other hand, are given taking into account the GSwE2009 (Graduated Software Engineering 2009) standard [8]. GSwE2009 is often used as a main reference for software engineering master programs [9]. The standard is mostly based on the content of the SWEBOK, plus some contents that are considered to reinforce the education of software engineering. Given the similarities between the SWEBOK and the GSwE2009, the results of comparing SWEBOK and PMBOK are also considered valid to enrich what the GSwE2009 proposes. So in the end the recommendations for practitioners end up being also useful for the academic community and their strategies to teach project management in the context of software engineering

Lilly Endowment Annual Report 2015

During 2015, the Endowment paid grants totaling $435.5 million. Community development grants accounted for$200.4 million (46 percent), religion grants accounted for $124.1 million (29 percent) and education grants accounted for$111.0 million (25 percent). Most grants were paid to organizations in Indiana - a total of $257.8 million (59 percent). Of the payment total of$435.5 million, $107.9 million (25 percent) was paid to nonMarion County grantees in Indiana and$149.9 million (34 percent) to Marion County (Indianapolis) grantees. Organizations outside of Indiana received $177.7 million (41 percent). Most of these grants paid outside of Indiana were religion grants.The annual report includes a complete list of 2015 grants

Vulnerabilities and responsibilities: dealing with monsters in computer security

Purpose – The purpose of this paper is to analyze information security assessment in terms of cultural categories and virtue ethics, in order to explain the cultural origin of certain types of security vulnerabilities, as well as to enable a proactive attitude towards preventing such vulnerabilities.\ud \ud Design/methodology/approach – Vulnerabilities in information security are compared to the concept of “monster” introduced by Martijntje Smits in philosophy of technology. The applicability of different strategies for dealing with monsters to information security is discussed, and the strategies are linked to attitudes in virtue ethics.\ud \ud Findings – It is concluded that the present approach can form the basis for dealing proactively with unknown future vulnerabilities in information security.\ud \ud Research limitations/implications – The research presented here does not define a stepwise approach for implementation of the recommended strategy in practice. This is future work.\ud \ud Practical implications – The results of this paper enable computer experts to rethink their attitude towards security threats, thereby reshaping their practices.\ud \ud Originality/value – This paper provides an alternative anthropological framework for descriptive and normative analysis of information security problems, which does not rely on the objectivity of risk

Is agile project management applicable to construction?

This paper briefly summarises the evolution of Agile Project Management (APM) and differentiates it from lean and agile production and ‘leagile’ construction. The significant benefits being realized through employment of APM within the information systems industry are stated. The characteristics of APM are explored, including: philosophy, organizational attitudes and practices, planning, execution and control and learning. Finally, APM is subjectively assessed as to its potential contribution to the pre-design, design and construction phases. In conclusion, it is assessed that APM offers considerable potential for application in predesign and design but that there are significant hurdles to its adoption in the actual construction phase. Should these be overcome, APM offers benefits well beyond any individual project

Transforming failure into success through organisational learning: An analysis of a manufacturing information system

This paper describes the idiosyncracies of a case study company, through highlighting issues and problems experienced during their attempts to evaluate, implement and realise the holistic implications of a manufacturing information system. Although the Information System (IS) was operational for a period of time, it was eventually deemed a failure. The reason for this was that a range of human and organisational factors prevented the organisation from embracing the full impact of the system. The eventual success of their information system was realised through a bespoke implementation, based upon a traditional systems development lifecycle that indirectly addressed learning issues following the earlier failed deployment. The paper highlights key issues relating to business success and failure, and then contrasts them alongside the presented case study. In doing so, the authors conclude by proposing methods through which manufacturing information systems can be transformed for business success. This is described achievable through both a realisation in the positioning of the organisation relative to technology management, and the related mapping of human and technological constructs that support information systems related succes

A conceptual architecture for semantic web services development and deployment

Several extensions of the Web Services Framework (WSF) have been proposed. The combination with Semantic Web technologies introduces a notion of semantics, which can enhance scalability through automation. Service composition to processes is an equally important issue. Ontology technology – the core of the Semantic Web – can be the central building block of an extension endeavour. We present a conceptual architecture for ontology-based Web service development and deployment. The development of service-based software systems within the WSF is gaining increasing importance. We show how ontologies can integrate models, languages, infrastructure, and activities within this architecture to support reuse and composition of semantic Web services

A Qualitative Method for Assessing the Impact of ICT on the Architectural Design Process

During the last thirty years or so, we have witnessed tremendous developments in information and communication technology (ICT). Computer processing power doubles each 18 months, as Gordon Moore predicted during the mid-1960s. The computer and communications world has been revolutionised by the invention of the Internet. It has changed the way of exchanging, viewing, sharing, manipulating and storing the information. Other technologies such as smartphones, wearable computers, tablets, wireless communications and satellite communications have made the adoption of ICT easier and beneficial to all its users. ICT affects the productivity, performance and the competitive advantage of a business. It also impacts on the shape of the business process and its product. In architectural design, ICT is widely used throughout the design process and its final product. The aim of this research, therefore, is to explore the key implication of using ICT in architectural design and what new changes and forms have occurred on buildings as a result of ICT developments and use by architecture practitioners. To achieve this aim, a qualitative research approach was adopted using a narrative review of ICT usage in the design of buildings. The literature found was subjected to a thematic analysis of how ICT adoption affected the architectural design process. The findings of this research indicate that there is a continuous change in the design process and its final products (buildings) as the technology evolves. The framework proposed provides a foundation for gathering evidence from case studies of the impact of ICT adoption by architectural designers. The research proposes that future empirical work has to be conducted to test and refine the relevance, importance and applicability of each of the components of the framework, in order to detect the impact of ICT on the building design process and its final product

Closing the gap between software engineering education and industrial needs

According to different reports, many recent software engineering graduates often face difficulties when beginning their professional careers, due to misalignment of the skills learnt in their university education with what is needed in industry. To address that need, many studies have been conducted to align software engineering education with industry needs. To synthesize that body of knowledge, we present in this paper a systematic literature review (SLR) which summarizes the findings of 33 studies in this area. By doing a meta-analysis of all those studies and using data from 12 countries and over 4,000 data points, this study will enable educators and hiring managers to adapt their education / hiring efforts to best prepare the software engineering workforce