Revision as of 10:58, 21 January 2011 (view source) Miikadeluxe (Talk | contribs) ← Older edit		Revision as of 11:05, 21 January 2011 (view source) Miikadeluxe (Talk | contribs) (→References) Newer edit →
Line 27:		Line 27:
	| <nowiki>[SSOArch]</nowiki>		| <nowiki>[SSOArch]</nowiki>
	| SSO Architecture Study		| SSO Architecture Study
-	| [https://cwiki.nokia.com/twiki/pub/AccountmgtL/ArchitechtureStudy/SSO-arch-study-0_5.doc https://cwiki.nokia.com/twiki/pub/AccountmgtL/ArchitechtureStudy/SSO-arch-study-0_5.doc]	+	| [xxx]
	|}		|}
		+
	== Glossary ==		== Glossary ==

---

Revision as of 11:05, 21 January 2011

[[Category:]]

Accounts architecture Subsystem Architecture Specification

Contents 1 References 2 Glossary 3 Summary of changes in current version 4 Architecture 4.1 Hardware 4.2 Licensing and IPR view 5 Performance 5.1 General Performance Considerations 5.2 Memory 5.3 Runtime 5.4 Power Consumption 6 Security 7 Open items

References

Tag	Document name	Repository (with hyperlinks)
[ArchGoals]	Architecture Goals	[xxx]
[SystemModel]	Maemo System Model	[xxx]
[SSOArch]	SSO Architecture Study	[xxx]

Glossary

Acronym or term	Description
API	Application Programming Interface
UI	User Interface

Summary of changes in current version

List the full set of dependencies.

Architecture

Hardware

No hardware dependencies.

Licensing and IPR view

Accounts subsystem is a newly developed Nokia software; no known OSS product provides the required functionality. libAccountsUI license is currently Nokia closed, while libaccounts-glib and libaccounts-qt have been released as open-source.

Performance

General Performance Considerations

The performances of the Accounts subsystem heavily depend on SQLite performances, as this is the database being used for storing the account settings.

A typical account will consist of less than 5 records in the SQLite database, plus 1 record for each service enabled on the account; an experienced internet user will have a few dozens of installed accounts.

The records in the database are fairly simple, consisting mostly of a pair of key and value (with values being typically strings, integers and booleans); the size of the accounts database can be reasonably estimated to be below 100KB.

There are no real time requirements known.

Memory

	Explanation	Size [kB]
Flash/OneNAND	Debian packages	500
Flash/eMMC	Account settings database	100
RAM/Idle	Memory footprint when account libraries are loaded	200
RAM/Peak	Memory footprint when libraries and plugins are loaded, account settings are loaded and accounts are being edited	2000

Runtime

The most frequent scenario of usage of the Accounts subsystem is application initializing its accounts’ data: Accounts libraries will be loaded along with the application, which will need to list the accounts enabled for the specific service(s) it uses, and load their settings. Once the accounts are loaded, the impact of the libraries on the system is negligible.

Power Consumption

Disc access happens only when loading accounts (which typically happens on application startup) and when editing them.

Security

Accounts settings are not sensitive data.

Below is a table depicting executables and their credentials.

Credentials required by Accounts subsystem executables

Executable	Credential
accounts-ui	nokiamessagingcds::ReadAccess
accounts-ui	nokiamessagingcds::WriteAccess

Open items

No open items.