Meetings with supervisor (summary)

Below are some of the pointers discussed during the meetings with our supervisor. These have been presented during meeting but are posted here in order to have them documented.

Meeting with supervisor Chris Peters 9/2 - 2017

Since last time

• PPD: 2 points 
• Try to reuse from the extensive PPD we created. 
• New requirements: Reduced 
• Show prototype: CSC  
• Color, think about this
• Toggle button

Findwise

• Licensing issues? 
• Sustainable for the system - duration. 
• Third party library - d3 library, check the license. 
• Show Findwise- license, perhaps draw a document. 

Documentation 

• Create Use cases
• Detail 2.1.5
• Risk/need/priority 
• Dependencies 
• Three columns 
• IEEE 830 - not every section is important. add do not change.
• Sketches 
• Visualization Filtering Task —> Visualization method 
• Priorities and stretch goals.

Meeting with supervisor Chris Peters 20/2 - 2017

Other project

Had a meeting with the other group and talked about similarities. 

New meeting will be held after the other group are done with their project. 

Group issues

• Now nine. 
• Think about how more people can leave and make a contingency plan
• Update roles (has been done). 

Documentation 

• Template has been created 
• Assumptions and Dependencies: libraries, people, technical, team members, licenses, plattform, KTH-system (api)
• Performance requirements: arbitrary value (5 seconds), threshold, how long does it take to run. Check with the demo. Optimization and basic plattform. Minimal plattform.  
• Design constraints: 
• Specific requirements: alla subsections.  
• Software system quality attributes: look through the document  

Use cases: 

• Prioritize so we know direction. 

Meeting with Chris 27/2 - 2017 

UML Class Diagram 

• Not part of SRS1 but still a grading criteria. Suppose to be 3.7. 
• Ask Karl about this on KTH Social. 

Loss of three members 

• Minimum requirement: focus on Findwise. 
• Prioritized - detail this in Use cases.
• Impact of that - SRS document. 

Next meeting 

• Friday the 10th of March - feedback for document. 
• Reflective / motivate content should be differentiated from the main body of the text. 

Focus on the project as well.

• Create a nice product and do not only focus on the documentation. 
• Balance documentation/product wisely. 
• Try to reuse content from the PPD. 
• This is a core development phase, do not forget the product(!).