Analisis dan Perancangan Aplikasi Construction Progress Calculation (CPC) for Piping Discipline Pada PT. IKPT

The purpose of developing the Construction Progress Planning (CPC) application is to help the piping discipline team to create planning and reporting to determine the progress of ongoing projects. As part of the governance project, each project must be measured its progress throughout the duration of the project. After obtaining the calculation of actual progress, it is then compared with the planned progress for the same period. System development methodologies used in completing the development of the CPC application is Phased Development Model. Phased Development is one approach of RAD (Rapid Application Development) as one of the SDLC. With the CPC application, planning and reporting data processing can be faster and more structured on the ongoing project. Online access facility provides up to date data that can help all interested parties to access the status or condition of the project with a transparent, easy and in real time manner.

A Comparison of Various Software Development Methodologies: Feasibility and Methods of Integration

<p class="Abstract">System development methodologies which have being used in the academic and commercial environments during last two decades have advantages and disadvantages. Researchers had tried to identify objectives, scope …etc. of the methodologies by following different approaches. Each approach has its Limitation, specific interest, coverage …etc. In this paper, we tried to perform a comparative study of those methodologies which are popular and commonly used in banking and commercial environment. We tried in our study to determine objectives, scope, tools and other features of the methodologies. We also, tried to determine how and to what extent the methodologies incorporate the facilities such as project management, cost benefit analysis, documentation …etc. One of the most important aspects of our study was how to integrate the methodologies and develop a global methodology which covers the complete span of the software development life cycle? A prototype system which integrates the selected methodologies has been developed. The developed system helps analysts and designers how to choose suitable tools or to obtain guidelines on what to do in a particular situation. The prototype system has been tested during the development of a software for an ATM “Auto Teller Machine” by selecting and applying SASD methodology during software development. This resulted in the development of high quality and well documented software system.</p>

EXPLORING THE INFLUENCES OF THE USE OF ELEMENTS COMPRISING INFORMATION SYSTEM DEVELOPMENT METHODOLOGIES ON STRATEGIC BUSINESS GOALS

As the competitive pressure of the global market for information systems (IS) continues to increase, IS development enterprises should start to consider if and how the use of IS development methodologies (ISDM) influences their main strategic business goals. More precisely, they should start to consider two different dimensions of the actual use of ISDM: the number of times an opportunity for ISDM use arises and the number of times the ISDM is actually used. Otherwise, they run the risk of mismanaging their ISDM-related investments. The goal of this study is to develop a model that would enable academics and IS practitioners to better examine and understand how different dimensions of the use of ISDM influence strategic business goals of cost leadership, differentiation and cornering niche markets in IS development enterprises. Given the limited literature on the research topic, this study was considered exploratory and theory building in nature. The main result of the presented exploratory study is a clearly defined model for examining how different dimensions of ISDM influence strategic business goals. Exploratory results show that the actual use of ISDM has a significantly positive influence on strategic business goals of differentiation and cornering of niche markets, but not the cost leadership.

Back to Basics

Massive failures of software development projects have been recorded in the literature, and particularly in the popular press, over the years. Yet, rarely if ever have we seen any objective, detailed analysis of the causes of these failures. Indeed, we usually can only surmise how the projects were managed or what the development methodology or approach was. This chapter analyses some aspects of software development projects and development methodologies in terms of the success or failure potential of these methodologies. The conclusion arrived at is that the system development methodologies handed down since the late 1970s as the preferred development approach, generally known as Structured Methodologies, based on the Structured Design Life Cycle methodology (SDLC), bear the seeds of their own failure. It is asserted that they cannot succeed because of the inherent nature and assumptions embedded in those methodologies. After some analysis of these assumptions, considered to be highly flawed and unworkable, the now not so recently published Agile Development methodologies are discussed and proffered as a workable and inherently successful approach to software system development.

Using Systems Engineering for the Development of Decision Making Support Systems (DMSS)

Decision Making Support Systems (DMSS) can mitigate the risks involved in highly uncertain processes where novelty is high, such as NPD resource management. However such systems manipulate complex organisational information and require embedding within the business it operates within. There is a risk of poor acceptance in the business if the DMSS does not take into account a number of business related considerations. Utilising a systems approach literature was analysed, from which a set of considerations pertinent to the development of DMSS was elicited. Through the assessment of a number of System Development Methodologies (SDM), it was found that no one System Development Methodology (SDM) took into account all considerations identified. There is therefore a clear gap in current research and a real need for such a methodology which addresses the considerations identified.

Using Systems Engineering for the Development of Decision Making Support Systems (DMSS)

Decision Making Support Systems (DMSS) can mitigate the risks involved in highly uncertain processes where novelty is high, such as NPD resource management. However such systems manipulate complex organisational information and require embedding within the business it operates within. There is a risk of poor acceptance in the business if the DMSS does not take into account a number of business related considerations. Utilising a systems approach literature was analysed, from which a set of considerations pertinent to the development of DMSS was elicited. Through the assessment of a number of System Development Methodologies (SDM), it was found that no one System Development Methodology (SDM) took into account all considerations identified. There is therefore a clear gap in current research and a real need for such a methodology which addresses the considerations identified.

Toward an Autopoietic Approach for Information Systems Development

Several weaknesses of information systems development methodologies have been identified and studied in the recent years. These weaknesses can be viewed from different perspectives such as: • The characteristics of the outcomes, i.e., information systems: The current methodologies are producing systems with rigid and inflexible that are difficult to maintain and to evolve (e.g., Loucopoulos, 1991). • The degree of the domain-independence: There is a gap between the way system development methodologies in the mainstream of scientific and technical literature and the way they are carried out in real life situations. This is mainly due to the domain-independence of most of these methodologies (Bansler & Bolker, 1993, Vessy & Glass, 1998). • The conceptual and philosophical bases: The dominance of the functionalistic view in the most of current methodologies (Hirschheim, Klein & Lyytinen, 1995, Iivari, 1991, Iivari, Hirschheim & Klein, 1998). In addition, most of information systems development methodologies under-utilize the richness of concepts and insights provided by new and emerging theories such as autopoiesis, self-organization, and fuzzy logic. Moreover, they do not accommodate the new emerging information systems and technologies such as component and framework technologies, web-enabled information systems and ERP.