|
Pro .NET 2.0 Code and Design Standards in C# PDF Download
This is not an e-book that tells you what you should or shouldn’t do! Yes, it is a e-book on standards, but the standards are not presented as a set of rules; rather, they are presented and explained as
a catalog of standard practices that are commonplace in the development community. My job
is to bring them to your attention, and it’s your choice whether you use them.
Generally, there are two categories of standards: internal and external. Internal standards
are those standards that are in-house standards, whereas external standards are standards
that are used between organizations to standardize a selection of industry practices (e.g.,
IEEE-1016 documentation for software design or IEEE-830 software requirements standard).
There are two leading organizations that develop external standards relevant to architects
and developers: IEEE and W3C. Whereas IEEE focuses on standards for a wide range of industries, including information technology, W3C has a sharper focus on Internet technology.
Note IEEE-SA is an acronym for Institute of Electrical and Electronics Engineers Standards Association.
The association is the leading developer of international standards for a wide range of industries: information technology, telecommunication, biomedical and health care, and power and energy, for example.
W3C is an acronym for the World Wide Web Consortium, which develops products and standards on Internet technology (e.g., HTML, XML, and Encryption).
This e-book is about internal standards only. Its role is to present to you a catalog of standards that are understood to be in the public domain and free to use and specialize for your situation. Standards have been categorized as code, design, and patterns. Code standards discuss policy, structure, development, and documentation of code. Design standards discuss code design from a policy, structure, development, and documentation perspective. Finally, pattern standards discuss a subset of the design patterns catalogued by Drs. Gamma, Helm, Johnson, and Vlissides (known as the “Gang of Four,” or “GoF”). It also acknowledges the contribution to the pattern community by Professor Alexander, Professor Reenskaug, and GoF.
The Motivation: Why Do We Need Standards?
There are three key reasons to use standards: success, uniformity, and transparency. First, in an industry as volatile as information technology, if a given code or design practice lasts for a few seasons, then it tends to do so because it is successful. However, that success does not mean that the given practice is the only way to do a given task; often, there are successful alternatives.
By and large, the community tends to make standards out of practices that they know
are effective, efficient, and intuitive, and, in the main, disregard practices that may be the ideal
but that are complex or unintuitive. Second, by using a standard, an organization can design
and develop with uniformity. Conforming to a uniform way of designing and coding applications minimizes risks and problems associated with application architects and developers switching projects, for example. Third, standards offer transparency: that assists governance by making clear how design and code are developed in an organization.
The Choice of Standards
A common problem with wanting to follow standards is trying to find them! Although there are organizations that offer standards and there are also a few e-books that discuss best practices, they tend to specialize or generalize or theorize or in the case of an organization take years to formally approve a standard—which is cool, when that is what you want. However, if you are time-poor and need to put together an in-house standard for C# development, then you would experience problems. So, this e-book does the work for you by cataloging a set of standards that are common to the C# community and broad in scope: code, design, and design pattern standards.
Code and design standards are presented from two perspectives: pure (policy) and
applied (structure and development). The pure and applied perspectives of code and design
merge in the presentation of design patterns. I am conscious that for you to adopt any standard, you will want to be convinced of its merit. So, rather than state the standard and give a quick example, I have prepared the standards in a common format that makes it easy for you to see if it is what you want, for your situation.
The Format of the Standards
The standards are presented using an intuitive format that has four sections: What, Where,
Why, and How. The What section identifies what the standard is; the Where section identifies
where to use it; the Why section identifies the motivation for using it; and the How section
identifies how to use it.
How to Use the Standards
The standards may be used in several ways, principally in the following manner: (1) as in-house team standards; (2) as a template to develop in-house team standards; (3) by professionals wanting to reference community standards; and (4) by students wanting to adopt community standards in preparation for a career as a developer or application architect.
In addition to the introduction of each standard, there is a short statement that acknowledges
its use in the community—for example: “The standard acknowledges . . .” Note that the
statement does not begin with “The standard recommends . . .” It is not the intention of this
e-book to make recommendations; as previously mentioned, the e-book is simply a catalog of standards. Determining the appropriate standard for your situation is for you to judge; you
know your circumstance. The choice is yours! However, only standards that are understood to be accepted and in common use have been included.
 |
Available Options: for Pro .NET 2.0 Code and Design Standards in C# PDF Download |
 |
Click the images to enlarge |
| CDR Media: |
|
| Download File: |
|
|
|
Main Categories
