When creating a computer program, what is the process i need to do before i start to code? - unix covering letter
Recently, the program has started with Unix and Java, but they told me my programs are everywhere, and I think that starts on the process before encoding. Do you have any advice or information about the processes which must be met before the scheduled start to build a program?
Tuesday, December 15, 2009
Unix Covering Letter When Creating A Computer Program, What Is The Process I Need To Do Before I Start To Code?
9 comments:
Learning to write "pseudo". Basically, write the steps that your code is implemented in plain English and use them as comments in the code.
According to this refined and you are satisfied with the whole process, start to plug the gaps with the code.
Also pay attention to how the structure of nested loops code.Not. Sensible names. With reusable functions
Note that a person must be able to read and understand the code, without any information about them.
Open coding a program such as Java or C + +. then u'll have to define values
For example, Sun answer1 as an integer
Further design analysis - Read more about UML.
Analysis:
The purpose of this program
Target Group - Ask questions, identify key issues and concepts, diagrams, use case, etc.
Design
Class diagrams, sequence diagrams, flowcharts simple, etc.
The re-use of utensils, keep it simple.
Plan on paper, with a natural language or pseudo code. Organization helps sometimes.
Write to perform in small modules or sub-routines that a particular task. This makes your code more readable and reusable.
Comments on the document code and thought processes. What you can not today so obviously blatent later.
How to wear any other kind of responsibility, breaks down. Walking back from the keyboard. Know your limits.
Above all ... Have fun.
Plan on paper, with a natural language or pseudo code. Organization helps sometimes.
Write to perform in small modules or sub-routines that a particular task. This makes your code more readable and reusable.
Comments on the document code and thought processes. What you can not today so obviously blatent later.
How to wear any other kind of responsibility, breaks down. Walking back from the keyboard. Know your limits.
Above all ... Have fun.
There are two methods that you should consider are the following:
Top-down and
Bottom-Up
You need top-down --
Basically, write in English what you want the program to do. Then you decide which bits in small "programs" that can carry out routine operations and provide information to other "PRGRAM can be divided"
Then write in English, so that each small These programs, then the name of each of the smaller programs, once the name we call them modules.
Then, if you know what and how the program trying to work here to begin for each module code. Focus on form and ignore the rest of the program on time and with the module steps until you in English translated into the code
You should try to make the code modular as possible, special functions / subroutines (or whatever) are referred to them in Java in order to fulfill certain tasks. Then add comments explaining each function, what it does. Try them individually and take the key code as simple as possible) (all bits of complicated functions.
In terms of planning, just think what you do and how they are in specific roles.
Do not go crazy with the planning, but if you show a proposal to your boss before you need to start.
It starts with a high-level design.
in solving their entrances and exits before them everywhere.
Be postponed until after their work at the interfaces of the report in order to interact with the flow of the document and how to control the data. Then you can define the process, then you can encode.
For coding professional, you should have all the interfaces, flow, data sets and procedures of the verbiage "paper" before you go anywhere near the computer. It's almost like the code because it requires little attention has been broken down into simple steps in the design of the structure.
It starts with a high-level design.
in solving their entrances and exits before them everywhere.
Be postponed until after their work at the interfaces of the report in order to interact with the flow of the document and how to control the data. Then you can define the process, then you can encode.
For coding professional, you should have all the interfaces, flow, data sets and procedures of the verbiage "paper" before you go anywhere near the computer. It's almost like the code because it requires little attention has been broken down into simple steps in the design of the structure.
Post a Comment