Computer Programming

Use single subscripted array(s) to solve the following problem. A company pays its sales people on a commission basis. The salespeople receive $200 per week plus 9 percent of their gross sales for that week. For example, a salesperson who grosses $3000 in sales in a week receives $200 plus 9% of $3000, or a total of $470. Design a program (using an array of counters) that determines how many of the salespeople earned salaries in each of the following ranges.

• $200-$299
• $300-$399
• $400-$499
• $500-$599
• $600-$699
• $700-$799
• $800-$899
• $900-$999
• $1000 and over

Use the %X modifier of printf.

Documentation

· Software documentation or source code documentation is written text that accompanies computer software.

· It either explains how it operates or how to use it, and may mean different things to people in different roles.

1. Requirements - Statements that identify attributes, capabilities, characteristics, or qualities of a system. This is the foundation for what shall be or has been implemented.

2. Architecture/Design - Overview of software. Includes relations to an environment and construction principles to be used in design of software components.

3. Technical - Documentation of code, algorithms, interfaces, and APIs.

4. End User - Manuals for the end-user, system administrators and support staff.

5. Marketing - How to market the product and analysis of the market demand.

A very important part of the design document in enterprise software development is the Database Design Document (DDD). It contains Conceptual, Logical, and Physical Design Elements. The DDD includes the formal information that the people who interact with the database need. The purpose of preparing it is to create a common source to be used by all players within the scene. The potential users are:

Database Designer;Database Developer;Database Administrator;Application Designer;Application Developer

When talking about Relational Database Systems, the document should include following parts:

· Entity - Relationship Schema (enhanced or not), including following information and their clear definitions:

o Entity Sets and their attributes

o Relationships and their attributes

o Candidate keys for each entity set

o Attribute and Tuple based constraints

· Relational Schema, including following information:

o Tables, Attributes, and their properties

o Views

o Constraints such as primary keys, foreign keys,

o Cardinality of referential constraints

o Cascading Policy for referential constraints

o Primary keys

Technical documentation

This is what most programmers mean when using the term software documentation. When creating software, code alone is insufficient. There must be some text along with it to describe various aspects of its intended operation. It is important for the code documents to be thorough, but not so verbose that it becomes difficult to maintain them. Several How-to and overview documentation are found specific to the software application or software product being documented by API Writers. This documentation may be used by developers, testers and also the end customers or clients using this software application. Today, we see lot of high end applications in the field of power, energy, transportation, networks, aerospace, safety, security, industry automation and a variety of other domains. Technical documentation has become important within such organizations as the basic and advanced level of information may change over a period of time with architecture changes. Hence, technical documentation has gained lot of importance in recent times, especially in the software field.

Often, tools such as Doxygen, NDoc, javadoc, EiffelStudio, Sandcastle, ROBODoc, POD, TwinText, or Universal Report can be used to auto-generate the code documents-that is, they extract the comments and software contracts, where available, from the source code and create reference manuals in such forms as text or HTML files. Code documents are often organized into a reference guide style, allowing a programmer to quickly look up an arbitrary function or class.

The idea of auto-generating documentation is attractive to programmers for various reasons. For example, because it is extracted from the source code itself (for example, through comments), the programmer can write it while referring to the code, and use the same tools used to create the source code to make the documentation. This makes it much easier to keep the documentation up-to-date.

In the case of a software library, the code documents and user documents could be effectively equivalent and are worth conjoining, but for a general application this is not often true.

Typically, the user documentation describes each feature of the program, and assists the user in realizing these features. A good user document can also go so far as to provide thorough troubleshooting assistance. It is very important for user documents to not be confusing, and for them to be up to date. User documents need not be organized in any particular way, but it is very important for them to have a through index. Consistency and simplicity are also very valuable. User documentation is considered to constitute a contract specifying what the software will do. API Writers are very well accomplished towards writing good user documents as they would be well aware of the software architecture and programming techniques used. See also Technical Writing.

There are three broad ways in which user documentation can be organized.

1. Tutorial: A tutorial approach is considered the most useful for a new user, in which they are guided through each step of accomplishing particular tasks.[1]

2. Thematic: A thematic approach, where chapters or sections concentrate on one particular area of interest, is of more general use to an intermediate user. Some authors prefer to convey their ideas through a knowledge based article to facilitating the user needs. This approach is usually practiced by a dynamic industry, such as Information technology, where the user population is largely correlated with the troubleshooting demands [2]

3. List or Reference: The final type of organizing principle is one in which commands or tasks are simply listed alphabetically or logically grouped, often via cross-referenced indexes. This latter approach is of greater use to advanced users who know exactly what sort of information they are looking for.

1. To excite the potential user about the product and instill in them a desire for becoming more involved with it.

2. To inform them about what exactly the product does, so that their expectations are in line with what they will be receiving.

3. To explain the position of this product with respect to other alternatives.

One good marketing technique is to provide clear and memorable catch phrases that exemplify the point we wish to convey, and also emphasize the interoperability of the program with anything else provided by the manufacturer.

We use Artificial Intelligence, or, AI, for multiple reasons. If we can find out more of AI, we could make a machine that could help us better in science and benefit the world.

• Robots are still under development, and even though we have come close at times to a sufficiently working AI, it has yet to succeed, due to the sheer fact that we can learn over time, and do trial and error. Robots, in a sense, unless we create them that way, can not. They could either not learn from doing something like, if we pushed someone, they'll push him back, (if we did a robot-on-robot) but he won't learn to stop. That's the hardest part.
• We use AIs to better our knowledge. Think about N.A.S.A. We didn't have to go to the moon, or even send satellites out there. But we did. Many people disagree with N.A.S.A. and their actions. If they knew how much things actually is in relationship with N.A.S.A., perhaps their view would change. For example, without N.A.S.A., we wouldn't have been able to use a G.P.S. or cell phones. That's a bit off topic, though, who knows, AIs might lead us to an even greater invention!

#include

#include

#include

void main()

{

int gd=DETECT,gm=4,i;

initgraph(&gd,&gm,"c:\\tc\\bgi");

setcolor(3);

for(i=0;i<150;i+=5)

{

circle(300,300,i);

}

getch();

}

You don't need to physically convert the array, you simply need to point at the first element and read the elements sequentially. The following code shows how to achieve this, as well as how to physically convert a 2D array to a separate 1D array. As can be seen, there is no practical benefit to making the conversion.

Example

#include

int main()

{

const int rows = 2;

const int cols = 3;

const int size = rows * cols;

// Create a static 2D array, intialise and print the matrix

int arr2[rows][cols];

std::cout << "2D array:\n" << std::endl;

for( int r=0; r

{

for( int c=0; c

{

arr2[r][c]= (r+1) * (c+1);

std::cout << arr2[r][c] << " ";

}

std::cout << std::endl;

}

std::cout << std::endl;

// Efficient conversion to 1D array:

// Point to the first element then print sequential values.

int* ptr = (int*) arr2;

std::cout << "1D array (using pointer):\n" << std::endl;

for( int i=0; i

std::cout << *ptr++ << " ";

std::cout << "\n" << std::endl;

// Inefficient conversion to 1D array:

// Copy the 2D array to a separate 1D array

int arr1[size];

ptr = (int*) arr2;

for( int i=0; i

arr1[i]=*ptr++;

// Print the copy:

std::cout << "1D array (using copy):\n" << std::endl;

for( int i=0; i

std::cout << arr1[i] << " ";

std::cout << "\n" << std::endl;

return( 0 );

}

Output

2D array:

1 2 3

2 4 6

1D array (using pointer):

1 2 3 2 4 6

1D array (using copy):

1 2 3 2 4 6

The formula for the Fibonacci series is

Fn = Fn-1 + Fn-2 for n ≥ 2 with F0 = 0 and F1 = 1.

In layman's terms, in the Fibonacci series each successive number is the sum of the previous two numbers, starting with 1. So we have 0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55 etc

To do this in Java or any computer program you will need to create a recursive program, one that picks up previous values. This is quite easy, even for a beginner, once one grasps the Fibonacci fundamentals. Here is an example in Java:

public class Fibonacci {

public static long fib(int n) {

if (n <= 1) return n;

else return fib(n-1) + fib(n-2);

}

public static void main(String[] args) {

int N = Integer.parseInt(args[0]);

for (int i = 1; i <= N; i++)

System.out.println(i + ": " + fib(i));

}

}

For n, enter the number of values required, otherwise the increasing values of the results will overflow the parameters of the data display!

This code can be adapted for any progamming language, e.g. pascal, basic etc. One can even use the principles to construct a spreadsheet that will show the Fibonacci series in successive rows in Excel, for example.

• For more information, enhanced development and downloadable Java code for generating Fibonacci numbers, see 'Related links' below this box

Java is a OOP language and it is not a pure Object Based Programming Language.

Many languages are Object Oriented. There are seven qualities to be satisfied for a programming language to be pure Object Oriented. They are:

1. Encapsulation/Data Hiding
2. Inheritance
3. Polymorphism
4. Abstraction
5. All predefined types are objects
6. All operations are performed by sending messages to objects
7. All user defined types are objects.

Java is not because it supports Primitive datatype such as int, byte, long... etc, to be used, which are not objects.

Contrast with a pure OOP language like Smalltalk, where there are no primitive types, and boolean, int and methods are all objects.