Acquisition, Development & Implementation of Information Systems

This post will be written in हिन्दी as well as English.
Do let me know in the comments below what do you think about this style.


Prototyping can be viewed as a series of four steps wherein Implementation and Maintenance phases followed by full-blown developments take place once the prototype model IS tested and found to be meet uses' requirements. The generic phases of this model are explained as follows:

  1. Identify information system requirements
  2. Develop the initial prototype
  3. Test & revise
  4. Obtain user signoff of the approved prototype

MNEMONICS (हिंदी मे)

इन numbers की sound इनके सामने लिखे words से मिलती है |  जैसे 1 (one ) की sound "Son " से मिलती है| 


10 ZEN

पहले "5" Strengths के लिए use होंगे, और बाद के "5" Weakness के liye.
अब इनका रिलेशन जैसे जैसे होगा वो मै बताने जा रहा हू | 
सबसे पहले मै सिर्फ sound की linkage बातयूंगा। 
(By the way it's cool to write in Hindi, let me know in the comments below is this helpful or not? or should i continue to write hindi in english alphabets).

If you haven't watched the Mnemonic video where the techniques are explained then watch it here.
DO watch the video to understand the linkage.


  • SON: Son difficult functions perform करता  है | 

  • SHOE: Shoes ka Quick implementation होता है, जल्दी से दाल लेते है हम Shoes.

  • FREE: Preeto (i.e Prototyping) ने free time मे अपनी requirements को properly define किया 

             Requirements मतलब उसे shopping करनी थी , list बना के दे दी उसने। 

  • CHOR: चोर pitchli चोरी की knowledge को अगली चोरी मई use करता है। 

  • WIFE: wife हमेशा encourage  करती है innovation 

  • VICKS: Vicks से behavioural problem ठीक हो जाती है i.e cold ठीक हो जाता है 

  • HEAVEN: Heaven जाने के लिए एक Approval process है (मतलब पहले से ही पता है की atche काम करोगे तो ही heaven जा पयोगे i.e  भगवान की approval लेनी parti है। 

  • WEIGHT: Weight loose करने के लिए user का significant time लगता है।  

  • WINE: Wine पी कर designer ने Quickly , prototype design कर दिया i.e without analyzing user की requirements { designer ने पी रक्खी थी तो किसी चीज़ का ध्यान नहीं दिया बस जल्दी से prototype design  कर diya }  

  • ZEN: Zen car customer की requirement के according change नहीं हो पाई इसलिए fail होगयी। 

MNEMONICS linkage will be shown as well.

Strengths: Some of its strengths identified by the experts and practitioners include the following:

It improves both user participation in system development and communication among project stakeholders.

  • It is especially useful for resolving unclear objectives; developing and validating user requirements; experimenting with or comparing various design solutions, or investigating both performance and the human computer interface. 3 = FREE

  • Potential exists for exploiting knowledge gained in an early iteration as later iterations are developed. 4 = CHOR

  • It helps to easily identify, confusing or difficult functions and missing functionality. 1 = SON

  • It enables to generate specifications for a production application.

  • It encourages innovation and flexible designs. 5 = WIFE

  • It provides for quick implementation of an incomplete, but functional, application. 2 = SHOE

  • It typically results in a better definition of these users' needs and requirements than does the traditional systems development approach.

  • A very short time period is normally required to develop and start experimenting with a prototype. This short time period allows system users to immediately evaluate proposed system changes.

  • Since system users experiment with each version of the prototype through an interactive process, errors are hopefully detected and eliminated early in the developmental process. As a result, the information system ultimately Implemented should be more reliable and less costly to develop than when the traditional systems development approach IS employed.

WeaknessSome of the weaknesses identified by the experts and practitioners include the following: 

  • Approval process and control are not strict. 7= HEAVEN

  • Incomplete or inadequate problem analysis may occur whereby only the most obvious and superficial needs Will be addressed, resulting in current inefficient practices being easily built into the new system.

  • Requirements may frequently change significantly. 10 = ZEN

  • Identification of non-functional elements is difficult to document.

  • Designers may prototype too quickly, without sufficient upfront user needs analysis, resulting in an inflexible design with narrow focus that limits future system potential. 9 = WINE

  • Prototype may not have sufficient checks and balances incorporated.

  • Prototyping can only be successful if the system users are willing to devote significant time in experimenting with the prototype and provide the system developers with change suggestions. The users may not be able or willing to spend the amount of time required under the prototyping approach. 8 = WEIGHT

  • The interactive process of prototyping causes the prototype to be experimented with quite extensively. Because of this, the system developers are frequently tempted to minimize the testing and documentation process of the ultimately approved information system. Inadequate testing can make the approved system error-prone, and inadequate documentation makes this system difficult to maintain.

  • Prototyping may cause behavioral problems with system users. These problems include dissatisfaction by users if system developers are unable to meet all user demands for improvements as well as dissatisfaction and Impatience by users when they have to go through too many interactions of the prototype 6 = VICKS

[Only 5-5 points are covered here]


Video coming soon... Stay tuned!