Formalizing the ISDF Software Development Methodology

Abstract

The paper is aimed at depicting the ISDF software development methodology by emphasizing quality management and software development lifecycle. The ISDF methodology was built especially for innovative software development projects. The ISDF methodology was developed empirically by trial and error in the process of implementing multiple innovative projects. The research process began by analysing key concepts like innovation and software development and by settling the important dilemma of what makes a web application innovative. Innovation in software development is presented from the end-user, project owner and project manager's point of view. The main components of a software development methodology are identified. Thus a software development methodology should account for people, roles, skills, teams, tools, techniques, processes, activities, standards, quality measuring tools, and team values. Current software development models are presented and briefly analysed. The need for a dedicated innovation oriented software development methodology is emphasized by highlighting shortcomings of current software development methodologies when tackling innovation. The ISDF methodology is presented in the context of developing an actual application. The ALHPA application is used as a case study for emphasizing the characteristics of the ISDF methodology. The development life cycle of the ISDF methodology includes research, planning, prototyping, design, development, testing, setup and maintenance. Artefacts generated by the ISDF methodology are presented. Quality is managed in the ISDF methodology by assessing compliance, usability, reliability, repeatability, availability and security. In order to properly asses each quality component a dedicated indicator is built. A template for interpreting each indicator is provided. Conclusions are formulated and new related research topics are submitted for debate.Keywords: Software Development Methodology, Innovation, Project Management(ProQuest: ... denotes formulae omitted.)IntroductionT he research efforts and results presented in the current paper apply exclusively to web applications. Though they might apply to other categories of software applications or to other fields altogether, they were validated only in the context of web applications. From the end-user's point of view, a web application is considered to be innovative if it's easier to use, faster, cheaper, more reliable or more secure than other applications that accomplish the same results or if it fulfils a need that has yet to be address in the online environment. In the context of the end-user, innovation targets the fulfilment of a specific need.From the project owner's point of view a web application is considered innovative if it:* includes at least a functionality that generates added value for the end-user and the functionality is not found in other web applications that target the same market;* includes a combination of functionalities that generate added value and the combination of functionalities is not found in the same configuration in any other web application that targets the same market; functionalities can be found separately in other web applications but not in the same configuration;* provides access to a graphic interface that includes elements or element combinations which improve user experience and are not found in other web applications that target the same market.In the context of the project owner innovation focusses on market characteristics and targets novelty and added value. From the project manager and from the development team's point of view a web application is considered to be innovative if it includes functionality that they have never implemented before. In the context of the project manager and the project team, innovation focusses on the degree of novelty of the current application compared to previously implemented applications. …