Re: A Couple of Questions
Sounds like a homework assignment
Re: A Couple of Questions
Uhm yes. it's part of a coursework assignment? Which is why I said I didn't want anyone to post the answer, but just to link to a bunch of material that's of relevance - Allowing me to try to find the answer myself and subsequently; learn from it.
Re: A Couple of Questions
Re: A Couple of Questions
I'm glad to see you know how to Search :)
I've tried searching for relevant information prior to starting this thread and found nothing relating to the questions.
The links lead to content that;
1) Doesn't explain the concept of modular design as a method of organising a computer program into self-contained parts that can be developed independently.
2) Doesn't explain the nature, purpose and possible benefits of the use of standard modules and sub program libraries.
Analogy-wise, you've given me information on Fruit, when I'm looking for information on the pips inside an Apple :D
Thx anyways.
Re: A Couple of Questions
I guess I'm just dumb then
Re: A Couple of Questions
This thread is a hoot!!
So, you don't want the answers, but you want a link to a site that has the answers in sufficient detail.
Tell you what, how about if we write the answers in this thread, then once you have enough information, we'll give you a link to this very thread, as it will then be guaranteed to have what you are looking for.
I'll start, because, heck, I'm not even sure that I understand the first question. Modular design can mean a couple different things. There is the semi-modular design that is Object Oriented design, where each data member is actually a class and each class calls members of other classes. All of .NET is built that way with every object deriving from a common base. The advantage of OO design is organization. A piece of data, and all the methods that work on that data, are contained within one code construct, which is an object. The ways that other parts of the program interact with this object are defined, and constrained, by the properties and methods. Using OO design, it would be possible for someone to write up a document outlining a program and how all the different parts fit together such that they could say:
"Object X handles the database and exposes these properties and methods: Yadda() Yadda() and Yadda(), etc."
At that point, any one person could write object X and implement it however they chose. So long as it did expose the methods required, then X could be written and re-written and what not, while the whole design would work. In fact, a stub class could be written to offer up the methods, while the real class is being developed by a separate team working on some test code. Once the real class is finished, it could replace the stub class.
A different meaning of modules, though, takes that concept much further. For example, I'm working on a program where there will be a core program and a series of modules. Anybody can write a module whenever they feel like, so I don't even know what modules will exist. All I can dictate is how they will interact with the main program. For this I use an Interface, which provides a contract. As long as a class implements that interface, then the interface itself will enforce that certain methods and properties exist. Exactly what they do is up to the person writing the module, but the interface guarantees that the items WILL exist, which is enough for me. The main program can work on the assumption that all modules will behave according to contract. What this means is that module development can be separated in both time and space. Not only do I not need to know anything about how the modules will work, I don't even need to know that they are being considered.
So that's how I would start off.
Re: A Couple of Questions
Okay, so where did I say that I wanted a link to a site that has the answers? If you take the time to read the posts in this thread, you'll know that I asked for a link to a site that has information related to the questions on there. So far the links that have been posed are of no relevance to the q's.
As for you understanding the questions, they're made up by the examination body and although i'm greatful for the info you posted, do you have any links that I can visit and construct an answer for myself?
Re: A Couple of Questions
No, not other than this one. You are being too coy about the whole thing. I have certainly read the post. You explicitly state that you don't want the answer. However, you want a site that talks sufficiently on topic for you to figure out an answer, yet isn't so directly on topic that it gives you the answer. Furthermore, when somebody doesn't successfully divine out what you feel is close enough without giving you the answer, you make some sarcastic comment. Frankly, that combination makes the whole request laughable.
Both of the questions you were asked are vague. They use terminology that is not specific enough to have only one possible interpretation. If you understand what the asker actually meant by the term module, that gives you some advantage. If you don't understand what the asker meant, then any answer you come up with could be wrong simply because you used the wrong definition for the term.
Quite frankly, I feel that the first link that GM posted has all that you should need short of giving you an explicit answer. Heck, it comes pretty doggone close. Close enough to an explicit answer that the difference is a bit dangerous. After all, modular design, regardless of your definition of it, is not some holy grail that makes all code easy to write. Do it well and it might provide some benefits. Mess it up and you will have a mess. Do you know when it is right and when it is wrong? Does anyone?
You want an answer closer than those two links, but not a direct answer, just a place you "may find help". You've found it. However, if you don't want THE answer, then ask questions that are about aspects of it. So far, you've asked us to read your mind about what you want on a topic that has multiple interpretations and plenty of skeptics. Perhaps starting a discussion about a subject related to the topic would provide whatever is missing.
Re: A Couple of Questions
Quote:
Originally Posted by
Shaggy Hiker
No, not other than this one. You are being too coy about the whole thing. I have certainly read the post. You explicitly state that you don't want the answer. However, you want a site that talks sufficiently on topic for you to figure out an answer, yet isn't so directly on topic that it gives you the answer. Furthermore, when somebody doesn't successfully divine out what you feel is close enough without giving you the answer, you make some sarcastic comment. Frankly, that combination makes the whole request laughable.
Both of the questions you were asked are vague. They use terminology that is not specific enough to have only one possible interpretation. If you understand what the asker actually meant by the term module, that gives you some advantage. If you don't understand what the asker meant, then any answer you come up with could be wrong simply because you used the wrong definition for the term.
Quite frankly, I feel that the first link that GM posted has all that you should need short of giving you an explicit answer. Heck, it comes pretty doggone close. Close enough to an explicit answer that the difference is a bit dangerous. After all, modular design, regardless of your definition of it, is not some holy grail that makes all code easy to write. Do it well and it might provide some benefits. Mess it up and you will have a mess. Do you know when it is right and when it is wrong? Does anyone?
You want an answer closer than those two links, but not a direct answer, just a place you "may find help". You've found it. However, if you don't want THE answer, then ask questions that are about aspects of it. So far, you've asked us to read your mind about what you want on a topic that has multiple interpretations and plenty of skeptics. Perhaps starting a discussion about a subject related to the topic would provide whatever is missing.
Well said Shaggy. I was getting quite annoyed at his responses, i was going to reply mean things... You took care of that in a nice way.
I think that Shaggy answered your question pretty well, as did Gary.
Re: A Couple of Questions
Quote:
Originally Posted by
dclamp
Well said Shaggy. I was getting quite annoyed at his responses, i was going to reply mean things... You took care of that in a nice way.
Lol.
Quote:
Originally Posted by
dclamp
I think that Shaggy answered your question pretty well, as did Gary.
Uhm where are the links in the posts that answer my question?
Re: A Couple of Questions
Quote:
So, you don't want the answers, but you want a link to a site that has the answers in sufficient detail.
Shaggy hit the nail on the head, you say you don't want the answers but really that's exactly what you are asking for. You want a sight that pretty much explains the question you have been set and discusses it which is as close to the same thing it makes no difference.
Garry posted some links which explain OO Concepts and modular design. If you read up on Modular design and understand it then it should become apparent to you how you would go about answering your questions. The knowledge is all there you just have to read it and interpret it.
Re: A Couple of Questions
No, I really don't want the answer. I like to read a gaggle of information so I can learn for myself and come up with my own answer, that way, if I get low marks I know it's my fault as opposed to using someone elses answer regretting not finding it for myself.
I've read the info on the pages Gary posed (I ignored the Wikipedia one) and although i did find some useful information for use in question 2, there wasn't enough for me to develop a good answer.
Re: A Couple of Questions
Re: A Couple of Questions
Also, I don't think module is the right word. Try searching on Plugins .NET or Plugins Design. Unfortunately, such a search will mostly return code examples, which is what I was looking for when I performed those searches. However, there may be something useful there. Module is too fuzzy a word to provide reliable search results because it has so many meanings. Plugin seems to be the more common terminology for the concept that the questioners seem to be trying to get at.
