r4 - 15 Mar 2007 - 22:14:50 - PriscillaChungYou are here: OSAF >  Journal Web  >  ContributorNotes > PriscillaChungNotes > DesignProcessTerminology

Design Process Terminology

In regards to terminology thrown around during the design process, I'm compling a list to refer back to when writing documentation.

  • "take it or leave it" - In order to work on some visual explorations, time may not allow for a proper "look and feel" review. So this line will be used when design needs to meet immediate needs in a low impact way.

  • "data availablity" - What you see is what you get. This was used in the Scooby project planning. Functionality in the early release of Scooby that has not met target users release.


Ways in which to prioritze features

Must have, should have, could haves.

  • Must have - must complete all of these features for the release to achieve it's goals
  • Should have - feature that should be worked on if time allows in the schedule
  • Could have - not hard to do, time allows, this would be a 'nice to have'.

P1 to P5

Must haves

  • P1 - enhancement directly affects the stability or performance of the product
  • P2 - enhancement dramatically improves the usability or capability of the product

Should haves

  • P3 - enhancement necessary long term or intermediate term for the product to be successful

Nice to haves

  • P4 - enhancement provides benefits but doesn't necessarily add value to the product
  • P5 - enhancement people want to do, but debatable value (not important until the product is well established)


Definition for Cosmo Target Users:

Applications Manager: Concerned with making sure the application works right for people in a functional sense, and performs management/administrative tasks. For example: managing users, assigning permissions, resetting passwords, looking at signup dates, etc. Service realm and client in using Cosmo.

Systems Administrator: Concerned with maintaining servers and installing cosmo at multiple servers. For example: making sure the server is responsive, that somebody can log into the UI, keeping the software running, that the version of the server which he sees running is the correct one, configuring it to operate in his specific environment, etc.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r4 < r3 < r2 < r1 | 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.