Re: Estimation for Remedy development
Hi Ramya Could you please throw some more light on the process to use this estimator? I was not able to understand by just viewing at the xls. Thanks Parikshit - Original Message From: Ramya Mudambi <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Thursday, 7 December, 2006 2:16:55 PM Subject: Re: Estimation for Remedy development ** Hi Jason, I have worked on the remedy estimator model. The estimation would vary from one requirement to the other. Pls. have a look at the attached estimator… This is one of the simplest ways… depends how complex u would like to make it J Have a great day ! With regards, Ramya From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jason McDonald Sent: Thursday, December 07, 2006 11:34 AM To: arslist@ARSLIST.ORG Subject: Re: Estimation for Remedy development ** Thanks Jennifer, that's exactly what I needed. Mark, Would it be possible for you to share with me a copy of the tool? Thanks On 12/6/06, Meyer, Jennifer <[EMAIL PROTECTED]> wrote: I did one several years ago for the Air Force, but I don't have a copy of the definition files. Mark, do you guys still use that Function-Point Analysis tool we built over there at AFWA? Essentially what we did was treat Remedy as a fourth-generation software development language, then perform function-point analysis, where we assigned a difficulty level to each requirement. Each requirement was broken down into the pieces of workflow required: Active Links, Filters, Forms, etc. Since some pieces of workflow are more complex than others, they're given a modifier with a higher number, e.g. forms are far more complex than filters, thus forms might get an 8 modifier, and filters might get a 2. Then each individual filter will be assessed as to how difficult it was based on number of actions, qualifications, etc, on a scale of 1 to 10. Finally, the skill of the developer is taken into account, and the project is given a third modifier. We pulled the formulas from a couple of textbooks on software development and function-point analysis and built the whole thing in Remedy. We even managed to tie it to our salaries and project the time it would take to complete future projects. The best part is that since Remedy is so efficient, compared to a second or third-generation development language like C, we look like GODS, coding millions of lines per year. Good luck with your efforts. Jennifer Meyer Remedy Support Engineer Strategic Technologies Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jason McDonald Sent: Wednesday, December 06, 2006 10:37 AM To: arslist@ARSLIST.ORG Subject: Estimation for Remedy development ** Hi All, If anybody has developed a remedy estimation model or are aware of one that already exists, please share the same with me. I need this for one of the Remedy developments that we are currently undertaking. Thanks Jason __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" __20060125___This posting was submitted with HTML in it___ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. __20060125___This posting was submitted with HTML in it___ __ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Estimation for Remedy development
Hi Jason, I have worked on the remedy estimator model. The estimation would vary from one requirement to the other. Pls. have a look at the attached estimator... This is one of the simplest ways... depends how complex u would like to make it :-) Have a great day ! With regards, Ramya From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jason McDonald Sent: Thursday, December 07, 2006 11:34 AM To: arslist@ARSLIST.ORG Subject: Re: Estimation for Remedy development ** Thanks Jennifer, that's exactly what I needed. Mark, Would it be possible for you to share with me a copy of the tool? Thanks On 12/6/06, Meyer, Jennifer <[EMAIL PROTECTED]> wrote: I did one several years ago for the Air Force, but I don't have a copy of the definition files. Mark, do you guys still use that Function-Point Analysis tool we built over there at AFWA? Essentially what we did was treat Remedy as a fourth-generation software development language, then perform function-point analysis, where we assigned a difficulty level to each requirement. Each requirement was broken down into the pieces of workflow required: Active Links, Filters, Forms, etc. Since some pieces of workflow are more complex than others, they're given a modifier with a higher number, e.g. forms are far more complex than filters, thus forms might get an 8 modifier, and filters might get a 2. Then each individual filter will be assessed as to how difficult it was based on number of actions, qualifications, etc, on a scale of 1 to 10. Finally, the skill of the developer is taken into account, and the project is given a third modifier. We pulled the formulas from a couple of textbooks on software development and function-point analysis and built the whole thing in Remedy. We even managed to tie it to our salaries and project the time it would take to complete future projects. The best part is that since Remedy is so efficient, compared to a second or third-generation development language like C, we look like GODS, coding millions of lines per year. Good luck with your efforts. Jennifer Meyer Remedy Support Engineer Strategic Technologies Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jason McDonald Sent: Wednesday, December 06, 2006 10:37 AM To: arslist@ARSLIST.ORG Subject: Estimation for Remedy development ** Hi All, If anybody has developed a remedy estimation model or are aware of one that already exists, please share the same with me. I need this for one of the Remedy developments that we are currently undertaking. Thanks Jason __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" __20060125___This posting was submitted with HTML in it___ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" Remedy Estimation model.xls Description: Remedy Estimation model.xls
Re: Estimation for Remedy development
Thanks Jennifer, that's exactly what I needed. Mark, Would it be possible for you to share with me a copy of the tool? Thanks On 12/6/06, Meyer, Jennifer <[EMAIL PROTECTED]> wrote: I did one several years ago for the Air Force, but I don't have a copy of the definition files. Mark, do you guys still use that Function-Point Analysis tool we built over there at AFWA? Essentially what we did was treat Remedy as a fourth-generation software development language, then perform function-point analysis, where we assigned a difficulty level to each requirement. Each requirement was broken down into the pieces of workflow required: Active Links, Filters, Forms, etc. Since some pieces of workflow are more complex than others, they're given a modifier with a higher number, e.g. forms are far more complex than filters, thus forms might get an 8 modifier, and filters might get a 2. Then each individual filter will be assessed as to how difficult it was based on number of actions, qualifications, etc, on a scale of 1 to 10. Finally, the skill of the developer is taken into account, and the project is given a third modifier. We pulled the formulas from a couple of textbooks on software development and function-point analysis and built the whole thing in Remedy. We even managed to tie it to our salaries and project the time it would take to complete future projects. The best part is that since Remedy is so efficient, compared to a second or third-generation development language like C, we look like GODS, coding millions of lines per year. Good luck with your efforts. Jennifer Meyer Remedy Support Engineer Strategic Technologies Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jason McDonald Sent: Wednesday, December 06, 2006 10:37 AM To: arslist@ARSLIST.ORG Subject: Estimation for Remedy development ** Hi All, If anybody has developed a remedy estimation model or are aware of one that already exists, please share the same with me. I need this for one of the Remedy developments that we are currently undertaking. Thanks Jason __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Re: Estimation for Remedy development
I did one several years ago for the Air Force, but I don't have a copy of the definition files. Mark, do you guys still use that Function-Point Analysis tool we built over there at AFWA? Essentially what we did was treat Remedy as a fourth-generation software development language, then perform function-point analysis, where we assigned a difficulty level to each requirement. Each requirement was broken down into the pieces of workflow required: Active Links, Filters, Forms, etc. Since some pieces of workflow are more complex than others, they're given a modifier with a higher number, e.g. forms are far more complex than filters, thus forms might get an 8 modifier, and filters might get a 2. Then each individual filter will be assessed as to how difficult it was based on number of actions, qualifications, etc, on a scale of 1 to 10. Finally, the skill of the developer is taken into account, and the project is given a third modifier. We pulled the formulas from a couple of textbooks on software development and function-point analysis and built the whole thing in Remedy. We even managed to tie it to our salaries and project the time it would take to complete future projects. The best part is that since Remedy is so efficient, compared to a second or third-generation development language like C, we look like GODS, coding millions of lines per year. Good luck with your efforts. Jennifer Meyer Remedy Support Engineer Strategic Technologies Inc. -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jason McDonald Sent: Wednesday, December 06, 2006 10:37 AM To: arslist@ARSLIST.ORG Subject: Estimation for Remedy development ** Hi All, If anybody has developed a remedy estimation model or are aware of one that already exists, please share the same with me. I need this for one of the Remedy developments that we are currently undertaking. Thanks Jason __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
Estimation for Remedy development
Hi All, If anybody has developed a remedy estimation model or are aware of one that already exists, please share the same with me. I need this for one of the Remedy developments that we are currently undertaking. Thanks Jason ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
