Science Forums 2

[CraigD]

Originally Posted by SidewalkCynic

Basically, what I am trying to determine is if I can classify engineering and computer programming as having the commonality of algorithms involved in the initiation of a task/project exercising either of the activities.

Taken far enough, nearly anything can be considered an algorithm, but in normal usage, we only refer to artificial lists of instructions as algorithm. So a computer program is an algorithm, while the chemical reaction of a virus encountering a particular cell is not, although the number, complexity, and consistency of execution of “coded” instructions for each may be similar.

Originally Posted by SidewalkCynic

My problem being that I understand algorithms as being the abstract concept that the initiator of a project requests engineers or programmers to detail.

I think you may be overcomplicating things.

An algorithm is simply a rule for doing something. For example

1. Set a counter named “A” equal to 1, one named “B” to zero
2. Compare B to a counter named “C”. If B is greater than or equal to C, state the value of C, followed by the words “factorial is” followed by the value of B, and stop.
3. Otherwise, increase B by 1, set A to A multiplied by B, and repeat from step #2

is an algorithm for stating the value of the factorial of an integer, C, ie: C! Note that it’s not a “bullet-proof" one, as it doesn’t check to assure that C is a non-negative integer.

There are some common and uncommon usages of the term “algorithm”, and some words meaning the same thing used more and less commonly in various contexts. A list of instructions performed by an electronic or mechanical computer, or by someone who knows how to act like one, is usually called a “program”. When spoken of abstractly, as something that could be performed by in principle any equivalent entity, it’s usually called an “algorithm”. When performed by a human being in a business setting, it might be called a “procedure” or “process”, and might be written in a strange way (the “how to make a sandwich” and “how to wash your hands” pictographs found in restaurants, for example)

Originally Posted by SidewalkCynic

So, I am probably looking for the term that describes the general classification of expectations of what a tool can be directed to do.

A common word for this, if I understand your meaning, is “specifications”. There’re many specialized business versions on the term, but “specification”, often with various modifiers (eg: “detailed specifications”, “business specification”, etc.) is, I think, the most widely used and recognized. Occasionally, one sees the word “specifications” replaced with another word – “solution” is a common one – but in my experience such substitutions are more trade art than meaningful language differences.

While specification and algorithms are clearly related, they’re very different and distinct things. In short, a specification describes is what an algorithm should do, an algorithm, how it is actually done.