CIS 524 Week 5 Discussion 2 – Developing Commands

“Developing Commands” Please respond to the following:

You have just finished reviewing a design project your team has submitted to you and noticed that the team members used a great deal of command abbreviations. Explain to your team the value of using abbreviations for commands and give them at least two advantages and disadvantages associated with using abbreviations. Support your answer.

Some commands and command keywords may be specified with just a few characters. Abbreviation parameters differ depending on which command line or programming language you are using. The most obvious advantage of using command abbreviation is that it saves time and reduces input errors. Clearly, the longer the command name, the longer it takes to type. This time is probably minimal for just a single command, but ads up the times for hundreds of commands a day and you will have a substantial chunk of time (Turull, 2003). Since the commands are shorter, simple logic dictates that there is a minimal chance of mistyping, especially when the programmer is familiar with the command abbreviations. Here is a comparison of an SQL expression with and without abbreviations:

Spelled out: var productNames = from product in products select product.ProductName;
Abbreviated: var productNames = from p in products select p.ProductName;

The main an most obvious disadvantages are the fact that the abbreviations needs to be design with good structure, not only for the programmer to learn them, but also so they will be logical representations to the function or command it is invoking. You will not setup a language with abbreviation (give) and attached it to the printing command. A good abbreviation for print will be (prnt). The other disadvantage is that when dealing with scenarios where multiple languages are used, they could be confused or completely misused hence providing errors in execution.

References:

http://search400.techtarget.com/tip/Abbreviated-commands-save-precious-time

From the e-Activity, Amore’s and Quesada’s article discusses the challenges of incorporating Natural Command Language Dialogs (NCLDs) into a phone system. One challenge pertains to sources of conflict in NCLDs. Discuss potential sources of conflict with an interface that you frequently use and devise a solution for preventing the conflicts.

Source of conflict occurs in many interfaces and for different reasons, but the main reason there is conflict when a user is utilizing NCLDs is ignorance. The user does not know exactly what functionality is available, or what commands are associated with them. The most obvious solutions is to provide an outlet were the user can find out such commands, a help menu, or to provide instructions on how to use the system; a how to video or demo.

Recently we bought a new car, and we have never own a car with voice recognition in the wheel. You can make calls; change the radio, read text messages from your phone and many other perks that I was not familiar with. The initial source of conflict was for the system to recognize my speech, my accent and the way to say commands. I have find out, since English is not my first language, that it is hard to interact with this voice recognition interfaces because of this issue. The second source of conflict was with functionality. I had no idea what I could do with the interface and the features or limitations of it. Going to user manual helped me a lot to overcome this particular conflict. The fact that whenever you hit the option on the will it gives you a quick message of what you can say also helped on the learning curve, this is called two way dialogue interactions.

References:

http://www.ling.gu.se/projekt/siridus/Publications/cooperative.pdf

Place an Order

Plagiarism Free!

Scroll to Top