FreeMind2HTML Mindmap

Imagemap
ReqsMgmtRequirementsFunctionalSecurityAllows authorized persons to update each ...Meta-dataExternal interfacesLinks to defect management systemLinks to source code management systemAllows requirements to be associated wit ...Provides useful reportsManagementEasy backup of requirements and meta-dat ...Easy export of requirements to various f ...User interfaceWeb interfaceFor entering suggestionsFor entering and working with requiremen ...For viewing reportsSupports a suggestion interfaceAbility to work offlineXML schema for individual requirements a ...Ability to merge a set of requirements f ...Provide forum for discussion about each ...Version tracking for each requirementSupports a workflow for requirements lif ...Provides a release frameworkSupports multiple, intertwined releasesContent of a release might changeA release might require another releaseReleases embody themesReleases may partially address a themeReleases may partially address multiple ...Releases are associated with a set of re ...(I might want to rename this concept to ...Releases have a lifecycle(Not sure what it should be)DraftIn processCompletedBetaGenerally availableMaintenanceEnd of lifeReleases have a code nameReleases have a version numberReleases may include other releases (the ...Releases may be used on a temporary basi ...Releases have a scheduleSchedule can be rolled up from associate ...Schedules can be overridden at the relea ...Releases have a costCost can be rolled up from associated re ...Releases have a budgetReleases have a target dateQuestion: Do we need a "feature" level, ...Properties of requirementsNameDescriptionUIDAssociated with zero or more use casesCostAssociated with zero or more defectsAssociated with a releaseAffinities with zero or more themesMay have child requirementsHas a parent requirementAssociated with zero more customersHas a priorityHas a difficultyDependent on zero or more requirementsVery large distributed projectsOpen source usersSupport for dev methodologiesWaterfall/stage gateAgile methodologies - what does this mea ...XPOthersNameGRAPPLE - General Requirements and Produ ...Project stepsGet nameGet SourceForge siteWrite initial requirementsRecruit advisory board of PMs, engineeri ...Recruit participants for various rolesGet development environmentDesign and build initial schemaDesign and build initial interfaceTest initial versionDevelopmentRuby on RailsMySQLUsersLicensingGPL?Creative Commons?Determine best choice
hideReqsMgmt
hideRequirements
hideFunctional
hideSecurity
leafAllows authorized persons to update each requirement, saving changes and change history
hideMeta-data
leafAllows requirements to be tagged and prioritized in multiple dimensions, including user-defined dimensions
hideAllows requirements to be ranked via any of several different approaches
leafBy customer importance
leafCost
leafAlignment with a theme
leafAllows requirements to be arranged hierarchically
leafAutomatically creates unique ID for each requirement that stays with it throughout its lifecycle
hideProvides for lots of meta-data on requirements, some user-defined
leafCustomer(s)
leafRelated defects
leafTheme
leafRelease
leafValue
leafCost
leafFeature associated with a requirement
hideExternal interfaces
leafLinks to defect management system
leafLinks to source code management system
leafAllows requirements to be associated with external documents and other links, in a many-to-many relationship
hideProvides useful reports
hideMRDs and PRDs
leafIn Word form
leafIn table form
leafWith and without supporting info
leafStatistics
hideAnalysis
leafCost of Release A vs Release B
leafSchedule of Release A vs Release B
leafRequirements satisfying or not a particular priority or priorities
leafRequirements addressing a specific theme or themes
leafRequirements addressing a particular customer's interests
hideManagement
leafEasy backup of requirements and meta-data
leafEasy export of requirements to various formats
hideUser interface
hideWeb interface
leafFor entering suggestions
leafFor entering and working with requirements
leafFor viewing reports
leafSupports a suggestion interface
hideAbility to work offline
leafXML schema for individual requirements and groups of requirements
leafAbility to merge a set of requirements from XML into the database
leafProvide forum for discussion about each requirement
hideVersion tracking for each requirement
leafNumbering
hideSupports a workflow for requirements lifecycle
hideSteps
leafSuggestion
leafDraft requirement
leafIn review
leafApproved
leafDeferred from a release
leafDeferred to a release
leafAssigned to a release
leafObsolete
leafDeleted
leafTracks requirements as they fall out of a specific version or fall into a specific version
leafTracks splitting of requirements into multiple sub-requirements
leafAllows a group of requirements to be assigned to a specific product version
leafVersion tracking for collections of requirements (aka PRD)
hideProvides a release framework
leafSupports multiple, intertwined releases
leafContent of a release might change
leafA release might require another release
hideReleases embody themes
leafReleases may partially address a theme
leafReleases may partially address multiple themes
leafReleases are associated with a set of requirements
leaf(I might want to rename this concept to "product" or something like that)
hideReleases have a lifecycle
leaf(Not sure what it should be)
leafDraft
leafIn process
leafCompleted
leafBeta
leafGenerally available
leafMaintenance
leafEnd of life
leafReleases have a code name
leafReleases have a version number
leafReleases may include other releases (they might be hierarchical)
leafReleases may be used on a temporary basis for reporting or analysis
hideReleases have a schedule
leafSchedule can be rolled up from associated requirements
leafSchedules can be overridden at the release level
leaf
hideReleases have a cost
leafCost can be rolled up from associated requirements
leafReleases have a budget
leafReleases have a target date
leaf
leafhelpQuestion: Do we need a "feature" level, between requirement and release?
hideProperties of requirements
leafName
leafDescription
leafUID
leafAssociated with zero or more use cases
leafCost
leafAssociated with zero or more defects
leafAssociated with a release
leafAffinities with zero or more themes
leafMay have child requirements
leafHas a parent requirement
leafAssociated with zero more customers
leafHas a priority
leafHas a difficulty
leafDependent on zero or more requirements
leafVery large distributed projects
leafOpen source users
hideSupport for dev methodologies
leafWaterfall/stage gate
hideAgile methodologies - what does this mean?
leafXP
leafOthers
hideName
leafbutton_okGRAPPLE - General Requirements and Product PLanning Environment
hideProject steps
leafbutton_okGet name
leafGet SourceForge site
leafWrite initial requirements
leafRecruit advisory board of PMs, engineering managers
leafRecruit participants for various roles
leafGet development environment
leafDesign and build initial schema
leafDesign and build initial interface
leafTest initial version
hideDevelopment
leafRuby on Rails
leafMySQL
leafUsers
hideLicensing
leafGPL?
leafCreative Commons?
leafDetermine best choice