|
The article about [[Lutefisk]] claims: "Lutefisk (prounounced loo-te-fisk) is a well-known food of Norway and Sweden (prounounced loo-ta-fisk)which consists of white fish (normally Cod) soaked in lye as a preservative, then dried until it hardens. It is edible after multiple rinsings of water to remove the otherwise poisonous lye, and has a jelly-like consistency after washing."
'''David Parnas''' is a pioneer of [[software engineering]] who developed module design, social responsibility, and professionalism.
This is actually wrong. The fish is dried first, [[Stockfish]], and then soaked in lye or another base (like birch ash). After this it is rinsed in water. And another thing; it tastes delicious :)
----
''Module Design:'' Parnas wrote about the criteria for designing modules, in other words, the criteria for grouping functions together. This was a key predecessor to designing objects, and today's object-oriented design.
''Social Responsibility:'' Parnas also took a key stand against the [[Strategic Defense Initiative]] (SDI) in the mid 1980s, arguing that would be impossible
to write an application that was free enough from errors to be safely deployed.
''Professionalism:'' Parnas became one of the first software engineers to earn a professional engineering license in Canada. He believes that software engineering is a branch of traditional engineering.
----
Dr. Parnas won an ACM "Best Paper" Award in 1979.
He won two "Most Influential Paper" awards from the
[[International Conference on Software Engineering]].
He won ACM SIGSOFT's "Outstanding Research" award in 1998.
Parnas earned his Ph.D. at [[Carnegie Mellon University]], and worked there as a professor for many years. He also taught at the University of North Carolina, the Technische Hochschule Darmstadt, and the University of Victoria.He then went to [[McMaster University]] in Hamilton, Ontario, Canada. He currently works at the [[University of Limerick]] in Limerick, Ireland.
==Quotes==
"...it is almost always incorrect to begin the decomposition of a system into modules on the basis of a flowchart. We propose instead that one begins with a list of difficult design decisions or design decisions which are likely to change. Each module is then designed to hide such a decision from the others."
==External links==
*[http://www.acm.org/classics/may96/ On The Criteria To Be Used in Decomposing Systems into Modules] (famous paper)
*[http://www.xp2003.org/xp2002/talksinfo/parnas.pdf Xp Versus MTP: The Limits of Extreme Programming] (slides for a presentation given at the XP2003 conference)
| 