"Programming competency is a prerequisite for design competency"
             As the arena of information systems continues to expand at a breathtaking pace, it is worthwhile to spend sometime to look into the methodologies and the salient features of software development life cycle to get a feel of the meanders in software development.
             Essentially, whatever software is developed nowadays is based on concrete analysis and designing paradigms. However every design is rendered useless unless it is selected for the real implementation of the software.
             Hence, as one explores the nooks and corners of software development one eye-catching feature which persistently raises its head trying to grab the attention of one and all is the relationship between programming and designing.
             Although logically it follows that designing precedes programming, it has often been argued that programming competency may not be a prerequisite to designing competency. This argument holds is open to debate. But this paper aims to highlight the value of programming competency in designing competency.
             Let us go onto to find out what do we mean by competency in this context. This becomes much simpler if we go onto derive its meaning from "Incompetence". Being incompetent means being inadequate for or unsuited to a particular purpose. Hence being competent would imply achieving a certain level of finesse in whatever might be undertaken.
             Here we come to a stage where we can define programming competency and design competency. Programming competency would pertain to the development of effective and syntactically correct programs from designs – programs which are hiccup free. Programming competency also implies a command over the language used to implement the design. Whereas, designing competency implies developing robust designs for systems under development.
             Programming competency gives us a command over the various features and concept
             ...