Skip to main content
Jump to: navigation, search

Difference between revisions of "Architecture"

m (Component Architecture moved to Architecture)
 
(31 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
+
=Goal=
Higgins 1.0 Component Architecture
+
This page introduce architecture principles to be adopted by PolarSys projects and packages.
 +
It will describe the overall architecture of the PolarSys projects ecosystem.
 +
The Architecture Committee is linked to [http://wiki.eclipse.org/Polarsys/TLPProposal PolarSys Top Level Project].
  
==Core Components==
+
=Architecture Overview=
''Note: In this diagram "PI" means a plug-in.'' <br>
+
To Be Done.
[[Image:Higgins-v28b.JPG]]
+
  
[[Core Components Changes]] --changes to the above diagram
+
=Policies=
 +
[[PolarsysPolicies|PolarSys policies]] are a set of rules that should be adopted by PolarSys projects.
  
===Core Components===
+
=Release Engineering=
* [[RP Enablement]]
+
This part describes the release engineering of Polarsys.
* [[I-Card Manager]]
+
* [[HBX Support]]
+
* [[ISS Web UI]]
+
* [[ISS Client UI]]
+
* [[I-Card Selector Service]] (ISS)
+
* [[I-Card Registry]]
+
* [[I-Card Provider]]
+
* [[Token Service]]
+
* [[Token Provider]]
+
* [[Identity Attribute Service]] (IdAS)
+
* [[Context Provider]]
+
  
==Client Components==
+
Topics:  
Client apps and services that use these core components are expected to include:
+
* [[Higgins Browser Extension]]
+
* "Relying Party" websites that will consume identity data provided by Higgins-based services. These would use at least the "RP Enablement" component mentioned below
+
* Eclipse RCP apps can leverage the [[ISS Client UI]] app for authentication
+
* Enterprise apps that could potentially rely on one or more of: [[I-Card Selector Service]], [[ISS Web UI]], [[ISS Client UI]], and [[Identity Attribute Service]]
+
  
==See Also==
+
*[[Polarsys/Release_Engineering/Definitions|Definitions]]  
* [[Component Matrix]]
+
*[[Polarsys/Release_Engineering/Policies|Policies]]
* [http://eclipse.org/higgins Higgins Home]
+
*[[Polarsys/Release_Engineering/Process|Process]]
** [http://wiki.eclipse.org/index.php/Higgins_Wiki Wiki]
+
 
** [http://www.eclipse.org/higgins/goals.php Goals]
+
Interesting resources are already provided by the Eclipse LTS IWG:  
** [http://www.eclipse.org/higgins/plan.php Plan]
+
 
** [http://www.eclipse.org/higgins/faq.php FAQ]
+
*[http://wiki.eclipse.org/LTS/LTS_Ready Description of Readiness for LTS]  
** Architecture: [[Core Components]]
+
*[http://wiki.eclipse.org/LTS#Value_Proposition LTS Value proposition]
** Components: [[Component Matrix]]
+
 
** [http://www.eclipse.org/higgins/resources.php Developer Resources]
+
=Work in progress=
** [http://www.eclipse.org/higgins/downloads.php Downloads]
+
* [[Architecture/Interoperability | Interoperability]]

Latest revision as of 08:52, 10 September 2013

Goal

This page introduce architecture principles to be adopted by PolarSys projects and packages. It will describe the overall architecture of the PolarSys projects ecosystem. The Architecture Committee is linked to PolarSys Top Level Project.

Architecture Overview

To Be Done.

Policies

PolarSys policies are a set of rules that should be adopted by PolarSys projects.

Release Engineering

This part describes the release engineering of Polarsys.

Topics:

Interesting resources are already provided by the Eclipse LTS IWG:

Work in progress

Back to the top