Approaches to software development


In this tutorial, you will learn about, Approaches to software development.

Approaches to software development:

The different approaches to system development are:

  1. Prototyping.
  2. Joint application design.
  3. Participatory design.

a) Prototyping: designing and building a scale down but a fundamental version of a designed system is known as prototyping. Prototyping is a form of rapid application development. The fundamental principle of any RAD methodology is to delay producing a detailed system design document until the user requirements are clear.

The process of prototyping approach is:

  • The analysist work with the initial and basic requirement of the system.
  • The analysist then deals with a prototype when the prototype is completed the user works with it and tells the analysist what they liked and what they dislike.
  • The analysist uses the feedback to improve the prototype and takes the new version back to the user.
  • The process is iterated until the user is satisfied.

b) Joint application Design: it is defined as a structured approach in which user, managers and the analysis work together for several days in a series of intensive meetings to specify or review system requirements.
The important features of JAD are drawing requirements planning, Which is a process whereby highly structured group meetings are conducted to analyse problems and define requirements, an added advantage is that group members are more likely to develop a shared understanding of what the information system is supposed to do.

The typical participants in a JAD are:

  • JAD session Leaders: he organizes and runs the meetings, the leader sets the agenda and sees that the agenda is fulfilled or not. He remains neutral throughout the session and concentrates on keeping the group on agenda, resolving conflicts and disagreements and appreciating all the ideas.
  • User: they are the only one who has a clear understanding of what it means to use the system on a daily basis.
  • Manager: the role of the manager during JAD is to approve projects objectives, establish project priorities, approve schedule and cost and to approve training needs and implementation plan.
  • System analysis: the member of the system analysis team attend the JAD session although their actual participation may be limited. Analysist are there to learn from its customers and manager but not to run or dominate the process.
  • Scribe: he takes down the notes during the JAD session.
  • IS Staff: (information system staff) IS Staff, Such as programmers, data analysis, IS Planner, date control person may attend the session to learn from the decision but the possibility to contribute their ideas is very limited.

c) Participatory design: participatory design emphasis more on the role of a user then the other techniques do. In some of the cases, the entire user community is involved in the development process. Each user has an equal share in determining the system requirements and in approving system design.

Comment below if you have queries related to the above topic, Approaches to software development.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.