Open Computer Forensics Architecture 2.1.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Open Computer Forensics Architecture 2.1.0 (Default branch)
# 1  
Old 03-18-2008
Open Computer Forensics Architecture 2.1.0 (Default branch)

The Open Computer Forensics Architecture (OCFA) isa modular computer forensics framework to automatethe digital forensic process, to speed up theinvestigation and give tactical investigatorsdirect access to the seized data through an easyto use search and browse interface. Thearchitecture forms an environment where existingforensic tools and libraries can be easily pluggedinto the architecture and can thus be made part ofthe recursive extraction of data and metadata fromdigital evidence. It aims to be highly modular,robust, fault tolerant, recursive, and scalable inorder to be usable in large investigations thatspawn numerous terabytes of evidence data andcover hundreds of evidence items.License: GNU General Public License (GPL)Changes:
This version includes some refactored subsystems that should make the architecture a bit faster and easier to integrate with other programming languages like Java and Perl. With the new treegraph library, it should now be a lot simpler to create custom treegraph-based modules for the architecture.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
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)