SystemAnalysis

Identified Subsystems

• GUI (see GUIAnalysis )
• Backend (see BackendAnalysis )
• Networking (see NetworkingAnalysis )

• a feed / a subscription
  • has a cached/permanent representation (stored items)
  • has runtime specific properties (next update, error infos)
  • may have permanent filters applied to it
  • has an availability and a correctness state
  • does contain a number of unique items

• an item / a headline
  • is read or unread
  • maybe flagged
  • is somehow unique
  • belongs to one feed

• an update request
  • assigned to a feed
  • requests the retrieval of a certain URI

• an update result
  • assigned to a feed
  • on success: contains the data of the retrieved feed
  • on error: contains error information

The following FMC diagram shows the interaction between the identified subsystems and the data types. (If you're unfamiliar with FMC: rectangles are actors, rounded boxes and circles are memories of all types, arrows to actors are read accesses, arrows from actors are write accesses, dashed arrows are pointers)

Note that the networking actor could also be used to read from local (but frequently updated) files or even command pipes. So maybe the name is not as perfect as possible.

Data Relations

When we abstract feed data to all the possibilities of the current syndicating standards (RSS, CDF, Atom, OCS and OPML) and define that each feed should be updated only once at a time we get the following data relations.

The next step is to refine the analysis of the subsystems. See GUIAnalysis , BackendAnalysis and NetworkingAnalysis

Please post comments, suggestions, errors...