to keep this thing rolling we'll use the ＷＡＴＥＲＦＡＬＬ ＭＯＤＥＬ
and make a new thread for each phase.
the first step is formulating the requirements as a set of ＵＳＥ
ＣＡＳＥＳ that describe all the interactions the users will have
with the software.
Name:
Anonymous2011-01-20 22:11
In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).
In addition to use cases, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). In addition to design constraints, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). In addition to design constraints, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). In addition to design constraints, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). In addition to design constraints, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). In addition to design constraints, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). In addition to design constraints, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). In addition to design constraints, the SRS also contains non-functional (or supplementary) requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).
Name:
Anonymous2011-01-20 22:29
USE CASE
Shave my anus hairs in the most excruciatingly painful way possible.
right, perhaps i should put more consideration in late night
posts, as i forgot to write down what the program is all about.
what we're going to write is a strongly anonymous distributed
chan and yes i'm 100% serious about this. i am going to write
this anyways since i can and i want to program something which
could have merit.
some terminology: a 'server' here means a single server that is
running behind a tor hidden service, the 'serverid' is the
hostname of that service (3g2upl4pq6kufc4m.onion). a
'network' means a collection of servers working together by
mirroring each other's posts.
I'll start with some requirements:
* anyone should be able to run a server and configure it to
mirror posts from other servers.
* it should be mathematically impossible for anyone to trace
the identity of a participant (user, server operator).
* the protocol itself should be simple enough that a simple
server can be implemented be the average /prog/rider in a few
hours.