Parallel approach & Pilot Approach

[indresh2152]

By implementation phase i mean the last phase of installing and maintaining the s/w and as it is clear from the link provided that the two approaches can be used for the same.

And as the respective moderators have suggested previously that there is no termed known as pilot approach, i would like to request them to please visit the link and check it out whether there is anything known as pilot approach or not.

Also they had said that they don't know what the heck i am talking about.

I would like to ask you a simple question that if the terms are not correctly used(or you may have not heard of the terms) then it means that the "McKinnon Secondary College in Australia" is giving us the wrong information. Is it like that?

I have already given the explanation that my teacher gave me, please suggest me that whether it is right or do you have any explanations for the terms.

Thanks

[indresh2152]

In my childhood i was taught by my physics teacher that "it is better for a science student to keep mum rather than answering wrong"

[RedSon]

In my childhood i was taught by my physics teacher that "it is better for a science student to keep mum rather than answering wrong"

First off let me say that is the most ridiculous thing I have ever heard. Your physics teacher should be defenestrated. If you think you know the answer then speak up. If you are wrong then you learned something.

Second, implementation phase in s/w development is when you sit down in front of your computer and start implementing the code. Installation and maintenance of the software is not the "implementa tion phase" it is the maintenance phase. So in answer to your question, the parallel and pilot approach do correspond to the ways in which a company or individual can install or "roll-out" a product, but it doesn't make any sense when applied to implementing software.

If you reread the previous posts, no one said that you don't know what the heck you are talking about. I said that you shouldn't expect me to know what you are talking about if we were in an interview situation.

Finally, your original question was:

what are Parallel approach & Pilot Approach in the implementation phase of the s/w development?

Given the link that you have provided I think we can say this has been answered. The answer is, there is no such thing as Parallel or Pilot approach to implementing software. There is however a parallel or pilot approach to deploying software to a group of users or consumers.

Does that resolve your issue?

[indresh2152]

i want to know the exact meaning of pilot approach and parallel approach in regard of s/w deployment.

And as you say that that a person should always answer whether he is right or wrong, it should be in the case when the person asking the question already knows the answer and not in the case if a person is seeking for answer

I was seeking an answer for my question and the reply came that there is no term known as pilot approach.

Now i hope that you will understand what i am trying to say. Please take it positively and not as argument

[indresh2152]

please help me find what are pilot approach and parallel approach with regard to s/w deployment and maintenance.

[RedSon]

I will take it positive, I don't think you are arguing.

I do not understand what you are looking for. The link you have provided (http://www.mckinnonsc.vic.edu.au/vce...tion/index.htm) gives a diagram of what a Pilot and Parallel deployment looks like.

Pilot:

In this image it shows the new system being deployed to a small group while the old system is still being used. At some point in time the decision is made to end the pilot deployment. At some later point in time the decision is made to directly convert the entire user base to the new system or to convert the user base in phases.
Parallel:

In this image it shows the new system being deployed to a small group while the old system is still being used. At some point in time the decision is made to directly convert the entire user base to the new system or to convert the user base in phases.

You have already answered your own question, you have the resources before you to figure out:

... what are pilot approach and parallel approach with regard to s/w deployment and maintenance.

What part of that are you still having trouble with?

[gits]

to be honest ... when i reread post#13 where you told us the answer of your teacher? i don't understand what this answer should have to do with what is shown on that given link ...

[RedSon]

Gits, you mean post #5?

[gits]

yes ... of course :) ... just answered more things at once and guess i mistyped it then ... so ... #5 of course :) - since that should be the answer of the OPs teacher ... that is just confusing in regards to the things that are shown on the OPs provided link ...

[cyberience]

I wonder if what he really means is the Quality driven practice of 2 Developers working together on a single Keyboard as apposed to a Single Gatekeeper who drives the development and all modules and developments are handed to the gatekeeper as a build owner?
Working as a Programmer and Analyst since 1989, I have heard of many terms that Marketing people like to come up with that have no or nearly no difference in the physical world, and only refer to a method of looking at a solution or approach, so when I see Parallel Development, I think of 2 things, 2 to 1 developers, and Back End + Front End at the same time, and tie them together after the prototype at the business layer.
When I look at developments from experience, and with 0 Failed projects in my life of over 40 projects, I have found Front to back to be more productive and successful, using the XP approach, give the users a Prototype screens to play with, and build the BL and DB to fit, with some DB common sense. I have also found that rebuilding the prototype is not required, if you build the prototype as a template architecture, you can use it in the final build if the differences are minor. but expect some Input or output to be thrown away/replaced or added to.
I am sorry I am not answering your question directly but sharing actual business experience in a fast changing environment.