Skip to topic | Skip to bottom
Home
Public


Currently logged in as TWikiGuest?

Public.CodeCompleter1.1 - 30 Jan 2005 - 17:50 - KevinJarnottopic end

Start of topic | Skip to actions

Code Complete

Notes

Chapter 2

  • Fred Brooks' idea to plan to throw first away is not good idea
  • Incremental, or evolutionary approach is much better methodology. Start with basic functionality and build on it over time.
    • This is the basis of the Agile method
  • Another good metaphor is bldg construction

Chapter 3

  • Software development is more than coding
  • Some form of req is necessary for successful project
  • WISCA syndrome - Why Isn't Sam Coding Anything?

Edit drawing `pyramid` (requires a Java 1.1 enabled browser)

  • Architectural components
    • Program organization
    • Major classes
    • Data design
    • Business rules
    • User interface design
    • Resource management
    • Security
    • Performance
    • Scalability
    • Interoperability
    • I18N/L10N
    • Input/output
    • Error processing
    • Fault tolerance
    • Architectural feasibility
    • Overengineering
    • Build vs buy decisions
    • Reuse decisions
    • Change strategy

Chapter 5

  • Desirable characteristics of a design
    • Minimal complexity
    • Ease of maintenance
    • Loose coupling
    • Extensibility
    • Reusability
    • High fan-in
    • Low-to-medium fan-out
    • Portability
    • Leanness
    • Stratification
    • Standard techniques

-- KevinJarnot - 30 Jan 2005
to top

I Attachment sort Action Size Date Who Comment
pyramid.draw manage 1.7 K 30 Jan 2005 - 18:16 KevinJarnot TWiki Draw draw file
pyramid.gif manage 2.1 K 30 Jan 2005 - 18:16 KevinJarnot TWiki Draw GIF file

You are here: Public > CodeComplete

to top

small<    [cached Nov 21 2008 at 17:43:09]>/small<-->

Copyright © 1999-2008 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Jarnot.com Wiki? Send feedback