-
Notifications
You must be signed in to change notification settings - Fork 30
Project Management
Michael Jastram edited this page Dec 4, 2015
·
235 revisions
This page provides an overview of the project status of the openETCS toolchain workpackage. In particular, there will be one section for each sprint. New sprints are added on top.
- Itea Slides: The slides for the final review have been uploaded. @all, plese review them.
- Demo Script: I created #512 for the demo script. Please help to complete it.
- WP7 artefacts: We created a list on our wiki entry page. All committers, please review and add missing artefacts.
- Product Backlog: We will shortly close three WP7-related backlog items, US-Traceability, US-Scade-to-Open and US-Toolchain-CI-Automation. Please speak up if there is a reason not to do this.
- Closing open issues: We're in the process of resolving open issues - there are just 5 left. Please help by reviewing and closing your issues.
- US-Traceability: Review has been concluded, thank you for everybody involved!
- US-Scade-to-Open: Review has been concluded, thank you for everybody involved!
- Workshop Munich: At the workshop in Munich, we revised the slides for the final workshop and decided on a demo scenario. More information will follow soon.
- ReqCycle bug resolved: David discovered a bug in ReqCycle, which was resolved with the help of Raphael.
- New Nightly Build: We included ReqCycle in openETCS, and we added the RT Tester GUI, which was accidentally dropped from the build. The latest is on CloudBees, we will perform a proper release soon.
- D7.5 Released: As we got no further review comments and the once found have been incorporated, we release D7.5 today.
- US-Traceability: So far, the review has been extremely constructive. There are still open review results pending, but we expect to close the review soon #506.
- US-Scade-to-Open: Silvano published a new version a week ago, taking into account all review comments. We will decide on Friday on whether we can conclude the review #505.
- Workshop in Munich: Thank you for your contribution to the Workshop Wiki. Important: At the workshop, we will decide on the demo regime for the final ITEA review. If you are interested in presenting a demo, but won't attend the workshop, let me know asap.
- D7.5: We finished a draft of the last open deliverable, D7.5, "Ecosystem Artefacts". We will start the review shortly and need reviewers.
- Issue Tracker: Our goal is to have all open issues closed by the end of the project. Please review issues that are assigned to you and resolve them.
- Missing activities: I believe we are on top of all of our responsibilities. Please let me know asap if you feel that we missed something.
- US-Traceability: We reached the end of the review and should decide whether the document is considered complete or needs more work #506.
- US-Scade-to-Open: We reached the end of the review and should decide whether the document is considered complete or needs more work #505
- Workshop in Munich: Please provide your information for exploitation on the Workshop Wiki.
- TdSE: Moritz and I presented the ReqIF-Work of openETCS at TdSE (German Systems Engineering Day, organized by the German chapter of Incose), which was well-received.
- US-Traceability: Review is currently tracked via #506 - please join the discussion.
- US-Scade-to-Open: Review is currently tracked via #505 - please join the discussion.
- Workshop in Munich: The main goal for the Workshop is the collection and documentation of specific outcomes of WP7. We will go through the list today.
- EclipseCon Europe & TdSE: I presented openETCS there this week, the talk was well-received. Next week there will be another talk at TdSE.
- US-Traceability: Raphael significantly revised and extended the Traceability Architecture Document. Please have a look at it. Unfortunately, he has to leave at 11:00, so he'll just miss the WP7 slot. However, he will be present from 9:45 - 11:00 Therefore: Stakeholders (WP3, WP4), please take advantage of his presence during your sessions.
- US-Scade-to-Open: Silvano has just published his draft of the Migration Scade to Open Alternative.
- US-Toolchain-CI-Automation: We fixed the build system, which is now stable again. The new build includes Acceleo and RMF 0.14.0. We will perform a clean release next week. In the meantime, the new build is available via CloudBees
- November Workshop: I set up a Wiki page for WP7
- US-Scade-to-Open: Silvano will publish a draft on Tuesday - we're looking for Reviewers.
- US-Traceability: Raphael will try to join to telco. He is working with Marc, Silvano and Esterel to complete the Traceability Architecture.
- US-User-Docu: We will start with restructuring the WP7 Homepage
- US-Scade-to-Open: Update from Silvano
- US-Traceability: Raphael is still in the process of getting up to speed (and getting to terms with Latex). We are about to conclude the committer election process.
- US-Model-Validation: Update Alexander (if any)
- US-Auto-Update: We changed then name to "US-Toolchain-CI-Automation" to make it clearer what activities are required to achive this task.
- US-SysML-to-B-demonstration: We will integrate Acceleo into the toolchain, so that David can continue on this one.
- Scade-to-open: Silvano made an initial proposal (#500) and will execute it. The first workshop took place Thursday.
- Traceability: Raphael got started at this. WP7 members, please vote on #501, so that Raphael can get write access to the repository.
- RMF 0.13.0 released: The new RMF has finally been released, we'll incorporate it into the toolchain soon.
- Papyrus Model incompatibilities: David discovered that some SysML models cannot be opened with the openETCS toolchain, and that other models produce errors. We should make sure that (1) for each model, we document the tool version (e.g. in a Readme in the same folder), and (2) that models that are supposed to work with the current tool actually work.
- Scade-to-open: Silvano will propose an outline for the report (#500)
- Traceability: Raphael will report on the progress of Samares (#471).
- Documentation: Getting the documentation to a state where it is self-contained is now the focus of our work.
- Addressing open Backlog Issues: WP7 currently has 6 backlog items which we need to address by the end of the project. This goes hand-in-hand with the following:
- Cleaning up Issue Tracker: We started to clean up the WP7 issue tracker, to ensure that all important tasks are taken care of, before the project officially ends. To that end, we may reassign issues and ask for your help to resolve them in a timely manner.
- Scade-to-open: An important backlog item is the migration to an open scade alternative. We created a project plan #500for Silvano to implement.
- Documentation: We started to work on US-User-Docu Prio, a high-priority backlog item. Please be aware that other WPs can take advantage of the documentation infrastructure, if they want to.
- Traceability: Samares is now getting up to speed, getting familiar with the infrastructure and the project.
- Traceability: Samares is now officially on board and started to work on traceability. He will essentially pick up with the Traceability Architecture at the point where Cecille left off in December.
- US-Master-Branch-Error-Free: We got one minor comment on the first draft of the process, see #498. If there are no further comments, then I guess we can close the issue.
- RMF-Release imminent: Still just imminent.
- RMF-Release imminent: RMF is still not released, as the Eclipse release process requires a lot of diligence. As soon as RMF 0.13.0 is released, openETCS will be updated.
- Traceability: Samares is now officially on board as a subcontractor. Raphael will start by updating the traceability architecture document that Cecille started in 2014, and which is now hopelessly outdated.
- US-Master-Branch-Error-Free: We finished a first draft of the process. Please comment via #498.
- RMF-Release imminent: We are in the final stages of releasing RMF 0.13.0.
- Traceability: Looks like we're making some progress on getting Samares as a subcontractor on board. This will be discussed today at the PMB meeting
- US-Master-Branch-Error-Free: Hopefully, next week, we'll have some results.
- US-Master-Branch-Error-Free: Please comment #498 if you have any more thoughts. We plan on realizing this starting next week.
- US-User-Docu: Formal Mind took over this issue, as SQS, who was originally assigned, is out of resources.
- Traceability uncertainty: Marc Pantel is working hard to get Samares on board, as they have the expertise to take on traceability. However, due to the unresponsiveness of the French Cluster Leader so far, this has not happened yet.
- US-Scade-to-Open: Silvano will work on this important topic. So far, no team member from LAAS has been nominated.
- US-Master-Branch-Error-Free: First process has been created #498
- US-Scade-to-Open: New Product backlog item, which Silvano will take over
- openETCS at EclipseCon: Talk accepted: openETCS - Eclipse in the Rail Domain
- Test Plan presentation: Izaskun presented the test plan, which will be uploaded to our YouTube-Channel shortly. With this, we also closed US-Test-Plan.
- SysML2B Implementation: With the workaround to the Acceleo-problem, we concluded today the user story US-SysML-to-B.
- SysML2B Demonstration: In addition, we created a new user story US-SysML-to-B-demonstration to create a case study that shows this technology on a small example. David will drive this.
- Lukasz leaves the team: Lukasz Fronc left LAAS, who was driving the traceability architecture. For the time being, Jan Welte will own traceability. Hopefully, Silvano (LAAS) will soon tell us who will fill in for Lukasz. Also, hopefully Raphaël Faudou from Samares will soon join the team.
- Talk accepted: Moritz and I submitted a talk to TdSE, which is the German INCOSE conference. The title is "Solide Anforderungen dank ReqIF im europäischen, grenzüberschreitenden Schienenverkehr" (Solid Requiremenets thanks to ReqIF in european, cross-border rail traffic"
- Modelling CI: The continuous integration for the modeling team via Jenkins (on Cloudbees) is up and running.
- SysML2B: We provided a workaround to the Acceleo-problem. However, this requires the tool to run via Eclipse, not ant, as it had been designed initially.
- Future of SysML2Scade-Converter: We had a brief discussion regarding the SysML2Scade converter from Fraunhofer. I don't think we can continue any development here, but would like to briefly bring it up in the discussion
- EclipseCon Europe: There were submissions by All4Tec and Formal Mind. Did anyone else from WP7 submit something?
- RMF release coming up end of August: We will update openETCS accordingly.
- Traceability: Hopefully, LAAS will provide an update at today's telco.
- Test Plan Presentation: Hopefully, Izaskun will provide an update at today's telco
- Q3/Q4 planning for WP7: As openETCS will end in less than half a year, we started to plan the activities for this time period. Expect some additional communication in the next days/weeks.
Activities continued informally during this time period.
- Traceability: Faiez (Laas) to work on #471. WP3 and WP4, please observe and comment these activities.
- Word-to-ReqIF-Converter: Moritz completed his Diploma Thesis - congratulations!
- SysML2B-Converter: Ingo and David made progress on the problems with Luna, and will report
- Test Plan presentation: Izaskun is coordinating with the project office and will hopefully announce the date and time on Friday.
- Luna rollout: The rollout will take place this afternoon.
- Test Plan presentation: Izaskun will coordinate with the project office to plan something for the 1st week of July. She may join today's telco to give an update in person.
- SysML2B: Ingo and David have been troubleshooting the problems with Luna (#486), and made some progress. Hopefully, a solution will be available soon.
- July plans: I have a lot of traveling coming up, as well as some vacation. This means that I will not be available the next five Fridays. Ingo will cover WP7 during that time, and I will be still available, via email at least.
- Luna rollout: We're still ironing out a few kinks in the release, mainly related to the copying of the binaries. The release is essentially done, the binaries available from cloudbees for now.
- Build automation for WP4: An initial implementation of the build automation is active. We are now working on improvements, as documented in in #492
- Test Plan presentation: No updates from Izaskun
- Traceability: No news from Faiez
- Luna rollout: The Luna branch has been merged into master and a build successfully triggered on cloudbees. The release is being prepared right now.
- openETCS installation problems: Peter reported problems with the latest release, being unable to unpack the zip file due to "file names that are too long". This is a known problem on Windows, but I could not reproduce it (on my Windows machine). Does anybody else have this problem, or has a workaround?
- Build automation for WP4: We started to work on US-Model-Building-CI Prio wor WP4. How this task evolved is documented in #487
- Traceability: Here is the update from LAAS (Faiez): "I have just completed reading the three documents (D7.1, D7.2 deliverables and the Traceability Architecture Document). Shortly, I wish obtain a detailed list of concrete tasks to do. "
- Luna rollout: We now have a working Luna build system and successfully built the toolchain on Cloudbees. We plan on merge the Luna branch into the master branch next week.
- Word-to-ReqIF Converter: As the converter has been completed, Moritz posted an updated version of the .reqif models. Additionally, he is actively reaching out to the community to ensure that his work will survive the projects. If anyone has c
- openETCS installation problems: There were problems with the current toolchain in Windows due to long filenames. We're looking into this.
- Munich workshop: As we have an extremely small team, there will not be a formal workshop in Munich in July 2nd.
- Traceability: Faiez started to study the existing materials to take over this important backlog item.
- Maven-Build: Matthieu confirmed that the build scripts are working.
-
Maven-Build working again: We managed to fix the maven build scripts to automatically create the openETCS product. We are still looking into automating it again on CloudBees. This is simple in principle, but we are concerned about the long-term viability of staying with CloudBees.
-
ReqIF Converter: Even though the Word-to-ReqIF conversion of Subset-26 already works extremely well, Moritz is continuing to make improvements. For instance, he is working on the recognition of recurring phrases for traceability.
-
LAAS to work on Traceability: Faiez started to work on traceability, which is now our highest priority project backlog item. He started by familiarizing himself with Cecile's traceability architecture document and will work with WP3 and WP4 to make sure that we will consider their requirements.
-
ENSEEIHT: There are still no news from Marc Pantel regarding using their funds. He is looking into using the funds to hire Raphael, who could provide ReqCycle expertise
- LAAS to work on Traceability: Our highest priority backlog item is US-Traceabiliy-Architecture. LAAS volunteered to take this on and will get started soon.
- Build System: We still didn't manage to fix our build system (Maven/Tycho/Jenkins) - please stay tuned for updates.
- All4Tec at EclipseCon France: All4Tec got accepted for an Ignite Talk at EclipseCon - congratulations!
- Acceleo incopatibility: David talked to Obeo regarding the Acceleo incompatibility - it looks like a workaround is available.
- Test Plan: We are still working on finding a timeslot for Izaskun to report her results.
- New Team Member: LAAS (Silvano) added a new team member to the project, Faiez Zalila. Welcome!
- Resource Bottleneck at ENSEEIHT: Marc Pantel currently does not have anyone for openETCS. He is trying to recruit external help.
- May Holiday: No Telco due to Holiday
-
Build System: During the migration from Kepler to Luna, our build system (Maven/Tycho/Eclipse/Cloudbees) stopped functioning. Matthieu took this on, allowing development to continue (Thanks!). We now need to automate the build system again and document the build process. Ingo (Formal Mind) will take on this task.
-
SysML2B: SysML2B is currently not functioning with Luna. David and Matthieu tracked this down to Acceleo. David has both a simple test setup, as well contacts with the three projects that are involved (Papyrus, Acceleo and theSysML2B). He is driving this issue.
-
Subset26-to-ReqIF: Moritz uploaded a new version of the converted Subset-26. Please check it out, he did a great job on this, thanks!. He is also resolving the remaining issues regarding licensing - there were some questions due to the libraries that his plug-in uses.
-
ProR rendering: Related to the Subset-26, we (Formal Mind) are working on improvements to the ReqIF editor. In particular, we are looking at ways to make it easier to see embedded images as a whole.
-
Test Plan Presentation: @idelatorre is working with the project office on identifying a time that works for all.
-
LAAS Availability: Lukasz (LAAS) is leaving openETCS, as he took on a new position. Congratulations to Lukasz, but WP7 loses a strong team member. Silvano will participate Friday (today), to propose an alternative solution to continue LAAS involvement in WP7.
- EclipseCon France: We decided to postpone a joint submission for EclipseCon Europe. I am not aware of any WP7-submissions, except one by myself that only marginally concerns openETCS.
- Thursday Telco: We now have a Thursday Telco slot from 9:00-10:00, which should show up in all your calendars (if not, please contact the project office). We will use this timeslot on an as-needed basis.
- Telco on Build Infrastructure: We will use next week's timeslot to straighten up the build infrastructure. This activity has been triggered by US-SysML-to-B, which can currently not be built, due to Eclipse dependency issues.
- Test Plan Presentation: There have been discussions on presenting the Test plan on Friday at 10:00. However, I have not seen an invitation to this. Therefore, @idelatorre, please send a reminder if it will take place.
- WP7 summer workshop: I started to work with DB to colocate a workshop with the 9th PCC meeting in Munich, probably the morning of July 2nd.
-
Active organizations: According to our survey, the following organizations are active in WP7 for the rest of the year - anybody missing?
- CEA
- Formal Mind
- Fraunhofer
- LAAS
- MERCE
- Regrouping after WP7 leadership change: In Q1, WP7 was lead by Alexander Stante. We just changed back to Michael Jastram, who will lead the WP for the reminder of the project.
- Catching up with partners: Michael talked to a number of partners in Paris, and had a number of individual phone calls this week to catch up.
- EclipseCon France: The call for contributions is running until April 14, and it would be nice to submit a joint talk. So far, there has been interest from Matthieu and Silvano.
Activities have not been recorded in this period, due to a change in WP Leadership in this time.
- End of Sprint: We reached the end of Toolsprint 24. We will have a two-week break and will resume on January 5.
-
Backlog grooming: We had a productive backlog grooming session on Tuesday. The owners of the most urgent User stories were present:
- US-Traceabiliy-Architecture Prio: 810 - @cecilebraun
- US-Data-Dictionary Prio: 800 - @lfronc
- US-User-Docu Prio: 750 - @idelatorre
- Scrum of Scrum progress: The process helped significantly to understand where WP7 can be most effective. We are in the process of finalizing a work plan for 2015.
- Michael unavailable in January: I will not be available in January. DB will take over WP7 leadership responsibilities until January 30, including the dissemination and roll-out of the 2015 WP7 work plan. Cecile will continue to act as the T7.3 task leader.
- Happy holidays, and all the best for 2015!
- ESF Review: All4Tec initiated the review of the ESF project (Eclipse Safety Framework). It belongs to the family of Polarsys projects and can be found here.
- Scrum of Scrum: This is progressing and quite helpful in prioritizing our activities. Please have a look at the backlog at any time to learn what's going on (we recommend to use waffle.io.
- Resources for 2015: Thank you for all who provided input regarding their 2015 availability. We have a dedicated private repository for this purpose. Still missing are: Alstom France, Alstom Belgium, Institut Mines-Télécom, enseehit, Mitsubishi, SQS, Bremen and Rostock.
- Activity Log: Please remember to fill out the Sprint Activity Log.
- Scrum of Scrum: On Thursday, we started with the alignment of WP7 activities with the new product backlog (not yet complete). We have a tentative assignment of partners to backlog user stories. Please have a look at the backlog at any time to learn what's going on (we recommend to use waffle.io.
- Limited CEA availability: Due to an accident of a colleague, Matthieu's workload increased significantly, so that he will not be able to contribute for the time being. He will still try to include ReqCycle on a Luna and Kepler Branch, so that we can do testing.
- Word-to-ReqIF conversion: Moritz gave a presentation on the latest state of his converter, where we resolved the question on how gaps in the hierarchy are represented in the requirements model (we decided to insert filler elements).
- SysML to B translator: David provided Documentation for the SysML to B translator. He is working with Izaskun to integrate it into the openETCS documentation. Thanks!
- Resources for 2014: As we had some repository issues, Peter set up a new, private repository for this purpose. I also distributed the current status via email for those who did not have access. Please provide your numbers, so that we can plan for 2015. Also, please remember to fill out the Sprint Activity Log.
- End of Sprint: We reached the end of another Sprint iteration. Cecile will report on whether a release is planned.
- RMF/ProR release: We just released ProR 0.12.0, which I will soon integrate into the build system. A question that came up was whether we should preinstall ProR Essentials, which are non-open improvements to ProR. Particularly useful would be the XHTML rendering. Adding it would only affect the binaries that reside on CloudBees.
- New Release: Cecile just released openETCS v1.0.M22 - please give it a spin. Unfortunately, the auto-update is still not working.
-
Documentation: Several partners complained about the lack of tool documentation. We have a lot of documentation, but we acknowledge that it is not always easy to find, and there is room for improvement. Having said that, please:
- If you have problems finding documentation that you think should be there, then please file an issue and assign it to Izaskun, who did a great job setting up our documentation infrastructure.
- Our main documentation is managed in gitHub: Toolchain Documentation. You find this documentation also in Eclipse (Help|Help Contents), and as a PDF on the openETCS Tool page.
- All Eclipse-Projects that we use come with user documentation that you can also access in Eclipse via Help|Help Contents. This includes Papyrus, RMF (ProR) and git, amongst others.
- We are aware of existing process documentation, notably D2.4 and D1.3.1. We will look for ways of making this documentation more accessible.
- ITEA/ARTEMIS Co-Summit: In March, there will be the Co-Summit. It would be great is someone there could present the WP7 results. Stefan will be there, but he has only limited bandwidth.
- Scrum of Scrum: There are a lot of grooming sessions going on right now, both within WPs, as well as between the WP leaders. There is visible progress. Once we're done with the overall product backlog, we will present the results. In the meantime you can have a look at the backlog at any time to learn what's going on (we recommend to use waffle.io.
- Sprint Conclusion: We're at the end of a sprint iteration, and Cecille will prepare a release. Most notably, it will make the ProR-Papyrus-Traceability available that Matthieu created. He is also working on documentation, which will be distributed shortly.
- Luna Timeline: Matthieu presented a first draft of a migration plan to Luna. Objectives are minimal disruption and minimal risk of having to roll back the model (Kepler and Luna models are not compatible). A first, broad estimate is that the migration will be complete in February 2015. A detailed schedule will be presented, once complete. We will perform the migration in close cooperation with WP3 and WP4.
- Mending models: Abandoning Scade Systems broke the chain from Eclipse to Scade, as we all know, resulting in two models with many redundancies. Fixing this is high priority. The most promising solution currently would be the Scade converter from Alex. The showstopper here is the status of the Scade API. There was some progress this week from Payman and others.
- Subset-26 convertion: Moritz distributed a first ReqIF model, generated by his converter.
- D7.3: We are close to delivering D7.3. We're ironing out a minor issue with respect to the review, and then we can finally submit it to itea.
- Test Plan: Work on the test plan proceeds.
- Scrum of Scrum: The WP leaders will have their first overall product backlog grooming session today.
- Sprint Extension: Due to Cecile's vacation (and low activity), I extended the sprint by one week.
- All Unit Tests Green again: We had some broken unit tests in the traceability plug-in, caused by the Papyrus integration. They have been fixed.
- Resources for 2014: I need your spent 2014 resources and planned 2015 resources in order to plan the remainder of the project. Currently, I have only 4 out of 16 responses. We have to wait for the French cluster issues to be worked out, but once this is done, please fill out your information asap.
- Scrum of Scrum: We're progressing slowly, as it is hard to find time for all stakeholders. I believe WP3, WP4 and WP7 all provided there user stories, what's missing is the joint grooming of the overall product backlog.
- Munich Workshop: Due to the workshop in Munich the Friday telco is cancelled.
- Resources for 2014: In order to properly plan our activities next year, please document your spent 2014 resources and planned 2015 resources by November 7, 2014. I am aware that some partners cannot commit to numbers, as some French cluster issues are being resolved.
- Scrum of Scrum: Jonas will help building the infrastructure for our scrum of scrum process that is currently being rolled out. We will make sure that the new process will not create additional burden for the partners doing the work.
- Traceability: Even though we are not done yet with backlog grooming, it is already clear that traceability will be a high priority topic. Moritz published the format for the Subset-26 IDs, and we reevaluate ReqCycle to see whether it is now fit for use.
- WP7 Sprints on Tuesday and Thursday: After the summer we are back to two sprints a week. We had some inconsistent gotoMeeting information posted, which we will fix. Please attend those meetings which cover your activities. Also, if you need a session for your WP7-related activities, please coordinate with Cecile.
- Scrum of Scrum: The new Scrum of Scrum process was received positively and is currently being implemented. The first overall backlog grooming session will take place next Friday (WP leaders only).
- Resources for 2014: As you are aware, we have resource issues in WP7, which have been escalated to the project office, cluster leaders, and itea. In the meantime, I started planning for 2015. So please document your spent 2014 resources and planned 2015 resources by November 7, 2014.
- Scrum of Scrum: The new Scrum of Scrum process was received positively and is currently being implemented by WP1, WP4 and WP7. We hope other WPs will follow.
- Toolchain Release: Cecile published OpenETCS Milestone 20, please check it out. Thanks!
- Migration to Luna: Matthieu took the lead on the migration to Luna (as decided in Munich). He has an initial version up and running (Caution: don't open production models, as you will not be able to open them with Kepler any more).
- Modeling redundancies and toolchain discontinuity: In Munich, we documented the ongoing modeling activities (thanks Véronique). This created two large problems: (1) the modeling team is doing a lot of redundant work (using Papyrus and Scade Suite, respectively); and by essentially abandoning Scade System, we do not have a link between Papyrus and Scade any more. We started to tackle this in Thursday's Scrum meeting. Cecile is taking the lead.
- Subset-26 parser and identifiers: Moritz Dorka, a student who is currently implementing a Word-to-ReqIF transformer, made significant progress that he presented in Munich. Particularly important is the generation of unique IDs, which he documented and everybody is invited to review.
- Budget: Please remember to fill out the Sprint Activity Log. Note that we discovered significantly discrepancies between these numbers and those reported to itea (see activities of 12-Sep-2014). We already brought these to the attention of the partners and project office. We now escalated to both itea and BMBF.
- Budget planning 2015: I will soon initiate budget planning for 2015. On the one hand, we'll have to stretch our budget due to the 6 month project extension. But as outlined above, a lot of WP7 partners seem to have used up less budget then pledged.
- Scrum of Scrum: As most of you know Peter worked hard to create a new Scrum-of-Scrum process, which will make communication within WPs more transparent, and will align how individual WPs work. The process has been published.
-
WP7 Workshop in Munich: We had a very constructive workshop on Wednesday in Munich, hosted by DB (thanks!). All decisions have been recorded in the for of issues in the tracker. Outcomes were:
- WP7 Product Backlog grooming: As part of the Scrum-of-Scrum process, we have an overall product backlog, which we groomed, according to WP7 needs and aligned with our toolchain issue tracker.
- Traceability high priority: Traceability is the single most important issue for WP3, and also has high priority for WP4. While we have some solutions in place, more features will need to be implemented, and the big picture is missing as well. Cecile will lead this effort, to ensure that we have an overarching traceability architecture and swift implementation of the most important user stories.
- Process Documentation. Tools should support processes. We noted that it is an impediment for WP7 that the processes we are supposed to support are not always properly defined. We extended our documentation with a section on processes, and request processes to be documented there (keep in mind that we generate Eclipse Help and PDF from this).
- Migration to Luna: We could not find a reason to stick with Kepler, as the use of Scade Systems has been abandoned (only Scade Suite is used). Therefore, we will initiate the migration to Luna.
- itea Proposal abandoned: We started work on an itea proposal for a follow-up project. Due to issues regarding consortium and timeline, this effort has been abandoned. While this is not WP7-specific, tool development would have been a strong focus of that proposal.
- Toolchain Release: Cecile issued a new release, please check it out. Thanks!
- Face-to-Face WP7 workshop on October 15: The main part of the workshop will (tentatively) be from 9:00 - 13:00. The afternoon is open for workshops. Please make suggestions directly on the WP7 Workshop Wiki Page
- Test Plan: Izaskun initiated the review of the test plan. Please see #429 for details and log your review notes directly on the issue.
- SysML-to-B-Translator: We discovered a name space conflict, resulting in a slight delay of integrating the code.
- Papyrus Traceability: Matthieu is almost done integrating the Papyrus-part of the requirements traceability.
- Product Backlog: I presented my ideas on how to manage the WP7 product backlog, until WP1 is ready to roll out a project-wide approach (20-minute recording). I plan on implementing it by the end of next week. Note that it will have little impact on the daily work: We will still work with the issue tracker. But issues will be tagged by their corresponding user story. For now, we keep the user stories in the playground. There is a useful free tool that provides a process-oriented view on the issues that also allows ordering called Waffle. Check it out, or watch the video to learn more.
- Regular Product Backlog Grooming: We (Marc, Bernd and myself) decided that it would be a good idea to start regular backlog grooming, aligned with our development sprint cycles. One suggestion was to do this on Fridays, every other week.
- Michael on Vacation: I will be on vacation for a week, October 6 - October 10.
- Face-to-Face WP7 workshop on October 15: Please visit the WP7 Workshop Wiki Page, which outlines objectives and a preliminary agenda. We now have responses from most partners (still missing are Eclipse Source, Institute Telecom, Rostock). So far we have 5 definite attendances and 4 maybes. Bernd pointed out that hotels in Munich start filling up.
- Finalizing Face-to-Face WP7 workshop Agenda: I suggest to use the WP7 time slot next week Tuesday for defining the focus of the face-to-face meeting.
- Test Plan: The work on the test plan has resumed, Izaskun will announce the review phase soon.
- SysML-to-B-Translator: The Translator from Mitsubishi is about to be integrated into the product - thanks to Mitsubishi for creating it, and thanks to Matthieu for taking care of the integration.
- Qualification Process Reivew: Officially, the review was over three days ago. Last chance to comment on #407 if you have comments.
- Scade API: Good news, we have permission from Esterel to include the Scade API in our open source tool. Thanks to Payman for driving this.
- WP7 Product Backlog: I created a product backlog, consisting of user stories, for our WP7 activities. I am still waiting to get detailed feedback from WP3 and WP4 leaders. Once reviewed, we will track these user stories using labels in the issue tracker. The underlying goal is to work on prioritized issues first.
- Face-to-Face WP7 workshop on October 15: Please visit the WP7 Workshop Wiki Page, which outlines objectives and a preliminary agenda. We are still awaiting a response from Bremen, Eclipse Source, Institute Telecom, Rostock and SQS.
- Budget: An analysis of the Sprint Activity Log in the time from February 17 to September 19, a time period of roughly 7 months, resulting in an effort of 1PM per month, while according to itea, we should have spent 7PM per months. We have to resolve this discrepancy.
- Test Plan: The test plan is delayed and currently on hold, as both Izaskun and Amaia are absent.
- Budget: Please provide your hours in the Sprint Activity Log, if you have not done so already. Note that the current iteration is four weeks, not two. Also, according to the log, only 3 partners are active (SQS, Systerel and Formal Mind). Please update the log if you are available for WP7.
- Test Plan: While Iaskun is on vacation, Amaia will complete the plan for review. The completion of the elaboration phase is planned for tomorrow.
- Face-to-Face WP7 workshop in October: We plan on having a workshop on October 15 in Munich. Details will be announced, but please save the date and answer this Doodle by the end of the week on whether you (or someone from your team) will attend.
- Sprint 17 complete: Toolsprint 17 has been completed.
- Sprint 18 extended: Due to the absence of many partners, Sprint 18 has been doubled, ending on September 19.
- Budget: Please provide your hours in the Sprint Activity Log, if you have not done so already.
- Test Plan Review: We had a review of the test plan today. Izaskun updated the schedule, and a revised version will be available on September 5. We are looking for partners willing to both contribute to the test plan review, as well as the test activities later on. Please check out the Test Plan and provide feedback via the issue tracker.
- Target Platform Definition: We had some problems with the target platform definition, due to including the Scade libraries.
- Sprint 17 about to complete: Toolsprint 17 will complete, with 1 issues resolved #313. This slow progress is mainly due to the holiday season, and due to the Horizon2020-Activities. Hopefully, we'll have a release today.
- Budget: Please provide your hours in the Sprint Activity Log, if you have not done so already. According to the log, only 8 hours have been contributed to WP7 in the last 2 weeks.
- Papyrus-ProR-Traceability not yet in product: Unfortunately, the plugin has been added to the code base, but not yet integrated into the product (#411). There are also still some technical issues (#410). We'll try to resolve them as quickly as possible.
- Follow-up Project: Many partners have been tied up in the preparations of the follow-up project, openIT4SR (Horizon 2020).
- Test Plan Review: Izaskun prepared a first draft of a Test Plan. Please provide feedback by the end of Sprint 18 (August 5) via the issue tracker. This is not the official review yet - I expect significant changes before we start the actual review.
- Sprint 16 complete: Toolsprint 17 has been completed, including the Papyrus-ProR-Traceability and some Data Dictionary work.
- Follow-up Project: Many partners have been tied up in the preparations of the follow-up project, openIT4SR (Horizon 2020).
- Sprint 16 about to complete: Toolsprint 16 will be completed by the end of this week, including the Papyrus-ProR-Traceability and some Data Dictionary work.
- Data Dictionary Workflow: Lukasz did some work on the Data Dictionary workflow and looked into using EMFCompare for team support (resolving merge conflicts). He may give a demo on Friday, if time permits.
- Budget: Please update the Sprint Activity Log.
- Sprint 16 extended: Due to a combination of features in the pipeline (e.g. Papyrus Traceability integration) and vacation schedules, we decided to extend Toolsprint 16 by a week, ending August 8th.
- Budget: Please update the Sprint Activity Log, accordingly.
- SysML-ReqIF-Traceability: Matthieu (CEA) completed the implementation of the Papyrus-Traceability-Proxy. Once published, this allows users to see traces between SysML and requirements not only in ProR, but also in Papyrus. This will be published by the end of next week.
- Data Dictionalry Activities: Cecile, Lukasz and Alexander are continuing to work on open issues with respect to the data dictionary.
- openETCS publication: I just published an article about the open ReqIF standard, using openETCS as a case study. This may be of interest to this community.
- Sprint 15 complete: No new binary build has been created, as no code changes were done during this iteration.
- Budget: Please provide your hours in the Sprint Activity Log, if you have not done so already.
- Safety Architect: All4Tec is working with WP4 to see how their Eclipse-based Safety Architect could be employed in the toolchain.
- Documentation: There is plenty of work waiting to be done on the documentation - please contact Cecile or Michael if you have WP7 budget and need something to do.
- Sprint 15 about to end: So far, only one issue has been resolved, relating to documentation. Unless there are additional commits to the code, I don't see the need for a milstone release.
- Budget: Please provide your hours in the Sprint Activity Log both for the ending sprint (by providing your actual numbers) and for the upcoming sprint (planned effort).
- git Training: Alexander Stante will offer a git training next Thursday. This is open to all, not just WP7.
- Milestone build 14 now available: The build artifacts for Milestone 14 are now available for download.
- Budget: Please provide your hours in the Sprint Activity Log.
- openIT4SR: The preparations for the follow-up project took place earlier this week in Paris.
- Charta: The openETCS Charter is currently being reviewed.
- Tool Development Sprint 14 about to complete: We completed 3 issues in this sprint. There will be a new binary build, in particular to make the integrated openETCS documentation part of the tool (using the Eclipse Help System).
- Budget: Please provide your hours in the Sprint Activity Log. Please make sure that your numbers for the past are also entered.
- Scrum of Scrum infrastructure: The Sprint Activity Log is not working very well, and is limited to our WP. Therefore, we are working with WP1, WP3 and WP4 to build a better scrum-based reporting infrastructure. This is driven by Bernd, and we plan on rolling it out by the end of summer. Until then, please continue to update the activity log.
- openIT4SR: Most are aware that we're working on a proposal for an openETCS follow-up project, to be funded through Horizon2020. There will be a project meeting next week in Paris, which will start the finalization process of the proposal. This matters to openETCS in so far, as we're currently reviewing our tool choices, together with WP4 and WP3, to ensure that we have a smooth transition from openETCS to openIT4SR. This may affect our openETCS tooling priorities as well.
- PDF of documentation is now generated: We now have the generation of the openETCS Handbook as PDF up and running on Jenkins - thanks Izaskun. Hopefully, with the next release, we will also integrate the documentation into the Eclipse Help system.
- Tool Qualification Plan: The qualification plan had been reviewed this week. After another iteration, it will hopefully be released.
- itea Review: The conclusions have been distributed via email by Klaus-Rüdiger.
- Resource Aggregation: I started the process of aggregating WP7 resources. The most promising news is that University of Bremen may provide an Eclipse Developer by the end of summer.
- Problems building the documentation: Izaskun has been trying to activate the documentation generation on Jenkins, so far unsuccessfully. Hopefully we have it up and running soon.
- Scade Integration: Alex made a proposal for integrating Scade.
- SysML-Requirements Traceability: We are working on extending the traceability plug-in to also manage proxies for the requirements in SysML. The ProR-side has been implemented, CEA will implement the Papyrus-side.
- itea review feedback: This week was dominated by the itea review on June 12. The WP7 slides are available.
- Review board acknowledges problems: In the presentation, we openly reported on the current challenges in WP7, which are (1) lack of maturity of used technologies, (2) Lack of crucial skills and (3) fragmentation of resources. The review board was grateful for the open and frank communication.
- Review board accepts proposed solutions: We proposed a number of specific solutions to these problems (see slides). The review board approves this. Particularly important, they confirm that we can shift resources between WPs without having to submit a change request, we just have to inform itea. This means that we can start aggregating resources.
- Bremen to lead establishment of a core team: Cecile will lead the effort of building a WP7 core team that meets physically on a regular basis, for getting work done (i.e. not just a day of presentations, but actual collaborative work). We already started to identify partners, which Cecile will contact shortly.
- SQS to lead testing effort: Izaskun is about to complete their two tasks documentation and tool qualification plan. Once completed, they will take on testing, as partly described in #262. Crucially, we will ensure that we have clear metrics on progress (e.g. test coverage).
- Formal Mind to aggregate resources: I will contact all 16 WP7 partners. We will stop work on activities where relevance to WP7 cannot be demonstrated. We will adjust fragmentation by either removing partners with too few resources, or by requesting them to increase their effort.
- DB to lead transparency via "Scrum of Scrums": Bernd will lead an effort to make progress trackable and comparable across WPs (once back from vacation). This is an effort started by WP4 and WP7. We have good processes that we will standardize and encourage to adapt across all WPs.
- French Funds available: Due to Alstom's reduction in funds, there are hundreds of thousands of Euros available, ready to be picked up by French organizations willing to engage. Therefore, I encourage again existing partners with WP7-specific skills to pick them up. Further, if you are aware of French companies with Eclipse-specific software development skills, I would be greatful if you could establish the contact.
- itea review coming up: Preparations are in the final stages for the itea review on June 12. Thanks all for outlining your contributions. The slides are available on gitHub.
- broken build: We temporarily had a broken build on Jenkins, which has been fixed in the meantine.
- Type Definitions: A discussion is underway, initiated by Lukasz, on whether the type definitions should be generated by Papyrus, instead of by custom code.
- Horizon 2020 Follow-up: Several partners are preparing for the H2020-Meeting in Munich on June 6/7, where openETCS-participants will present results from openETCS so far.
- itea review coming up: There are also various activities regarding the itea review on June 12. Thanks all for outlining your contributions. Still missing are enseeiht and Alstom.
- Holiday ahead: Due to tomorrow's holiday (May 22) and the fact that many partners are taking Friday off, there will be no further WP7 activities this week.
- Tool Development Sprint 11 about to complete: We completed 3 issues in this sprint. No binary build will be provided, as none of the resolved issues affects the code base.
- Budget: Please provide your hours in the Sprint Activity Log. Please make sure that your numbers for the past are also entered.
- New Team Member from LAAS: Ning Ge from LAAS will join WP7 activities - welcome!
- Progress on Migration to Luna: Matthieu worked hard to get openETCS ready for a migration to Luna. There are some implications with respect to migrating the model, but nothing major. The biggest issue seems to be that the Scade integration is still based on Kepler, and it is not clear (and unlikely) whether the same model can be edited with Kepler (via Scade) and Luna at the same time. Therefore, we'll stay with the Kepler-based version for the time being.
- Holiday ahead: Next week Thursday (May 22) is a holiday in Germany, with many organizations closed on Friday as well. Therefore, The Tuesday Sprint meeting will be the only WP7 meeting next week (Thursday and Friday is cancelled).
- Tool Development Sprint 10 has been completed, Sprint 11 started: We completed 4 issues in sprint 10.
- Budget: Please provide your hours in the Sprint Activity Log. Please make sure that your numbers for the past are also entered.
- Update from Institute Telecom: Ana Cavalli will give an update on their work (Work on SysML to IF transformation using IFx-OMEGA. Development of a Java simulator to test IF models).
- Please provide information for itea review: All partners, please provide your contributions in year 2 for WP7 asap on the wiki. Still missing are CEA, ERTMS Solutions, LAAS, enseeiht EclipseSource and Alstom. Thanks to all those who provided their information.
- Product Backlog: We're looking for ways to make it easier for non-programmers to contribute to WP7, and for customers (WP3 and WP4) to monitor our activities. For this purpose, we created a wiki page that provides a user-story based view on our bug list. Please join our two weekly meetings to help shaping this.
- Tool Development Sprint 10 about to complete: We completed 3 small issues in this sprint. No binary build will be provided, as none of the resolved issues affects the code base.
- Budget: Sprint 10 is almost over, but only one partner provided their hours for the Sprint Activity Log (thanks, TWT). However, the sprint's progress reflects this, unfortunately.
- Please provide information for itea review: All partners, please provide your contributions in year 2 for WP7 asap on the wiki. Still missing are CEA, ERTMS Solutions, LAAS, SQS, Mitsubishi, Systerel, TWT, enseeiht, EclipseSource, Institute Telecom and Alstom. Thanks to all those who provided their information.
- Budget: Please update your budget for Sprint 10 on the Sprint Activity Log. Most information is missing, please provide it as soon as possible.
- Tool Development Sprint 9 completed: As there was no change on the code base, no binary release has been made.
- Tool Development Sprint 10 started: We have 8 issues in this sprint, it would be nice if we manage to close most of them.
- Training: Cecile will distribute information on whether there will be another training next week Thursday. Please check for upcoming trainings on the training wiki page.
- Tool Development Sprint 9 about to complete: In this iteration, we only closed two issues, related to documentation. No code has been modified, therefore, no new build will be released. Please follow our Milestone releases on the release page.
- Pace of Progress: We are still progressing really slow in WP7. While Easter is partly to blame in this sprint, the discrepancy between pledged resources (9 person-days in Toolsprint 9= vs. results (2 closed issues, one training) is worrying.
- Training: This week's training by Alexander Stante on how to write Validators was well-received - thanks! Please check for upcoming trainings on the training wiki page.
- Budget: Please update your budget for Sprint 10 on the Sprint Activity Log.
- itea Review: Please provide your effort in Year 2 of openETCS and a description of your achievements on the WP7 itea Review page.
- Budget: Pledged Budget for Sprint 9: 73 hours = 9 person-days. Thank you all for updating the Sprint Activity Log.
- Training: The next trainging will take place next Thursday (24-Apr-2014), on how to create validators with the EMF Validation Framework. More information on the training wiki page. Please enter your name so that we have an idea on participation, as well as questions you may have.
- Project extension by 6 months got accepted: This has been discussed at the 17-Apr-2014 telco. Most partners will need to reduce their weekly engagement to spread the budget. There was a consensus to try to reduce hours towards the end of the project, as we need to be responsive to the needs of the other WPs right now. While we do actual development now, hopefully towards the end, focus will shift to maintenance, which should be less labor intensive.
- Showstoppers in issue tracker: We have a label Showstoppers to mark particularly critical issues. We currently have no showstoppers.
- Happy easter: We can already feel the impact of the easter holidays and expect correspondingly less progress in this sprint. Happy egg hunting!
Earlier iterations use the sprint numbers we established when openETCS started.
Later iterations use the sprint numbers from the Toolsprints.
- Training: The first training tool place on setting up up the openETCS development environment. We did record it and WP1 is looking into ways to make this and future recordings available, if there is interest. Trainings will take place every two weeks. More information on the training wiki page.
- Tool Development Sprint 8 about to complete: Please follow our Milestone releases on the release page. So far, we closed 7 issues in this iteration.
- Availability of WP7 partners: Partners with WP7 resources, please make sure that you update the Sprint Activity Log with your actual hours for Sprint 8 and your availability for Sprint 9.
- Project extension by 6 months got accepted: This has few implications for WP7, as this will simply result in roughly 12 more sprints.
-
- Showstoppers in issue tracker: We have a label Showstoppers to mark particularly critical issues. We currently have two of them.
- Training: The first training will take place next week Thursday, with the topic Setting up the openETCS product and how to build it. Please add your questions on that page. You can find information about planned trainings on the training wiki page.
- Tool Development Sprint 7 has been completed: Please follow our Milestone releases on the release page.
- Availability of WP7 partners: Partners with WP7 resources, please make sure that you update the Sprint Activity Log on a regular basis.
- Cecile taking on Quality Lab: Cecile took responsibility for issue #262 for now, which is very important. Thanks!
- Papyrus issues: We have a number of serious issues with respect to Papyrus. Mathieu is working full-time on resolving them. We have workarounds.
- Documentation: We're making progress on the documentation, Jenkins build and infrastructure for breaking the documentation into pages is now available (but not yet active).
- Tool Development Sprint 7 about to complete: On Friday, we will conclude Sprint 7 (so far 12 out of 23 backlog items have been resolved).
- Improvements to Development Process: Cecile updated the Releaes process, which includes the description of Milestone builds which we will perform at the end of every sprint cycle. We will be more disciplined in following it.
- Training: Cecile updated the information regarding the WP7 trainings. Information can be found on the training wiki page which will be updated regularly. The first training will probably take place on Thursday, April 3, 10:30. Stay tuned for updates.
- Availability of WP7 partners: Partners with WP7 resources, please make sure that you update the Sprint Activity Log with your actual hours from Sprint 7 and with your expected hours for Sprint 8. We need this information by Sunday, March 30.
- Owner wanted for Quality Lab: Issue #262 currently does not have an owner. Any volunteers? This is fairly important.
- Papyrus issues: We have a number of serious issues with respect to Papyrus. Mathieu is working full-time on resolving them.
-
Tool Development Sprint 7 has started: We updated our process by now requesting partner availability from each partner for each sprint iteration. Information for Sprint 7 is still missing from CEA, FhG and enseeiht. Also, please complete your effort for Sprint 6 (still missing are Rostock and enseeiht).
-
Change in Training: After receiving few sign-ups and some constructive feedback, we decided not to offer a 3-day training, as originally planned. Instead, we will perform regular online-trainings. Cecille will distribute information regarding these trainings soon.
-
Documentation location: We now have a place to put toolchain documentation. There is plenty to be done here. If you have WP7 resources, please have a look at the page and feel free to contribute content wherever you find a TODO.
-
WP7 Hot Topics: Please check out the open issues to see what's going on. The currently active topics include: Documentation; Traceability; Data Dictionary; Development Process; Papyrus data integrity issues.
-
Next Tool Development Sprint 7 will start next week: Due to low resources, and to catch up with our processes, we took a break from the development sprints. We'll start with Sprint 7 next week.
-
Software Developers desperately wanted: We made up an attempt to organize a training for partners who would like to contribute coding. We got one interested person (Cecile), but also got some feedback, why so few partners signed up. Basically, the requirements for participating in the training were too steep. See training description. So far, we have only one candidate.
-
Documentation location: We now have a place to put toolchain documentation. There is plenty to be done here. If you have WP7 resources, please have a look at the page and feel free to contribute content wherever you find a TODO.
-
WP7 Hot Topics: Please check out the open issues to see what's going on. The currently active topics include: Documentation; Traceability; Data Dictionary; Development Process; Architecture.
-
Tool Development Sprint 7 postponed by two weeks: We have now completed six sprints, and take a break for two reasons: First, we're not yet living the process as we would like to; second, we're low on resources this week (Cecile on vacation) and even lower next week (Cecile still on vacation, Michael traveling). We will pick up with Sprint 7 on March 17.
-
Software Developers desperately wanted: We have a full backlog, but not enough resources to do the work. Specifically, we are low on implementors. If you have WP7 resources (list of partners), please identify suitable developers in your organization to participate in the training we plan to offer. So far, we have only one candidate.
-
D7.2 complete: As we got no further feedback regarding D7.2, it will be submitted to itea.
-
Documentation location: We now have a place to put toolchain documentation. The currently monolithic structure will be broken down into subpages. The scripts for generating Eclipse Help and PDF are not complete yet.
-
Traceability Plug-in available: The ProR-SysML-Traceability plug-in is complete and included in the latest build.
-
WP7 Hot Topics: Please check out the open issues to see what's going on. The currently active topics include: Documentation; Traceability; Data Dictionary; Development Process; Architecture.
- Tool Development Sprint 6 about to complete: The sixth tool sprint will complete this week, so far, 4 issues have been resolved.
- D7.2 about to complete: The issues regarding D7.2 that surfaced last week have been addressed. Unless there are objections at the Friday Telco, it will be uploaded to itea. Thanks to Marielle for driving this deliverable, and to everybody who contributed!
- D7.3 review ongoing: Please provide your feedback regarding the ongoing D7.3 review.
- Documentation Infrastructure: SQS (lead by Izaskun) has problems resolving #241.
- Tool Development Sprint 5 complete: The fifth tool is now complete, 8 issues have been resolved.
- JRE Problems resolved: It looks like the JRE Problems have been resolved. Due to some changes, we strongly encourage everyone to download a new version of the toolchain, rather than to use the update mechanism. This will not affect the workspace, so this should not at all affect your workspace (unless you place it in your installation directory, which is the default, I believe. So be careful!)
- WP7 parcicipation: We now have all partners engaged that have significant WP7 resources. They will help with Documentation (SQS), Traceability (University Toulouse) and Data Dictionary (LAAS)
- WP7 development telcos: We changed the structure of the development telcos, by giving each telco a focus. This allows partners to only attend those telcos that affect their activities. Cecile set up and maintains a Development wiki page for this purpose. The page also shows the dial-in information for your convenience.
- D2.4 approved: The review of D2.4, OpenETCS methods has been concluded. As the toolchain is supposed to support the process described in D2.4, all WP7 partners should make themselves familiar with it.
- D7.2 now official: There have been no further contribution to D7.2 since our review in January. Therefore, the deliverable will now be uploaded to itea. Note that, due to the nature of the secondary toolchain, we will still allow subsequent contributions to this deliverable. Thanks to Marielle for driving this deliverable!
- D7.3 review ongoing: Please provide your feedback regarding the ongoing D7.3 review.
- Tool Development Sprint 5 about to complete: The fifth tool sprint will complete this week, so far, 5 issues have been resolved.
- Update on Architecture: Stefan and Cecile have revised the Feature Overview and are working on the architecture.
- Requirement-SysML-Traceability: A solution for traceability #274 will be implemented - please provide feedback by 17-Feb-2014. If no major objections arise, this will be implemented as part of the next tool sprint.
- Toolchain Development Telcos: The time for the toolchain sprints (9:30) was select to avoid conflict with WP4 telcos, but those don't exist any more. We may change the times of those telcos.
- WP7 Wiki entry page: This is a reminder that the WP7 front page is actively maintained to make it easy to find relevant information.
- Activities in Paris: Many WP7 participants attended the SysML and Traceability workshops in Paris. Therefore, there were few activities.
- Tool Development Sprint 4 complete: The forth tool sprint has been completed. Unfortunately, only 2 issues have been resolved. We still have a major problem engaging all partners who have WP7 resources.
- Qualification Process Document: This is now on gitHub. Like with the other activities, engagement is at an all-time low. If you have WP7 resources, please read the document and provide feedback.
- D7.2: D7.2 is open to contribution from volunteers. Likewise: If you have WP7 resources, please read the document and provide feedback at the least. Even better we still active need contributions. Please engage.
- Engage: If you would like to contribute but don't know how, please Check out the open issues, participate in the telcos on Tuesdays and Thursdays (9:30) as well as Friday (11:00), or contact Cecile or me directly.
- Pace of development: This is still a problem. In particular, so far only one issue has been resolved in this sprint (I expect a second tomorrow). There is still a mismatch between pledged resources (according to itea) and actual engagement of partners. See the List of Partners.
- Qualification Process Document: This is now on gitHub. Please send your suggestions to Cecile before the official review launch on Friday 7th February.
- Traceability Workshop in Paris: The Paris SysML training has been shortened slightly, to make room for a Traceability Workshop on Thursday, February 6th, in the afternoon (start time TBD). Please indicate your participation in this doodle.
- D7.2 help wanted: D7.2 is open to contribution from volunteers. They can contact Marielle in any case of trouble.
- Tool Development Sprint 3 complete: The third tool sprint has been completed, 11 issues have been resolved.
- Pace of development: The pace at which tool development proceeds is concerning. Specifically, there is a mismatch between pledged resources (according to itea) and actual engagement of partners. See the List of Partners.
- D7.2 help wanted: D7.2 is open to contribution from volunteers. They can contact Marielle in any case of trouble.
- Workshop in Munich: This week was dominated by the workshop in Munich.
- Toolchain Development: We started the third toolchain Sprint, please check the issue tracker for activities.
- T7.1: In preparation of next week Tuesday meeting, please to let Marielle know if some activities and progress have been done for T7.1 since our Braunschweig decision meeting. You can have a look on the deliverable D7.1 and the minutes of the meeting. Please provide feedback ideally today, tomorrow the latest.
- D7.2: The report on the secondary toolchain D7.2 is currently in the works. Please support Marielle with the finalization activities.
- D7.3: The deliverable on toolchain qualification is in the works and due by the end of January. Cecile will distribute information regarding D7.3 shortly.
- Munich Workshop: I look forward to seeing all of you at next week's workshop.
- Toolchain Development: We are about to complete the second toolchain Sprint, as of this writing, 6 issues were resolved. A new built will be triggered shortly.
- No auto-update available yet: The built-in mechanism for updating has not yet been implemented. Therefore, you will have to download and install the new version for now. Your existing data will NOT be deleted - no worries! Just point your new install to your old workspace. (Pro-Tip: You can also have multiple workspaces).
- Christmas Break: Due to the holidays, there will be no official activities from 20-Dec-2013 - 06-Jan-2014. This means no WP7 telco this Friday, the next telco will be the WP7 Sprint telco on 07-Jan-2013. Sprint 3 will start officially on 06-Jan-2013, but I won't stop you from starting earlier.
- Secondary Toolchain: Marielle started the work on D7.2, as we decided cut the evaluation process short.
- Toolchain Development: We completed the first toolchain Sprint, which resulted in 5 resolved issues and a downloadable tool. Thanks to the team to make this happen.
- 2nd Toolchain Sprint: The second sprint is underway. Please contribute, if you can. What's already clear is that we do not have enough people with Eclipse development expertise.
- High-level Overview: Cecile created and maintains the Toolchain Feature Overview that shows what we have and what we are working on.
- Secondary Toolchain: Escalation: We have a problem with respect to T7.2. Quote from Marielle: "Despite different calls, we are lacking (...) assessments and assessors. (...) Indeed, I am now totally demotivated to spend hours in unused documents."
- This opinion was seconded by Jonas, and I agree that we have a problem here that needs to be escalated. We won't find a solution tomorrow, but we will raise awareness at the weekly meeting and decide on the next steps. I see roughly two possible courses of action:
- Escalate this issue to the project office, and delay the deadlines further to allow people to catch up.
- Acknowledge the problem and, in the spirit of a meritocracy, stop the process. Instead, we'll simply use tools where there are volunteers, rather than using tools that were identified through a thorough evaluation process. We would capture the results to date and this decision in D7.2.
- I feel that option b is the more realistic one.
- Toolchain Development: Development activities are accelerating, Cecile is active in mobilizing partners. We now have two "Scrums" for the toolchain development, Tuesdays and Thursdays, at 9:30. Please join us, if you have resources to participate in the toolchain development.
- Toolchain Feature Overview: Cecile created a bitmap of the dataflow, which is shown on the Feature Overview page and allows you to quickly get an overview, without having to install Papyrus.
- Toolchain release: Jonas and his team worked hard to set up a build server for the openETCS tool. Tomorrow, we should have access to a download that can quickly be installed and is preconfigured with ProR and Papyrus.
- Delegates for external Projects: We still need delegates, see Collaborations. Any volunteers?
- Week-long SRS-Meeting in Berlin: Due to the WP3 meeting in Berlin, some WP7 activities were slowed down this week, as many people are active in both WPs.
- Secondary Toolchain activities: Tool presentations continue, please check out the Secondary Tools Analyses Wiki page.
- Toolchain Dataflow: Cecile created a model depicting the dataflow within the toolchain. You need to install Papyrus to view this.
- Toolchain Development Scrums: We know have two "Scrums" for the toolchain development, Tuesdays and Thursdays, at 9:30. Please join us, if you have resources to participate in the toolchain development.
- Toolchain Backlog: For now, we use the Toolchain issue tracer as the backlog. Once activities increase, we will follow Jonas' Process, which will track activities in project-specific issue trackers.
- Next openETCS Release: The first Sprint will complete on December 6. We plan on having a continuous build system set up by then, and a public download site for openETCS.
- Delegates for external Projects: We need to make sure that we are aware of outside activities, and that related projects outside openETCS are aware of our work. We created a list of all interesting projects. We still need delegates for shift2rail, Crystal, SafeCap and SAFE. Any volunteers?
- January Workshop: If you have not done so already, please mark your calendar for the next face-to-face openETCS event January 15 - 17 in Munich. This will be a joint workshop for all WPs. We started to work on the WP7 agenda, please let us know if you think something important is missing. Also, be prepared for more activities to be tugged before or after the event.
- Toolchain first release complete (D7.4): The official review of D7.4 has been completed, the document is now considered delivered.
- Secondary Toolchain activities: Tool presentations continue, please check out the Secondary Tools Analyses Wiki page. As discussed last week, we made some changes to the process to accelerate the activities and adjusted the timeline.
- Toolchain Dataflow: Cecile created a model depiciting the dataflow within the toolchain. You need to install Papyrus to view this. In the near future, you'll be able to use openETCS to view this.
- Tool Development Weekly Telcos We started with weekly T7.3 telcos Thursdays at 9:30. If you can participate in these activities, please join us.
- Toolchain Ambassador: We need to make sure that we are aware of outside activities, and that related projects outside openETCS are aware of our work. I am looking for a volunteer to take on this role.
- January Workshop: If you have not done so already, please mark your calendar for the next face-to-face openETCS event January 15 - 17 in Munich. This will be a joint workshop for all WPs. We started to work on the WP7 agenda, please let us know if you think something important is missing.
- Secondary Toolchain activities: Please check out the Secondary Tools Analyses Wiki page.
- Toolchain first release (D7.4): The official review phase of D7.4 will end tomorrow. Please provide feedback to Cecile, if you have not done so already.
-
Tool Development activities: Cecile worked a lot behind the scenes to get things ready for tool development (T7.3). Here are the details:
- Tool Development Weekly Telcos Starting next week, we will have weekly telcos. We propose Thursdays, 10:00. We'll discuss tomorrow whether we'll stick with this time slot. Down the road, we may change to even shorter meetings, multiple times a week (following WP4's example)
- Development Process: Cecile is working on a lightweight development process, which will be published tomorrow.
- Status Page: We have a Status Page, which lists the ongoing T7.3 activities. This will be based on the Backlog Process that Jonas provided.
- Using the Data Dictionary: We will use the development of the Data Dictionary to test the process. This resulted in a Design Specification. Sorry if you can't access it right now, as the Data Dictionary repository is still private.
- January Workshop: If you have not done so already, please mark your calendar for the next face-to-face openETCS event January 15 - 17 in Munich. This will be a joint workshop for all WPs.
- Secondary Toolchain activities: Please check out the Secondary Tools Analyses Wiki page.
- Toolchain first release (D7.4): The official review phase of D7.4 has started. Please provide feedback to Cecile.
- Data Dictionary: The data dictionary will be used as the first component for WP7 development.
- Tool Webpage: We created a new menu item "tool" on http://openetcs.org and created a corresponding landing page, please check it out.
- Naming the Toolchain: The toolchain name is openETCS Extended Tool Construction Set, conveniently abbreviated as openETCS. Thanks to David for the suggestion.
- Secondary Toolchain activities: Please check out the Secondary Tools Analyses Wiki page. The focus is now on V&V tools.
- Toolchain Development activities: We started to sketch out various ideas regarding the development process, using the Data Dictionary as the concrete example to play around with.
- Backlog Process: Jonas made a proposal for a light-weight process, how the backlog for WP7 will be filled. Please provide feedback!
- Toolchain first release (D7.4): We will shortly enter the official review phase of D7.4. Please provide feedback to Cecile.
- Secondary Toolchain activities: Please check out the Secondary Tools Analyses Wiki page and engage in the activities.
- Criteria for Management Tools: The criteria have been completed and are available in O7.2.1
- SysML/Papyus Training: Matthieu is organizing Training sessions. Please record your interest and availability.
- D7.4 Tool chain first release: Please check out and comment the D7.4 draft. We will make a preliminary version of this document available by the end of the month and engage in a proper review phase. It would be great to have a solid document before starting the review, so please comment via the issue tracker. Cecile is driving these activities.
- Naming the Toolchain: We have a number of naming suggestions for the toolchain. We will try to make a decision tomorrow. If we don't reach agreement quickly, we will launch a doodle.
- Secondary Toolchain activities: Please check out the Secondary Tools Analyses Wiki page and engage in the activities. The timeline has been updated. Tomorrow is the "End of contributions and review on criteria for management tools"
- SysML/Papyus Training: Matthieu is organizing Training sessions. Please record your interest and availability.
- D7.4 Tool chain first release: We will produce this, according to plan, by the end of October. This will be just a short document, describing where to download which version of Papyrus, how to configure it with ProR, and how to connect it to gitHub. Cecile will drive these activities.
- Naming the Toolchain: With the release of the tool chain imminent, it would be nice to have a catchy name for it. Please make suggestions for a good name. It may seem silly, but a good name can help to increase awareness, allow us to identify with the tool, make it easier to be found on Google, etc. Thanks for your contributions!
- Braunschweig Workshop: This week was dominated by the workshop, which was covering WP3, WP4, WP5 and WP7 activities.
- D7.1 accepted by the PCC: The PCC voted on D7.1 and accepted it. A few issues have been identified that need clarification. These will be collected via the issue tracker and added to D7.1 as an Errata.
- Secondary Toolchain activities: Please check out the Secondary Tools Analyses Wiki page and engage in the activities. Criteria have to be finalized, assessors are wanted, tool evaluations have to be made, etc. Marielle will post an updated timeline shortly.
- D7.4 Tool chain first release: We will produce this, according to plan, by the end of October. This will be just a short document, describing where to download which version of Papyrus, how to configure it with ProR, and how to connect it to gitHub. Cecile will drive these activities.
- D7.1 Review is complete, D7.1 officially "delivered": The Review of D7.1 is closed, the deliverable is complete. Thank you to all for your hard work and your contributions, and in particular to Marielle, who was acting as the product owner on this deliverable.
- Secondary Toolchain: We still need assessors, please contact Marielle if you can take on the assessment of a secondary tool.
- Braunschweig: Final preparations for the Braunschweig Workshop were made.
- D7.1 Review: One issue is left open, which will hopefully be resolved at the telco.
- Secondary Toolchain: Contributors are invited to present their tools, sessions have been set up by Marielle for this purpose. Also, volunteers are wanted for assessments, please contact Marielle.
- Workshop in Braunschweig: The agenda is pretty much complete.
- D7.1 Review: We are really, really close, only a few issues remain open.
- *Secondary Toolchain: Feedback is coming in on the evaluation criteria.
- Review of D7.1: As of this writing, only 4 (primarily technical) issues remained on D7.1. It was decided to resolve these bilaterally, without another review meeting. Once the reviewers approve D7.1., there will be a short period for vetoes, after which D7.1 will be considered delivered.
- D7.1 Decisions: The decisions in D7.1 will not be official, until they have been voted for during the PCA meeting in October. If anybody plans on voting against, please conteact Michael or the project office, to find a solution.
- WP-Workshops in Braunschweig: While the agenda is still being worked on, the date for the Braunschweig workshops (including WP7) now stands. Please check out the agenda to decide what you would like to attend, and save the date.
- Secondary Tools Criteria: Marielle published a draft version of criteria template for secondary tools, but raised a number of questions, which we will briefly discuss at tomorrow's telco.
- Vacation deputy T7.3: Cecille will be on vacation until the fall workshop, please contact Jan Peleska with urgent T7.3-related issues. Have a nice vacation, Cecille.
- Review of D7.1: A lot of progress has been made on the deliverable D7.1, but a lot of open issues remain. Please, all help to resolve them. It's not clear what the conclusion and recommendation will be that all agree on, but the core ideas have been recorded in this wiki page.
- More Review Meetings: Hopefully, we will conclude the D7.1 review next week. In tomorrow's telco we will find timeslots, please fill out the Doodle.
- WP-Workshops in Braunschweig: While the agenda is still being worked on, the date for the Braunschweig workshops (including WP7) now stands. Please check out the agenda to decide what you would like to attend, and save the date.
- D7.1 review closed: Review meeting (telco) Tuesday 3rd of September 14:00 Issues have been assigned and can be taken into account by authors. Complements are welcomed
- T7.2 Secondary Toolchain: The plan and timeline have been documented here. There are four subpages for the following four categories. All of these need to be checked, and completed:
-
Verification and validation -
Model transformation and code generation -
Data, function and requirement management -
Safety activities supports page -
A data model will be proposed on github today to benchmark of SSRS supporting tools - some draft version of template of criteria are on github
- T7.3 Toolchain Development: Beginning of Tool chain architecture plan
-
D7.1 review ongoing: The first draft of D7.1 is complete, and currently under review. Details are documented in the review plan. Review will end Monday 26th evening Issues have been assigned and can be taken into account.
-
T7.2 Secondary Toolchain: The plan and timeline have been documented here. There are four subpages for the following four categories. All of these need to be checked, and completed:
-
Verification and validation -
Model transformation and code generation -
Data, function and requirement management -
Safety activities supports page -
A data model will be proposed on github today to benchmark of SSRS supporting tools -
T7.3 Toolchain Development:
- D7.1 review ongoing: The first draft of D7.1 is complete, and currently under review. Details are documented in the review plan.
- Secondary Toolchain: The plan and timeline have been documented here. There are four subpages for the following four categories. All of these need to be checked, and completed:
-
Verification and validation -
Model transformation and code generation -
Data, function and requirement management -
Safety activities supports page
- D7.1 first draft ready: The first draft of D7.1 is complete, and currently under review. Details are documented in the review plan.
- Secondary Toolchain: The plan and timeline have been documented here. There are four subpages for the following four categories. All of these need to be checked, and completed:
-
Verification and validation -
Model transformation and code generation -
Data, function and requirement management -
Safety activities supports page - Case Study for data, function and requirement management: It was suggested by Marc Behrens to use a case study based on §6 - this has been documented on the wiki. We need a volunteer to sketch this out.
- Deliverable D7.1: For the next few weeks, the deliverable D7.1 will be our main focus. Everybody is invited to contribute. You can provide feedback and content via email, gitHub issues, gist or, as a committer, by editing the Latex.
- Scope of D7.1: In particular, please check out pages 1-5, which define the scope of D7.1. If you disagree with anything written there, please speak up asap.
- D7.1 Timeline: Originally, Appendix-Owners were supposed to have completed their chapters by the 24th, which did not happen. Therefore, we will give them more time, aiming to complete the document by the end of the month (31-Jul-2013). We will then have a review until 20-Aug-2013.
- Secondary Toolchain: We are starting the evaluation of secondary tools. Please find all relevant information in the model-evaluation wiki. Don't be shy and get involved.
-
Deliverable D7.1: For the next few weeks, the deliverable D7.1 will be our main focus. We now have a total of 3 alternative tool chain proposals (Appendix A - C), all of them assuming Papyrus/SysML as the starting point.
-
D7.1 Timeline: We readjusted the timeline to accommodate the author's needs and the fact that Marielle will be on vacation. While Marielle is gone, I'll assume ownership of D7.1:
-
24-Jul-2013: Appendix-Owners have completed their Appendices
-
31-Jul-2013: First draft of D7.1 complete, start of review phase
-
20-Aug-2013: Conclusion of review
-
Secondary Toolchain: We are starting the evaluation of secondary tools. Please find all relevant information in the model-evaluation wiki.
-
Topcased/Polarsys: There were a few discussions regarding Topcased (tool) and Polarsys (Eclipse Working Group). Specifically, two elements that are also part of Topcased have been selected for openETCS (Eclipse and Papyrus), and Polarsys and openETCS have similar goals. There already is some content on this in D7.1.
- Preparation of D7.1: The Paris Workshop kicked off the creation of D7.1., which is due by the end of the month. We will follow the following timeline:
-
19-Jul-2013: The Review version of D7.1 will be complete -
14-Aug-2013: The final version will be released (technically with a 2-week delay, but I believe that this is acceptable in order to have enough time for the review). -
The Tool Selection Process has been described for a while - Action Items from Paris: We recorded a number of tasks (see minutes, please note that I updated them once more with IDs).
-
T2: You have until Friday to propose alternative toolchains, in particular if they compensate for the lack of openness in Scade. One alternative has been proposed (see below) -
T6: We need to clarify on how we will deal with closed-source solutions. This should be captured in D7.1. -
T7: Who volunteers in secondary tool criteria definition? Who is willing to assess? Please contact Marielle. -
T9: Volunteers wanted for SSRS tools and SSRS support. Please respond asap to Marielle. - Alternative Open-Source tool chain with EFS und Xtend: On Thursday, Stan proposed an alternative tool chain based on EFS and Eclipse Xtend.
- Telco on D7.1 Monday, 10:00: We reserved a 2-hour timeslot on Monday to kick off the D7.1 activities.
- Paris: Many of you spent time in Paris this week for PCA, itea review and WP7.
- itea Review: The review went well, congratulations to the team.
- WP7 Workshop: Minutes and tasks are on the WP7 wiki. Please let me know if you have concerns, but don't edit the wiki directly.
- Review of O7.1.3_O7.1.7: This crucial output has been produced, Review will continue only until the 30th of June. Please make sure to provide feedback via gitHub tracker - obviously it is less than optimal to have such a short review period.
- Paris Meetings next week: There are a number of meetings taking place next week with respect to itea review, PCA, SSRS and WP7. Please make sure that you are aware of what is taking place when. If you have questions, please contact the project office.
- WP7 Workshop on Thursday: Please note the updated agenda. Also, please make sure that your RSVP (Doodle) is up to date, so that we can get a room of proper size (so far, we have 16 RSVPs).
- Next week's telco is canceled due to the Paris meeting.
- WP2 deliverables accepted by WP7: At last week's telco we decided to not initiate a separate sign-off for the latest WP2 deliverables.
- Wp4 documents: These documents are open for comments
-
V&V Plan -
Preliminary Safety Evaluation Criteria - FPP and PCA: These are close to finalization.
- Dissemination: A dissemination project has been proposed.
- WP7 Workshop: The Workshop Agenda has been updated to reflect the needs of WP4.
- Assessments: Assessments that are not delivered today (Friday) will not be considered for the benchmark evaluation
- DoW and FPP: In preparation of the itea review, we noticed some discrepancies between the WP7 DoW and the revised FPP. We updated both, but would really appreciate if you could also have a look.
- itea Review: Please make sure that you provide all necessary information to the project office. In particular, please verify the status of WP7 deliverables.
- Tool Platform Evaluation: The document for the evaluation of tool platform is now ready for review - please provide plenty of comments and feedback. This effort is lead by Cecile.
- Secondary Tools:
-
Proposals are being accepted on the wiki page. -
We try to coordinate with WP4 to provide a list of criteria for VnV tools and Safety tools, we have planned to have a preliminary version for the end of June. -
An issue was raised during the VnV telco yesterday: Do we need technical presentations of the candidates for VnV and maybe secondary tools? See agenda below. - WP2 Deliverables: WP2 officially delivered all its deliverables in their final version, except D2.4 (which is due in September). A copy of these deliverables (for reference) was stored in the WP7 repository. Please note that D2.2 is labeled inside as "intermediate", even though it is the final version. A status summary has been created on the WP7 project page.
- Model Evaluation:
-
Lots of assessments are still missing: Deadline is 15th of June to have a final version of the document ready for the meeting of July! -
Looks like Why3 evaluation will be dropped in favor of GNATprove. -
Description on Core is still missing - SafeCap Presentation: On Tuesday (June 18th) at 10:30, there will be a GotoMeeting-Presentation on SafeCap. SafeCap is a project that may be of interest to the openETCS community. "The overall aim of the SafeCap project is to develop modelling techniques and tools for improving railway capacity while ensuring that safety standards are maintained."
| ID | Description | Due | Status | Notes |
|---|---|---|---|---|
| D2.1c | Report on existing methodologies | 31-May-2013 | delivered | |
| D2.2c | Set of requirements to be fulfilled according to CENELEC standards | 31-May-2013 | delivered | Note that this document is incorrectly labeled as "intermediate". |
| D2.3c | Definition of the overall process for the formal description of ETCS and the rail system it works in | 10-Jun-2013 | delivered | |
| D2.4c | Definition of the methods used to perform the formal description | 30-Sep-2013 | not yet due | |
| D2.5c | Methods and tools benchmarking methodology | 31-Mar-2013 | delivered | |
| D2.6c - D2.9.c | Requirements | 15-May-2013 | delivered | Aggregate of D2.6c - D2.9c |
- T7.1: Benchmark on means and tools: we have started the assessment phase. Assessors, please fill the document O7.1.3_O7.1.7 by the 15th of June
- T7.2: Benchmark on secondary tools: we are starting to investigate which examples are appropriate for the benchmark. Please check and update the wiki page.
- Tools for SSRS activities: The choice of tools to support the SSRS activites has now a high priority level, Marielle created a wiki page for this purpose. Please check and complete your proposal.
- Missing information: We are still missing benchmark information. Please complete asap CORE and Gnat Prove information.
- Review of Requirement document: WP2 produced a preliminary requirements document (D2.6 to D2.9). The review is scheduled until May 15 - please be sure to participate, if you have a stake in this document.
- SSRS Activities: This week's SSRS Activities will directly affect WP7s activities. No results from the Munich workshop have been published yet.
- Requirements Tool for SSRS: In order to start their activities, the SSRS team needs a compliant tool for requirements engineering. Finding such a tool is part of T7.2 (secondary tool chain). We may need to accelerate T7.2 activities to support the SSRS team.
- WP2 deliverables: A number of WP2 deliverables are due by the end of this month (i.e. Friday), including D2.1 (final), D2.2 (final), D2.3 (final), D2.4 (intermediate), D2.6 - D2.9 (final). Once officially delivered, we should make sure they fulfill our expectations.
- Benchmark activities: We are now late on the first step : providing items to the assessment (initial date was 17th of May).
-
Ready for assessment: SCADE, ERTMSFormalSpec, EA-SysML, Event-B -
Not ready for assessment: CORE, Classical-B, Gnat-Prove, Papyrus- sysML, System C, Why3 -
Noting on gitHub: GOPPR, PetriNet
- Evaluation Document: Marielle started the creation of O7.1.3 (Evaluation of the models against the WP2 requirements) and O7.1.7 (Evaluation of the tools against the WP2 requirements) - feel free to check it out and comment.
- Benchmark activities: We are still looking for assessors for some of the methods being evaluated. Please check the model evaluation wiki for what's missing and contact Marielle if you would like to volunteer.
- No face-to-face WP7 meeting until July 4th: For the upcoming WP7 activities, we will not organize a face-to-face meeting. But please be prepared for an increased number of online meetings to bring T7.1 and T7.2 to conclusion.
- Final Review of PCA: The PCA will be finalized soon and the review continues until June 4th. PCA and FPP can be found in the management repository.
- Model Evaluation (Marielle)
- Urgent: model evaluators, please fill in list of criteria: Tomorrow (Friday) has been set as the deadline to provide information about your method/tool. Please provide this information by tomorrow, and contact Marielle if you have questions.
- Benchmark activities on "secondary" means and tools: These activities have started and can be tracked on their wiki page. A corresponding email has been sent by Marielle. Please contact her if you would like to participate in these activities.
- SCADE-Model available for assessment: Uwe officially announced the Scade model to be ready for assessment. He will assist anybody interested in the assessment process.
- Ongoing Reviews (WP2)
- Review of D2.6 - D2.9 (final): The review has been officially closed.The aggregated review comments are not yet available. The final version of D2.6 - D2.9 will be published ty 30-Sep-2013
- Review of D2.4 (intermediate): The review comments have been aggregated, one item is still open. The review will continue until 18-May-2013. This is the review of the intermediate version, which will be published by 31-May-2013. The final version of D2.4 is due 30-Sep-2013.
- Review of D2.1, D2.2 and D2.3. (final): No news here, to the best of my knowledge, reviews continue until 18-May-2013.
- Status of ongoing reviews: Some of the ongoing reviews are documented int he governance repo. Finding a central place for documenting all ongoing reviews is under consideration.
- Project Management (Michael)
- Please ensure your effort for WP7: We have a lot of activities coming up in WP7: Marielle (T7.1 and T7.2) needs help with the model evaluations, and Cecille (T7.3) is preparing the implementation phase. We need to know who is going to provide resources for this work. The project office (Baseliyos) is currently updating their numbers and will announce it next week. Once the numbers are distributed, please check them and report errors back. Some numbers have been floating around the past few days, but we're still waiting for the official numbers.
- Face-to-Face meeting: We were hoping that WP3 would organize a workshop that we could tag onto for some of our own activities, as well for a knowledge exchange with WP3. It seems that no WP3 workshop will take place. As none of the WP7 tasks leaders sees the need for a face-to-face meeting before our 4-Jul-2013 workshop, there will not be one.
- Glossary and Bibliography: Cecille made a shared glossary and bibliography available (in Latex), please take advantage of it.
- FPP and PCA: Updated versions of these documents are now available.
- New shared Calendar: The Project Office is transitioning to a new shared calendar. IMPORTANT: You need to request read access from the project office.
- You will NOT receive calendar invitations for WP7 events any more - instead, they will just pop up in your calendar.
- As no invitations are sent any more, important events or changes will be announced on the mailing list.
- Shorter Friday meetings: The PMB decided to shorten the Friday meetings to 15 minutes. The WP7 Telco will take place from 11:00 - 11:15. This is already reflected in the new shared calendar. Reviews: The following reviews are currently taking place (please let me know if I have forgotten any). Please be sure to participate in the review process if you are a stakeholder!
- Until May 18th: D2.3 OpenETCS process proposed a description of the design process to apply during the project. This is a final version of the document.
- Until May 18th: D2.4 OpenETCS methods gives an introduction to formal methods and will be complete after the decision meeting of July. This is an intermediate version of the document.
- Until May 15th: D2.6 - D2.9 (Requirements). Please send your review results to Sylvain via the Review sheet (Excel)
- Evaluations: Marielle initiated the next step of the benchmark evaluations:
-
Files are available for O7.1.3_O7.1.7_O7.1.9. Participating partners are invited to fill the corresponding Latex file by May 17th. - Also, please check that all the elements necessary for the assessment are available on the model-evaluation repository and the wiki pages are updated.
- When you have finished please to inform the assessors and Marielle that the assessment phase can start.
- The evaluations are taking advantage of the gitHub issue tracker for their work. Please check it out if you are interested in the activities.
- WP3 Meeting: Pierre-Francois Jauquet is currently evaluating the need for a WP3 meeting end of May/early June. Should such a workshop take place, WP7 should be prepared to use it to ensure that WP3 needs are incorporated into our method evaluation (beyond what's documented in the WP2 deliverables).
- Review of Requirement document: WP2 produced a preliminary requirements document (D2.6 to D2.9). The review is scheduled until May 15 - please be sure to participate, if you have a stake in this document.
- Status of D2.3 (Definition of the overall process for the formal description of ETCS and the rail system it works in): This deliverable will be made within a day or two for review. This will be the draft for the final (rather than intermediate) deliverable.
- Review Template and Evaluation Matrices: Marielle is currently working on a revision of the Review Template, which will also clarify the roles of the various matrices, see next item.
- Evaluation Document: Marielle started the creation of O7.1.3 (Evaluation of the models against the WP2 requirements) and O7.1.7 (Evaluation of the tools against the WP2 requirements) - feel free to check it out and comment.
- Review & Sign-off Process: There has been quite a bit of discussion regarding the review process and the (now renamed) sign-off, that has been taking place for deliverables to WP7. It is important that we have a clear understanding of a defined process and follow it. This issue has been escalated to the project office.
- Assessors: We got new assessors, but are still looking for assessors for some of the methods being evaluated. Please check the model evaluation wiki for what's missing and contact Marielle if you would like to volunteer.
| ID | Description | Due | Status | Notes |
|---|---|---|---|---|
| D2.1c | Report on existing methodologies | 31-May-2013 | not yet due | There will be few differences to the intermediate version. |
| D2.2c | Set of requirements to be fulfilled according to CENELEC standards | 31-May-2013 | not yet due | |
| D2.3c | Definition of the overall process for the formal description of ETCS and the rail system it works in | 31-May-2013 | not due yet | Review until 18-May-2013. |
| D2.4b | Definition of the methods used to perform the formal description | 31-May-2013 | not yet due | Review until 18-May-2013. According to Sylvain, it's due mid April; Marielle: "I think it is better to wait the results of WP7 Task1 to write this document, thus my proposal was to postpone its date. For the moment nothing is clearly decided." |
| D2.4c | Definition of the methods used to perform the formal description | 30-Sep-2013 | not yet due | |
| D2.5c | Methods and tools benchmarking methodology | 31-Mar-2013 | delivered | This deliverable is also the final deliverable. |
| D2.6c | Set of requirements for the model used and the modeling process: | 15-May-2013 | not yet due | Review until 15-May-2013. D2.6 - D2.9 are contained in one document (in the D2.6 folder) |
| D2.7c | Intermediate Set of requirements for API | 31-May-2013 | not yet due | |
| D2.8c | Set of requirements for the tools used | 31-May-2013 | not yet due | |
| D2.9c | Set of requirements for the tools used | 31-May-2013 | not yet due |
- WP7 Workshop Materials: The materials from the workshop are now online - enjoy.
- Review of Review Template (O7.1.3): Please provide feedback by May 3 to Marielle.
- Evaluation Matrices: The session on April 16 in Munich initiated a lot of activities and discussions regarding this topic. Amongst others, it was decided to create a tool artifact matrix and a compliance matrix. So right now, there are three matricees:
- WP2: Requirements to be fulfilled by Tools to be used within openETCS by Merlin as part of D2.2. The review period for D2.2 has been extended to 3-May-2013.
- WP4: Jan Welte distributed a Safety Evaluation Criteria Matrix via email.
- WP4 Marc Behrens distributed a V&V Evaluation Criteria Matrix via email.
- Subsystem-Requirements Specification: There is now a repository for these activities.
- QA Plan: A revised QA-Plan is available, feedback is requested by Friday to DB (Rico and Baseliyos) Review results of D2.1, D2.2 and D2.5: We closed collecting feedback on the deliverables and distributed a summary of the results. The raw feedback is also available. Parallel to this, there was the announcement that D2.1 and D2.5 are being updated again.
- Assessors: We are still looking for assessors for some of the methods being evaluated. Please check the model evaluation wiki for what's missing and contact Marielle if you would like to volunteer.
We just closed the evaluations of three deliverables that are important for WP7. You find the raw feedback and snapshots of the deliverables on gitHub. You find a summary of the feedback below. The rating took place on a scale from 2 (Accept) to -2 (Reject).
- D2.1 Methodologies (almost final version)
-
The deliverable was accepted with a score of 1.5. There were 6 people evaluating it. -
At least one reviewer considers the document preliminary: "I miss more details on support tools such as requirement tracing, team organization and versionning. These are considered as 1 criteria and such kind of tools are not explicitly covered. " -
While another rates it as excellent on all aspects: "Excellent state of the art document" -
Considering the relatively consistent rating (almost all scores were 1 or 2), we consider this deliverable sufficient for our WP7 activities. - D2.2 CENELEC requirements (intermediate)
-
The deliverable was weakly accepted with a score of 1.17. However, this is due to one rating of -1, while all others were 1 or 2. There were 6 people evaluating it. -
The negative rating was associated with low confidence of the reviewer (Jonas Helming). I would suggest for Merlin and Jonas to get in touch to understand the concerns. -
One reviewer (Marc Behrens) posed a number of specific questions that should be addressed in the next version of this document -
Considering the relatively consistent rating (almost all scores were 1 or 2), we consider this a sufficient intermediate deliverable for our WP7 activities. - D2.5 Benchmarking Methodology (final)
-
The deliverable was weakly accepted with a score of 1.17. There were 7 people evaluating it. -
The strongest criticism was with respect to the scope. The reviewer (Stefan Rieger) found the content of the document incomplete with respect to its title (and by extension, I would guess, with respect to the FPP). He states that "it does not contain any process or methodology for benchmarking as the title suggests. Thus, in my opinion it is an incomplete and not a final document". -
Considering that this is a final deliverable, we need to discuss further within WP7 on whether this deliverable can serve as the foundation for benchmarking in its current form.
- WP7 Workshop: The workshop this week in Munich was very constructive. Workshop artefacts (minutes, videos, etc.) are being circulated right now.
- Upload your Workshop slides: Marielle created a repository location for the presenter's slides - please upload your materials, ideally converted to PDFs.
- WP1 UnConference: More activities will take place next week Monday and Tuesday.
- Next WP7 Workshop on July 4 in Paris: We decided to organize WP7 workshop right after the itea review in Paris, so please save the date. This event will take place right after the decision on method, tools and tool platform have been made. So the objective of this workshop will be the dissemination of the results of the corresponding deliverables (D7.1 and D7.2).
- Reviews of WP2 Deliverables: Please provide feedback on the completed WP2 deliverables by Monday, April 22.
- Reviews of WP2 Deliverables: Please provide feedback on the completed WP2 deliverables by Friday, April 12:
-
D2.1 Methodologies (almost final version). https://docs.google.com/forms/d/1lkOtecm4jWrG971s5YLCH4WrqKuoX3z-WYfLFitHIT0/viewform -
D2.2 CENELEC requirements (intermediate). https://docs.google.com/forms/d/1xJ5Hf-fnbBuP_-GmJYOu0tjN-HEZn-9wxnBxrIifAoI/viewform -
D2.5 Benchmarking Methodology (final). https://docs.google.com/forms/d/150D_mnXuu5ra1rO4vdJ1kwRW6pJ1veplgiebn1Dc9cU/viewform - WP7 Workshop: The agenda received further updates - please check for the latest information. In particular, the events for April 22 and 23 were added. Please update your attendance status accordingly.
- Criteria: Marielle created a first draft of tool evaluation criteria. It is my understanding that this list will be further discussed on April 16 at the evaluation matrix session at 16:00.
- Method Evaluation Presentations: Marielle created a guildeline for the content to be presented. We encourage the presenters to structure their content as shown there, to aid the comparison of methods. Further, we encourage presenters to create and/or maintain a wiki page describing their approach following this template.
- Assessors wanted: We need volunteers to assess the model evaluations. Please contact Marielle if you would like to volunteer. In particular, we need assessors for Core, Classical B, Gnat Prove and GoPRR.
- Munich Workshop: All information regarding the Munich workshop (starting Monday, April 15) can be found in the WP7 wiki. Please make sure that the information shown there is up to date, especially if you offering a talk or a training.
- Dinner on Monday, April 15: We are happy to announce that DB Netz will sponsor a dinner on Monday, April 15 in Munich on site - thank you very much. If you intend to stay for dinner, please indicate this on the following Doodle by Monday, April 8, so that we know how much food to order.
- WP2 Deliverables: Due to the safety strategy discussions, the delivery of some WP2 deliverables was postponed - here is the status of the 9 deliverables. Others have already been delivered in their final (or almost final) version (D2.1, D2.5).
As of April, all updated deliverables should be available. The deliverables can be found in the WP2 repository.
Note that technically, three intermediate deliverables are delayed, and three intermediate deliverables will be revised once more. This is no big deal. We now expect all deliverables end of March.
| ID | Description | Due | Status | Notes |
|---|---|---|---|---|
| D2.1b | Report on existing methodologies | 15-Mar-2013 | delivered | This is almost the final version, which will provide informations on the interviews. It should not alter the summaries on the methods. |
| D2.2b | Set of requirements to be fulfilled according to CENELEC standards | 15-Mar-2013 | delivered | |
| D2.3b | Definition of the overall process for the formal description of ETCS and the rail system it works in | 12-Apr-2012 | postponed | A review version will be distributed by Marielle on April 12. |
| D2.4b | Definition of the methods used to perform the formal description | 15-Apr-2013 | not yet due | According to Sylvain, it's due mid April; Marielle: "I think it is better to wait the results of WP7 Task1 to write this document, thus my proposal was to postpone its date. For the moment nothing is clearly decided." |
| D2.5b | Methods and tools benchmarking methodology | 31-Mar-2013 | delivered | This deliverable is also the final deliverable. |
| D2.6b | Set of requirements for the model used and the modeling process: | n/a | postponed | Sylvain: D2.6 to 9 is delayed in order to reflect what was decided on the safety strategy. It will not cause change in the main “requirements” part, but mostly on the process part (and it should be minor). I do not have an ETA for the moment, because I will wait for the MoM of Charleroi workshop to be finalized before updating my document. |
| D2.7b | Intermediate Set of requirements for API | n/a | postponed | see above |
| D2.8b | Set of requirements for the tools used | n/a | postponed | see above |
| D2.9b | Set of requirements for the tools used | n/a | postponed | see above |
- QA Document: Work on the QA document document continued.
- Safety Strategy Minutes:* The Minutes of the Paris meeting have been published. The minutes are complemented by a figure provided by Mr. Jauquet (attached). It has been planned to incorporate the figure into the minutes. The results from the meeting will be used to revise the WP2 deliverables.
- Status Deliverables WP2: Three documents that are relevant for WP7 have been delivered. Note that the requirements repository is private. Therefore, the links will only work if you are logged into gitHub and if you have read access to the repository.
-
**D2.1b Report on existing methodologies:** This is almost the final version, which will provide informations on the interviews. It should not alter the summaries on the methods. -
**D2.2b Set of requirements to be fulfilled according to CENELEC standards:** The current version states "preliminary" in the document, even though it should be intermediate. -
**D2.5b Methods and tools benchmarking methodology:** This deliverable is already the final deliverable, ahead of time. Thanks! - WP7 Workshop, Day 1: The agenda of the workshop on April 15th is now complete. The activities on the 15th are open to the public, so please spread the word (the link provided is public, too). Please make sure that your attendance status in the Doodle is correct.
- WP7 Workshop, Day 2: The WP7 activities on the second day are coordinated by Marielle and also documented on the workshop page.
- WP1 UnConference: The activities for the UnConference are coordinated by Mr. Jacob and Dr. Hase and are currently documented in the doodle. (check the comments). One definite activity is the 1-day ERTMSFormalSpecs training on the 17th (please update the doodle if you plan to attend).
- Toolchain repository is now public: As decided by the PMB
- Status of WP2 Deliverables: All intermediate deliverables will be available end of March, the precise status is, documented here.
- Use of a semi-formal model: One result of the safety-meeting in Paris was the there will be a semi-formal model as an intermediate to the final model.
- QA document: A revised version of the QA document is available. As this affects our work (even though it is not a direct input), we have to make sure it fits our needs.
In March, a number of WP2 deliverables are due. The deliverables can be found in the WP2 repository.
Note that technically, three intermediate deliverables are delayed, and three intermediate deliverables will be revised once more. This is no big deal. We now expect all deliverables end of March.
| ID | Description | Due | Status | Notes |
|---|---|---|---|---|
| D2.1b | Report on existing methodologies | 15-Mar-2013 | delivered | This is almost the final version, which will provide informations on the interviews. It should not alter the summaries on the methods. |
| D2.2b | Set of requirements to be fulfilled according to CENELEC standards | 15-Mar-2013 | delivered | The current version states "preliminary" in the document, even though it should be intermediate. |
| D2.3b | Definition of the overall process for the formal description of ETCS and the rail system it works in | 31-Mar-2013 | not yet due | |
| D2.4b | Definition of the methods used to perform the formal description | 31-Mar-2013 | not yet due | According to Sylvain, it's due mid April; Marielle: "I think it is better to wait the results of WP7 Task1 to write this document, thus my proposal was to postpone its date. For the moment nothing is clearly decided." |
| D2.5b | Methods and tools benchmarking methodology | 31-Mar-2013 | delivered | This deliverable is also the final deliverable. |
| D2.6b | Set of requirements for the model used and the modeling process: | 31-Mar-2013 | not yet due | |
| D2.7b | Intermediate Set of requirements for API | 31-Mar-2013 | not yet due | |
| D2.8b | Set of requirements for the tools used | 31-Mar-2013 | not yet due | |
| D2.9b | Set of requirements for the tools used | 31-Mar-2013 | not yet due |
- Paris Workshop: This week was dominated by the paris workshop, results are being disseminated. There were few other activities this week.
- Userstories: The userstories have been published (Sharepoint).
- Glossary/Terminology: WP2 (Jan Welte) distributed via email a first catalogue of word from the English and German FPP, which will serve as the starting point for a glossary.
- New deliverables from WP2: There were some announcements on WP2 deliverables. Next week, I'll create a summary of the updated deliverables that are relevant for WP2.
- WP2 Deliverables: There are preliminary versions of WP2 deliverables available. The intermediate versions are due mid March. The aim is to launch a discussion of the contents of these documents. To do so, please respond to the messages that were sent by Mariellle, Sylvain and Guillaume. The deliverables are:
- D2.3 (Definition of the overall process for the formal description of ETCS and the rail system it works in)
- D2.4 (Definition of the methods used to perform the formal description)
- D2.5 (Methods and tools benchmarking methodology)
- QA Plan: An intermediate version of the QA plan is available. Feedback is requested by Rico by March 18.
- Eclipse Platform Evaluation Propsal: The Proposal got accepted.
- Governement Proposal: There is a new Proposal by Bernd Hekele (DB)
- API Requirements: Pierre-Francois Jauquet distributed a preliminary API Requirements documents. As of this writing, it was only distributed via email.
- Paris Workshop March 11-13: There will be a workshop on "requirements on API" and "safety strategy" in Paris. For WP7, Marielle will attend. If you have questions or would like to attend, please coordinate with Marielle. The program is confirmed (apart from a few minor issues).
- WP7 workshop: The workshop now stands, the various model evaluation teams are assigned to time slots (this effort is lead by Marielle). Please make sure that you have accommodation, if you decide to attend. DB will help with accommodation.
- Project Plan Matures: The WP leaders and the Project Office are almost done with the overall project plan. WP7 coordination with all other WPs is complete.
- Benchmarking Activities: Preparation for the benchmarking has started, lead by Marielle.
Goals: Reviewing WP2 Deliverables
- WP7 Workshop: There will be a WP7 Workshop in Munich from 4/15 (afternoon) - 4/16 (morning). This event is co-hosted with the WP1 UnConference. If you are participating in a WP7 method evaluation, we strongly encourage you to participate.
- WP1 UnConference: The UnConference provides an opportunity for method evaluators to offer trainings and to continue networking.
- WP2 Requirements Review Feedback: WP2 summarized some important disagreements on the requirements deliverable and will work on resolving these. Please participate in the discussion if you are a stakeholder.
- WP2 Deliverables D2.1 and D2.2 accepted: Quite a while ago, WP2 produced the two deliverables Methodology-Report (D2.1) and Report on CENELEC EN 50128 compliance (D2.2). We consider these deliverables as accepted as well.
- Project Plan Matures: The Project Office distributed an aggregated version of the project schedule. The DoW has been updated to reflect this information. Particularly important for us are the WP2 deliverables.
- WP2 Schedule: WP2 will provide three versions of each deliverable: a preliminary, an intermediate and a final version. 6 preliminary deliverables have been produced, the rest are due end of February. The intermediate deliverables will be available mid and end of March.
- WP2 Deliverables: Methodology-Report (D2.1), Report on CENELEC EN 50128 compliance (D2.2) and Requirements Synthesis (D2.6, D2.7, D2.8, D2.9)
- Feedback on WP2 Deliverables: We promised high-level feedback on the requirements by tomorrow (Friday). You can still give feedback. As a preliminary result, the WP7 community seems to weakly accept it. Weaknesses exist especially in Chapters 7 and 8. The final result will be published tomorrow.
- Model Evaluation: Please note the updates on the wiki pages of the model evaluation: And Benchmark activities.
- WP7.1 Task leadership: Last late year, CEA withdrew as task leader for WP7.1, and Systerel took over interim leadership. CEA is now engaged again and is actively supporting Marielle. Considering that the task will complete in the middle of this year anyway, we decided that it does not make sense to switch task leadership again. Therefore, Systerel will take on permanent leadership of WP7.1.
- WP7 workshop: Announced for a long time, we can finally plan a WP7 workshop. The reason for the delay was the pending project plan. Due to the delivery schedule of WP2, it makes sense to plan the workshop in a way, such that we can give timely feedback to the intermediate WP2 deliverables. This would suggest early April (a separate email will be send shortly).
The goal of this Sprint is the finalization of the overall project plan, including time line and dependencies to other WPs.
The following deliverables from WP2 are now available:
- Methodology-Report
- D2.1: Report on existing methodologies
- Report on CENELEC EN 50128 compliance
- D2.2: Set of requirements to be fulfilled according to CENELEC standards (state-of-the-art)
- Requirements Synthesis
- D2.6: Set of requirements for the model used and the modeling process:
- D2.7: Set of requirements for API:
- D2.8: Set of requirements for the tools used:
- D2.9: Set of requirements for the verification and validation process:
- Model Evaluation Repository: (since Dec-12): Please visit the model-evaluation project to follow the activities. Currently, five evaluations have artefacts in git (Classical B, Event-B, SysML, GNATprove and Why3). Also check out the wiki for information on how to contribute.
- Model Description Template: Matthias Güdemann provided a template for the model description, which should facilitate comparing models. (Example, provide Feedback)
- Overall Project Plan / WP coordination: (since 14-Jan): This week, another coordination meeting took place, this time in Cologne. The project office is currently aggregating the information. Expect changes to the WP7 DoW next week to reflect the new information.
- WP7 workshop: (time tbd): We are currently deciding whether there will be a stand-alone WP7 workshop, or whether it will be held together with another WP (WP2 or WP3). Expect more information and a doodle next week.
- Open Workshop on Formal Methods (FM) for openETCS: (time tbd): This is NOT a WP7 event, but an even organized by the project office. (Doodle Poll)
- Requirements from WP2 (D2.3): WP2 produced a draft deliverable, that is essential for the work in WP7. They expect feedback by next week Friday (15-Feb). Please provide feedback using this form.
The goal of this Sprint is to prepare for the change request meeting in Munich (1/15 and 1/16), and to take actions from the result of this meeting.
Further, the prototyping efforts will continue.
Happy Holidays!
The goal of this Sprint is to start work on the actual tasks. This work is lead by the task leaders.
A crucial input of the prototyping is a representative subset to be formalized. Such a subset has not yet been defined yet (even though prototyping has already started, see below). We need to work with WP2 to create such a subset as quickly as possibly, ideally taking the prototyping work already into account.
There are already a number of prototyping activities underway. It is important to align these activities. Known activities are listed at EvaluationProposal
The WP2 meeting in Paris fell into the middle of this sprint. Therefore, the goal of this sprint is validation of the DoW with all participants and validation of the timeline.
Same as for Sprint 5
In particular due to the delay from WP3b (because of the missing WP leader), we extend the review of the DoW by one sprint iteration.
Also, in order to actually start working, input from WP2 is needed (which is not yet available). Therefore, this will be a relatively quiet sprint.
- Resolve all open tracker issues
- Solicit feedback from interfacing work packages mainly (WP2 and WP3b)
- Straighten out the schedule (inputs, outputs, dates) and validate with other work packages.
At the end of the sprint, there were still two tracker issues open. We got some great feedback from WP2 (WP3b did not have a leader at that point). The schedule was straightened out, except task 1.
In this sprint, the task managers are responsible for achieving their sprint goals. At this point, this is:
"Distill their task description in the DoW into a 1-page section that has well defined subtasks with inputs and outputs".
This time we split the ownership of the sprint between the different sections, see below.
Expertise of the participants is documented on the Team page.
| Name | hours |
|---|---|
| Daniel Plagge | 10h |
| Hardi Hungar | 12h |
| Jonas Helming | 20h |
| Marielle Petit-Doche | 40h |
| Stanislas Pinte | 40h |
Owners of the chapters of the DoW:
- Core Tool Chain Analyses and Recommendations: Stanislas Pinte
- Supporting Tools Analyses and Recommendations: Marielle Petit-Doche
- Define and Develop Tool Chain: Jan Pelska
- Develop Open Source Ecosystem: Jonas Helming
Goal: "Validate the DoW with all stakeholders"
The "owner" of this sprint is Stanislas Pinte.
Expertise of the participants is documented on the Team page.
| Name | hours |
|---|---|
| Cecile Braunstein | 25h |
| Chokri Mraidha | ?? |
| Christophe Gaston | ?? |
| Daniel Plagge | 5h |
| Jan Peleska | 8h |
| Jonas Helming | 40h |
| Michael Jastram | 5h |
| Silvano dal Zilio | ?? |
| Stanislas Pinte | 40h |
| Virgile Prevosto | ?? |
Goal: "Adapt and refine the DoW as we see fit, coordinating with other WPs as needed"
We won't practice proper Scrum at this time - for instance, trying to perform "Daily Scrums" currently does not make much sense. Over time, we will adapt more and more Scrum practices, as we see fit.
- If you participate in this sprint, please let the group know (via this list) how much time you will spend on this iteration.
- Please go ahead and work on the document. At least initially, please report your activities on the mailing list.
- Don't ask to add new content, just do it. If thinks are unclear or you want to comment, then please write these in the margin (the way I already did).
- Whether you participate or not, please take advantage of this sprint to explore our tools: Make a clone of the repository and use Latex to modify the document.
- I didn't apply the Latex template from Fabien yet. Maybe someone would like to do this?
- It's not clear to me what the best process for contributing is for those that are not committers yet. The ecosystem project should be able to provide us with some guidance. Please pose such question on the ecosystem mailing list. For now, you can use gist to submit patches.
- I'd like to use the Friday 11:00 slot for discussion. Please let me know if you think we should have a telco sooner than that.
- Attendance-Information: http://doodle.com/ydtsy2icd34qe9fe
- This Sprint will be "interrupted" by the git/scrum workshop in Munich, 8/21-8/22
Expertise of the participants is documented on the Team page.
| Name | Company | Munich | hours |
|---|---|---|---|
| Merlin Pokam | AEbt | yes | 12 |
| Norbert Schäfer | AEbt | yes | 4 |
| Klaus-Rüdiger Hase | DB | yes | |
| Stanislas Pinte | ERTMS Solutions | no | 28 |
| Uwe Steinke | Siemens | yes | 8 |
| Alexander Stante | FhG | yes | |
| Michael Ditze | TWT | ? | |
| Jens Gerlach | FhG | ? | |
| Michael Jastram | Formal Mind | yes | 20 |
| Fabien Belmonte | Alstom | no | 8 |
| Total | 6 |
Note: Considering the available resources and the state of the project, the best use of time is to get up to speed with the tools to be used, considering that most team members have no experience with it yet.
| ID | Task | Owner | h |
|---|---|---|---|
| T-11 | Create a personal gitHub account. Familiarize youself with the account | all | |
| T-12 | Create a Repo on your gitHub account (this will be public, so don't add anything openETCS-specific). | all | |
| T-13 | Create a few wiki pages on your repo, and cross-link them. | all | |
| T-14 | Explore the Issue tracker by creating an issue, and closing it. | all | |
| T-15 | If time permits: Get involved with other WP3a team members and clone someone else's repository. Then make a change and find a way to commit those changes to the other repo. | all |
Unprocessed relevant information goes here, for now.
A comment of older email sent in August.
[ About Sprint Backlog ] Le 07/08/2012 23:22, Michael Jastram a écrit :
Compile a list of target tools
Fernando Mejia of Alstom already compiled a pretty extensive list of available formal methods and presented it at an openETCS meeting. This should be used as starting point.
Moreover, I am maintaining a list of Free Software that can be used for formal verification: http://gulliver.eu.org/free_software_for_formal_verification
This can also be used as input.
Best regards, david
| ID | Task | Owner | h |
|---|---|---|---|
| T-1 | Create and review the Workpackage charter. | ||
| T-2 | Complete the DoW description1 by collaborating with the WP3b leader to make sure the separation of WP3a and WP3b is clearly defined. | ||
| T-3 | Follow the openETCS process and create a proper project or contribution for the work to be done. |
| ID | Task | Owner | h |
|---|---|---|---|
| T-4 | Create backlog items, based on deliverables and in collaboration with product owner. | ||
| T-5 | Identify and document dependencies to other WPs. | ||
| T-6 | Identify backlog items with no or few dependencies (to be used for subsequent sprints). |
| ID | Task | Owner | h |
|---|---|---|---|
| T-7 | Create list of tool evaluation criteria. | ||
| T-8 | Create and document the infrastructure for documenting tools (Wiki? Latex? ...?). | ||
| T-9 | Compile a list of target tools. | ||
| T-10 | For each tool: evaluate against criteria. |
Proposed by Silvano Dal Zilio
Just to put, in a writing form, the proposal I put forward after our lunch break. The idea is to send a questionnaire asking the participants some information on the tools they plan to use/develop/integrate during in the context of the project.
This questionnaire could be merged with other similar initiative at the WP level, so that we do not send several similar questionnaire in a short period.
For task M3.1.2, it would be useful to have the following information.
- name of the tool you want to interface
- type of tool (Modeler/editor; simulation, test-generation, code generator; ...)
- contact email
- url for documentation
- list of projects or toolboxes (only list the representative examples) where the tool has been integrated + some information on the toolchain architecture that has been used (e.g. Eclipse Modeling / OSGI)