Academic
Publications
Information systems development: methodologies

Information systems development: methodologies,D. Avison,G. Fitzgerald

Information systems development: methodologies   (Citations: 55)
BibTex | RIS | RefWorks Download
Published in 1995.
Cumulative Annual
    • ...It is also possible to try out a run using real data, perhaps generated by the users themselves [6]...

    K. Chandra Sekaranet al. Executable specification and prototyping of network protocols using UM...

    • ...The framework that was chosen to assist in this comparison exercise is the framework that was put forward by Avison and Fitzgerald [1]...
    • ...The BCS Information Systems Analysis and Design Working Group defined a software methodology as “recommended collection of philosophies, phases, procedures, rules, techniques, tool, documentation, management, and training for developers of information systems” [1]...
    • ...The most prevalent of these was a framework put forward by Avison and Fitzgerald [1]...
    • ...Bjorn-Anderson suggested a much broader range of issues to consider when choosing a software development methodology than Avison and Fitzgerald [1]...
    • ...It is also stated that it makes some assumptions, such as if user participation is really desired [1]...
    • ...The evaluation consists of three elements [1]: The ‘problem situation’ (the methodology context)...
    • ...Davis [1] advises the contingency approach, by selecting of an approach as part of the framework or methodology itself...
    • ...He suggests measuring the level of uncertainty of a system, by taking into account [1]:...
    • ...Avison and Taylor [1] identify five different classes of situation, and then suggest appropriate approaches to address these situations:...
    • ...The framework as suggested by Avison and Fitzgerald [1] was chosen to aid the decision making process...
    • ...According to Avison and Fitzgerald [1], the underlying principles of a methodology underscore all other aspects...
    • ...As a guide to the underlying principles the four factors of paradigm, objectives, domains, and targets are highlighted below [1]...
    • ...As a guide to the underlying principles the four factors of paradigm, objectives, domains, and targets are highlighted below [1]. There are two paradigms of relevance [1]...
    • ...According to Kuhn, as quoted by Avison and Fitzgerald [1], a paradigm is a specific way of thinking about problems, encompassing a set of achievements which are acknowledged as the foundation of further practice...
    • ...The Separation of Logical Design implies that there should be a separation of requirements, and how it is implemented, i.e. what versus how [1]...
    • ...Rules support the notion that methodologies should provide formal guidelines to cover phases, tasks, and deliverables, and their ordering, techniques and tools, documentation and development aids, and guidelines for estimating time and resource requirements [1]...
    • ...The model works on a number of difference levels [1]:...
    • ...A methodology should ideally cover the entire systems development process from strategy to maintenance [1]...
    • ...According to Avison and Fitzgerald [1], the practice can also refer to the degree to which the methodology can be, and is altered or interpreted by the users according to the requirements of the particular situation...
    • ...The Understanding of the Information Resource refers to the ability of a methodology to ensure effective utilization of an organisation’s information resources, such as existing business process and data [1]...
    • ...Documentation Standards refers to the ability of a methodology to output documentation according to agreed standards that are understandable by business and technical users [1]...
    • ...The Validity of Design dictates that there should be a means of checking for inconsistencies, inaccuracies, and incompleteness of the deliverables of a methodology [1]...
    • ...Early change refers to the requirement that any changes to a system design should be identifiable as early as possible in the life cycle [1]...
    • ...Inter-stage Communication supports the notion that the full extent of work carried out should be communicable to other stages, with each stage being consistent, complete, and usable [1]...
    • ...Careful monitoring is required, as well as the support of development in a planned and controlled manner in order to contain costs and time scales [1]...
    • ...Increased Productivity should be visible for users of the methodology, such as analysts, as well as for stakeholders of the project that was undertaken using the methodology [1]...
    • ...Improved Quality for a software methodology is measurable in terms of the improvement of the quality of analysis, design, and programming products, and hence the overall quality of the information system [1]...
    • ...Visibility of the Product requires that a methodology should maintain the visibility of the emerging and evolving information system as it evolves [1]...
    • ...Users as well as technologists should understand the various techniques in a methodology in order to verify analysis and design work, and train others to use it [1]...
    • ...These may not all be areas of computerisation [1]...
    • ...Designing for Change requires that the logical and physical designs should be easily modified [1]...
    • ...Effective Communication should be provided between analysts, IT, and users [1]...
    • ...Simplicity refers to the ease of use of the software methodology [1]...
    • ...It should be capable of being extended so that new techniques and tools can be incorporated as they are developed, but still maintain overall consistency and framework [1]...
    • ...This should be practiced wherever possible, as they can enhance accuracy and productivity [1]...
    • ...The Consideration of User Goals and Objectives of potential users of a system should be noted, so that when an information system is designed it can be made to satisfy these users and assist them in meeting goals and objectives [1]...
    • ...Integration of Technical and Non-Technical Systems refers to the ability of a software methodology to not only address the technical and non-technical aspects of a system, but should make provision for their integration [1]...
    • ...Rather than being viewed as simply a solution to existing problems it should be seen as an opportunity to address new areas and challenges [1]...
    • ...Each software methodology on the shortlist was assessed per assessment criteria as per Avison and Fitzgerald’s framework [1]...

    Riaan Klopperet al. Assessment of a framework to compare software development methodologie...

    • ...17. Alexander et al. (1977 )x 18. Bax (1989 )x 19. Jones (1980 )x 20. Lawson (1980 )x 21. Le Cuyer (1999 )x 22. Avison and Fitzgerald (1988 )x 23. Jalote (1991 )x 24. Pressman (1992 )x 25. Rechtin (1991 )x 26. Rumbaugh et al. (1991 )x 27. Sodhi (1991 )x 28. Sommerville (1992 )x 29. Winograd et al. (1996 )x 30. Dym (1994 )x 31. Finger and Dixon (1989a, b )x 32. Hubka and Eder (1996 )x 33. Pahl et al. (1988 )x 34. Ullman (1992 )x 35. VDI ...

    I. M. M. J. Reymenet al. A domain-independent descriptive design model and its application to s...

    • ...This approach is justifled by the fact that increasingly more software development projects consist of extending or enhancing existing systems, as opposed to developing new ones [3,12]...

    Jesus Bisbalet al. A formal framework for database sampling

    • ...Avison and Fitzgerald [7] see prototypes as learning models that aid system design, and argue that, with a prototype, users can discover what they want from the system and learn what is feasible...
    • ...Avison and Fitzgerald [7] identify situations where prototypes are particularly useful:...
    • ...Avison and Fitzgerald [7] identify two diverse views of systems development: the conventional versus the humanoriented, the former specialises in aspects of technology, whereas the latter is more interested in the organisation as a whole and the user as a creator in that environment...
    • ...This view is also related to the socio-technical approach [7] that recognises the interaction of technology and people in any technical system and the need to optimise them jointly...

    P. A. Leal De Matoset al. Decision support for flight re-routing in Europe

Sort by: