Algorithms

Just to clear something up, this approach to what you want do is not an algorithm. Its a process flow. The repeated parts would simply be decision gates, depicting what must be done next. No algorithm that i am aware of is going to help you define user steps.

well i donno i was told this is a algorithm...

"Do it like this and you'll get marks." so thats just what i did... (cause i don't know any better) (and cause the work is Increasingly stupid)

I was actually hoping they would teach us how to program rather than write databases :sick:

So yeah...
 
Well they are idiots, its not an algorithm. Its a process flow of sorts, a UML if you would. But you cant really tell them they are idiots lol...
 
Not even UML - it's pseudo-code / use-case. Helps you plan the flow and interaction of the system and business processes.

Anyway, database-driven development is very important, so learning how to "write databases" is very important. Learn the basics now and when/if you go to varsity, you won't feel too alienated.
 
Open Database
Click options
Click enable Content
Click ok
Login with Username and Password
Goto New Customer Order
Choose Customer
If Customer ID does not exist
Then open add client
End if
If Customer ID does exist
Choose Customer ID
If product >1 then
Choose product
Choose Quantity of Product

Sorry i fail to see how that is pseudo-code.

if <condition>
do stuff
else
do other stuff

while <condition>
do stuff

for <variable> from <first value> to <last value> by <step>
do stuff with variable

function <function name>(<arguments>)
do stuff with arguments
return something

<function name>(<arguments>)

Telling someone to click a button, and then click another button is process flow.
 
Well, that's not really process flow either. The "click and do" scenario borders on use-case. So lets settle on pseudo-process-case. Aiight?
 
Top
Sign up to the MyBroadband newsletter
X