Changes between Version 15 and Version 16 of PLATFORM_STANDARDS_DESIGN


Ignore:
Timestamp:
01/16/09 00:53:22 (16 years ago)
Author:
pap
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PLATFORM_STANDARDS_DESIGN

    v15 v16  
    3333 * A good design should point out what classes/methods should be created. If you use the pro-lib you should say what kind of property you would use. --pap@2009-01-15 
    3434 * Also I'd like to note that a reminder of the '''Work towards the goal. ''' rule should be added to every standard.  --pap@2009-01-15 
     35 * Perhaps it wont be bad to give a link to some good articles about TDD because it sounds frightening when it is first met. --pap@2009-01-15 
     36 * It should be noted that our design relies heavily on the properties library and so generally of our classes should be either !ProObjects or immutable. And that !ProObjects should have only properties or static final fileds.  --pap@2009-01-15 
     37 * Document's design should point the general layout structure of the documents. --pap@2009-01-15 
     38 * Maintenance design should point which parts need maintaining. If it is aboud some documents then these would be the paragraphs and so on. --pap@2009-01-15 
     39 * Setup design should link to tutorials that should be used for making the setup. --pap@2009-01-15 
     40 * UML Diagrams and reqired libraries sound strange for a bugfix.  --pap@2009-01-15