EXPLORATORY STYLE OF SOFTWARE DEVELOPMENT

-

EXPLORATORY STYLE OF SOFTWARE

 DEVELOPMENT


 The exploratory program development style refers to an informal development style where the programmer makes use of his own intuition to develop a program rather than making use of his own institution to develop a program rather than making use of the systematic body of knowledge categorized under the software engineering discipline . The exploratory development style gives the complete freedom to the programmer to choose the activities using which to develop the software. Though the exploratory style imposes no rules a typical development starts after an initial briefing from a customer. A schematic of this work sequence in a build and fixed style has been shown graphically below.


An initial development style can be successful when used for developing very small programs, and not for professional software.

What is wrong with exploratory style of software development ?

* Though the exploratory software development style is intuitively obvious, on software team can        remain competitive if it uses this style of software development. Let us examine, how do the time       and effort is required to develop a professional software increases with the size of programming     size. Let us consider the exploratory style is being used to develop a professional software. The       increased in development effort and time with problem size has been indicated .


*It can be seen that as the problem size increases, the required effort and time increases almost exponentially. For large programs, it would take too long and cost too much to be practically meaningful to develop the program using the exploratory style of the development. The exploratory development approach is said to break down after the size of the program to be developedincreases beyond certain value.



Now, let us try to understand why does the effort required to develop a program grow exponentially with program size when the exponential style is used and then the approach to develop a program completely breaks down when the program size become large? To get an insight into the answer to the question, we need to have some knowledge of the human shall see. Please note that the perceived complexity of a problem in not related to the time or space complexity issues with which you are likely to be familiar with from a basic course on algorithms.


The psychological or perceived complexity of a problem concerns the difficulty level experienced by a programmer while solving the problem using the exploratory development style.


Even if the exploratory style causes the perceived difficulty of a problem to grow explonentially due to human cognitive limitations,





Comments

Post a Comment

Popular posts from this blog

causes and solutions of software crisis

-
Image
Causes of and solutions for software crisis.  Software engineering appears to be among the few options available to tackle the present software crisis.  To explain the present software crisis in simple words, consider the following. The expenses that organizations all around the world are incurring on software purchases compared to those on hardware purchases have been showing a worrying trend over the years.  Fig. 1.6: Change in the relative cost of hardware and software over time  Organizations are spending larger and larger portions of their budget on software. Not only are the software products turning out to be more expensive than hardware, but they also present a host of other problems to the customers: software products are difficult to alter, debug, and enhance; use resources nonoptimally; often fail to meet the user requirements; are far from being reliable; frequently crash; and are often delivered late. Among these, the trend of increasing software costs
Read more

STACK Programming in C

-
Image
STACK Programming in C Language- Stack Data Structure Stack is a linear data structure which follows a particular order in which the operations are performed. The order may be LIFO(Last In First Out) or FILO(First In Last Out). There are many real-life examples of a stack. Consider an example of plates stacked over one another in the canteen. The plate which is at the top is the first one to be removed, i.e. the plate which has been placed at the bottommost position remains in the stack for the longest period of time. So, it can be simply seen to follow LIFO(Last In First Out)/FILO(First In Last Out) order. problem statement:perform the following operations -1. PUSH,                                                                                        2.POP                                                                                        3.PEEP                                                                                        4.DISPLAY C-CODE: #incl
Read more