PM Architecture
Upcoming SlideShare
Loading in...5
×
 

PM Architecture

on

  • 699 views

Andy Keller and Dave Shepperton, Traction Software. Traction User Group, Oct 14 2010, Newport RI. TUG 2010 Newport slides, agenda and more see www.TractionSoftware.com

Andy Keller and Dave Shepperton, Traction Software. Traction User Group, Oct 14 2010, Newport RI. TUG 2010 Newport slides, agenda and more see www.TractionSoftware.com

Statistics

Views

Total Views
699
Views on SlideShare
699
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

PM Architecture PM Architecture Presentation Transcript

  • PM Architecture
    • Andy Keller Director of Engineering
    Dave Shepperton Senior Software Engineer
  • Two main parts
    • Data model
    • Implementation
    2
  • Data Model: 3 entry types
    • Projects
    • Milestones
    • Tasks
  • Data Model: Spaces vs. Projects
    • In Traction 4.x, we referred to Spaces as Projects
    • The term Project is now used for a set of Tasks and Milestones
    • In the SDK and SDL:
      • Project is still used for Space
      • Goal is used for Project – to avoid confusion ;-)
  • Data model: Projects
    • Normal Entry
      • Title, Body, Author, Tags, Attachments, Comments, etc.
    • Additional Metadata
      • Due Date
      • Owners
      • Members
      • Status
    • Associated Entries
      • Has Milestones
      • Has Tasks
  • Data model: Milestones
    • Normal Entry
      • Title, Body, Author, Tags, Attachments, Comments, etc.
    • Additional Metadata
      • Due Date
      • Status
    • Associated Entries
      • Has Tasks
      • May belong to a Project
  • Data model: Tasks
    • Normal Entry
      • Title, Body, Author, Tags, Attachments, Comments, etc.
    • Additional Metadata
      • Due Date, Start Date
      • Status, Priority
      • Assignees
      • Estimate, Duration
    • Associated Entries
      • May belong to a Project
      • May be associated with a Milestone, which provides a default Due Date
  • Entry Labels: used for PM Task Project Milestone Milestones have Project Tasks have Project and Milestone
  • Data model: Task associations
    • Task
    • Task associated with a Milestone
    • Task in a Project
    • Task in a Project and Milestone
  • Data model: Relationships
    • Tasks can belong to a project and assigned a milestone (optional)
    • Milestones can belong to a project (optional)
    • Tasks, milestones, and projects can all have a due date and other metadata
  • Implementation
    • Indexes task metadata in a database
    • Uses new features of the Traction SDK
      • Custom entry types
      • Entry decorators
      • Entry labels
      • XML Forms
  • JavaDB for the index
    • Content is stored in Traction as Entries
      • Title and description
      • Labels
      • Entry properties
    • Indexed in the DB
      • Simple SQL queries
      • Sorting, totals, etc.
  • Pipeline
    • Custom forms
    • Content stored in the journal
    • Event listener indexes metadata in database
    • db.query tag to query the database
    • db.entries tag turns query results into entries
  • XML Forms
    • Covered this morning in customizing profiles
    • 5 forms
      • taskinline, taskitem, taskdialog
      • milestone
      • goal
  • XML Forms: triggering
    • renders a form inline in the page
    • creates a button to add or edit a form in a dialog
    • fqid= attribute will trigger an edit
  • XML Forms: HTML rendering
    • taskinline and taskdialog use HTML rendering
    • offers more customization of layout, but still using XML controls
  • XML Forms: HTML rendering < gwt.rpc.form > < gwt.rpc.field > Turns an HTML block into a form, replacing fields. Replaced with a control from the schema.