quote:Original post by Magmai Kai Holmlor To me, that''s the essence of software engineering, and focuses on the development process (things like RUP, ROPES, CMM, or XP). Is that the type of thing you had in mind?
No. That conclusion expresses exactly the same problem of mechanism over method that you were demonstrating earlier. Good software is largely independent of the tools used to develop it.
You think RUP, ROPES, CMM, & XP are all mechanisms and not methods?
What is an example of a method then?
- The trade-off between price and quality does not exist in Japan. Rather, the idea that high quality brings on cost reduction is widely accepted.-- Tajima & Matsubara
Magmai Kai Holmlor - What is an example of a method then? Sabreman - How does good software get written? Hint: none of those approaches write good software.
Then no good software is written.
- The trade-off between price and quality does not exist in Japan. Rather, the idea that high quality brings on cost reduction is widely accepted.-- Tajima & Matsubara
A person writes software and they have to think to do it. Do you propose those thought patterns should be design patterns?
- The trade-off between price and quality does not exist in Japan. Rather, the idea that high quality brings on cost reduction is widely accepted.-- Tajima & Matsubara
quote:Original post by Magmai Kai Holmlor A person writes software and they have to think to do it.
Right.
quote: Do you propose those thought patterns should be design patterns?
You''re getting warmer. The rationale of the expert designer is what goes into a pattern. Given a specific problem, why make certain choices over alternatives? What effect does each choice have? How doe each choice affect subsequent choices? Why is one choice "better" than another?
- The trade-off between price and quality does not exist in Japan. Rather, the idea that high quality brings on cost reduction is widely accepted.-- Tajima & Matsubara
quote:Original post by Magmai Kai Holmlor A specific problem?
A specific problem from the problem domain, not the solution domain. If you then capture the "thought processes" of an expert designer as she works toward a good solution, the result is a pattern.
quote:Original post by SabreMan A specific problem from the problem domain, not the solution domain. If you then capture the "thought processes" of an expert designer as she works toward a good solution, the result is a pattern.
Total aside: Any chance that you know the origins of the feminine pronoun you used there? I've googled it and can't find anything and I've only seen it when the antecedent is a programmer.
[edited by - NotAnAnonymousPoster on April 24, 2003 7:54:25 AM]
"C combines all the power of assembly language with all the ease of use of assembly language"
