-
Notifications
You must be signed in to change notification settings - Fork 10
Milestone July 2018
Harsh Shah edited this page May 14, 2018
·
23 revisions
Work package Name | Use Case - Panama Papers |
---|---|
ID | 0 |
Summary | In this use case, we will explore the panama paper files (https://www.kaggle.com/zusmani/paradisepanamapapers), transform them to RDF and investigate the Knowledge Graph content via keyword search and question answering as well as via visualisations/ml-techniques through our intelligent data assistant. |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | Task 0.0 SASK should be able to load, transform and analyze the panama papers. Task 0.1 SASK should be able to visualize simple connections such as how many company owners come from which country. Task 0.2 SASK should be able to answer questions such as "Who own company XYZ?" Task 0.3 SASK should be able to find "company owned by DAVID, RONALD". Task 0.4 SASK should support finding a british actor owning companies on the bahamas via the intelligent data assistant. Task 0.5 SASK should be able to find similar companies to a given on via the intelligent data assistant. |
Deliverable | Deliverable 0 - A working demo of the aforementioned tasks which feels natural. |
Work package Name | Complex workflows |
---|---|
ID | 1 |
Summary | The application should be able to handle more complex workflows |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | Task 1.1 (Lead: Andrè, Participants: Kevin) The backend (executer) should be able to handle more complex workflows Task 1.2 (Lead: Kevin) The frontend (webclient) should be able to create more complex workflows |
Deliverable | Deliverable 1.1 (Task 1.1, Lead: Andrè, Due Date: 2018-07-16, Type: Software in the Master) Deliverable 1.1 (Task 1.2, Lead: Kevin, Due Date: 2018-07-16, Type: Software in the Master) |
Work package Name | Exception & Message handling |
---|---|
ID | 2 |
Summary | The application should log everything on a central location |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | Task 2.1 (Lead: Sepide, Participants: Suganya) Setup Logstash Docker Task 2.2 (Lead: Sepide, Participants: Suganya) Setup Kibana Docker Task 2.3 (Lead: Sepide, Participants: Suganya) Setup Logging microservice |
Deliverable | Deliverable 2.1 (Task 2.1, Lead: Sepide, Due Date: 2018-07-16, Type: Documentation) A wiki page with a guide to start logstash Deliverable 2.2 (Task 2.2, Lead: Sepide, Due Date: 2018-07-16, Type: Documentation) A wiki page with a guide to start Kibana Deliverable 2.2 (Task 2.2, Lead: Sepide, Due Date: 2018-07-16, Type: Software in Master) A new microservice to collect all logs and use lostash |
Work package Name | Integrate chat in UI |
---|---|
ID | 3 |
Summary | The chat should be intregrated in the UI |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | Task 3.1 (Lead: Nilanjan, Participants: Kevin) create a (paper) prototype with the integrated chat window Task 3.2 (Lead: Nilanjan, Participants: Kevin) create a functional prototype with the integrated chat window Task 3.3 (Lead: Nilanjan, Participants: Kevin) integrate the chat in the ui |
Deliverable | Deliverable 3.1 (Task 3.1, Lead: Nilanjan, Due Date: 2018-05-14 Type: Document) A digital or paper prototype Deliverable 3.2 (Task 3.2, Lead: Nilanjan, Due Date: 2018-06-04, Type: Software) A functional prototype of the new UI Deliverable 3.3 (Task 3.3, Lead: Nilanjan, Due Date: 2018-07-16, Type: Software in Master) The chat should be integrated in the UI |
Work package Name | Ensemble learning |
---|---|
ID | 4 |
Summary | To extract data from training data To implement ensemble learning to predict which extractor fit |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | Task( 4.1 Lead: Harsh, Participant : Kevin) To extract data from training data Task( 4.2 Lead: Harsh, Participant : Kevin) To implement ensemble learning version for testing Task( 4.3 Lead: Harsh, Participant : Kevin) To integrate into system |
Deliverable | Deliverable 4.1 (Task 4.1, Lead: Harsh, ,Due Date: 2018-07-16, Type: Document)Extracted Data Deliverable 4.2 (Task 4.2, Lead: Harsh, Due Date: 2018-07-16, Type: Software) Ensemble Learning Software Deliverable 4.3(Task 4.3, Lead: Harsh,Due Date: 2018-07-16, Type: Software in Master)Ensemble Learning implemented in our software |
Work package Name | Visualize the database content |
---|---|
ID | 5 |
Summary | The user should be able to display database content as graph and table in the UI |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | Task 5.1 (Lead: Nilanjan, Participants: Kevin) Display database content in the UI |
Deliverable | Deliverable 5.1 (Task 5.1, Lead: Nilanjan, Due Date: 2018-07-16 Type: Software in Master) |
Work package Name | Auto Index Refinements |
---|---|
ID | 6 |
Summary | Auto Index should be highly customizable from both configuration and Rest interfaces, Close pending issues |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | Task1: (Lead: Prashanth, Participants: Idrees) Customize Labels , Add Unit tests , Single Surface form and other bug fixes Task2: (Lead: Idrees) Quality Improvement(Codacy/Better Code) and Unit test coverage |
Deliverable | Due Date: 2018-07-16 Type: Software in Master which is very highly flexible and customisable) |
Work package Name | Intent Classification |
---|---|
ID | 7 |
Summary | Weka tool must be able to predict which component to delegate the query to |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | (Lead: Divya) 1. Add Weka Code which predicts classification from a training set 2. Incorporate user feedback to improve future predictions |
Deliverable | Due Date: 2018-07-16 Type: Software in Master |
Work package Name | Deployment of Chatbot SASK Component |
---|---|
ID | 8 |
Summary | Come up with a generic framework for deployment of Chatbot microservices |
Start Date | 2018-04-23 |
End Date | 2018-07-16 |
Tasks | (Lead: Guru) 1. Dockerize the miroservices 2. Write a ansible playbook deploying the chatbot related microservices |
Deliverable | Due Date: 2018-07-16 Type: DevOps software in Master |