Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Open Computer Forensics Architecture 2.0.6pl3 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Open Computer Forensics Architecture 2.0.6pl3 (Default branch)
# 1  
Old 01-17-2008
Open Computer Forensics Architecture 2.0.6pl3 (Default branch)
The Open Computer Forensics Architecture (OCFA) is a modular computer forensics framework to automate the digital forensic process, to speed up the investigation and give tactical investigators direct access to the seized data through an easy to use search and browse interface. The architecture forms an environment where existing forensic tools and libraries can be easily plugged into the architecture and can thus be made part of the recursive extraction of data and metadata from digital evidence. It aims to be highly modular, robust, fault tolerant, recursive, and scalable in order to be usable in large investigations that spawn numerous terabytes of evidence data and cover hundreds of evidence items. License: GNU General Public License (GPL) Changes:
A bug was fixed in the indexer Web frontend. If you were having problems with the frontend showing empty green pages, you should upgrade.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

test::bdd::cucumber::manual::architecture

Test::BDD::Cucumber::Manual::Architecture(3pm)		User Contributed Perl Documentation	    Test::BDD::Cucumber::Manual::Architecture(3pm)

NAME

       Test::BDD::Cucumber::Manual::Architecture - Structural Overview

VERSION

       version 0.11

INTRODUCTION

       This short document exists to give you an idea how the different components of this distribution fit together.

MODELS

       The core of a Cucumber-based test suite are the feature files and the step definitions files. By convention, these are saved under
       "/features/" and "/features/step_definitions/" respectively.

       The feature files are encapsulated by the classes in "Test::BDD::Cucumber::Model".

			 one to one
	TBCM::Feature<----------------->TBCM::Document
	     |				     |
	     +-------------------+	     |
	     | has many 	 | has a     | has many
	     V			 |	     V
	TBCM::Scenario		 +----->TBCM::Line
	     |				  ^  ^
	     +----------------------------+  |
	     | has many 		     |
	     V				     |
	TBCM::Step---------------------------+

EXECUTOR

       We build up a Test::BDD::Executor object, in to which we load the step definitions. We then pass this in a Test::BDD::Model::Feature
       object, along with a Test::BDD::Model::Harness object, which controls interaction with the outside world.

AUTHOR

       Peter Sergeant "pete@clueball.com"

LICENSE

       Copyright 2011, Peter Sergeant; Licensed under the same terms as Perl

perl v5.14.2							    2012-05-20			    Test::BDD::Cucumber::Manual::Architecture(3pm)