Appropriate language for introducing object oriented programming in tertiary institutions

Object Oriented Programming (OOP) has attained a level of acceptance in the software development community so much so that one is now considered a charlatan to have a degree in computing without the flare for OOP. Computing students must therefore be equipped with this skill. The need to do this using the most appropriate language is critical. We are not aware that any such language has been identified based on scientific instruments or parameters, except on individual opinion or affiliation. To this end, adopting the enhanced Alexander’s scheme, we identified and defined a set of criteria critical to the selection of the most appropriate programming language for introducing students to Object-Oriented concepts and programming. Furthermore, based on these criteria, we produced a rating showing the appropriateness of selected programming languages to the teaching and learning of OOP. The rating showed the suitability of these languages to the teaching and learning of OOP. The programming languages selected were the programming  languages rated among the IT skills required in a tough job market: Java, C#, C++, C and Visual BASICKeywords: OOP, teaching and learning, programming languages, selection criteri

Process model for building quality software on internet time

The competitive nature of the software construction market and the inherently exhilarating nature of software itself have hinged the success of any software development project on four major pillars: time to market, product quality, innovation and documentation. Unfortunately, however, existing software development models are either a bunch of ponderous bureaucratic serial processes or unstructured set of agile processes. While the former ensures appropriate documentation and quality of software product, it undermines the criticality of innovation and time to market, the latter holds time and innovation in high premium but treats the issue of quality and documentation as secondary. We therefore lack, but need a software process model that holds these four success factors in high esteem. This paper proposes one such model – the MULTIPARL model. The MULTIPARL model is a structured time driven model that ensures that a software product is constructed and delivered as increments of partial functionality. In particular, the MULTIPARL model stood out as the most appropriate process model for Web-based application development when it was subjected to the Onibere’s process selection criteria alongside some active software process models.Keywords: Software, internet, Software process model, MULTIPARL mode

Impact of postoperative acute kidney injury in patients undergoing major gastrointestinal surgery on 1-year survival and renal outcomes: a national multicentre cohort study

Abstract Background The intermediate-term impact of acute kidney injury (AKI) in patients after major gastrointestinal and liver surgery has not been well characterized. This study aimed to evaluate the 1-year mortality rate and renal outcomes associated with postoperative AKI in a national prospective cohort. Methods This prospective multicentre, observational cohort with 1-year postoperative follow-up included adults undergoing major gastrointestinal and liver surgery across the UK and Ireland between 23 September and 18 November 2015. AKI was defined according to Kidney Disease Improving Global Outcomes (KDIGO) criteria. The primary outcome was death at 1-year after surgery, and the secondary outcome was Major Adverse Kidney Events (MAKE-365). Cox proportionate and multilevel logistic regression were used to account for case mix. Results Of 5745 patients across 173 centres, 1-year follow-up data was completed for 3504 patients (62.2 per cent, 126 centres), with attrition largely explained by centre non-participation (63.1 per cent). Some 13.6 per cent (475 of 3504) patients developed AKI by 7 days after surgery (stage 1: 9.2 per cent; stage 2/3: 4.3 per cent). At 1 year, 10.8 per cent (378 patients) experienced a MAKE-365 endpoint (303 patients had died, 61 had renal replacement therapy and 78 had renal dysfunction). Patients who experienced AKI by 7 days after surgery had a higher hazard of death at 1 year for KDIGO stage 1 (hazard ratio 1.50 (95 per cent c.i. 1.08 to 2.08), P = 0.016) and KDIGO stage 2/3 (hazard ratio 2.96 (95 per cent c.i. 2.02 to 4.33), P &amp;lt; 0.001). Both KDIGO stage 1 (odds ratio 2.09 (95 per cent c.i. 1.50 to 2.92), P &amp;lt; 0.001) and stage 2/3 (odds ratio 9.26 (95 per cent c.i. 6.31 to 13.59), P &amp;lt; 0.001) AKI were independently associated with MAKE-365. Conclusion AKI events within 7 days after gastrointestinal or liver surgery are associated with significantly worse survival and renal outcomes at 1 year. </jats:sec