Software Development Notes
-
Introduction
- An Apology: Whether you're a veteran or a novice webpage builder, this introduction shows how easy it is to underestimate a task -- or should I say "a project?"
-
New Development Note Procedure: The Journal
- New Procedure: A new procedure is in place -- I've decided that I will now begin all development notes in the journal. As they "mature" in terms of their substance as an idea, and in the precision of their (my) writing, I will "promote" them first into the archives, and if they develop fully -- I'll make them full-fledged Software Development Notes on this page.
-
IDEF1X Notation Conventions
- Whatever a data modelling approach is chosen, a set of notations and conventions must be used in order for software development team members to be able to communicate the needs of the user community to one-another, to the users, to the detail implementation groups. IDEF1X is one possibility:
- This particular item heading presents no discussion on which methodologies are the more appropriate, nor recommendations on which (I feel) should be applied once give the project characteristics or circumstances. This section only presents conventional symbology for reference.
- These diagrams were passed around in the SBIS program; They were originally from an IDEF methodology textbook. If anyone knows how to properly document this source, let me know and I'll give credit where it is due.
- Some people today may be more familiar with UML, but this approach has been in greater use for stable or less volatile structures as one finds in database constructs.
-
An Outline of Scott Meyers' book, Effective C++
- An Outline/Summary: Scott Meyers makes sure intermediate students stay on the right path to C++ wizardry. He supplies ``50 Specific Ways to Improve Your Programs and Designs.'' If you want a beginner's text, my suggestion would be to check out Jesse Liberty's work.
That's all I have for now . . .
<=Back to Ernie's Place=>
This page hosted by
Get your own Free Home Page