Projects

jUCMNav

jUCMNav is a graphical editor for the User Requirements Notation (URN), which includes the Use Case Map (UCM) notation and the Goal-oriented Requirement Language (GRL). jUCMNav is an Eclipse plug-in.

Isotrol RequMNGT Redmine Plugin

RequMNGT is a Redmine plugin that allows you to manage in your software project: * system and software requirements. * traceability. * baseline and Request For Change. 1. you can identify business artifacts, software artifact and others like Business Actor, Business Use Case,... 2. you ... [More] can manage and check the (Horizontal and vertical) TOTAL TRACEABILITY between the different artifact of a software project: * Feature, Requirement, Use case, classes, test case, code ... 3. You can create, delete, modify one or several baseline and manage the requests for change. 4. You can generate different reports (requirement, usecase, testcase, Metrics ...) 5. If you install the risk management plugin RiskMNGT, you could classify the requirements or scenarios according to the exposure level [Less]

CAIRIS

CAIRIS (Computer Aided Integration of Requirements and Information Security) is a Requirements Management tool for specifying secure and usable systems. CAIRIS was built from the ground-up to support the elements necessary for usability, requirements, and risk analysis. Its features include: * ... [More] Support for KAOS goal and obstacle modelling, and traceability between goal, requirements, security, and usability model elements. * Support for entering and managing usability data, such as personas, tasks, and use cases * Support for entering and managing risk analysis data. * Automatic visualisation of models, and quantitative/quantative scoring of security and usability data * Automatic document generation of a VOLERE compliant requirements specification. [Less]

concrete-scenarios

A concrete scenario documents a user task performed in a particular situation with a sequence of precisely written system states. Concrete scenarios are both precise and understandable. They are useful in the specifications of functional requirements. Collections of concrete scenarios have been ... [More] used to create formal speciifcations in Z and executable specification in CLIPS systematically. Without appropriate tools, the process to derive specifications from concrete scenarios is tedious and error-prone. This project aims to develop tools to improve the effectiveness and efficiency of the process. Concrete scenarios were invented by Oliver Au as part of his PhD research at Loughborough University under the supervision of John Cooke and Roger Stone. Oliver is currently an instructor with the Computer Science Department at the City University of Hong Kong. [Less]

divvy

divvy is a Wealth Management & Planning app that focuses on creating wealth by managing incomes, expenses, savings, investments and then adds planning and scenario capabilities.

fixture-scenarios

Copyright (c) 2007 Tom Preston-Werner FixtureScenariosThis plugin allows you to create 'scenarios' which are collections of fixtures and ruby files that represent a context against which you can run tests. DisclaimerThis software is in Beta. Send feedback to tom at rubyisawesome dot com ... [More] or find me (mojombo) on irc.freenode.net. InstallationFixtureScenarios should work on both 1.1.6 and edge rails. Currently you must install this plugin from the subversion repository script/plugin install http://fixture-scenarios.googlecode.com/svn/trunk/fixture_scenariosWARNINGBecause this plugin clears out fixture data between your test classes, you may see some of your tests fail after installation. If this occurs, look at your tests to see if you didn't actually load a required fixture for that test class. If you forgot to add it and your tests passed anyway (because of fixture contamination), just add the missing fixture(s) and you'll be good to go. The BasicsTo create a scenario, simply create a subdirectory under test/fixtures in your Rails app. The name of the subdirectory will be the name of the scenario. Inside this new directory, you can place fixture files, and/or Ruby files. [RAILS_ROOT] +-test/ +-fixtures/ +-brand_new_user/ +-users.yml # in users.yml borges: id: 1 name: Jorge Luis Borges active: 1To load the scenario for testing, you simply use the +scenario+ method instead of the normal +fixtures+ method. require File.dirname(__FILE__) + '/../test_helper' class UserTest < Test::Unit::TestCase scenario :brand_new_user def test_should_be_active assert users(:borges).active? end endAll of the fixtures placed into your scenario directory will be loaded when you invoke the +scenario+ method with your scenario name. In addition, any Ruby files you place in the scenario directory will be run after the fixtures. You can use a Ruby file to create non-database model instances, set up relationships between fixtures (instead of creating fixtures for the join tables), or replace fixtures entirely by creating your database items with Ruby code. In this example, +scenario+ will actually load all fixtures from the fixture directory and your scenario directory. This is useful if you have some fixtures (such as lookup data) that you'd like to have in most of your scenarios. To prevent the loading of fixtures in the fixtures root directory, use the :root option. This can be very useful if you still have tests using regular fixtures. scenario :brand_new_user, :root => falseTo keep things DRY in your scenarios, you can extend or layer scenarios on top of each other. Following with our example, to create an 'experienced user' scenario, we could create another subdirectory under the existing 'brand_new_user' that would contain fixture/Ruby files that add upon the 'brand new user' scenario. [RAILS_ROOT] +-test/ +-fixtures/ +-brand_new_user/ +-users.yml +-experienced_user/ +-articles.ymlNow when you load the +experienced_user+ scenario, it will load any fixture/Ruby files in 'fixtures', then in 'brand_new_user', then in 'experienced_user'! Building off of your existing scenarios keeps data redundancy to a minimum, and makes it easy to change data for multiple scenarios simultaneously. Testing your scenariosScenarios represent your assumptions about a given context. If these assumptions are wrong, your tests will be inaccurate. Your scenarios should be unit tested along with the rest of your application. This plugin allows you to place scenario tests in a 'scenario' directory under your 'test' directory. [RAILS_ROOT] +-test/ +-scenario/ +-brand_new_user_test.rb +-experienced_user_test.rbYou can run these tests with rake. rake test:scenarios # run just scenario tests rake # run unit, functional, integration, and scenario testsScenario tests will protect you from accidentally changing your assumptions in a dangerous or transparent way when modifying existing scenarios. [Less]

sxsm

A tool which creates custom SIP protocol sequences for testing purposes.