Hi,

It's the beginning of 2018 and I am here to share with you a new approach to software development, applicable to the development of Java based web applications.

Conventionally, you assign a team of programmers and non-programmers (testers, functional experts, managers) to a project. Requirements have to be well understood by the programmers and when a programmer leaves, it is a project risk because a replacement would take long to gain any project specific knowledge.

Here is a technology -- its internal name is MGF -- that changes this. It lets you develop software in 3 steps:

  1. Draw a flow of the software (visual diagram)
  2. Get the modules developed individually
  3. Burn the application (like you burn a CD)

The good news is that steps 1 and 3 are non programmatic. This means that the non-programmers can be more productive. Think about it: if the functional expert draws the flow, then the need to teach the programmers the domain expertise in detail goes down. You just have to spec out the individual modules as opposed to the whole program. The managers and testers are happier with the visual flow diagram which is guaranteed to be up to date with the actual running of the application (as opposed to conventional process where the design documents are rendered useless after a few months).

Also, in case you missed it, the modules are developed individually -- which means that a programmer has to think of only one module at a time. It is quite simple and fast as opposed to worrying about the whole application.

Now if your programmer is leaving, you just have to ask her to complete her present module. The replacement can start with the next module, with least learning. In fact, people may walk in and walk out of your project more freely, and that imparts scalability to your development process itself. Just add people if a project is running behind schedule.

Do you think this could make sense on any of your projects?

Ashish

connect@10Xofy.com
98900 56365

Views: 199

Reply to This

Replies to This Discussion

@Ashish,

Since the OOPS concept started in programming languages, no one is using procedural languages like c and earlier, in most of projects. Each and every language is object oriented. Take any language like PHP, .NET, JAVA are the OOPS languages. 

OOPs language projects structures are generally hierarchical.

Example :

1) Many functions ( methods ) makes a class

2) Many such classes makes a package

3) Main function is to decide flow of above.

Still it will require a master developer as there are still many dependencies and many cases needs to be handled.

If you are talking about independent modules like JAR / WAR / EAR / AAR...

Still it will require a master developer as there are still many dependencies and many cases needs to be handled.

Your Point number 1

1) Draw a flow of the software (visual diagram :

Definitely it will help a new developer or programmer to understand the concept 

2) Get the modules developed individually

In this case too there must be a master developer who knows all ins and outs and how project will work on specific device, who can only decide point 1 and aggregate modules to be developed in chunks.

3) Burn the application (like you burn a CD)

Such thing never happens as where is main program to decide which modules and on what cases it should be called? And what to do if inappropriate things returned by modules called...? These all things needs to be programmed with exception handling. Again what to do in exceptions is also needed to be coded.

It never happened before and at least would not happen next 50 years at least. Impossible

I am a engineering graduate and had worked in linux file system development, responsive web development, Object oriented development across linux, windows, mac os x, android , iphone, robotics.

rushikant pawar

pawarrushikant@gmail.com

RSS

© 2018   Created by Santosh.   Powered by

Badges  |  Report an Issue  |  Terms of Service