Software Code Help - General

The definitive Acronym list

Raj Shekhar — Wed, 20 Jan 2010 05:19:02 GMT

1MW 1 Microsoft Way
1TBS 1 True Brace Style
21D teach yourself ___ in 21 Days
3COM COMputer, COMmunication, COMpatibility
3Dwm 3-Dimensional Window Manager
3G 3rd Generation
3GIO 3rd Generation Input/Output
3GL 3rd Generation Language
3LD 3rd-Level Domain {IANA}
3NF 3rd Normal Form (databases)
3W World Wide Web
4GL 4th Generation Language
4WCD 4 Wire Conditioned Diphase
A/D Analog/Digital
A/UX Apple UniX
A2A Application TO Application
AA Administrative Authority
AA AntiAliasing
AAA Administration, Authorization, and Authentication (security)
AAA Asp Application Aggregator
AAAI American Association for Artificial Inelligence
AAB All-to-All Broadcast
AAC Advanced Audio Coding
AAEPS Anywhere Anytime Email Proxy Server
AAF Advanced Authoring Format
AAL Atm Abstraction Layer
AAMOF As A Matter Of Fact {chat}
AAP Application Access Point
AARP Appletalk Address Resolution Protocol {Apple}
AART Aggregate Average Response Time
AAS All-to-All Scatter
AAS Auto Area Segmentation
AASE Associate Accredited Systems Engineer {Compaq}
AASP Ascii Asynchronous Support Package
AAT Average Access Time
AAUI Apple Attachment Unit Interface {Apple}
ABA Address Book Archive
ABAP Advanced Business Application Programming
ABC A Bit Cypher
ABC Atanasoff-Berry Computer
ABCPP ABC PreProcessor
ABEL Advanced Boolean Expression Language
ABEND ABnormal END
ABGP
ABI Abstract Binary Interface
ABI Adaptive Brain Interface
ABI Application Binary Interface
ABIOS Advanced Basic Input/Output System
ABIST Automatic Built-In Self Test
ABLE Adaptive Battery Life Extender
ABM Anything But Microsoft
ABM Asynchronous Balanced Mode
ABNF Augmented Backus Normal Form
ABNF Augmented Backus-Naur Form
ABR Area Border Router
ABR Auto Band Rate
ABR Available Bit Rate
.
.
.
And retrieve the complete list fromt the attached Word document.

The definitive Acronym list.doc (1.06 MB)

Good General Interview Question.

Raj Shekhar — Mon, 18 Jan 2010 08:35:21 GMT

TYPES OF QUESTIONS

1. Close-ended questions. These questions may sometimes be helpful when an interviewer(s) wants to know certain information at the onset or needs to determine specific kinds of knowledge. Example: "Could you name the five specific applications involved in...?"

2. Probing questions. These questions allow the interviewer(s) to delve deeper for needed information. Example: "Why?", "What caused that to happen?", or "Under what circumstances did that occur?"

3. Hypothetical questions. Hypothetical situations based on specific job-related facts are presented to the applicant for solutions. Example: "What would you do if..", "How would you handle..."

4. Loaded questions. These questions force an applicant to choose between two undesirable alternatives. The most effective way to employ a loaded question is to recall a real-life situation where two divergent approaches were both carefully considered, then frame the situation as a question starting with, "What would be your approach to a situation where...".

5. Leading questions. The interviewer(s) sets up the question so that the applicant provides the desired response. When leading questions are asked, the interviewer cannot hope to learn anything about the applicant.

6. Open-ended questions. These are the most effective questions, yield the greatest amount of information, and allow the applicant latitude in responding. Example: "What did you like about your last job?"

Examples of open-ended effective probing:

1. What are/were the three main responsibilities in your current/last position? Which responsibilities do/did you enjoy the most? Why?

2. Of the three main responsibilities, which do/did you enjoy the least? Why?

3. Describe your supervisor's management style. Did/Do you like his or her style of management? Why or why not?

4. Describe your particular style of management, or the style of management you would choose if you were a manager.

5. In the past have you worked in a team environment or independently? Which did you prefer and why?

6. What amount of hours do you/ did you put in at your current/last position? How did you feel about working those hours?

7. What are three of your strongest work related qualities and how were you able to demonstrate these on your job?

8. What are three areas, with regard to your work, that you would like the opportunity to develop?

9. Why did you/are you leave/leaving your last/present position?

10. Of all the jobs you've held, which one did you like the most and why?

11. What major problems have you encountered so far in your professional life and how did you deal with them?

12. What have you learned from your mistakes?

13. How do you react to pressure?

14. What types of decisions are most difficult for you?

15. How have your prior experiences and education prepared you for this job?

16. What has been your biggest work-related frustration to date? How did you handle the situation?

17. Have you ever supervised anyone in a work setting? Have you ever hired or fired anyone?

18. What experience do you have in this field? How have you prepared yourself to switch fields?

19. How have you influenced productivity and results in your previous work experiences?

20. How have you prepared yourself to assume the challenges of this position?

21. How do your current skills apply to this position?

22. In what ways do you expect your relationships with current peers to change? How will you manage this shift?

Repeated Questions break rehearsed answers

1. What did you like about your previous job/manager?

2. What else did you like about your previous job/manager?

What are the meaning of Conceptual Design, Logical Design and Physical Design?

Raj Shekhar — Thu, 07 Jan 2010 05:54:42 GMT

Conceptual Design

A conceptual design is an abstract or high level design which includes only the most important components and entities. The main goal of a conceptual design is to provide an understandable picture of the overall purpose of the proposed solution. Components may include major technology systems, external systems that are required for integration or overall functionality, high level data flow, and system functionality. Think of this as the "black box" diagram where portions of the diagram may be simply a technology component to-be-named-later but is identified with its role and purpose.

Logical Design

A logical design is a more detailed design which includes all major components and entities plus their relationships. The data flows and connections are detailed in this stage. The target audience is typically developers or other systems architects. However, it is possible to create logical designs for business purposes to ensure that all components and functionality is accounted and well understood. Logical designs do not include physical server names or addresses. They do include any business services, application names and details, and other relevant information for development purposes.

Physical Design

A physical design has all major components and entities identified within specific physical servers and locations or specific software services, objects, or solutions. Include all known details such as operating systems, version numbers, and even patches that are relevant. Any physical constraints or limitations should also be identified within the server components, data flows, or connections. This design usually precludes or may be included and extended by the final implementation team into an implementation design.

How to achieving good coding practices

Raj Shekhar — Thu, 19 Nov 2009 11:36:40 GMT

Here are several techniques for achieving good coding practices that are less heavy-handed than laying down rigid coding standards:

Assign two people to every part of the project

If two people have to work on each line of code, you’ll guarantee that at least two people think it works and is readable. The mechanisms for teaming two people can range from pair programming to mentor-trainee pairs to buddy- system reviews.

Review every line of code

A code review typically involves the programmer and at least two reviewers. That means that at least three people read every line of code. Another name for peer review is “peer pressure.” In addition to providing a safety net in case the original programmer leaves the project, reviews improve code quality because the programmer knows that the code will be read by others. Even if your shop hasn’t created explicit coding standards, reviews provide a subtle way of moving toward a group coding standard—decisions are made by the group during reviews, and, over time, the group will derive its own standards.

Require code sign-offs

In other fields, technical drawings are approved and signed by the managing engineer. The signature means that to the best of the engineer’s knowledge, the drawings are technically competent and error-free. Some companies treat code the same way. Before code is considered to be complete, senior technical personnel must sign the code listing.

Route good code examples for review

A big part of good management is communicating your objectives clearly. One way to communicate your objectives is to circulate good code to your programmers or post it for public display. In doing so, you provide a clear example of the quality you’re aiming for. Similarly, a coding-standards manual can consist mainly of a set of “best code listings.” Identifying certain listings as “best” sets an example for others to follow. Such a manual is easier to update than an English-language standards manual and effortlessly presents subtleties in coding style that are hard to capture point by point in prose descriptions.

Emphasize that code listings are public assets

Programmers sometimes feel that the code they’ve written is “their code,” as if it were private property. Although it is the result of their work, code is part of the project and should be freely available to anyone else on the project that needs it. It should be seen by others during reviews and maintenance, even if at no other time.

One of the most successful projects ever reported developed 83,000 lines of code in 11 work-years of effort. Only one error that resulted in system failure was detected in the first 13 months of operation. This accomplishment is even more dramatic when you realize that the project was completed in the late 1960s, without online compilation or interactive debugging. Productivity on the project, 7500 lines of code per work-year in the late 1960s, is still impressive by today’s standards. The chief programmer on the project reported that one key to the project’s success was the identification of all computer runs (erroneous and otherwise) as public rather than private assets (Baker and Mills 1973). This idea has extended into modern contexts including Extreme Programming’s idea of collective ownership (Beck 2000), as well as in other contexts.

Reward good code

Use your organization’s reward system to reinforce good coding practices. Keep these considerations in mind as you develop your reinforcement system:

The reward should be something that the programmer wants. (Many programmers find “attaboy” rewards distasteful, especially when they come from nontechnical managers.)
Code that receives an award should be exceptionally good. If you give an award to a programmer everyone else knows does bad work, you look like Charlie Chaplin trying to run a cake factory. It doesn’t matter that the programmer has a cooperative attitude or always comes to work on time. You lose credibility if your reward doesn’t match the technical merits of the situation. If you’re not technically skilled enough to make the good-code judgment, don’t! Don’t make the award at all, or let your team choose the recipient.

One easy standard

If you’re managing a programming project and you have a programming background, an easy and effective technique for eliciting good work is to say “I must be able to read and understand any code written for the project.” That the manager isn’t the hottest technical hotshot can be an advantage in that it may discourage “clever” or tricky code.

Maharshi Dayanand Saraswati University (MDS) Rohtak, online counseling for B.Ed course (http://www.hrybedcounselling2009.nic.in)

Raj Shekhar — Wed, 05 Aug 2009 04:39:02 GMT

Maharshi Dayanand Saraswati University (MDS) Rohtak, online counseling for B.Ed course from 5th August - 17th August 2009 on http://www.hrybedcounselling2009.nic.in/

From 16th August - 19th August 2009, the candidates can download their admission letters and report at the respective allotted colleges for verification of documents and depositing the fees.

MDU Rohtak B.Ed Counselling details are available on MDU Rohtak Website -

http://mdurohtak.com/

Direct Link to MDU Rohtak B.Ed Counselling Details -

http://mdurohtak.com/Site/Details.aspx?pid=H&id=12

HTTP Channel and TCP Channel

Raj Shekhar — Sun, 21 Jun 2009 10:33:06 GMT

HTTP Channel
The HTTP channel transports messages to and from remote objects using the SOAP protocol. All messages are passed through the SOAP formatter, where the message is changed into XML and serialized, and the required SOAP headers are added to the stream. It is also possible to configure the HTTP Channel to use the binary formatter. The resulting data stream is then transported to the target URI using the HTTP protocol.

TCP Channel
The TCP channel uses a binary formatter to serialize all messages to a binary stream and transport the stream to the target URI using the TCP protocol. It is also possible to configure the TCP channel to the SOAP formatter.