Lecture #23 - System Structure

Repository Concept:

• Control current baseline
• manage package dependencies where the root of a dependency tree may be:
  • Any component, e.g., System, Program, or Module
  • A "pseudo component", e.g., a parent of all orphans, or all leaves in dependency graph
  • A parent of a namespace.
  • May also be the parent of a category, e.g., reusable, GUI, library, ...
• browse the current baseline
  • queries - show packages owned by some Root, either as a group, or as a sequence that can be browsed, one-at-time.
    • show collections of all Namespaces or all Systems
    • show all packages in Namespace or System or Program or Module
    • show subsets of the above in a time interval, from a specified set of authors, by date of last test, etc.
• disclose state of current baseline
  • Code not passing all tests
  • Code not meeting code standards
  • Open check-ins
  • most volatile modules and packages
    • most volatile testing
    • most volatile check-in of new versions

Critical Issues:

• Concurrent file access
• Ease of use
• Flexibility

Pluggable Policies:

• Ownership
• versioning
• Check-in and Check-out

Agents

• Extracter - support dependency based extraction, only need to cite root file.
• Viewer - support browsing repository, showing descriptions from metadata.
• Dependency Analysis - build metadata from source code using type-based analysis.
• Check-in checker - report open check-ins.
• Test results notifier - report failed tests to all dependers.