CREATING STANDARDS AND PROCESSES

  1. Have team documentation standards.

  2. Have team coding standards (see the Microsoft .NET Design Guidelines):

    • Use Pascal case for class names, enumerations, events, custom exceptions, interfaces, namespaces, method names, and properties.

    • Use camel case for parameters and private variables.

    • No Hungarian notation (variable prefixes that identify scope and data type).

    • For custom exceptions, inherit from ApplicationException and always use "Exception" as the suffix.

    • Consider standard patterns such as Finalize and Dispose, Callback, or Timeout.

    • Be aware of security when designing classes.

  3. Have standards for code reviews.

  4. Have user interface (UI) standards, and consider needs for accessibility.

  5. Have standards for testing.

  6. Establish a testing process, which will probably include unit testing (low-level functional), assembly testing, QA testing, and load testing.

  7. Have a process for reviewing (and approving) documentation.

  8. Have a process for reviewing (and approving) code.

  9. Have a well-defined, stable build process.

  10. Use a source code repository to facilitate team development and avoid overwriting another's work.

  11. Have a change management process that is facilitated by clear requirements.

  12. Consider Enterprise Templates when some team members are new to the .NET language being used or when you want to pass on knowledge. Templates enable you to include "starter" code, exclude unused or confusing IDE features, and provide custom help inside the IDE.

  13. Make sure you understand the ROI of any solution you propose:

    graphics/fminf01.gif



Analyzing Requirements and Defining. Net Solution Architectures (Exam 70-300)
MCSD Self-Paced Training Kit: Analyzing Requirements and Defining Microsoft .NET Solution Architectures, Exam 70-300: Analyzing Requirements and ... Exam 70-300 (Pro-Certification)
ISBN: 0735618941
EAN: 2147483647
Year: 2006
Pages: 175

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net