 |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | |
| By N2H | ||||||||||||||||||||||
Systems development methodology
October 30, 2007
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting and have a nice day!
A methodology can be described as a collection of procedures, techniques, tools and documentation aids which will help the system development. A methodology can thus be said to have various features. These features can be categorized into technical model and managerial model.
A methodology needs to have a technical model. This model includes features like the tools, processes and procedures. A methodology needs to have tools which will help the developers in the process of developing an Information System. These tools help in every phase or sub phase involved in the methodology e.g. CASE tools, project management tools, Drawing tools, Data dictionary e.t.c.
A methodology also needs to have a technique. Technique help to verify and expound on the methodology, thus they enable the phase and sub phase of methodology to be carried out according to the methodology’s principle. Technique acts as guides of methodology’s phase. Techniques address different parts (phases) of a methodology. A methodology can have many techniques. Techniques also enable easy understanding of what the methodology requires e.g. Decision trees/tables, Entity Life Cycle, Structured diagrams, normalization e.t.c.
A methodology also needs to have a philosophy, in that it needs to have the underlying theories and assumptions that the authors of the methodology believe in. This feature helps to shape and guide the development of an Information System. It also enables the understanding of the methodology.
A methodology also has a managerial model. This feature is that of the development structure, in that a methodology needs to have a development structure that;
-
Identifies the phases, sub phases, steps and tasks to be done in the methodology.
-
Identifies the outputs to be produced and under which circumstances they should be produced.
-
Constraints to be applied and people to be involved. This feature provides for the development process to be really managed and controlled.
The rationale for writing a methodology
A better end product: In that the methodology should improve the end product of a development process i.e. a better I.S.
A better development process: In that the methodology should provide improved management and project control so that the organization can gain from the benefits that accrue from a tightly controlled development process.
A standardized process in that people take up a methodology that can provide a common approach through out the organization so that they gain from the benefits of standardization mainly;
-
Better integration of projects or systems.
-
A base of common knowledge and experience is achieved.
Practical issues to be considered when selecting a methodology?
The practical issues are budget constraints; the organization should consider the cost associated with the methodology e.g. training, hardware, software costs, CASE tools, consultancy e.t.c.
Dependency on automated tools: in that the organization should look to see if the methodology depends on these tools and if the organization is happy with that or not.
Learning curve is another issue that the organization should consider.
Aids to future developments: if the methodology is feasible and can be adapted as technology changes.
Relevance to the application:
Comments
Got something to say?
Powered by FireStats