EditAttachWiki Help
r13 - 07 Feb 2006 - 15:27:14 - LisaDusseaultYou are here: OSAF >  Projects Web  >  ProductManagement > DesignOverviewPage > TemplateDesign

Template for Design Overview Pages

Contents

Summary

This page serves as an example of what our Design Overview Pages will look like. Had this been a real Design Overview Page, this Summary section would have given a quick three-sentence description of the topic at hand.

Terminology

Warning: Can't find topic Glossary.Osaf

Warning: Can't find topic Glossary.Chandler

Use Cases

These are just a few example use cases, to give a feel for the topic. This is not meant to be a comprehensive list.

  • Canoga Use Cases
    1. Jotting down a quick note that contains lots of different info
      • for example, "Meet Joe at Freddy's 216-555-1212 -- pick up dry cleaning first"
    2. Delete a Calendar Event

  • Use Cases that are not in scope for Canoga
    1. Turn a Contact into a Calendar Event
    2. Turn a Calendar Event into a Contact

Structure

(Mimi, can you give an example of the type of entry that would go in the structure section here? -- BrianDouglasSkinner - 23 Mar 2004)

Workflows

When Workflow Name Motivation
canoga_in.png Canoga Stamp an item Stamping is a way to provide users with a quick and easy way to mark up their items. It is similar to Flagging in today's PIMs, but we're hoping to improve on current designs in both 1) ease of use and accessibility and 2) depth of functionality.

Narrative

Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd.

Storyboard

When Workflow Name Motivation
canoga_in.png Canoga Moving a stamp Make it easy to...

Narrative

Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd. Sfd afd sdf sd f jlsdfsd jlasdfkjioer f sdfiuoj werj k sfdsd.

Storyboard

Feature List

# When Feature Description
1 canoga_in.png Canoga example feature This is an example of a feature entered in the feature table.
2 canoga_in.png Canoga seond example feature This feature has an associated bugzilla bug, which we're using to track the task of implementing the feature. Here's a link to the bug: Bug 1364
3 canoga_waitlist.png Canoga Waitlist third example feature This feature would be cool to have, but probably won't make it into Canoga.

Open Issues

# Feature Description
1 nested-frobs? We know we'll allow at least a single level of frobs, but should we allow frobs to be nested?
2 bookmarked frobs? Can a user select a frob and bookmark it?

Notes

Contributors

Comments Welcome

Question Reply
ChaoLam, 24 Mar 2004: should the Feature List section precede Workflow? Made sense for CanogaSharingCircleDesign doc I just wrote.  
ChaoLam, 26 Mar 2004: Do you have any proposed policy for the #s associated to feature lists and issues? e.g. is it ok if they aren't numerically ascending? does each row ever change it's #? etc. BrianDouglasSkinner, 28 Mar 2004: My inclination is to use the automatic row numbering feature provided by the EditTablePlugin. The main advantages are (1) it does all the numbering automatically, so it's almost no work, and (2) that way each of the features and open issues has a unique number, so that we can refer to them when we're talking about them. The downside is that EditTablePlugin automatically renumbers the rows whenever you delete rows or move rows around, so we can't count on a line item having the same row number from one week to the next.
ChaoLam, 31 Mar 2004: is there a way to keep the edit table plugin from renumbering items? It's hard to reference items when they are likely to be renumbered. BrianDouglasSkinner, 31 Mar 2004: If we use the automatic numbering feature of the edit table plugin, then it will always automatically renumber, and there's no way to stop it. However, there's no reason that we have to use the automatic numbering feature in the first place. We could just declare that column as a plain old text field rather than an automatic numbering field. Of course, then we have to maintain the line numbers by hand. I'm game either way.
BrianDouglasSkinner, 31 Mar 2004: How do we want to organize all the use cases?  
BrianDouglasSkinner, 31 Mar 2004: How do we want to relate features and workflow to schedule planning?  
BrianDouglasSkinner, 31 Mar 2004: How do we want to organize the ProjectOverviewTable2005 so that it's a useful table of contents that points to these pages?  
BrianDouglasSkinner, 31 Mar 2004: We've talked about different ideas for somehow connecting the dot release specs (like the 0.4 deliverable) to Canoga specs (like the sharing spec). For example, one thing to do would be have the Canoga Sharing spec just be marked up to show what items are scheduled for 0.4  
BrianDouglasSkinner, 31 Mar 2004: Chao and Mimi and Brian also need to get together to go over this material: DesignGroupMeeting20040301  
BrianDouglasSkinner, 31 Mar 2004: Chao and Mimi and Brian also need to get together to go over this material: DesignGroupMeeting20040325  
BrianDouglasSkinner, 13 Apr 2004: Katie, after looking at ItemCollectionDesign, suggests moving the "terminology" section down below the "structure" section. It might also be good to keep the terminology sections shorter than the the one that appears in ItemCollectionDesign. We could do that by having shorter definitions or by fewer terms (include only terms related to the current design, not historical terms).  
BrianDouglasSkinner, 8 Apr 2004: Lisa, after looking at CanogaSharingDesign20040419, suggests that we link the use cases to the workflows. We need to have some persistent way to reference individual use cases and workflows (e.g. have each use case have a unique number like "5", or a simple name like "AGT", or have anchor tags for each use case).  
PageInfo
PageType DesignOverviewPage
MaintainedBy BrianDouglasSkinner
PageStatus Work in progress -- this page is still being drafted? no.png
Trash.CommentsWelcome2 Feel free to contribute comments?, either by adding to the Comments Welcome section of this page, or by posting to the dev list, or by sending mail directly to the person listed as maintaining the page.
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r13 < r12 < r11 < r10 < r9 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.