-
Notifications
You must be signed in to change notification settings - Fork 24
Weekly Meetings
Stefan Krüger edited this page Mar 21, 2018
·
87 revisions
- Minute taker: @sushmi
- Absentees: @ravi, @kreugers
- Deadline extended for Final report submission.
- Presentation demo is on 26th March, 10 a.m.
- Bring the notebook that was given during seminar phase for submission. You may get bonus points for making good use of the note. If you miss to bring the note on 26th, then it can be submitted til 29th.
- Merge all sub-group branches.
- Maintain consistency (In user study and testing part).
- Summarize the user study well. Ex: count number of participants.
- Do not add citations in abstract.
- Talk about the test coverage and flaky tests.
- In future scope add the incomplete tasks and planned but not done tasks.
- worked on test coverage.
- small UI changes.
- @abirke working on presentation.
- worked on documentation.
- test coverage completed.
- writing test cases.
- worked on Unit testing.
- Made to display Compare dialog as in eclipse. Have to display proper contents inside the comparison panels.
- Minute taker: @taran
- No absentees
- Next week the meeting is at 10 am.
- Everyone worked on Documentation.
- @ravishaw working on Unit testing.
- @rthorat worked on Advance mode and adding Clafer feature task.
- @abirke and @rthroat writing Javadocs.
- @ahmed-bt work on java project and done user test cases.
- @singh-tarandeep and @anusha completed the clafer part and working on documentation.
-
Code provider part left.
-
In advance mode, character has label.
-
Working on unit testing.
-
@kruegers google the test coverage tool to check the testing coverage.
-
Make sure create one branch as soon, so it can review.
-
There is no need for developer guide for UI. For User Guide, check the CogniCrypt.
- Minute taker: @abirke
- No absentees
- implementation
- TI group working towards a fully-functioning wizard
- CP group finishing implementation this week
- UI group finished implementation except some requests from Prof. Bodden
- documentation
- TI group working on documentation this week
- CP group Anusha has been filling the documentation, drafting will be finished until Friday night
suggestion by @kruegers: freeze the implementation at some point to be able to document it
- TI group freezing implementation on March 19th, to be able to fix minorities from March 12th, where the document will be send out, to March 19th
- will be held on March 26th, 10am in ZM 1-28
- will include a motivation part (about 2 minutes)
- will be less than 30 minutes in total
- @ahmed-bt implemented the jar file generator
- @ahmed-bt has been implementing compilation of the Java classes given by the developer
- minor bug-fixes
- work on the final report
-
this week
- finish the documentation
- implement the SPI
- write test cases
- @singh-tarandeep has implemented about 4 to 5 RCPTT test cases about the primitive integration that cover most parts of the UI
- @rthorat has been solving the issue in suggesting attributes in the XSL view
- @abirke has been working on validation
- @ravishaw has been writing UI test cases
- @ravishaw Should the UI test cases test pages individually or rather complete sequences of the going through the wizard
- @kruegers test different sequences through the wizard in a way that as many "branches" that can be taken through the wizard are covered
- @kruegers this can be done by combining different scenarios each of which is quite complex about one of the pages and implements the minimum necessary in the other pages
- @ravishaw questions can be reordered now
- @kruegers sync with the UI group this week, please
- problems in merging with the master branch have been fixed
- the ui branch is now corrupt, a new one has been established on ui-group-new
- the "compare algorithms" view can now show the diff of two algorithms properly
- Minute taker: @ravi
- Absentees: @anusha, @stefan
- Ravi: Dividing the questions to put into different pages logic implemented. Working on writing test cases for task integrator plugin
- Rajiv: Worked to fix the problem of Xsl page which was discussed last week. The problem is almost solved
- Andre: Created a pattern dialog box. Showed the work-ability of the pattern dialog box
- Ahmed: worked on new task code which generates JAR file of the provider. Worked on testing.
- Ahmed Should we merge with UI or Master branch?
- Lisa: Merge your branch with Master first and then merge with each other. The final idea is to push your things to Master branch
- Taran: Worked on clafer part and some part of documentation
- @Lisa asked everyone to specify their contribution till now in the project group.
- Ravi: Created the UI to receive questions details and for back-end part worked on the creation of the json file containing the question details given by the user in the UI.
- Rajiv: Initially worked on creating the general composites. Then mostly worked on the Xsl part
- Andre: Most of the commits are related to clafer part and monitored the UI framewrok
- Taran: Worked on some json related part, related to wizard, Some UI testing
- Sushmitha: Worked on the Default Algorithm Page, creation of the help button and the code preview page
- Anan: Worked on Compare algorithm page, beautification and alignment page
- Minute taker: @anan
- Absentees: @singh-tarandeep
- Ravi: solving problems in different question pages.
- Rajiv: working on the problem of xsl part, where to add text and to generate text.
- Abirke: Another way to add feature to the clafer file.
- XML is generated at the end of the task.
- Created two xsl file (cipher and provider).
- Will be doing the test cases for xsl and xml in coming days.
- Taran in on vacation.
- Anusha: Working on the wizard,task related to the UI and working on clafer.
- Sushmi: Code Preview page wizard page Advanced mode enhancement.
- Anan: Compare algorithm page
- Give clarity for the titles.
- Add motivation of the project.
- Implementation part: Details about the features of the pages and the details of that.
- Feature section: About the libraries, architecture and extensions.
- Design : what was our original plan,what we had done, what we didn't do.
- Do not repeat the sections.
- Minute taker: @rajiv-thorat
- Absentees: @singh-tarandeep, @ahmed-bt
- No exceptional update.
- Explanation of the constraint dialog question : Stefan: add the constraint on the higher level constraint. Check the other clafer features, and look for scenarios that may be more difficult to implement compared to the Enum.
- The Enum extending integer for the security feature is important. Question: Why don't we use the default syntax for enums where the contents of the enum are inline to the declaration.
- Next continue working on the documentation.
- Anusha wishes to give a smaller demo to Stefan. UI issues being fixed. Next will work on the documentation.
- Ahmed working on the Java project part.
- Taran working on the Clafer part.
- Question: On the browse button, what is the type of file that is to be selected. Ans: probably .jks.
- Comparision of the algorithms completed. Thinking about highlighting the differences.
- Confusion about what Sarah expected from her filed issue.
- Minute taker: @ahmed-bt
- Absentees: @singh-tarandeep
- Showed a demo
- In few weeks a user study will be conducted ( more probably at beginning of March )
- End of the implementation will be end of February
- Changes will be done for the High-level questions part
- Thinking about a recovering system
- Documents: JavaDoc, Developer guidelines, Report(user study), presentation
- RCPTT for the new high-level questions UI
- @Stefan: Potential unit-test : xsl attack does it produces a valid xsl document or not ? same for clafer model
- @Stefan: Labels on the checkboxes should be rephrased
- @Lisa: Try to have less boxes
- No improvements with the clafer model generation
- Java project: Get right methods
- XSL has not still been created
- Anusha + Taran working on the clafer, Ahmed works on the rest
- @Stefan: have you considered user study ? does it make sense to it now ? (@ahmed-bt: If it is finished in time, why not)
- @Lisa: English level must be similar among all the wizards
- @Stefan: change keys to keysizes, and add a note to explain the two type of the keysizes
- @ahmed-bt: not sure to finish everything in time by my own
- Trying to fix some bugs
- Added a scale for the security level
- Best algorithm (according to the user's answer) page has been included
- Info icon has been also added
- UI testing for next week
- Changing the code preview
- improve readability of the instance
- a browser button will be added
- @Stefan: Change algorithm to solution, add some note to explain the enabling and disabling of the checkbox on the advance mode page.
- Will the CP group some ui-enhancements
- Minute taker: @sushmi
- Absentees: @taran, @anusha, @abirke
- Sub-groups should show a demo of what they have done and should show their time plan for the remaining weeks on 29th of January.
- Try run for presentation on last week of March
- All the coding part should be completed before end of March
- Presentation can be done until second week of April
- @abirke working on clafer
- Writing file, checking for missing features
- Working to isolate unused features
- Now, compiling clafer file by using binaries
- @rajiv: Splitting XSL files. Testing the split function
- Creating an idea to validate text boxes
- Behaviour of wizard pages
- Currently, pages are static. Should make them dynamic.
- @ravi: Breaking high-level questions page
- Answers are linked to the questions box.
- Overridden the Next button. Now working on Backend
- JSON file has been created now while clicking Finish button
- Doing UI tests
- @stefan: Write unit tests to check the expected was happened
- User study was good.
- Changed the wizards based on the user study.
- Creating XML files at the end when the user enters information about the provider
- @anusha and @taran stuck with clafer
- Completed validation of the fields
- Aligned questions on one side and answers on the other side
- Aligned the lists and buttons for task three
- Changed the Info icon since the previous one was small
- Added back and next icons to switch the algorithms
- Added a menu to view previously viewed algorithms. But the page is filled up
- Planning to align the page differently
- @stefan: If it is not looking good then ignore that feature
- Comparison button is being added and working on it. Opens a separate window when the button is clicked
- Minute taker: @manakan-anusha
- Absentees: @taran, @lisa
- @stefan: Would only respond to emails once or twice a week during Christmas holidays.
- If any mail, mail to both Stefan and Lisa.
- Fix test issues.
- Update CP and UI branches.
- Working on controller
- Altering the way task.json works
- Made changes in a branch from master
- @stefan: Create a pull request
- @rajiv: Have doubts regarding CP-group task
- Does the user pick the provider name from the instance being generated?
- @stefan: Provider depends on the chosen algorithm, an algorithm depends on the user choice.
- Right now we only have one provider
- @rajiv: What should I expect from CP-wizard?
- We will contact CP-Group for further details
- Conducted user study previous week
- 4th participant user study on Tuesday
- Reviews: Scaling in the wizard-No indication, confused by the description box, instance list page pretty confusing.
- @stefan: Add more options
- rephrase other possible algorithm combinations
- @sushmitha: Mandatory fields in the wizard where not mentioned.
- Planning to add a mandatory field with the help of an asterisk.(*)
- @stefan: Make sure that the user understands what asterisk means
- @sushmitha: Add info icon(currently too tiny to see, will replace them)
- Thinking of adding next and previous boxes to the wizard pages which has many algorithms, thinking to filter the list and present few algorithms
- @stefan: Imagine we have 2 different algorithms. We would be having 30 combinations. Then the user should click 30 times
- @sushmitha: He still has the option of clicking the arrows and see only a few algorithms.
- Pop-up to show previously viewed algorithms.
- @Stefan: If applied then the current UI gets busy.
- @Stefan: Not happy with the pop-ups.
- @ahmed: Why not use a filter, by using the criteria given by the user.
- @stefan: But that is what instance list page is doing.
- If more providers then double the instances.
- @stefan: Cognicrypt tells you this is the perfect instance. If you do not agree you already know what to look for.
- The only goal is to ask more questions and make the task more easy for the user.
- User of CogniCrypt: Somewhat experience of java and no experience of cryptography.
- User study cancelled today.
- Dates of user study changed.
- @ahmed: Fixed some issues in UI.
- @ravi: Working on solving feedback from the user study.
-
- Try to create a json file
-
- Enhance the previous UI.
-
- Time: Will work 3 days a week.
- @rajiv: Finish advance mode, XSL
-
- XSL page: Found eclipse XSL editor.
-
- @stefan: Eclipse editor expects a user to write actual XSL.
-
- Would start off with skeleton things of what it should do.
-
- Jump into clafer thing if all these things are completed on time.
- @stefan: All tasks should have own XSL files.
- @anusha: Would work on clafer generator.
-
- Try to understand XSL working.
-
- Start off documentation.
-
- Understand how provider works technically.
- @ahmed: Start and finish XSL.
-
- User study updates.
-
- Create final wizard for the second part.
-
- Clean the code.
-
- Learn code generation.
-
- Time: 30 hours per week.
- @sushmitha: work on properties displayed in an instance details in a more better way.
-
- would work on the issues.
-
- Would work on the new previous and next buttons on the algorithm page.
-
- Time: 3 weeks
- @anan: Work on the issues.
-
- work on Advance mode.
- @Andre: Clafer serialization
- offline from 24th December to 2nd January.
- @ What about progress in testing?
- TI group has written 2 test cases. what are those?
- @andre: One about clafer syntax and one about clafer variable.
- Figure out what the test cases are doing and fix them.
- If you leave the tests then the new person should understand how they work.
- Make sure you have synchronization in testing.
- UI group: No testing plans currently.
- Currently its just the text field.
- Implement some criteria or validate the field.
- You can get some meaning full test cases.
- Minute taker: @ravishaw143
- absentees: @rajiv-thorat, @taran
- Announcements
- Sub-group reports
- Lisa will be back next week
- @ahmed: 4 person in the group will be busy in writing the seminar paper, so they will give less time to the project group this week
- Anusha & Taran working on the clafer part
- Ahmed started working on new wizard
- Ahmed targets to complete the Xsl file part during holidays
- @ahmed: Thinking to create Xsl file for each primitive for the providers
- @kruegers: Try to create one Xsl file not seperate. Xsl files for cipher, digest needs to be created seperately
- @kruegers: Don't spend too much time on Xsl tutorials
- Replaced Combo box
- Removing maximize button is not done
- @kruegers: Disable the maximize button for first few pages & enable it for the last few pages?
- @lisa: Consisting issue
- Code preview page background should be white
- @andre & @lisa: V_SCROLL for TLS task
- Framework for placing the file in right place
- @andre: Working on clafer dialog , disabling the OK button when fields are not filled
- @ravi is working on high level question page dialog
- Ravi explained to andre the work-ability of RCPTT
- @andre discussed whether the code dependencies in Json file should be an array or not. As no case was found where multiple code dependncies are defined for an answer.
- Auto generation of code dependency field name and boolean value discussed
- Minute taker: @abirke
- Sub-group reports
- recent work
- decorations added
- default algorithm in algorithm list shown as a label
- introduction of radio button as a question type
- code preview
- help content for the sidebar
- @kruegers: The html file for the help content should be generated when clicking on the question mark. The xml file referenced from the source code should only contain a dummy link.
- next week: user study
- future work
- add a slider for the security level
- change the naming of security levels
- user study was conducted with one participant, more appointments will be made
- recent work
- Clafer dependencies
- discussion on Eclipse locations
- @kruegers: getResourceFromWithin method is supposed to work with both the run configuration Eclipse Plugin when built from the source code and an installed version of the CogniCrypt plugin
- unit tests including SWT dependencies fail with an error referencing 32bit libraries of SWT
- @kruegers: remove 32bit builds if that solves the problem
- see issue #122
- Minute taker: @anan
- Absentees:Taran
- Announcements
- Sub-group reports
- Next week meeting time with Stefan is from 1 pm to 3 pm.
- Lisa is not for the next week meeting.
- They will put the screen shot of user interface of the advanced mode alignment in GitHub.
- The default algorithm from the last wizard page should not be excluded.
- First User Study is finished.
- Discussed about the user study with stefan and Lisa.
- Lisa asked them to include both bottom-up and top-down approach if possible.
- Some text of syntax can be included or some examples can be given so that the user can use that or edit it and use.
- Stefan asked them to include the Graph library to visualize like a tree and in the graph view the user can add the properties and constraints.
- They suggested changing the xsl file that is shown in the UI.
- Next week they will be doing the controller things and starting with the back end.
- They will be parallely working with the feedback from the user study.
- Their First user study is on Wednesday.
- Three of the group members will be there for the user study.
- Ahmed will be working on the new wizard.
- Taran and Anusha will be working on the clafer thing.
- Minute taker: @ahmed-bt
- Absentees: no one
- Remote: @lisa
- Sub-group reports
- General remarks
- Updated version of the protocol of the user study has been forwarded to Lisa & Stefan
- Lisa: The protocol is way much better than the previous one. The protocol is very good, nothing has be to be changed
- User study is scheduled to be done in 10 days ( 15th November )
- Stefan have found participants for the subgroup user study. List of a couple of emails will be sent to the group soon
- Number of participants has been changed from 2 to 3 to have better results at the end of the user study.
- Lisa: you have to ask UI group about the prototype for the user study !
- Taran made the RCPTT work and testing was successful
- Ahmed: Tried to get the list of the developer project methods using reflection but it was impossible
- Stefan: you can look for AST (Abstract Syntax Tree) Parser/Visitor API
- Anusha prepared some questions about Message digest, and she will support the team with a document about some engine methods. She has to post the question on github and tag Stefan for a review.
- Worked lately on the user study ( Fixed some issues and made some changes )
- all members will handle the user study and takes notes (on Andre's machine)
- Lisa: make sure that one of you is the main contact with the participant
- User study: a room has already been booked, it will be done on Andre's machine, and recording the screen from Virtual Box will be used.
- The group had lately merging problems with the new version of the master. The problem is now almost fixed.
- Anan completed advanced mode arrangements.
- Working on the last wizard page will be the task for this week.
- Stefan: Try to implement Ravi's suggestion
- Stefan: Read a json file, then create a temporary html file, and later show the help content
- Stefan: you should merge the ui branch into the master, it may be helpful for other subgroups
- Make sure to work 20 hours per week.
- Achieving all milestones and working less, it won't affect your grade. However, if the final work is not finished in time, then fulfilling 20 working hours per week (or not) will affect your grade.
- Setting time blocks in your schedule will help you more to achieve the weekly 20 working hours.
- no meeting on 18th December ( last meeting this year will be on 11.12.2017 )
- The first meeting of 2018 will be on 08.01.2018 if Lisa is available, otherwise it will be on 13.01.2018
- Minute taker: @taran
- Absentees: @sushmi21 @stefan
- Remote: @lisa
- @ahmed: Discuss about protocol and prototype send to @lisa and @stfan for review. Going to give two algorithms to users 1 is Blowfish and 2nd is custom algorithms.
- @lisa: When are you planning to do user study?
- @ahmed: 15th November.
- Creating new wizard for user study.
- @taran is working on UI testing using RCPTT plugin and created the new prototype for user study.
- @anusha is working on protocol and message digest questions which will review by @stefan.
- Milestone:
- @ahmed: We will start with XSL file and the wizard for next step.
- Good thing that we have the prototype for next part which is created by @taran.
- @anan: Last week working with help button on the wizard and its working now. Change the combo box to radio buttons and then change the alignment. Working with description part but the description is not yet confirmed.
- @lisa: Two questions.
- The help button covers complete wizard or on some wizard pages?
- @anan: In every page, the help button is coming but the relative content is not done yet.
- @lisa: you started working on text?
- @anan: No, we were working on description box.
- @lisa: When you have something that is working but missing content, make sure you push it so that everyone can see it.
- @anan: Next week we are working on description box and also we are trying to change the YES/NO questions from the combo box to radio buttons.
- @lisa: Also remembers one of the subgroups start their user study and you have to help them, so did you guys working on together?
- @rajiv: We were planning with UI group so that show them protocols and they also give us some feedback.
- Milestone:
- @anan: Finish the preview button.
- Work on issues currently present on CogniCrypt.
- @rajiv: We stuck with merging issue so we are trying to solve it but not completed yet.
- @rajiv: @ravi and @andre working on bugs in the popup and solve it today and @rajiv is working on setting the milestone for October up to date and setting up for November. In November we will be concentrating on the backend.
- @ravi is working with high-level questions.
- @andre has been working with Clafer.
- @rajiv worked on non-guided mode page and continue working on the backend as well.
- @lisa: Hows testing going?
- @ravi: Last week I started looking at RCPTT tools. Later I got clafer feature from the clafer page, so I stop working on testing and started with high-level question page.
- @lisa: @ravi and @taran should meet together cause they are working on testing.
- @ravi: If we have some issue using RCPTT, somebody here who can help?
- @lisa: If you have any question just mail us.
- Minute taker: @sushmi21
- Absentees: @taran @ahmed
- Remote: @lisa
- Problem with XSL popup is fixed for user study.
- What is the role of UI group in our User study?
- @Stefan: Help in preparing the study protocol and will give some feedback about it. They can only say how the study should be done.
- @lisa: They can be there during the study, if they need. But there should be only 2 interviewers per participant.
- We have started working on controller part.
- @Stefan: Have you completed the prototype for the study?
- @Stefan: What is the time plan for backend?
- Working quicker than expected.
- Modify the UI after the User study.
- Next week's plan: Work on User study
- Anusha -Working on message digest questions, Ahmed is preparing 3 algorithms for the User study and Taran is writing sample test cases.
- @Lisa: If you need help in writing test cases, please let us know.
- @Lisa: About the User Study protocol, 'Giving 3 algorithms and giving 15 minutes to understand it' What does it mean?
- The algorithms will be in indirect way.
- @Lisa: Is it a brand new algorithm? How will you measure if the tool is 'visually appealing'? Ask questions to the users to find the answer for this. For efforts: How many times they tried? How long they took?
- @Lisa: Questions in Questionnaire session are vague. Rephrase them.
- @Lisa: When is the study?
- @anusha: 15th November
- @Stefan: Has Ahmed handed over the clafer model?
- @anusha: He is working on wizards. He will divide tasks into minor tasks and will give us.
- @Stefan: Taran and Anusha should have a clear idea about what Ahmed is doing. Please communicate with each other properly.
- Have added tooltip to Input fields and description for some questions.
- Adding Help contents to the Help view that gets displayed when the help button is clicked.
- @Stefan: Why do you need Help? Tooltip will be providing the description, so what is the purpose of help?
- Tooltips are added only for the input fields. Help will be added describing all the questions and answer options.
- Worked on Code Preview button, but the pop up is not showing the code now.
- @Stefan: Copy some parts of code from XslBasedGenerator class and try it.
- The Help contents are stored in html file and they are referenced from an xml file. Extension points for those xml files are added in plugin.xml.
- @Stefan: Try storing the contents in json file.
- Minute taker: @manakan-anusha
- Absentees: @taran
- Remote: @lisa
- Announcements
- Sub-group reports
- We have build server.
- Now is the right time to start writing tests.
- Stefan: I will constantly ask for the reviews about the tests.
- Added description box in the first wizard page. Now if a task is selected from the combo box, a description of it will be displayed below it. Currently, only sample text is added. Exact text description will be added with some help.
- Stefan: Come up with the description and I and lisa will comment.
- The advance mode check box has been modified. the name advanced mode has been misleading the users when we did the user study so we changed it.
- A button for code review is added in the last wizard page.
- This will display a pop up with the code that will be generated into the java project.
- @Stefan: Why only pop-up at each stage ? Why not pop-up at every question?
- @Stefan: Add the Screen shot's of code preview of the consequences of every page.
- @Anan is working on the tool tip.
- The issue related to UI group has been taken over by @ahmed but now will be solved by the UI group.
- @Lisa: Where are you adding the changes?
- @Sushmitha: Current version of CogniCrypt.
- @Lisa : Reviews on User Study Protocol
- What kind of things are you measuring?
- What is the name of your character ?
- What do you consider as success?
- @Rajiv: Pretty subjective in mind. If they go through the task without any interference then that is the measure of success for us.
- When is the user study?
- Rajiv: Stuck on two things Pop-ups by @Ravi and @Rajiv.
- By next week we hope we have the user study.
- We will send you the details of the participants by next week. You can contact them.
- Stefan: How is the test writing going on?
- Difficult to come up with tests.
- @Stefan: ui.testplugincall.rcptt. Its a bit buggy.
- rcptt tests in CogniCrypt are a bit outdated.
- They should give an idea how it works.
- We have protocol.
- User Study: The user will have to answer some questions from the ui related to the custom algorithm.
- We are planning to have two test-users; one with average cryptography knowledge and the other would be cryptographic expert so that we have different reviews.
- Stefan: You can get valuable feedback from Cryptographic expert.
- Stefan: Are you sure wheather the questions are right? You should be sure as you have read the documentation.
- First do the user study with symmetric ciphers and then contact the cryptographers.
- Send us the protocol by mid of the week.
- Stefan: Any testing reviews?
- @Taran is studying about testing and helping us.
- Oct 28th ( Skype meeting by Lisa)
- Stefan: I have finally got the other plugin integrated. Merge it into the master of your local repositories subgroup. For UI its easy as you have only 10 commits. For other groups it will be tough.
- Minute taker: @anan
- Absentees: @sushmi21, @lisa
- Announcements
- Sub-group reports
- The meeting room for next week is F1.310 in the HNI building.(till november 6).
- For the first 4 weeks the meeting hours will be from 9 am to 5 pm.
- Afterwards from 9 am to 4 pm.
- Should show the updation on friday.
- Send the document of the protocol to lisa and stefan.
- Should have an idea about the connection between Cognicrypt and their work.
- User Study:
- Number of participants: 2 or 3
- Participants: Mix of people(know about CogniCrypt and do not know CogniCrypt)
- Question: 15 minutes duration
- Clafer part:30 minutes
- XSL part: 30 minutes
- Expectations from User Study: Usability feedback from observing the users, suggestions,are they able to complete the task
- Lisa: setting limited time is not a better option.
- Cris will be there as an participant to give feedback n the actual tool.
- Protocol should be stend before next week.
- They will do their User Study within one month.
- Next week they will be ready with the protocol.
- Make an interface within the group members.
- Minute taker: @rthorat
- Absentees: @sushmi21, @anan, @RaviShaw143, @lisa
- CP September milestone report
- Sub-group reports
- General remarks
- The wizard is not yet complete. Currently working on Symmetric block cipher.
- Stefan: what is the behavior when the possibility of more than one key is selected? Ahmed: The UI to update the ranges for all the keys will be displayed.
- Ahmed: how detailed the description of the algorithm be? Stefan: Doesn't really matter, but a short one (60-80 words is preferable)
- The name of the algorithm can be read from the Clafer file, the author information can be asked off the user.
- Ahmed: how may keys are possible. Stefan: difficult to say.
- The implementation of generating the Clafer model is not completed yet.
- Next: Start working on the provider, and attempt the catch up till the next milestone.
- [IMP] Stefan: make sure to define the interfacing data structures between classes so that everyone can continue working independently on their assigned tasks.
- Showed the approximation of the contents and the expectations of first user study.
- Next: target to finish the user study document and send it to Stefan and Lisa along with the UI group. Begin working on the Controller classes until the feedback on the UI.
- Date: September 26th, 2017
- Minute taker: @abirke
- Absentees: @singh-tarandeep, @sushmi21, @anan, @manakan-anusha
- Remote: @lisa
- Feedback Design Document
- Sub-group reports
- General remarks
- encorporate a revision of the evaluation part in the final document
- plan for more time for the final version (also consider exams, paper assignments, ...)
- also consider the final presentation, have a dry run
- send a revision of the document to Lisa and Stefan, if desired
- give access to the document repository, if available
- presentation of the current UI implementation
- @kruegers: do not mention Clafer in the UI, the user shouldn't be required to know about it
- @kruegers: consider guiding the user, if views are very busy, where is he/she supposed to start?
- @kruegers: can any details in the Variability Modeling page be left out? it seems busy
- @rajiv-thorat: evaluating integration of the Eclipse editor into the plugin
- seems inconvenient
- @rajiv-thorat: Look at the high-level questions draft as a tabbed dialog. We came across a doubt, here. The linking questions tab might be unnecessary UI when users haven't created all the questions yet, so it might be moved to an isolated dialog.
- @kruegers agrees, but changes can be postponed
- @Lisa: views are not necessarily too busy, stick with the current ideas and discuss them with the UI group before user evaluation
- presentation of the current dialogs implementations
- @Lisa: did the UI get validated by the UI group?
- yes, as mock-ups, so far, the implementation doesn't deviate
- @kruegers: will you be able to catch up until the next milestone or drop features?
- will catch up, next milestone is on backend implementations
- @ahmed-bt finished working issue #40, keeps working on the wizard
- progress of the other team members has to be discussed
- next milestone: wizard and creation of the Clafer model
- Ahmed's part: link clafer model to the wizard
- the others were supposed to prepare the backend
- @kruegers: send an update to Lisa and Stefan about what the others did
- @ahmed-bt: if updating the wizard finished, would starting on the user study earlier make sense?
- @kruegers: do not conduct a full user-study but rather a user test on particular parts of the current implementation
- @ahmed-bt: the milestone will most likely not be reached in time, linking the Clafer model to the wizard takes too much time, catching up with the milestones will be possible
- Team members have to catch up with their working hours when sick or absent
- If absent, give feedback about the progress to the sub-group lead for them to be able to pass it on during the meeting
- Consider the working hours for the project group when choosing courses for the next semester. The group will have to agree upon a meeting day.
- October 3rd is a public holiday. The group will agree on an alternative meeting next week.
- Date: September 19th, 2017
- Minute taker: @Ravishaw143
- Absentees: @singh-tarandeep, @sushmi21, @rthroat, @anan
- Remote: @lisa, @ahmed
- Announcements
- Reviews of Design Document
- Sub-group reports
- Seminar phase performance of each project member has been evaluated. All members will get to know their grades within this week.
- Design documents grade given - 2,3
- @kruegers : Finished almost all my trips so won't be cancelling the meetings. October last week meeting could be cancel.
- @kruegers : Description part was good. Evaluation and Time planning sections lacked concrete details. Concrete feedback will be given by the end of the week.
- @lisa : Gantt charts were not readable in the design doc
- @anusha & @singh-tarandeep : Working on clafer model
- @ahmed is working on wizard which will be displaying more than one questions in it.
- @kruegers: look in the existing code of CogniCrypt to get help. Specifically look for Package name AbsConstraint in that look for a Class called InstanceGenerator.
- @ahmed is working on an issue 40 and has commented on that issue
- @kruegers: keep focusing on milestones. How are you gonna show the milestones achieved?
- @anusha: Thinking to update the design document to show the milestones achieved
- @kreugers: If you decide to update the milestones in Design document then all groups should update their milestones in design document only.
- @abirke: Don't agree with updating the design document to show the milestones as it does not give technical supports compare to what we get in github or gitlab.
- @anan said @anusha to report the following:
- working on issue 91
- Will be changing prototypes to come up with a improve UI and then present to lisa
- @kruegers: Prototypes should be mail to me also.
- To come up with user testable UI by end of this week
- @rthroat is working on reusable feature of Clafer functionality
- @Ravishaw143 is working on code insertion part of Xsl template
- @abirke is working on dialogs feature
- Next week plan is to have part of the UI user testable with dummy data
- To have a detailed user study of Clafer related UI as this is the complex one
- @lisa asked about the user needed to carry out the study.
- prototypes of the UI to be sent to @lisa and @kruegers
- Date: September 5th, 2017 - 1 p.m.
- Minute taker: @singh-tarandeep
- Absentees: @RaviShaw143, @sushmi21
- Remote: @lisa
- Announcements
- Sub-group reports
- Stefan will let us know about next week meeting.
- Stefan will be on a vacation for two weeks.
-
@ahmed: Presented the first milestone.
-
Total three milestones:
- Creation of Wizard
- Creation of Clafer
- Creation of Provider
-
The wizard prototype reviewed by UI team.
-
We create new JSON file containing all the questions and then we started implementation.
-
Explained the updated prototype after UI review.
-
@kreugers: What if you choose Asymmetric (step: 2/10)?
-
The second question on that page should disappear.
-
@kreugers: What happens if I click on check examples?
-
@ahmed: Explained about the wizard and prototype.
-
@kreugers: How do you know in advance about key size?
-
@ahmed: Maybe we can give them the range of key size.
-
@kreugers: You give them just regular text field and a + button and allow the user to enter and add.
-
@ahmed: We can give radio buttons for range value.
-
Explained about modes of operation in multiple check boxes.
-
@kreugers: Add another checkbox and allow the user to specify their own mode of operation. But for now, this is good.
-
@singh-tarandeep: We can add an extra checkbox with named other.
-
@ahmed: For next page, we are not sure about the classes yet.
-
kreugers: They can have one class with 2 methods. Maybe instead of asking for classes, ask for methods.
-
Created json files for block cipher, message digest.
-
Added a button in CogniCrypt wizard. Finished our first wizard page to show the type of primitives from which we can go to a specific page. Currently, working only on one cipher type.
-
Adding provider - @anusha will be implementing the CSP's mockup.
-
@lisa: Are you updating on the shared repository?
-
@ahmed: yes, before working update everything.
-
Creating new mock-up and it will be shown to Stefan as soon as possible.
-
Current Plan:
-
Updating Wizard that matches the prototype.
-
Working on issue 40.
-
Create clafer model.
-
Creating a provider mockup.
- First wizard page working by @rthroat
- Getting an idea of infrastructure and UI part.
- @kreugers: What in force guided mode?
- Explained about the changes that @rthroat made to the code.
- @abirke worked on pop-up
- Able to set clafer constraints in a similar way of featureIDE.
- @kreugers: Asked about problems facing in it.
- @abirke: We want to generate clafer syntax or try to pass UI to java code.
- @kreugers: Get regular clafer model because at one point you just need .cfr. You can also watch featureIDE in CogniCrypt as they are using binary.
- Current Plan: Next week probably Clafer. If we have clafer then we have a solid base for next pages.
- Present prototype to @lisa.
- Explained about the newly added task description for easy to understand.
- @kreugers: Do you switch the change?
- @anan: If a checkbox is selected it will take to beginner mode.
- @kreugers: There should be beginner mode by default.
- Explained about the wizard.
- The three questions come in a single page.
- Explained the wizard page showing first basics of instance detail and then briefly after pressing show more button.
- @Lisa: Can the user edit the text?
- @kreugers: I don’t think to allow the user to edit the detail. Just give the filter.
- @anan: Only for padding or every option.
- @kreugers: Don’t make one filter for each option, make one filter for all options.
- @kreugers: What is in TI compare tab?
- @anan: Nothing we haven’t do anything here yet.
- @kreugers: Make sure you merge Master branch first so that others can merge after.
- Date: August 29th, 2017 - 6 p.m.
- Minute taker: @sushmi21
- Absentees: @RaviShaw143, @anan
- Remote: @kruegers
- Announcements
- Sub-group reports
- Next week the meeting will be at 1 p.m (Note: It can also be earlier or later. Lisa will let us know by Monday).
- Stefan will be available for the next week's meeting.
- Stefan will be on a vacation in two weeks.
- New prototypes reviewed by UI group and changed it again.
- Created packages and classes for current milestone ending on 5th of September.
- Created json files for block cipher, message digest.
- Added a button in CogniCrypt wizard. Finished our first wizard page to show the type of primitives from which we can go to a specific page. Currently, working on only one cipher type.
- Will finish implementation next week.
- This milestone was to create wizard pages dynamically. i.e. json file created depending on the type of primitives and questions in pages.
- @kreugers : Are you reading the content of the wizard page from a file?
- Next milestone to create clafer model.
- Adding provider - @anusha will be implementing the CSP
- Creating new mock-up and it will be shown to Stefan as soon as possible.
- Next week: Milestone review
- Sent pull request for issue 41. Found an issue while merging so altered the code slightly.
- Explained about the changes that @abirke made to the code.
- Maintaining a list of pages instead of maintaining a list of questions. The object of the question will be passed, so that the method could be accessed.
- Milestone : Created Basic infrastructure. i.e.Created packages and basic classes inside it.
- Finalizing the mockup is the next milestone.
- Pencil prototype was created and got it reviewed from UI group.
- Showed and explained about the functionality of each page in the prototype.
- @kreugers :
- Will the wizard page change dynamically? What are the other options in the dropdown?
- Will the library location text field be hidden?
- Explained about the pop-up
- @kreugers :
- How will someone, who does not know about clafer, understand abstract and concrete?
- Better to give it in Object oriented terminology like class and instances.
- Will the complex clafer be in one screen?
- @lisa: Have a page that behaves like an index
- @kreugers : Maybe give like a tree overview
- @ahmed-bt : Add a button to help two tasks which only slightly differ. Help in click reduction.
- Explained about the pop ups separated by tabs.
- @kreugers : Will it also show the questions along with hashes?
- @lisa : Why do you want an id. As an user, it is easy to remember the question I asked than remembering some string. You use the id in background and show only the question.
- @kreugers : Will you be running coherence check on free text fields?
- Validation will be done at every stage.
- @kreugers : How will I encode code options?
- Explained about Creating XSL file UI.
- @lisa : Do you have any checks for adding invalid texts?
- Checking will be done in the background.
- @lisa : Opening code in eclipse editor is better. Think about high level display and editing of XSL.
- @kreugers :
- Translate the commands in XSL.
- Make it more abstract with may be if commands or something like that.
- Showing code is fine but reduce number of XSL commands
- Explained about grouping existing features.
- @kreugers : Explain what is grouping to the user
- Started working on next milestone. Creating fragments of UI in a class.
- Did a presentation about the results of the user study.
- Explained about the protocol and purpose of the study.
- The drawbacks in the tool observed during the study was presented.
- Asked for the clarification in the question : 'Will your application regularly encrypt data chunks of several gigabytes?'
- @kreugers : The question means 'Will the encryption be performed regularly on several gigabytes'. It does not mean that the encryption is performed regularly or not.
- @Lisa : The results are very good. How are you planning to use them? Will you come up with entirely new UI ?
- We will add descriptions for the answer option.
- Add some tool tip or information.
- Reformulate the existing questions.
- Asked whether changes in the Instead details part could be made. Can we show only security and performance? Can we show only less number of algorithms?
- @kreugers :
- Check if the instance details part is really editable. I don't think so it is editable.
- Number of algorithm can be reduced at least in beginner mode. Can have one algorithm combination from per security per performance.
- You can show only the default one or come up with some other idea
- @lisa : May be a question is added telling the user that this the default one and do you want to view the other available combination.
- Why is it showing the algorithms with medium security, even after selecting (during task configuration) the security level as very secure?
- @kreugers : Then open an issue in gitHub and report it.
- Date: August 15th, 2017 - 6.20pm
- Minute taker: @ahmed-bt
- Absentees: @RaviShaw143, @singh-tarandeep, @sushmi21
- Remote: @kruegers
- Announcements
- Sub-group reports
- No meeting next week
- If needed, request Lisa for a meeting
- Tasks are already decomposed and added to github, but it looks like it was not a good idea. For this reason, everything is migrated to gitlab for now
- @kruegers: you can only close issues, not delete them.
- highlight issues will be kept in Github
- It would be wasting of time, if issues will be migrated back to github in another repository
- @kruegers: Keep the high-level issues in the github repository, close the very granular ones, and for code reference the issue in your commit message.
- First milestone: Create all the models and classes + paper prototypes
- Second milestone: Create all the views and link them to the model : in September
- @kruegers: if you will have to share some documentation, then I would rather go with extra repository like CP is going.
- From September until January/February the subgroup will focus on the business logic
- @kruegers: Patrick has reviewed your issue, and I will review it it the following days.
- 2 Situation will be given to the user
- The user will be allowed to use the google set
- By next week, 3 user studies will be finished
- @Lisa:
-
- Finding out someone who's confused might help you to have more accurate results just by being there.
-
- will review the protocol
-
- The current plan is very fine
- Next Saturday is the first user study
- e2 guidelines have been mentioned, what are they about?
- @kruegers: They are recommendations for crypto experts on how to prevent side-channel attacks and so on. Most likely they will be provided as text files which means that if the CP group has to implement an interface to display those guidelines, it will probably just show text.
- the group created a public GitHub repository
- @kruegers: Private ones can be created within CrossingTUD. The CP group's repository will be moved there.
- studying implementation of new cryptographic primitives
- milestone: dealing with symmetric encryption (either this or next month)
- @kruegers: Don't spend too much time on mock-ups. Begin implementing. Only then, constructive feedback can be given.
- first milestone: creation of the CP group-specific wizard
- @kruegers: What will be done until next week?
- create Java packages
- create the wizard
- collect further questions
- @kruegers: The new wizard should be pointed to (by a button, for example) from CogniCrypt's main wizard ("Integrating a cryptographic component"). There, a user should be able to decide between a new task or primitive.
- Date: August 8th, 2017 - 1pm
- Minute taker: @manakan-anusha
- Absentees: Ravi
- Announcements
- Sub-group reports
- Meeting timing next week(15-08-2017)-Skype meeting-6pm by stefan.
- White board- Email sent by the mentor
- Created a new container page,hardcoded the json files,match the containment.Changing few validations.
- @kruegers:If the next page is sequential, why do you need a next id on the page
- @rajiv: Good question
- @kruegers: The next ID automatically links to the next page. We still need something.
- @abirke: In case we have a merge point later, the page movement would not be sequential, and the next page id needs to be saved
- @rajiv: Reviews on design Document
- No formalization on exactly what we should do.
- @lisa: Reviews on the Design Document
- No need of much details in the Design Document.
- Check whether the goals are in scope.
- Decision on one main goal.For example the creation of stub for c/c++(CP group responsibility) is a huge task.
- Milestones where not defined in the document.
- Decision on empty milestones,monthly presentations.
- Only smaller objectives defined ,defining a set of clear milestones.
- @rajiv: Rethinking of the designed plan. We would prefer to work on the most difficult wizard page. Make the code that is running in the background more robust rather than concentrating more on the user studies.
- @kruegers: More better solution is testing a subset. Just having the UI some other way. Doing some random test without actual implementation.
- @lisa: The intermediate study will not be an actual study. Analyze of the users how they understand the UI.
- @lisa: The implementation of the subgroups should be going in 2 different directions: Coding,UI design. The UI can be tested without the hard code. Models for the back end. Similar UI design in the front end.
- Current plan: @rajiv
- Getting the answers and creating json file.
- Link to XSL.
- Creating a UI for clafer.
- Creating a UI for XSL.
- @kruegers: Divide the tasks into smaller tasks. Pen an issue and assign it to your respective subgroup members.
- Creation of Prototype(Reviewed by UI gROUP)
- Explanation about the design of the prototype.
- @ahmed: UML diagrams to understand the sequence of working.
- Explanation about the Code Extraction.
- @kruegers: Mock integration of block cipher.
- Implement the creation of own provider.
- @lisa: Do not overload the pages nor have pages with single questions.Based on the reviews of the user study 1 code can be changed. The goal of code analysis is a complex one.
- Reviews on the Design Document CP part: Huge Text fields in the prototypes are not good.
- Next week goals: Wizard complete by next week.
- @kruegers: Reviewing the diagrams is not necessary by the mentors.
- @lisa: Finalize the planning.Documentation related to the project should be kept in one single place. Milestones should be defined in one single file and compulsory access to the mentors.
- @kruegers: Try to implement as many engine classes as possible.
- @sushmitha: Two types of prototypes created.
- One will be created by @sushmitha the second prototype will be created by @anan.
- By the end of next week the prototypes will be implemented and the user study will be conducted.
- @Lisa: Asked for Schedule ,plan, number of users,materials.
- Usage of a software which will be able to record video for a long time.
- @sushmitha: Can we give working prototypes for the user or implemented tool.
- @lisa: Better to give the tool to the user.
- @anan: Weekly milestone
- Two different tools.
- Suggestion on user studies by @lisa
- Do not compare the current UI to the designed UI.
- @Lisa : How easy was it?
- How many prototypes will you test?
- How long will be the task?
- How long are you planning to to give him the task?
- metric for measurement?
- What is wrong with the current UI?
- Couple of questions related to every wizard should be defined.
- Date: August 1st, 2017 - 1pm
- Minute taker: @abirke
- Absentees: Ravi, Lisa
- Announcements
- Sub-group reports
- AOB
- the design document will be reviewed by end of August
- there's another reservation of the conference room every other Tuesday from 11am to 12pm (starting on August 8th, 2017), other than that, the room is booked until the end of the year
- currently working on issue #41, conceptually the solution is set, it will be continued until next week, if major problems come up, splitting up to start with issue #11 is reconsidered
- creation of prototypes is in progress
- planning on conducting a user study this month using the UI prototypes created so far
- changes to the UI that are suggested in various issues are reconsidered when user feedback about the new drafts is available (for example issues related to the advanced mode)
- current prototypes are developed in Pencil
- @kruegers: Prototypes might rather serve discussions among developers of CogniCrypt, but are hard to use for evaluation by users. An actual implementation would be more suitable to be presented to study participants.
- @kruegers: study participants with Java knowledge can be found among the students, if cryptography knowledge is needed, members of the department are willing to participate
- room bookings for studies can be done via @kruegers
- issue #25 is resolved
- issue #40 has been revised, it is now in revision by @kruegers
- custom providers will be kept in a textfile in the repository as a start
- concerning main issue #13
- an advanced mode does not seem to be needed
- manual editing of files by the cryptographer is not needed
- issue #14 is to be seen as an extension to #13
- today's work: conceptual work on integrating new providers
- signing providers for testing? implementations can be tested either way, but providers can be signed by the department supposed to be integrated at some point
- @kruegers: roadmap for differentiating between provider-based implementations and others
- given a jar-file decide whether it contains a suitable master class for a provider
- do a context switch in the wizard depending on whether one has been found or not
- workflow without providers should be targeted first
- until next week: prototyping, discussion with the UI group, preparation of the implementation
- rough estimate for the implementation of a wizard for non-provider-based algorithms: 45 days
- student assistents' work in the department
- @CCPah
- build server management and configuration
- new task on user authentication (currently discontinued)
- has ideas on merging questions into single pages
- @anson91
- new task on trust establishment
- new UI widgets might arise (will be announced by @kruegers)
- connection test in the TLS task (contains a button as a new widget)
- @CCPah
- issue #47 (blank window)
- details on reproduction should be gathered by the TI group
End: 1.32pm
- Minute taker: Ravi
- Attendees outside the SICS project group: Sneha,Patrick
- Absentees: ___
-
Instead of having "Compare two" and "Compare all" button have one compare button which allow user manually to select the algorithm they want to compare.
-
Decide when intermediate UI study to be done for all the groups.
-
User study tip-
-
what do you want to find out?
-
What do you want to measure?
-
Carry out the user study even its not complete to figure out what user liked.Though it is not complete.
-
UI group should be up to date about the functionality of the other group functionality
-
Add a wizard page giving the option to keep the default instance or they can change it.
-
Reform the question in the beginner mode
-
Specify somewhere in the wizard about the order in which instance list is shown
-
Prepare different prototypes to select among them
- Minute taker: Anan
- Attendees outside the SICS project group: Sneha, Patrick
-
August 13th to September 15th Stefan is not in Paderborn
-
From September 1st for 3 months lisa is unavailable
- August 15th & 29th Lisa will handle meeting, Stefan patched in through Skype
- August 22snd either handled by Lisa alone or cancelled
- September 5th Stefan will try to set up a meeting
- September 12th cancelled
-
In clafer file: take input from the user by giving options(Algorithm from JCA or custom library)
-
XSL file: For JCA algorithms the whole code is taken from the XSL file so user don not want to type the code.
- Tuesday 9 am every week.
- Minute taker: Rajiv
- Attendees outside the SICS project group: Sneha, André
- Absentees: Lisa, André
The UI should
-
accept the type of algorithm being integrated
-
allow the creation of a new provider, or integration into an existing custom provider
-
accept a name for the algorithm
-
accept the binaries/code for the algorithm being integrated
-
analyse the code, to identify the public methods based on the type of algorigthm. Save the identification
-
check the existing clafer files for the type of algorithm being integrated, and update the file with the required data
-
send an email out (?) [unsure who the recipient should be]
-
[CP group] Please add/update any point if I missed any, or if you have any concerns.