I never knew what pseudo-code was before this post...I had actually never planned a single one of my programs out before!!
Wow...learn something new everyday, huh?
I'll definately start using it
Every time
Sometimes (depends...)
Never
I never knew what pseudo-code was before this post...I had actually never planned a single one of my programs out before!!
Wow...learn something new everyday, huh?
I'll definately start using it
I'm surprised & happy to know that such a senior member like you is getting something to learn from the board. I'm inspired.
[ Never code before desk work ]
-------------------------------------:-->
A man who fears Nothing is the man who Loves Nothing
If you Love Nothing, what joy is there in your life.
=------------------------------------------------------= - I may be wrong.
>>I never knew what pseudo-code was before this post...I had actually never planned a single one of my programs out before!!
Neither did I...
Does it help at all?
Sauron a few seconds before his defeat:
"What? A 'division by 0' error?!?"
The main purpose of pseudo-code is to present the algorithm in your own natural language. And often no care is taken of the final programming language. It's just describing an algorithm in your own words. But since many programmers do already think in an algorithmic way, I don't think it is very valuable.
Since I'm now using the 100% OOP language called C# I'll be creating 'Use Cases' and 'UML diagrams', but not too much pseudocode or flowcharts. They are antiquated!
You are using UML? I also use UML, though I program in C++. Not pure OOP, but for electronics it's better than C# or Java.
What kind of elements of UML do you use most? I often only use the class diagrams, state diagrams and sequence diagrams.
Geez, I dunno about you guys, but if you ask me... the REAL purpose of pseudocode is so that you have something to do on your notepad during class.
And drawing pictures counts as pseudocode too, so nyeh.
Callou collei we'll code the way
Of prime numbers and pings!
Those and Use Cases. They are the main UML diagrams although there are others. I have the Booch/Rumbaugh manuals. Also, I strongly disagree that C# will not be utilized for embedded systems. For one thing I noticed that Windows CE.NET is now available.What kind of elements of UML do you use most? I often only use the class diagrams, state diagrams and sequence diagrams.
>>I'm surprised & happy to know that such a senior member like you is getting something to learn from the board. I'm inspired.<<
Well I've never had a school course in anything but VB (urgh, I still get sick remembering I took that...I feel dirty...must...get...clean!). They don't exactly teach you anything useful like pseudo-code in a VB course...but thanks.
i tried using pseudocode in the first couple of months of learning to program but i found it a bit too simplistic and something that i wrote in pseudo code would then need to be completely reworked in the actual program as it didnt work in reality.
I think if you use it or not is often according to if you have had a formal education in c/pascal etc etc programming. People who have learned programming at school/university etc may use it more as they began learning to code by using it. Those of us without a formal programming background therefore 'wing it'
Do not meddle in the ways of dragons, for thou art crunchy and taste good with ketchup
When you start OOP, try Use Cases and UML. Their utility is much clearer but they are not useful for procedural languages like C although perhaps the Use Case is, but not the UML diagrams.
I guess the starter will be encourage to rephrase his question.
The perspective of the question was to have some preparation before doing code. For C it's pseudocode even for C++..(if not a huge where OO is not involved). But when OOP.. ?
What is OOP? where concept is the main stream. As I have leaned for last 8 months almost all are theories on .................................................. ...................................
Methodologies for object-orientation
Requirements modeling
Finding candidate objects
Candidate objects- Modeling heuristics
Objects: state,behavior,life-cycle,identity
Preparing Data Dictionary
Object modeling & CRC analysis
Objects, messages and methods-the object/message paradigm
Attributes values and domains
Attributes values and domains- modeling heuristics
Class- class versus instance methods and attributes
Class- general UML notation
Classes- modeling heuristics
Associations- modeling heuristics
Aggregations- modeling heuristics
Constraints- modeling heuristics
Inheritance- modeling heuristics
Abstract versus concrete classes
Single versus multiple inheritance
Extension versus restriction inheritance
Inheritance- general UML notation
Inheritance patterns- dimensions
CRC analysis
Responsibility analysis
Collaborations
Collaborations graphs
Dynamic modeling-topics
Messages and responses
Message Sequence Diagrams
State transition diagrams
Relation sequence diagrams
Relation dynamic model/CRC Cards
And .........................................
Design Activities
System design
Technical architecture
Application architecture
Weak coupling- information hiding
Client-server versus peer-to-peer
Layered Construction
Metrics about structure and size of a class
Tree impurity
Yin and Winchester design measure
Shepperd's refinement of the Henry-Kafura measure
Fenton's global coupling measure
Application architecture - frameworks
CommonPoint (Taligent)
The Model-View-Controller framework
Application architecture - design patterns
Design patterns
Design patterns Vs Frameworks
Representing associations
Representing Constraints
Representing Inheritance
Derived data policy
Add redundant associations
Eliminate associations
Rearrange computation
Persistence
Detailed CRC Cards
.................. What all things.
All I have got is that the preparation to sit for doing code.
When you got a CRC Card.. does anyone think that pseudocode is comparable with it?
Here the starter asked for non OO programming or small application programming or problem solving or function level where target is code < 500 lines. (As I have understood)
[ Never code before desk work ]
-------------------------------------:-->
A man who fears Nothing is the man who Loves Nothing
If you Love Nothing, what joy is there in your life.
=------------------------------------------------------= - I may be wrong.
>Geez, I dunno about you guys, but if you ask me... the REAL
>purpose of pseudocode is so that you have something to do on
>your notepad during class.
:-)
Besides to me pseudocode and the use of diagrams isn't the same. However, UML is a language just as natural language is. Then diagrams are also pseudocode. Well, isn't everybody doing pseudocode then?
>When you start OOP, try Use Cases and UML. Their utility is >much clearer but they are not useful for procedural languages >like C although perhaps the Use Case is, but not the UML >diagrams.
Well, some UML diagrams are very useful in procedural languages. The state diagrams and sequence diagrams for example.
Someone set an expiration date for this poll and close the thread. Someone has bumped it with a vote...
