Many organizations are moving towards “diskless client” systems - what are the g

Question

Many organizations are moving towards “diskless client” systems - what are the general advantages and disadvantages? Consider the following scenarios and then discuss whether diskless is a good idea or not (your defense is important)

a. Regular business office users

b. Uses are engineers utilizing high-end graphics programs (AutoCAD, etc.)

c. Programmers/Programming team designing applications for the system

d. High speed, real-time requirement users that are always reading/writing/processing data from central database.

Explanation / Answer

Perhaps one of the most influential aids to understanding the logical flow of an application is how the various elements of the application are named. A name should tell "what" rather than "how." By avoiding names that expose the underlying implementation, which can change, you preserve a layer of abstraction that simplifies the complexity. For example, you could use GetNextStudent() instead of GetNextArrayElement().

A tenet of naming is that difficulty in selecting a proper name may indicate that you need to further analyze or define the purpose of an item. Make names long enough to be meaningful but short enough to avoid being wordy. Programmatically, a unique name serves only to differentiate one item from another. Expressive names function as an aid to the human reader; therefore, it makes sense to provide a name that the human reader can comprehend. However, be certain that the names chosen are in compliance with the applicable language's rules and standards.

Following are recommended naming techniques:

Routines

Variables

Tables

Microsoft SQL Server

Miscellaneous

Related Questions

Navigate

• Browse (All)
• Browse M
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.