Difference between Top down and bottom up Design?

Top down design proceeds from the abstract entity to get to the concrete design. Bottom up design proceeds from the concrete design to get to the abstract entity. Top down design is most often used in designing brand new systems, while bottom up design is sometimes used when one is reverse engineering a design; i.e. when one is trying to figure out what somebody else designed in an existing system. Bottom up design begins the design with the lowest levelmodules or subsystems, and progresses upward to the main program, module, or subsystem. With bottom up design, a structure chart is necessary to determine the order of execution, and the development of drivers is necessary to complete the bottom up approach. Top down design, on the other hand, begins the design with the main or top-level module, and progresses downward to the lowest level modules or subsystems. Real life sometimes is a combination of top down design and bottom up design. For instance, data modeling sessions tend to be iterative, bouncing back and forth between top down and bottom up modes, as the need arises.

What is the difference between high level language and low level language(computer languages)? High level languages allow much more abstraction than low level languages. This allows algorithms and functions to be written without requiring detailed knowledge of the hardware used in the computing platform. The compiler provides this interface transparently for the programmer. Low level languages will require more involvement with the actual register and interrupt interfaces to the hardware. This can provide more control and efficiency for the program and can be good for applications which need high speed execution, but high level compilers are much better at optimizing for speed now. Examples of high level languages include C, C++, Java, etc. Examples of low level languages include machine language specific to each processor and assembly language specific to each processor. Difference between compiler interpreter assembler? Compiler -- reads human-readable source code, produces machine-executable binary code. Examples are C, COBOL, Java, etc. Easiest for humans to program, but does not always produce the most efficient executables. Interpreter -- Reads human-readable code, line at a time, and produces and

executes machine instructions "on the fly". Example is good old BASIC. Good for testing, but is VERY slow. Assembler -- Converts machine-manipulation coding directly into binary machine instructions. Produces the most efficient executables, but is the most difficult (for humans) to work with. Differentiate between a source code and an object code? Answer: Source code is code written in a programming language, such as C++ or Java. It is designed to be architecture-independent and human-readable. Source code must be converted to object code (aka machine code) before it can be executed. Object code is architecture-dependent and is not easily human-readable (think ones and zeros). The point of this setup is that you can ensure that code you write in a programming language (source code) can be executed on ANY architecture that has a proper compiler. Executable file An executable file is a file that is used to perform various functions or operations on a computer. Unlike a data file, an executable file cannot generally be read because it has been compiled. On an IBM compatible computer, common executable files are .BAT, .COM, .EXE, and .BIN. Depending on the operating system and its setup, there can also be several other executable files. Additional information and listings of file extensions can be found here. To execute a file in MS-DOS and numerous other command line operating systems, type the name of the executable file and press enter. Other command line operating systems such as Linux or Unix may require the user to type a period and a forward slash in front of the file name, for example ./myfile would execute the executable file named myfile. To execute a file in Microsoft Windows double-click the file. To execute a file in other GUI operating systems commonly a single or double-click will execute the file.