System Requirements

Requirements > Mass article submitter

ELGG Social Network automation tool
Mass article submitter -- Batch Posting
The Project Requirements >
.
* spreadsheets.google link will be provided as parametric input for a List-of-social-networks to be visited and dully processed
.
The client needs an application which will:
.
1) register account automatically at a List-of-social-networks
- The virtual user accounts must be created automatically (using proxies - user agent customization - decapther)
.
2) maintain a database of accounts
- It will periodically check if they are still live and replace any of them which is deactivated
.
3) publish content at a List-of-social-networks
- Mass article submitter must post blogs to the List-of-social-networks or Tweeter style status updates
.
4) web application needs to have a simple content editor (WYSIWYG and plain html mode )
the user will be able to input, edit and MASS PUBLISH the content of each post
.
4a) it needs to support SPINTAX and to generate output-article permutations
SPINTAX enables you to write a single article, then re-word certain areas of it to read differently, but have the same SEMANTIC meaning. (look at the figure above)
.
4b) a flickr hook will be implemented to auto insert a flickr MASHUP based on TAG in the content page
.
.
5) Error/Success status report of entire batch job posting transaction will be generated.
.
The features such as decaptcher, proxy support and user agent randomization must be included
The social-networks such as:
mediawiki,
openwiki,
tikiwiki,
macosx server - MediaWiki,
elgg,
jisko,
hiku,
revou,
mahara,
statusnet( laconica),
bloghoster,
lifetype
...
are the ones the client would like to start with.


Answers to these questions can sometimes discover unrealistic business targets coupled with too low budget and or poor planing.

1. Who will be creating and writing the "product specifications": Developer/Coder? Customer? Tester?

2. Will customer also provide a Product Testing, in order to find out if the product features meet his requirements and test specifications?

3. Who will be reading/validating these specifications: product manager? Customer? Tester? User? Coder?

4. Who will be maintaining them (this can often be the hardest part)?

5. What is the purpose of the specifications? Is it to ensure that the software works as desired? Are specifications intended to fully cover all of the possible use cases, or only a cross-section? Are they "start-to-finish" tests, i.e., a full business use case, or are they scenarios?