Computer Programming

Stacks are often implemented using the same node structure as a linked list.

Certainly not, typical Assembly languages are entirely platform-specific.

Some modern Assembly languages, however, are platform independent. Those languages apply not to a particular physical processor or family of processors, but apply to a virtual processor. MSIL, the Microsoft intermediate language, which is at the very core of the .NET system, is such an assembly language.

You can copy data to an Universal Serial Bus Device or USB device. For example Pen Drives or USB hard disks.

to copy photos form a computer to a USB device you must follow the following procedure.

1. Make sure your photo is on the computer. You can download the photo or access it form the drives or camera.

2. Make sure the USB is plugged in.

3. Once the USB is functional ( if the light on the usb device glows) you can right click any file or folder on your computer and use the option send to <USB device Name> and the stuuf you want will be copied to the USB device.

4. Safely remove the device if your task is done.

Let's start with graphs. A graph is a collection of nodes and edges. If you drew a bunch of dots on paper and drew lines between them arbitrarily, you'd have drawn a graph.

A directed acyclic graph is a graph with some restrictions: all the edges are directed (point from one node to another, but not both ways) and the edges don't form cycles (you can't go around in circles forever).

A tree, in turn, is a directed acyclic graph with the condition that every node is accessible from a single root. This means that every node has a "parent" node and 0 or more "child" nodes, except for the root node which has no parent.

A binary tree is a tree with one more restriction: no node may have more than 2 children.

More specific than binary trees are balanced binary trees, and more specific than that, heaps.

A binary tree can be empty ..whereas the general tree cannot be empty

It is file transfer protocol, As a send the file inside the network, One of the oldest of the interner services, file transfer protocol makes it possible to move one or more files securely between computers while providing file security ans organization as well as transfer control.

That you are ineligible for health insurance.

In C, a struct is simply a type that can hold several sub-objects.

In C++, struct is almost the same as "class". It can have member functions, parent structs and classes, etc. The only difference between struct and class is that the members of class are by default private, while the members of struct are by default public. Thus, a standard C struct is also a good C++ struct - simply one that has no member functions and no parents.

1. In a group an individual is accountable and In a Team a team member are accountable.

2. In a team they share leadership roles and in a group the leader is solo.

3. The team discuss , decide and does work together but in a group the leader decide and delegate duties.

4. The team has specific purpose but in a group the purpose is same as organization mission.

5. In a team performance goals are set by the team members and in a group the performance goals are set by others.

6. In a team there is collective work product while in a group is individual work performance.

There are many programming languages all suitable for many purposes. (Except Java, that one is lame)

The largest list of programming languages I could find is at

http://en.wikipedia.org/wiki/Alphabetical_list_of_programming_languages

A programming language is a medium to solve any problem step by step.

Programming languages can be used to create programs that control the behavior of a machine and/or to express algorithms precisely.Programming or coding is a language that is used by operating systems to perform the task.Basically there are two different programming approaches; procedure oriented and object oriented. The procedure oriented programming (POP) approach focuses on creating and ordering procedures or a block of code keeping in mind to accomplish a specific job. The key features of this kind of approach are: use of procedures, sequencing of procedures and sharing global data.However, in case of the object oriented programming (OOP) approach the focus is totally towards identifying objects or data and not on creative activities. Now a days most of the high level programming languages such as Java, C#, C++, and Visual Basic are based on object oriented approach.

Although bubble sort is one of the simplest sorting algorithms to understand and implement, its O(n2)complexity means it is far too inefficient for use on lists having more than a few elements. Even among simple O(n2)sorting algorithms, algorithms like insertion sort are usually considerably more efficient.

C language is developed by Dennis Ritchie at Bell Laboratories in 1972. To know more about C Programming and to learn C Programming from basics to advance with lot of examples visit codeforhunger .

Software design principles represent a set of guidelines that helps us to avoid having a bad design. The design principles are associated to Robert Martin who gathered them in "Agile Software Development: Principles, Patterns, and Practices". According to Robert Martin there are 3 important characteristics of a bad design that should be avoided: * Rigidity - It is hard to change because every change affects too many other parts of the system. * Fragility - When you make a change, unexpected parts of the system break. * Immobility - It is hard to reuse in another application because it cannot be disentangled from the current application. * Software entities like classes, modules and functions should be open for extension but closed for modifications.* High-level modules should not depend on low-level modules. Both should depend on abstractions. * Abstractions should not depend on details. Details should depend on abstractions. * Clients should not be forced to depend upon interfaces that they don't use. * A class should have only one reason to change. * Derived types must be completely substitutable for their base types. * Data design - created by transforming the analysis information model (data dictionary and ERD) into data structures required to implement the software. Part of the data design may occur in conjunction with the design of software architecture. More detailed data design occurs as each software component is designed. * Architectural design - defines the relationships among the major structural elements of the software, the "design patterns" than can be used to achieve the requirements that have been defined for the system, and the constraints that affect the way in which the architectural patterns can be applied. It is derived from the system specification, the analysis model, and the subsystem interactions defined in the analysis model (DFD). * Interface design - describes how the software elements communicate with each other, with other systems, and with human users; the data flow and control flow diagrams provide much of the necessary information required. * Component-level design - created by transforming the structural elements defined by the software architecture into procedural descriptions of software components using information obtained from the process specification (PSPEC), control specification (CSPEC), and state transition diagram (STD). These models collectively form the design model, which is represented diagrammatically as a pyramid structure with data design at the base and component level design at the pinnacle. Note that each level produces its own documentation, which collectively form the design specifications document, along with the guidelines for testing individual modules and the integration of the entire package. Algorithm description and other relevant information may be included as an appendix. In order to evaluate the quality of a design (representation) the criteria for a good design should be established. Such a design should: * exhibit good architectural structure * be modular * contain distinct representations of data, architecture, interfaces, and components (modules) * lead to data structures that are appropriate for the objects to be implemented and be drawn from recognizable design patterns * lead to components that exhibit independent functional characteristics* lead to interfaces that reduce the complexity of connections between modules and with the external environment * be derived using a reputable method that is driven by information obtained during software requirements analysis These criteria are not achieved by chance. The software design process encourages good design through the application of fundamental design principles, systematic methodology and through review.

The main strength is that it gives complete control over the machine at the lowest possible level. The main weakness is that everything must be encoded in terms the machine can understand. For instance, the otherwise simple operation of x = y + z requires that we move the values stored at the addresses identified by y and z into the appropriate CPU user registers, then invoke the appropriate ADD instruction, then move the accumulator register value into the address identified by x. That's a lot of work for an otherwise simple operation.

Before the phone, but after the common use of electricity, the most common method of communication quickly across country was the telegram. Before electricity, smoke signals were used, or sometimes signal flags of some kind.

-23

The data model determines the data structures needed, which in turn influences the data storage requirements. Choosing the correct storage structure will reduce the storage requirements, while choosing in inappropriate structure will increase the requirements pointlessly. When storing a person's age, using 8 bits (0-255) is most likely sufficient: using more bits would be wasteful until humans begin to live longer than 255 years, and using less would risk not being able to accurately represent the person's age.

In computer programming, because space is abundant, but still limited, it is important to choose the data structure that is most suited to the task. Programmers are often given choices as to how they would like to represent a piece of data, and this choice is driven by functionality requirements.

Numeric values, for example, can be stored as binary, binary-coded decimals (BCD), or strings. Storing the number as a string makes it easy for humans to modify the value in a text editor, but uses more storage than BCD. BCD is useful for reading the number in a debugger, because the number appears as a normal decimal number when read in hexadecimal, but is still less efficient than a binary representation in terms of space. Binary numbers are the most efficient with storage usage, but are not easily readable in a memory dump or editing by hand in a text editor.

Often times, programmers will need to choose a data structure that balances between desired functionality and the associated limitations of using that structure. Using ASCII encoded values uses half the space (or less) than some versions of Unicode, but can only display a limited set of characters. This means that a programmer may choose to use ASCII for a primarily Latin-based language audience (English, Spanish, and so on), but may need to choose Unicode for international audiences (Japanese, Chinese, etc).

In linked list if there is no any element inside it than we can say linked list is underflow.

An object is an instance of a class. A class is the broad definition of something, and an object is one particular one of those. In the real world Dog is a class. A particular individual dog is an object. The class defines what a dog is, what characteristics it has, what it can do etc.

In computing you could have a bank account class, defining characteristics and things that you can do with it. It could define that a bank account has an account number, the owner of the account, a balance, a facility to lodge money, a facility to with draw money etc. That is the case for any bank account. Your bank account is an object, an instance of that class. Your account isn't my account, but both of our accounts are objects and have the characteristics as defined by the bank account class.

Memory manager works with pages and segments;these are different things, don't confuse them.

Public Sub Swap()

dim inta as integer

dim intb as integer

dim intc as integer

inta=4

intb=5

intb=inta

intc=intb

inta=intc

End Sub

To explain an object oriented programming with real time examples, try using a packet of sweetener. A packet of sugar has a rectangular shape, made of paper, inked wording and contains something sweet. The same can be said for a packet of Splenda. They both have properties inherited from the abstract packet.

the reason why we translate is that source code may be in assembly( low level language) or high level language and the only language computer understand is 0s and 1s which is binary code so the program written in either assembly or high level language must be convert or translate to binary and program written in HLL are in English form while the assembly are equivalent machine language.