Journal articles on the topic 'Information Systems Development Methodologies'

To see the other types of publications on this topic, follow the link: Information Systems Development Methodologies.

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Information Systems Development Methodologies.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

Avison, D. E., H. U. Shah, R. S. Powell, and P. S. Uppal. "Applying methodologies for information systems development." Journal of Information Technology 7, no. 3 (September 1992): 127–40. http://dx.doi.org/10.1057/jit.1992.19.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Avison, D. E., H. U. Shah, R. S. Powell, and P. S. Uppal. "Applying Methodologies for Information Systems Development." Journal of Information Technology 7, no. 3 (September 1992): 127–40. http://dx.doi.org/10.1177/026839629200700302.

Full text
Abstract:
Many organizations develop their information systems without the use of any information systems development methodology. However, even when organizations identify the need for the use of such methodologies, it is not always obvious which to use, or whether a blended combination might be appropriate. Further, in using either stand-alone or blended information systems development methodologies in practice, a number of difficulties are encountered. This paper discusses the use of an information systems development methodology which consisted of a blend of other methodologies in a real-world situation (a large telecommunications company) where no formal methodology had been used previously. A number of difficulties arose in practice, some of which were not anticipated. Examples are given of the types of difficulty encountered, and these fell into three broad categories: those related to the deficiencies in the design techniques and tools themselves; those related to implementing the system from the design; and those related to the particular environment.
APA, Harvard, Vancouver, ISO, and other styles
3

Pícka, M. "Metamodeling and development of information systems." Agricultural Economics (Zemědělská ekonomika) 50, No. 2 (February 24, 2012): 65–70. http://dx.doi.org/10.17221/5168-agricecon.

Full text
Abstract:
Metamodeling is becaming an important part of information systems development. When metamodeling we are working with metamodel which define the syntax and the semantics of models. There are a lot of standards for definition of metamodel e.g. COMMA, GOPRR, MOF. Metamodeling is used for defining and creating of new methodologies, their implementation into CASE and metaCASE tools. Metamodeling is used for manipulation of data and metadata and for optimalization of information’s system design with utilization of generic models. The aims of this article are: to discusse fundamental concepts of metamodeling, demonstrate some theoretically and practically important meta-metamodels and to position metamodeling principles in the development of information systems.
APA, Harvard, Vancouver, ISO, and other styles
4

Westrup, Christopher. "Information Systems Methodologies in Use." Journal of Information Technology 8, no. 4 (December 1993): 267–75. http://dx.doi.org/10.1177/026839629300800407.

Full text
Abstract:
Research into information systems development (ISD) methodologies is generally restricted to the creation or elaboration of methodologies or the provision of CASE support. This paper proposes that a fruitful area of research, which will provide insights into the effectiveness of ISD methodologies, must centre on the observation of the practice of systems developers, users and managers, and the study of methodologies in use. Such a programme requires certain techniques, ideally longitudinal ethnographic case studies. Preliminary results from a couple of case studies indicate that ISD methodologies are not used as prescribed but this does not necessarily prevent the successful completion of development projects.
APA, Harvard, Vancouver, ISO, and other styles
5

Wynekoop, Judy L., and Nancy L. Russo. "Systems development methodologies: unanswered questions." Journal of Information Technology 10, no. 2 (June 1995): 65–73. http://dx.doi.org/10.1057/jit.1995.9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Wynekoop, Judy L., and Nancy L. Russo. "Systems Development Methodologies: Unanswered Questions." Journal of Information Technology 10, no. 2 (June 1995): 65–73. http://dx.doi.org/10.1177/026839629501000209.

Full text
Abstract:
Despite over a decade of study, little is really known about information systems development and the use of systems development methodologies. There has been little evaluation of methodologies in use or examination of the selection, development, adaptation or use of methodologies in practice. This paper discusses this lack of knowledge and its ramifications for research and practice.
APA, Harvard, Vancouver, ISO, and other styles
7

Walters, S. A., J. E. Broady, and R. J. Hartley. "A Review of Information Systems Development Methodologies." Library Management 15, no. 6 (September 1994): 5–19. http://dx.doi.org/10.1108/01435129410067331.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Sakthivel, Sachidanandam. "Methodological Requirements for Information Systems Development." Journal of Information Technology 7, no. 3 (September 1992): 141–48. http://dx.doi.org/10.1177/026839629200700303.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
9

Michalec, Lukasz, and David Banks. "Information Systems Development Methodologies and all that Jazz." Issues in Informing Science and Information Technology 1 (2004): 0227–35. http://dx.doi.org/10.28945/733.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

H. Zaied, Abdel Nasser, Samah Ibrahim Abdel Aal, and Mohamed Monir Hassan. "Rule-based Expert Systems for Selecting Information Systems Development Methodologies." International Journal of Intelligent Systems and Applications 5, no. 9 (August 1, 2013): 19–26. http://dx.doi.org/10.5815/ijisa.2013.09.03.

Full text
APA, Harvard, Vancouver, ISO, and other styles
11

Fitzgerald, Brian. "Systems development methodologies: the problem of tenses." Information Technology & People 13, no. 3 (September 2000): 174–85. http://dx.doi.org/10.1108/09593840010377617.

Full text
APA, Harvard, Vancouver, ISO, and other styles
12

Connors, Danny T. "Software development methodologies and traditional and modern information systems." ACM SIGSOFT Software Engineering Notes 17, no. 2 (April 1992): 43–49. http://dx.doi.org/10.1145/130840.130843.

Full text
APA, Harvard, Vancouver, ISO, and other styles
13

Kautz, Karlheinz, Bo Hansen, and Dan Jacobsen. "The Utilization of Information Systems Development Methodologies in Practice." Journal of Information Technology Case and Application Research 6, no. 4 (October 2004): 1–20. http://dx.doi.org/10.1080/15228053.2004.10856051.

Full text
APA, Harvard, Vancouver, ISO, and other styles
14

Kavvadia, Helen. "Information Systems Development Methodologies: A Review Through a Teleology Approach." HighTech and Innovation Journal 2, no. 4 (December 1, 2021): 373–83. http://dx.doi.org/10.28991/hij-2021-02-04-09.

Full text
Abstract:
The information systems analysis and design methodologies devised at the outbreak of the third industrial revolution shaped the systems analysis disciple and have trickled down to all systems influencing most aspects of human development. To cope with the explosion of digital technology, these methodologies had to be developed rapidly, drawing from a wide range of theoretical backgrounds, based mainly on the “hard” scientific method and the “softer” systems approach. In the run-up to industry 4.0, with multiple information systems emerging, reflection on systems’ design fundamentals is important. Intended to serve human activity and well-being, information systems are anthropocentric. Their success lies in their ability to serve human goals. Information systems analysis and design methodologies play a role in this by ensuring the best match between what is sought from systems and what they deliver in terms of the systems’ underlying final cause, or “telos”. The paper investigates the teleological orientation of four founding systems analysis and design methodologies. Using the Wood-Harper and Fitzgerald taxonomy in order to identify the conceptual origins of the four methodologies under review, it categorizes and subsequently incorporates them in an extended taxonomy, assesses whether and how they are devised to cater to the incorporation of goals and explains the inferred results based on the taxonomy. The paper posits that the founding information systems analysis and design methodologies do not have a marked teleological orientation and do not dispose of techniques for adequately incorporating systems’ goals. Doi: 10.28991/HIJ-2021-02-04-09 Full Text: PDF
APA, Harvard, Vancouver, ISO, and other styles
15

Meneses, Beatriz, and João Varajão. "A Framework of Information Systems Development Concepts." Business Systems Research Journal 13, no. 1 (June 1, 2022): 84–103. http://dx.doi.org/10.2478/bsrj-2022-0006.

Full text
Abstract:
Abstract Background: Information Systems Development (ISD) is responsible for designing and implementing information systems that support organizational strategy, leveraging business models and processes. Several perspectives on this activity can be found in the literature, addressing – often in an undifferentiated manner – approaches, lifecycles, methodologies, and process models, among others. Objectives: The vast diversity of ideas and concepts surrounding ISD and the multiple underlying views on the subject make it harder for researchers and practitioners to understand the relevant aspects of this important activity. This article aims to systematize and organize ISD’s main concepts to create a coherent perspective. Methods/Approach: We conducted a literature review and thematic analysis of ISD’s main concepts. Results: To contribute to filling the research gap, this article proposes a new framework that addresses the key aspects related to ISD. Conclusions: The framework comprises ISD’s core concepts, such as lifecycles, process models, deployment approaches, and methodologies.
APA, Harvard, Vancouver, ISO, and other styles
16

Fitzgerald, Brian. "Formalized systems development methodologies: a critical perspective." Information Systems Journal 6, no. 1 (January 1996): 3–23. http://dx.doi.org/10.1111/j.1365-2575.1996.tb00002.x.

Full text
APA, Harvard, Vancouver, ISO, and other styles
17

Fitzgerald, Brian. "Formalized systems development methodologies: a critical perspective." Information Systems Journal 6, no. 1 (January 1996): 3–23. http://dx.doi.org/10.1046/j.1365-2575.1996.00100.x.

Full text
APA, Harvard, Vancouver, ISO, and other styles
18

Hopelain, David, and Bob Loesh. "Automated development methodologies." Data Processing 27, no. 2 (March 1985): 43–45. http://dx.doi.org/10.1016/0011-684x(85)90018-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
19

Onokoy, Lyudmila, and Jurijs Lavendels. "Evolution and Development Prospects of Information System Design Methodologies." Applied Computer Systems 23, no. 1 (May 1, 2018): 63–68. http://dx.doi.org/10.2478/acss-2018-0008.

Full text
Abstract:
Abstract The article investigates different approaches to the design of information systems. Much attention is paid to comparative analysis of criteria for selecting methodologies for software development, and also to not well-known methodology of DevOps (Development & Operation) [1], [2], which aims at consolidation of software developers (Development) and IT professionals’ (Operation) efforts, and automation of implementation process. In conclusion, based on the retrospective analysis and practical experience, the authors formulate regularities and prospects of information systems design methodology development.
APA, Harvard, Vancouver, ISO, and other styles
20

Iivari, Juhani, Rudy Hirschheim, and Heinz K. Klein. "A Paradigmatic Analysis Contrasting Information Systems Development Approaches and Methodologies." Information Systems Research 9, no. 2 (June 1998): 164–93. http://dx.doi.org/10.1287/isre.9.2.164.

Full text
APA, Harvard, Vancouver, ISO, and other styles
21

Avison, D. E., and V. Taylor. "Information systems development methodologies: a classification according to problem situation." Journal of Information Technology 12, no. 1 (March 1997): 73–81. http://dx.doi.org/10.1080/026839697345224.

Full text
APA, Harvard, Vancouver, ISO, and other styles
22

Marsh, David. "Information Systems Development Methodologies: Evidence and Experience from the NHS." OR Insight 17, no. 4 (October 2004): 15–21. http://dx.doi.org/10.1057/ori.2004.16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
23

Avison, D. E., and V. Taylor. "Information Systems Development Methodologies: A Classification According to Problem Situation." Journal of Information Technology 12, no. 1 (March 1997): 73–81. http://dx.doi.org/10.1177/026839629701200106.

Full text
Abstract:
Information systems development methodologies are frequently classified according to themes or features. Yet potential users are more concerned with the situations in which different approaches are appropriate. In this paper, five problem situation types are identified: (1) well-structured problem situations with a well-defined problem and clear requirements, (2) well-structured problem situations with clear objectives but uncertain user requirements, (3) unstructured problem situations with unclear objectives, (4) situations where there is a high user interaction with the system and (5) complex problem situations. Typical information systems development methodologies are placed in each of these groups. Some strengths and weaknesses of this classification are discussed. One conclusion is that most projects will fall within the category of complex problem situations, for organizations (and therefore their information systems needs) are invariably complex in terms of the human and social aspects at least as much as any technological ones. The Multiview approach is discussed in more detail because the authors claim it is suitable for such situations.
APA, Harvard, Vancouver, ISO, and other styles
24

Binsaleh, Muazzan, and Shahizan Hassan. "Systems Development Methodology for Mobile Commerce Applications." International Journal of Online Marketing 1, no. 4 (October 2011): 33–47. http://dx.doi.org/10.4018/ijom.2011100103.

Full text
Abstract:
There are several systems development methodologies including traditional and agile methodologies being utilized in current systems development. However, it could be argued that when developing mobile commerce applications, suitable development framework should be investigated as these applications are utilized in different contexts from fixed ecommerce applications. This study identifies suitable system development methodology framework for mobile commerce applications. In order to achieve this aim, the practitioners from seven organizations were asked to provide information about their development methodologies by answering the questions regarding mobile commerce application development. The questions were opened and aimed to explore practitioner’s perspectives on the development methodologies. From the practitioner’s perspectives, it was found that there were several development methodologies being used in mobile commerce application development and these can be classified into two different development frameworks which are heavyweight/traditional and lightweight/agile methodologies. The suitable methodology framework for mobile commerce application development thus was identified.
APA, Harvard, Vancouver, ISO, and other styles
25

Fitzgerald, Brian. "An empirical investigation into the adoption of systems development methodologies." Information & Management 34, no. 6 (December 1998): 317–28. http://dx.doi.org/10.1016/s0378-7206(98)00072-x.

Full text
APA, Harvard, Vancouver, ISO, and other styles
26

Mitev, Nathalie N. "The Business Failure of Knowledge-Based Systems: Linking Knowledge-Based Systems and Information Systems Methodologies for Strategic Planning." Journal of Information Technology 9, no. 3 (September 1994): 173–84. http://dx.doi.org/10.1177/026839629400900302.

Full text
Abstract:
It is first argued that the commercial failure of knowledge-based systems (KBS) is due to the lack of business emphasis of KBS development methodologies. This article outlines the evolution of KBS methodologies and the recent change of emphasis from a technology-driven to a business-led approach. It further examines the ‘application identification and selection’ activities of two KBS methodologies, KADS and STAGES. Their weaknesses are highlighted and it is argued that an integrated strategic methodological approach to the development of information systems and knowledge-based systems is required. The strategic phase of an IS methodology is then summarized; specific points within it where KBS-related activities could be incorporated are identified. This exercise illustrates how IS methodologies could be used as a basis for the joint strategic planning of IS and KBS systems.
APA, Harvard, Vancouver, ISO, and other styles
27

Huisman, Magda, and Juhani Iivari. "Deployment of systems development methodologies: Perceptual congruence between IS managers and systems developers." Information & Management 43, no. 1 (January 2006): 29–49. http://dx.doi.org/10.1016/j.im.2005.01.005.

Full text
APA, Harvard, Vancouver, ISO, and other styles
28

Kljajić, Miroljub. "The Relevance of Systems Methodologies in the Development of Organizational Systems." Organizacija 42, no. 4 (July 1, 2009): 119–28. http://dx.doi.org/10.2478/v10051-009-0009-y.

Full text
Abstract:
The Relevance of Systems Methodologies in the Development of Organizational SystemsThe relationship between systems development and systems methodologies is discussed in this paper. As the measure of system development on the macro level, Gross Domestic Product (GDP) is assumed to be the consequence of systems Research and Development (R&D), which is estimated indirectly by the number of published articles in the last 40 years. It was supposed that profit and governmental organizations are systems comprised of Production, Management and Information Systems (IS), and that their quality performance is related with its income generation, which in the future would impact the overall GDP of a country. Under such view, we also assume that such organizational processes are qualitatively improved by the application of knowledge generated by research publications, and in this study, we research for the specific case of the Systems Approach (SA), Systems Engineering (SE), Operational Research (OR), Information Systems Development (ISD) and Simulation, as the research topics for coping with organizational improvement. We looked for the articles containing the afore-mentioned variables as topic keywords, which indicate sufficient correlations with GDP and carrying information on sustainable development. We found a positive trend in the evolution of research methodologies, such as SE, ISD and OR, towards a Systems Approach and Simulation as a holistic methodology. As a result, we have proved the dynamic hypothesis of a high correlation between GDP of Top 10 + Slovenia and R&D expressed by the above-mentioned variables.
APA, Harvard, Vancouver, ISO, and other styles
29

Abdalla, Reem, and Alok Mishra. "Using Agent-Based Methodologies in Healthcare Information Systems." Cybernetics and Information Technologies 18, no. 2 (June 1, 2018): 123–32. http://dx.doi.org/10.2478/cait-2018-0033.

Full text
Abstract:
Abstract This paper carries out a comparative analysis to determine the advantages and the stages of two agent-based methodologies: Multi-agent Systems Engineering (MaSE) methodology, which is designed specifically for an agent-based and complete lifecycle approach, while also being appropriate for understanding and developing complex open systems; Agent Systems Methodology (ASEME) suggests a modular Multi-Agent System (MAS) development approach and uses the concept of intra-agent control. We also examine the strengths and weaknesses of these methodologies and the dependencies between their models and their processes. Both methodologies are applied to develop The Guardian Angle: Patient-Centered Health Information System (GA: PCHIS), which is an example of agent-based applications used to improve health care information systems.
APA, Harvard, Vancouver, ISO, and other styles
30

Struzik, V. A., S. V. Hrybkov, and V. V. Chobanu. "DETERMINATION OF REFACTORING PLACE IN MODERN METHODOLOGIES OF INFORMATION SYSTEMS DEVELOPMENT." Scientific notes of Taurida National V.I. Vernadsky University. Series: Technical Sciences 5, no. 1 (2019): 173–77. http://dx.doi.org/10.32838/2663-5941/2019.5-1/28.

Full text
APA, Harvard, Vancouver, ISO, and other styles
31

Iivari, Juhani, Rudy Hirschheim, and Heinz K. Klein. "A Dynamic Framework for Classifying Information Systems Development Methodologies and Approaches." Journal of Management Information Systems 17, no. 3 (December 2000): 179–218. http://dx.doi.org/10.1080/07421222.2000.11045656.

Full text
APA, Harvard, Vancouver, ISO, and other styles
32

Goulielmos, Markos. "Outlining organisational failure in information systems development." Disaster Prevention and Management: An International Journal 12, no. 4 (October 1, 2003): 319–27. http://dx.doi.org/10.1108/09653560310493132.

Full text
Abstract:
Defines the concept of “organisational failure” in information systems (IS) development, and proposes a diagnostic model drawn from research done into IS consultancy firms that develop systems using a variety of methodologies. The research involved a qualitative study aimed at the nature of the development process and the role of organisational issues in this process. The model’s elements and relationships were determined by the research findings. Presents two cases of failure that show how IS failure is rooted in organisational pathology and examine existing failure concepts. The concept and model proposed can be used by practitioners and management before and during a project for diagnosing organisational failure before it interferes with IS development and afterwards for extracting deeper rooted organisational learning from failure.
APA, Harvard, Vancouver, ISO, and other styles
33

Kaluza, Jindrich. "Systemy informatyczne w administracji publicznej." Zeszyty Naukowe Instytutu Administracji Akademii im. Jana Długosza w Częstochowie. Gubernaculum et Administratio 1(11) (2015): 77–88. http://dx.doi.org/10.16926/gea.2015.01.06.

Full text
APA, Harvard, Vancouver, ISO, and other styles
34

Romanenko, G. S., A. N. Tolchkov, and A. A. Chumichkin. "Modeling information systems." Informatization and communication, no. 1 (March 31, 2020): 89–97. http://dx.doi.org/10.34219/2078-8320-2020-11-1-89-97.

Full text
Abstract:
The article considers the task of modeling advanced information systems. The work is based on research on the development of a methodological apparatus for substantiating requirements for military-grade information systems. Currently the requirements for advanced information systems are formed in a natural language, the expressive properties of which are not enough for a concise and unambiguous description of them. The developed methodological approach is based on the construction of a complex of models of system with the integrated use of methodologies of functional and object-oriented modeling of the information system and related management processes, as well as the developed notation of user interface modeling. The use of a unified modeling language provides unambiguous interpretation of models by all participants in the process of developing an information system – from the customer to the developer.
APA, Harvard, Vancouver, ISO, and other styles
35

Ríos, Jimmy Molina, and Nieves Pedreira-Souto. "Approach of Agile Methodologies in the Development of Web-Based Software." Information 10, no. 10 (October 13, 2019): 314. http://dx.doi.org/10.3390/info10100314.

Full text
Abstract:
The current inclusion of agile methodologies in web-oriented projects has been considered on a large-scale by software developers. However, the benefits and limitations go beyond the comforts that project managers delimit when choosing them. Selecting a methodology involves more than only the associated processes or some documentation. Based on the above, we could define as the main concerns the approach with which we identify the methodology, the needs of the company, the size, and qualities of the project, and especially the characteristics of agile development that they possess. However, there are several difficulties in selecting the most appropriate methodology due to the features in common; Will it be suitable for my project? What challenges will be presented in the process? Will my team understand each stage? Will I be able to deliver software that satisfies the client? Project managers create these questions, which seem manageable but have huge effects. This paper presents a systematic literature review based on the analysis of the approaches of six web development methodologies. The aim of the study is to analyze the approaches presented by relevant methodologies, identifying their common agile characteristics and managing to contrast both its benefits and limitations during a project. As a result, we could itemize five common features, which are presented within the processes; (1) flexibility, (2) constant communication of the workgroup, (3) use of UML, (4) the inclusion of the end-user and (5) some documentation.
APA, Harvard, Vancouver, ISO, and other styles
36

Conger, Sue. "Software Development Life Cycles and Methodologies." International Journal of Information Technologies and Systems Approach 4, no. 1 (January 2011): 1–22. http://dx.doi.org/10.4018/jitsa.2011010101.

Full text
Abstract:
Information Systems as a discipline has generated thousands of research papers, yet the practice still suffers from poor-quality applications. This paper evaluates the current state of application development, finding practice wanting in a number of areas. Changes recommended to fix historical shortcomings include improved management attention to risk management, testing, and detailed work practices. In addition, for industry’s move to services orientation, recommended changes include development of usable interfaces and a view of applications as embedded in the larger business services in which they function. These business services relate to both services provided to parent-organization customers as well as services provided by the information technology organization to its constituents. Because of this shift toward service orientation, more emphasis on usability, applications, testing, and improvement of underlying process quality are needed. The shift to services can be facilitated by adopting tenets of IT service management and user-centered design and by attending to service delivery during application development.
APA, Harvard, Vancouver, ISO, and other styles
37

Vessey, Iris, and Robert L. Glass. "APPLICATIONS-BASED METHODOLOGIES Development by Application Domain." Information Systems Management 11, no. 4 (January 1994): 53–57. http://dx.doi.org/10.1080/07399019408964671.

Full text
APA, Harvard, Vancouver, ISO, and other styles
38

Bréant, C. "Health Information Systems: Current Challenges and Developments." Yearbook of Medical Informatics 17, no. 01 (August 2008): 52–54. http://dx.doi.org/10.1055/s-0038-1638583.

Full text
Abstract:
Summary Objectives To summarize excellent current research in the field of Health Information Systems. Method Synopsis of the articles selected for the IMIA Yearbook 2008. Results HIS is a broad field that includes many fruitful areas of research and development. Some current topics were selected for this IMIA yearbook. Conclusions The best paper selection of articles on health information systems shows examples of original developments in the area of: medical record systems to meet specific requirements in a developing country, methodologies to identify strengths and weaknesses of hospital information systems, networking of hospital information systems towards an integrated regional health platform, and development of an open source picture archiving and communication systems to facilitate the integration of advanced new imaging functionalities.
APA, Harvard, Vancouver, ISO, and other styles
39

Molina-Ríos, Jimmy, and Nieves Pedreira-Souto. "Comparison of development methodologies in web applications." Information and Software Technology 119 (March 2020): 106238. http://dx.doi.org/10.1016/j.infsof.2019.106238.

Full text
APA, Harvard, Vancouver, ISO, and other styles
40

Yao, James, John Wang, Qiyang Chen, and Ruben Xing. "Core Methodologies in Data Warehouse Design and Development." International Journal of Robotics Applications and Technologies 1, no. 1 (January 2013): 57–66. http://dx.doi.org/10.4018/ijrat.2013010104.

Full text
Abstract:
Data warehouse is a system which can integrate heterogeneous data sources to support the decision making process. Data warehouse design is a lengthy, time-consuming, and costly process. There has been a high failure in data warehouse development projects. Thus how to design and develop a data warehouse have become important issues for information systems designers and developers. This paper reviews and discusses some of the core data warehouse design and development methodologies in information system development. The paper presents in particular the most recent and much heated hybrid approach which is a combination of data-driven and requirement-driven approaches.
APA, Harvard, Vancouver, ISO, and other styles
41

Low, Graham, and Richard Looi. "An Investigation of Client/Server Application Development Methodologies." Journal of Information Technology 12, no. 3 (September 1997): 187–96. http://dx.doi.org/10.1177/026839629701200303.

Full text
Abstract:
Client/server application development is becoming increasingly popular in commercial organizations. However, previous research has found that current application development methodologies provide little or no support for client/server computing possibly due to the relative newness of the technology in commercial environments. This research is the first step in demonstrating the applicability of the client/server methodology enhancements proposed in a commercial Management Information System (MIS) environment. It examines the application of traditional development methodologies to the client/server environment, the problems associated in using these methodologies and the respondent's rating of the importance of the various client/server application development issues included in the proposed methodology.
APA, Harvard, Vancouver, ISO, and other styles
42

Clarke, S., and B. Lehaney. "Mixing Methodologies for Information Systems Development and Strategy: A Higher Education Case Study." Journal of the Operational Research Society 51, no. 5 (May 2000): 542. http://dx.doi.org/10.2307/254185.

Full text
APA, Harvard, Vancouver, ISO, and other styles
43

Clarke, S., and B. Lehaney. "Mixing methodologies for information systems development and strategy: A higher education case study." Journal of the Operational Research Society 51, no. 5 (May 2000): 542–56. http://dx.doi.org/10.1057/palgrave.jors.2600865.

Full text
APA, Harvard, Vancouver, ISO, and other styles
44

Taylor, M. J., J. McWilliam, H. Forsyth, and S. Wade. "Methodologies and website development: a survey of practice." Information and Software Technology 44, no. 6 (April 2002): 381–91. http://dx.doi.org/10.1016/s0950-5849(02)00024-1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
45

Fuentes, Honorato C. Teissier. "Systemic methodologies in regional sustainable development." Systems Research and Behavioral Science 23, no. 5 (December 11, 2006): 659–66. http://dx.doi.org/10.1002/sres.801.

Full text
APA, Harvard, Vancouver, ISO, and other styles
46

Fitzgerald, B. "The use of systems development methodologies in practice: a field study." Information Systems Journal 7, no. 3 (July 1997): 201–12. http://dx.doi.org/10.1046/j.1365-2575.1997.d01-18.x.

Full text
APA, Harvard, Vancouver, ISO, and other styles
47

Noorman Masrek, Mohamad, Norhayati Hussin, and Norashimawati Tarmuchi. "An exploratory study on systems development methodologies for web‐based applications." Information Management & Computer Security 16, no. 2 (June 6, 2008): 137–49. http://dx.doi.org/10.1108/09685220810879618.

Full text
APA, Harvard, Vancouver, ISO, and other styles
48

Kendall, Kenneth E., Sue Kong, and Julie E. Kendall. "The Impact of Agile Methodologies on the Quality of Information Systems." International Journal of Strategic Decision Sciences 1, no. 1 (January 2010): 41–56. http://dx.doi.org/10.4018/jsds.2010103003.

Full text
Abstract:
Systems developers and IT project managers who apply agile methods for developing information systems (IS) subscribe to a set of values and principles. This adherence to a set of values and principles, along with a passion or fervor surrounding the agile philosophy, made us question whether the adoption of agile methodologies has an effect on information systems built, and in particular, the quality of the IS developed. In this paper we construct a conceptual model, conduct a survey of software developers, and analyze our results, which support our hypotheses about the importance of the strategic selection of a development methodology. We conclude that practicing project managers should consider the decision to use certain methodologies as part of the strategic process.
APA, Harvard, Vancouver, ISO, and other styles
49

Mitev, N. N. "Convergence and divergence in information systems and knowledge based systems development methodologies: a case for integrated strategic planning." European Journal of Information Systems 4, no. 4 (February 1996): 237–47. http://dx.doi.org/10.1057/ejis.1996.5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
50

Howard, Geoffry S., Thomas Bodnovich, Thomas Janicki, Jens Liegle, Steven Klein, Paul Albert, and David Cannon. "The efficacy of matching information systems development methodologies with application characteristics – an empirical study." Journal of Systems and Software 45, no. 3 (March 1999): 177–95. http://dx.doi.org/10.1016/s0164-1212(98)10077-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography