Kevlar Core team
Working draft of Kevlar knowledge base and Information management
1. Teams
2. Knowledge Base
2.1. 0.0 Master Documentation
2.1.1. 0.1 Kevlar Core documentation
2.1.1.1. 0.1.1 Mother-load
2.1.1.2. 0.1.2 Kevlar Introduction
2.1.1.3. 0.1.3 Core components
2.1.1.4. 0.1.4 System design approach
2.1.1.5. 0.1.5 Authentication Interoperability
2.1.1.6. 0.1.6 Kevlar use cases
2.1.1.7. 0.1.7 Dauth use cases
2.1.1.8. 0.1.8 Governance
2.1.1.9. 0.1.9 Business Model
2.1.1.10. 0.1.10 Finance
2.1.2. 0.2 Backlog Index
2.1.2.1. 0.2.0 Comprehensive list of assignments
2.1.2.2. 0.2.1 Active assignment list
2.1.2.3. 0.2.2 High priority assignments
2.1.2.4. 0.2.3 Low priority assignments
2.1.3. 0.3 Community and Contributor FAQ
2.1.3.1. 0.3.0 An open invitation to the community
2.1.3.2. 0.3.1 The core team Involved
2.1.3.3. 0.3.2 Contributors - Individual
2.1.3.4. 0.3.3 Contributors - Entities
2.1.3.5. 0.3.4 FAQ
2.1.3.6. 0.3.5 Community guidelines
2.1.3.7. 0.3.6 Contribution guidelines
2.1.4. 0.4 Resource directory
2.1.4.1. 0.4.0 Sitemap.xml
2.1.4.2. 0.4.1 Glossary
2.2. 1.0 Core development
2.2.1. 1.1 Documentation
2.2.1.1. 1.1.1 System requirements specifications
2.2.1.2. 1.1.2 Functional requirement specifications
2.2.1.3. 1.1.3 Design specifications
2.2.1.3.1. 1.1.3.0 Solution design schematics
2.2.1.3.2. 1.1.3.1 UX/UI design specifications
2.2.1.4. 1.1.3 Development module specifications
2.2.1.5. 1.1.3 Data and Dashboards specifications
2.2.1.6. 1.1.4 Security and Infrastructure specifications
2.2.1.7. 1.1.5 Testing and QA specifications
2.2.2. 1.2 Work breakdown structure
2.2.2.1. 1.2.1 Breakdown of the project into milestones
2.2.2.2. 1.2.2 Breakdown of milestones into assignments
2.2.2.2.1. 1.2.2.1 Individual assignments with time estimations
2.2.2.3. 1.2.3 Project Gantt
2.2.3. 1.3 Assignment pipeline
2.2.3.1. 1.3.1 Upcoming assignments
2.2.3.2. 1.3.2 Active assignments
2.2.3.3. 1.3.3
2.2.3.3.1. QA
2.2.3.4. 1.3.4 Finished assignments
2.3. 2.0 Service layer
2.3.1. 2.1 Documentation
2.3.1.1. 2.1.1 System requirements specifications
2.3.1.2. 2.1.2 Functional requirement specifications
2.3.1.3. 2.1.3 Design specifications
2.3.1.3.1. 2.1.3.0 Solution design schematics
2.3.1.3.2. 2.1.3.1 UX/UI design specifications
2.3.1.4. 2.1.3 Development module specifications
2.3.1.5. 2.1.3 Data and Dashboards specifications
2.3.1.6. 2.1.4 Security and Infrastructure specifications
2.3.1.7. 2.1.5 Testing and QA specifications
2.3.2. 2.2 Work breakdown structure
2.3.2.1. 2.2.1 Breakdown of the project into milestones
2.3.2.2. 2.2.2 Breakdown of milestones into assignments
2.3.2.2.1. 2.2.2.1 Individual assignments with time estimations
2.3.2.3. 2.2.3 Project Gantt
2.3.3. 2.3 Assignment pipeline
2.3.3.1. 2.3.1 Upcoming assignments
2.3.3.2. 2.3.2 Active assignments
2.3.3.3. 1.3.3
2.3.3.4. 1.3.4 Finished assignments
2.4. 3.0 Explorer
2.4.1. Same as 2.0
2.5. 4.0 Web Clients
2.5.1. 4.1 Validator Clients
2.5.1.1. Same as 3.0
2.5.2. 4.2 Administrative client
2.5.2.1. Same as 3.0
2.5.3. 4.3 Individual IDMS
2.5.3.1. Same as 3.0
2.5.4. 4.4 Entity IDMS
2.5.4.1. Same as 3.0
2.5.5. 4.5 Accreditation provider client
2.5.5.1. Same as 3.0
2.6. 5.0 iOS App
2.6.1. 5.1 Kevlar App
2.6.1.1. 5.2 Same as 3.0
2.6.2. 5.2 Covid-19
2.6.3. 5.3 Cayman Islands
2.6.4. 5.4 Dating application
2.7. 6.0 Android app
2.7.1. 4.0 Web Clients
2.7.1.1. 4.1 Validator Clients
2.7.1.1.1. Same as 3.0
2.7.1.2. 4.2 Administrative client
2.7.1.2.1. Same as 3.0
2.7.1.3. 4.3 Individual IDMS
2.7.1.3.1. Same as 3.0
2.7.1.4. 4.4 Entity IDMS
2.7.1.4.1. Same as 3.0
2.7.1.5. 4.5 Accreditation provider client
2.7.1.5.1. Same as 3.0