Ontological Foundations of Information Systems Analysis and Design

2011 ◽  
pp. 322-344 ◽  
Author(s):  
Boris Wyssusek ◽  
Helmut Klaus
Keyword(s):  
Information Systems ◽  
Systems Analysis ◽  
Systems Development ◽  
Information Systems Development ◽  
Analysis And Design ◽  
Systems Analysis And Design ◽  
Systems Research ◽  
Information Systems Research ◽  
History Of ◽  
Research Ontology

Ontology has attracted considerable attention in information systems analysis and design (ISAD) research. Ontology is philosophy and bears its own substance and history of debates, which quite often have not been accounted for in information systems research. A more comprehensive consideration of well-known philosophical issues of ontology may help to apprehend precisely the transfer of ontological concepts into ISAD, including insights regarding their limitations and to articulate directions towards further research. In particular, this requires expanding of the scope of current debates in information systems towards the socio-philosophical aspects of ontology. Only then, it will be possible to determine whether ontology can direct the project of theoretical foundation for ISAD. An outline of the critique of the prevailing rationalistic methodical understanding of information systems development in contemporary IS literature illustrates how the indiscriminating borrowing of philosophical presuppositions has encumbered current understandings. Critical reflection upon these presuppositions can get over persuasions and bring about theorisation.

Methodological Requirements for Information Systems Development

1992 ◽  
Vol 7 (3) ◽  
pp. 141-148 ◽  
Author(s):  
Sachidanandam Sakthivel
Keyword(s):  
Information Systems ◽  
Systems Development ◽  
Information Systems Development ◽  
Development Methodology ◽  
Systems Research ◽  
Information Systems Research ◽  
Computer Based ◽  
Tools And Techniques ◽  
Research Studies

A systems development methodology is a collection of procedures, tools, and techniques to develop computer based information systems. To develop better information systems, research studies have suggested several requirements for these methodologies. These requirements may not be equally important for practitioners. Identification of their importance for practitioners can guide researchers to solve practical issues in systems development. It will also be useful to evaluate and compare various methodologies. A study in which theoretical requirements were presented to practitioners for evaluation is presented and its findings described.

Teaching Teamwork in Information Systems

2011 ◽  
pp. 1-24 ◽  
Author(s):  
Connie E. Wells
Keyword(s):  
Information Systems ◽  
Virtual Teams ◽  
Systems Development ◽  
Team Development ◽  
Information Systems Development ◽  
Team Members ◽  
Course Content ◽  
Analysis And Design ◽  
Systems Analysis And Design ◽  
Programming Courses

Teamwork is very important in information systems development. Therefore, most courses in systems analysis and design and many programming courses require students to work on group projects. However, a project group is not the same thing as a team. Furthermore, for a group to become a team, there are several important characteristics that must be developed. These characteristics do not always develop automatically. This chapter discusses the requirements for effectively forming, building, managing, and evaluating teams in information systems courses. Students should be taught these concepts in addition to the regular course content. This chapter also addresses two special issues that deal with team development and team management: managing cultural diversity and managing “virtual” teams, where the team members are geographically separated.

Bringing the Social and Organisational Issues into Information Systems Development

2003 ◽  
pp. 5-21 ◽  
Author(s):  
David Avison ◽  
Trevor Wood-Harper
Keyword(s):  
Information Systems ◽  
Development Process ◽  
Systems Development ◽  
Information Systems Development ◽  
The Social ◽  
History Of ◽  
Oriented Approach ◽  
Contingency Approach

Multiview is a framework to support the information systems development process. It was formulated originally in 1985, but has been developed and changed since that time. It was originally defined to take into account the human and organisational aspects of information systems development, as the alternative methodologies of the time–and most since that time–took a very technology-oriented approach. Furthermore, it is a contingency approach, and again this compares with the alternative bureaucratic and prescriptive methodologies. In this chapter, we describe the history of Multiview, and we reflect on the experiences of using it in action in many organisations.

Sign in / Sign up

Export Citation Format

Share Document