Skip to main content

Home/ BARE+IA Requirements Engineering Information&Business Analysis/ Group items tagged tool integration

Rss Feed Group items tagged

Peter Van der Straaten

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
Peter Van der Straaten

Magic Quadrant for Enterprise Architecture Tools - 0 views

  • Mega has a clear identification and understanding of stakeholder expectations across the entire organization
  • Web-based integrated platform that includes EA, GRC, and application portfolio management, and delivers an integrated set of solutions that deliver operational excellence for organizations facing complex integration issues with business and technology
  • Mega consistently integrates industry best practices in many aspects of its product offering. One example is the Object Management Group's Meta Object Facility (OMG MoF 2)-compliant repository
Peter Van der Straaten

iRise Connect for HP QC - 0 views

  •  
    HP QC v10, iRise v8
Peter Van der Straaten

Use Cases for Business Analysts - The New School - 0 views

  • In my experience use cases are very powerful tools - their purpose is show the view from a *user's point of view*. The presented example is already very technical, and specifies a lot of details.
  • May I offer alternatives to the example in the article?A) A few brief classic requirements (for business) & a diagram (BPMN or UML activity diagram) (for the engineers)B) A use case with a lot less details (maybe 4-8 steps) & user interface design & a list of business rules (describing the essence of the details)C) No use case. One single sentence describing the goal & rationale ("As a user I want to have a recovery method when I forget the password because ....") & brief description of the important parts, business rules (no flow details!) & user interface design
  • May I offer other improvements to the "classic" use case in the example?- Instead of a summary, formulate it as a goal (remove redundancy)- Adding how frequently this is done ("Frequency: seldom, max. once per month ... once every few years")- Keep the main flow under 10 points- Remove pre-conditions and post-conditions. Keep it simple.- Integrate the alternative flows into the main flow (if possible, leave away details)
1 - 12 of 12
Showing 20 items per page