Design Methods ??
-
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc... Thank You
-
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc... Thank You
What you need to do is define an interface that exposes the public face of the algorithms you want to develop. Then you could create individual classes that implement the interface using something like Test Driven Development. Bringing them together is the easy part - and you may want to look at something like a Class Factory to choose the relevant implementation at run time.
Deja View - the feeling that you've seen this post before.
-
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc... Thank You
Julia4u wrote:
Basically i am answering one question but using different algorithms.
Sounds like a classic case of designing by contract (a la plug-ins). See the Bridge[^] pattern and for a concrete implementation of plug-ins, see .NET 3.5's new
System.AddIn[^] namespace, although I think that may be overkill at this point (unless you want discoverability, versioning, etc. for free). /raviMy new year resolution: 2048 x 1536 Home | Music | Articles | Freeware ravib(at)ravib(dot)com
-
What you need to do is define an interface that exposes the public face of the algorithms you want to develop. Then you could create individual classes that implement the interface using something like Test Driven Development. Bringing them together is the easy part - and you may want to look at something like a Class Factory to choose the relevant implementation at run time.
Deja View - the feeling that you've seen this post before.
-
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc... Thank You
don't think so :)
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips: - before you ask a question here, search CodeProject, then Google; - the quality and detail of your question reflects on the effectiveness of the help you are likely to get; - use PRE tags to preserve formatting when showing multi-line code snippets.
-
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc... Thank You
-
Sorry to say but the answer to my question is AGILE METHODOLOGIES like XP(Incremental development) Thanks for trying at least. It took me some time to figure out but i am surprised to see that none of you know this easy answer. Strange... Anyway
-
Julia4u wrote:
AGILE METHODOLOGIES like XP(Incremental development)
WRONG! :-\
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
Incremental development is a scheduling and staging strategy in which the various parts of the system are developed at different times or rates, and integrated as they are completed. This might help you a bit to calm down. If it's not correct show me the proof like i did. ta
-
Incremental development is a scheduling and staging strategy in which the various parts of the system are developed at different times or rates, and integrated as they are completed. This might help you a bit to calm down. If it's not correct show me the proof like i did. ta
Julia4u wrote:
Incremental development is a scheduling and staging strategy in which the various parts of the system are developed at different times or rates, and integrated as they are completed. This might help you a bit to calm down. If it's not correct show me the proof like i did.
Every bloody development has various bits developed at different times and added together - there's nothing Agile about this as it applies equally to waterfall, RAD, SCRUM and the like. What we told you were the ways you should look at doing it, not the name of a methodology because we thought you were a professional developer, not a troll wanting somebody to do her homework for her. That's not what we do here.
Deja View - the feeling that you've seen this post before.
-
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc... Thank You
Julia4U - you seem to have a little bit of an attitude on you, so let me explain a couple of things to you:
Julia4u wrote:
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc...
This question is open to interpretation - you asked what the design methodology was here, but that's totally unimportant. You were told the best approach to take developing it - as I explained above the methodology is largely irrelevant if you don't know how to actually develop the code. That's why people told you how to actually develop the software - which is far more important to a real developer than the name of a methodology. BTW - which Agile method are you referring to? There are so many. Now - I assume you want a career as a developer. You're going to have to learn how to take criticism and heat. Don't play the gender card, because it just demeans you and other women. Learn how to listen and respond politely - don't get into flame wars because YOU WILL LOSE.
Deja View - the feeling that you've seen this post before.
-
Sorry to say but the answer to my question is AGILE METHODOLOGIES like XP(Incremental development) Thanks for trying at least. It took me some time to figure out but i am surprised to see that none of you know this easy answer. Strange... Anyway
Julia4u wrote:
Sorry to say but the answer to my question is AGILE METHODOLOGIES like XP(Incremental development) Thanks for trying at least. It took me some time to figure out but i am surprised to see that none of you know this easy answer. Strange...
"easy answer" This is what you originally posted:
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies.
From reading your initial description, how would anyone know that what you were talking about is the Agile Method? It's very vague. If I had to call it anything, it would be bottom-up design.
-
Julia4U - you seem to have a little bit of an attitude on you, so let me explain a couple of things to you:
Julia4u wrote:
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc...
This question is open to interpretation - you asked what the design methodology was here, but that's totally unimportant. You were told the best approach to take developing it - as I explained above the methodology is largely irrelevant if you don't know how to actually develop the code. That's why people told you how to actually develop the software - which is far more important to a real developer than the name of a methodology. BTW - which Agile method are you referring to? There are so many. Now - I assume you want a career as a developer. You're going to have to learn how to take criticism and heat. Don't play the gender card, because it just demeans you and other women. Learn how to listen and respond politely - don't get into flame wars because YOU WILL LOSE.
Deja View - the feeling that you've seen this post before.
Oh brother, I just read "her" replies in the other thread that got moved over here. As far as I'm concerned this person has burned "her" bridges here.
-
Julia4U - you seem to have a little bit of an attitude on you, so let me explain a couple of things to you:
Julia4u wrote:
I want to develop an application in .NET. Basically i am answering one question but using different algorithms. So therefore, i prefer it doing it seperately. And once i get all the algorithms working, then i can bring all the implementation together under one single project. Yeh i will be defining classes not assemblies. So what is this design methodolgy called so that i know what i am doing. I can see so many designing methods and i am confused like which one is best for me..I have read waterfall approach, agile methodology, etc etc...
This question is open to interpretation - you asked what the design methodology was here, but that's totally unimportant. You were told the best approach to take developing it - as I explained above the methodology is largely irrelevant if you don't know how to actually develop the code. That's why people told you how to actually develop the software - which is far more important to a real developer than the name of a methodology. BTW - which Agile method are you referring to? There are so many. Now - I assume you want a career as a developer. You're going to have to learn how to take criticism and heat. Don't play the gender card, because it just demeans you and other women. Learn how to listen and respond politely - don't get into flame wars because YOU WILL LOSE.
Deja View - the feeling that you've seen this post before.
-
Oh brother, I just read "her" replies in the other thread that got moved over here. As far as I'm concerned this person has burned "her" bridges here.
Yup. Ladylike she ain't.
Deja View - the feeling that you've seen this post before.