Skip to main content

Home/ Groups/ BARE+IA Requirements Engineering Information&Business Analysis
4More

INCOSE - RM Tools Database - 2 views

  • INCOSE Requirements Management Tools Survey
  • The survey responses, including the rating of compliance with each question or feature, are provided by the tool vendors directly. However, the TDWG reserves the right to review and correct any "informational injustices" (i.e. exaggerated answers).
  • Requirements Management Tool Survey Responses
  •  
    Survey responses by tool vendors; Microfocus tools not available
15More

Requirements Management Tools - Vendors and Freeware Suppliers - 0 views

  • Trends
  • Low Cost, Low Maintenance
  • Niche Specialisation
  • ...11 more annotations...
  • Not Calling it "Requirements" at all
  • Integration
  • Requirements Management Tools
  • Use Case Tools
  • Agile Development Tools
  • Industry-Specific Tools
  • Tools to Check & Validate Requirements
  • Tools to Animate & Simulate Requirements
  • Tools to Diagram & Visualize Requirements
  • Free & Shareware Tools
  • Free Trials
  •  
    Extensive list with short descriptions for each tool, grouped by type of tool
3More

Volere requirements resources - Tools - 0 views

  •  
    Extensive list, though outdated (e.g. CaliberRM 2005 & RequisitePro 2003 version)
1More

Google Insights - comparison IREB and BABOK CBAP - 1 views

  •  
    IREB bigger than BABOK/CBAP? Or is the analysis on Google insights on CPRE (in category computers) returning irrelevant results. Note: in US the HOOD group offers CPRE certification and e-learning (which would qualify as correct search results).
6More

InfoQ: IIBA announce Agile Extension to the Business Analysis Body of Knowledge - 1 views

  • IIBA(tm)) announced the release of a draft of the Introduction for the Agile Extension to the Business Analysis Body of Knowledge (BABOK
  • many business analysts are struggling to understand how the role changes in Agile projects
  • "weak" or "sham" Agile implementations in organisations where "doing Agile" is not accompanied by any real cultural or governance change
  • ...2 more annotations...
  • public draft of the introduction to the extension.  This is available from the IIBA website 
  • Simultaneously Chris Matts and others formed the Agile BA Requirements Yahoo group
  •  
    Also other remarks on Agile and BA
1More

About EBG:Experienced Business Consulting & Business Analysis - 1 views

  •  
    book: Requirements by collaboration (P.Kalmijn)
2More

IREB - Downloads (Preparation) - 1 views

  • CPRE FL - Prüfungsordnung
  • Erläuterung der unterschiedlichen Fragetypen mit je einigen Beispielfragen.
1More

Google Insights - UML tools - 0 views

  •  
    Note: Papyrus is also a ECM tool
1More

Requirements by Collaboration Book - Ellen Gottesdiener - 0 views

  •  
    Ellen has years of hands-on experience with Agile projects, with a focus on requirements. Key-note speaker on DREAM 2011; met her at evening workshop on 20110920.
4More

MKS Inc. - Wikipedia, the free encyclopedia - 0 views

  • In 2008 Forrester proclaims MKS as the leader in requirements management in the independent research report
  • MKS positioned in the 'Leaders' quadrant in Gartner's first ever Magic Quadrant for Software Change and Configuration Management (SCCM) for Distributed Platforms
  • Gartner positioned MKS as a leader in the 2009 Magic Quadrant for Software Change and Configuration Management (SCCM) for Distributed Platform
  • ...1 more annotation...
  • Forrester named MKS as a leader in Agile development management tools in Forrester Research Inc., May 2010
2More

"The Forrester Wave(tm): Agile Development Management Tools, Q2 2010," Forrester Resear... - 0 views

  • MKS Named a Leader in Forrester’s Analysis of Agile Development Management Tools
  • MKS is pleased to offer you a complimentary copy of this independent research
2More

Why Software Requirements Traceability Remains a Challenge - 0 views

  •  
    Interesting article! And many of the issues it mentions are addressed by caliber
  •  
    Interesting article! and many of the issues are addressed by CaliberRM (I'm using it at rijkswaterstaat)
1More

spider - 0 views

  • SPIder is een Nederlands netwerk van IT-professionals waarin kennis en ervaringen gedeeld worden op het gebied van software­ontwikkelmethodieken, processen en modellen, (software)­procesverbetering (SPI), kwaliteit, kwaliteitsboring (QA), ontwerp en test, metrieken en invoeringstrategieën
1More

iRise Connect for HP QC - 0 views

  •  
    HP QC v10, iRise v8
1More

CollabNet - The Leader in Agile Application Lifecycle Management - 0 views

  •  
    ScrumWorks pro - agile project management
18More

Alistair.Cockburn.us | Why I still use use cases - 1 views

  • XP pretty much banned use cases, replacing them with the similar sounding “user stories”
  • Scrum did similar, using the “product backlog” instead of user stories
  • Yet as I go around projects, I keep running across organizations suffering from three particular, real, painful, and expensive problems
  • ...15 more annotations...
  • User stories and backlog items don’t give the designers a context to work from
  • don’t give the project team any sense of “completeness
  • don’t provide a good-enough mechanism for looking ahead at the difficulty of upcoming work
  • Staring at the set of extension conditions in a use case lets the analysts suss out which ones will be easy and which will be difficult, and to stage their research accordingly
  • Here 5 reasons why I still write use cases
  • The list of goal names provides executives with the shortest summary of what the system will contribute to the business and the users
  • The main success scenario of each use case provides everyone involved with an agreement as to what the system will basically do, also, sometimes more importantly, what it will not do.
  • The extension conditions of each use case provide the requirements analysts a framework for investigating all the little, niggling things that somehow take up 80% of the development time and budget
  • The use case extension scenario fragments provide answers to the many detailed, often tricky business questions
  • The full use case set shows that the investigators have throught through every user’s needs, every goal they have with respect to the system, and every business variant involved
  • how much should be written up front to get the project estimate into a safe place
  • several sticky parts for people using use cases
  • iteration/sprint lengths are so short that it is not practical to implement an entire use case in just one of them.
  • Writing good use cases (or any other requirements) requires thinking, communicating, and thinking again. It is much easier just to write user-story tags on index cards and let the project blow up later
  • We have adopted many of the concepts of Agile development—such as daily build and test, build the smallest piece of functionality that delivers value, etc.—but have retained our up-front work. It’s worked extremely well
1 - 20 Next › Last »
Showing 20 items per page