INTRODUCTION TO INFORMATION TECHNOLOGY-WEEK 8

There were some problems with the electricity in ICT building again in this week. We had to move to library to study the next lecture. My lecturer explained briefly about the lesson to my group. Therefore, I have learned some main points about information system development methodologies.


Actually there are various methodology definitions. According to what i have understood, a methodology is a collection of procedures, tools and documentation aids which will help the systems developers to implement a new information system. A methodology for developing information systems is needed to bring order and structure to a complex technical and organizational process

There are many different methodologies used in systems development, such as: Gane and Sarsons (STRADIS), Information Engineering (IE), Jackson System Development, Structured approach (SDLC), and so on.


I would like to summarize the main ideas of some important ISD methodology.
The first is about STRADIS. The focus of analysis in this method is the Data Flow diagram, which is used to describe the processes of the system, and how the processes transform data.

 The second is about IE. It's an architectural approach to planning, analyzing, designing, and implementing applications within an enterprise. The figure below is the steps of IE methodology:

 The next is about Jackson system development (JSD). It is a method of system development that covers the software life cycle either directly or, by providing a framework into which more specialized techniques can fit. JSD is a technical method. Other technical methods include Structured Analysis and Design and Object-Oriented Systems Analysis and Design.

Last but not least, it is about SDLC-The oldest and most known methodology used to coordinate the efforts of information systems development is known as the “Waterfall”. 
This model is based on a set of generic life cycle stages to guide developers from an initiating through maintenance of the completed systems.
It covers many activities starts from understanding why the system should be built, studying the project feasibility, analyzing problems, choosing the system design and architecture, implementing and testing it, up to delivering the system as product to the user.