This page contains information about the different actors we expect to interact with or be part of the censorship monitoring project. Actors can be individuals, groups of people, system components or third party systems that interact with our system.

Actors are used as the protagonists in use cases and user stories. (To make such a reference a link to the relevant section of this page should be included.)

Our system consists of three software sub-systems, as inferred from the architecture page:

The blocked.org web site
The probe (for a number of platforms)
The middleware that provides a REST API for probe interaction

Web Site Actors

Human Web User

A person visiting blocked.org.uk. A user could be performing one or more of the following roles:

the account-holder for a home connection
a casual web surfer using a private connection
a casual web surfer using a public connection
an administrator responsible for a private network
an administrator responsible for a public network
an employee of a business
a website owner or webmaster
an ISP employee
an employee of the state (government, legislature, judiciary, police, etc.)
a solicitor, barrister, lawyer etc.
a researcher or academic
an ISP user ( may want to respond to notification of a blocking etc)

The source files for the diagrams on this page can be found in this github repository.

Administrator

Will there be more than one level?

Bot user

Bots and script performing automated data mining / reporting / integrations with this data --RedFred (talk) 18:20, 8 January 2014 (GMT) is this valid as a Web Site actor??

Probe Actors

Probe User

People who run probes.

There is a list of roles for the OONI project that probably intersects with our list of actors.

Middleware Actors

Probe

A probe wanting to submit/retrieve data.

Relevant User Stories can be found at User stories

Censorship Monitoring Project Actors

Contents