Each team creates a github repository, which should contain a deliverables directory located at the root. In this directory, two files are mandatory:
status.mda markdown file, updated each Sunday at midnight at the latest. This file should contain a log for each week, showing what was achieved, what is planned for the following week, what are the blockers and risks. Do not drill down in the content details, this is just a status report, but fill it consistently and honestly. In addition, indicate a Red/Yellow/Green flag showing your perception of where you think you are compared to where you think you should be. Each week, you should add the status to this file, on top, with the date, but leave previous week statuses below, do not replace, so you can see the full history in the blink of an eye.architecture.pdfcontains the current state of your architecture. The format of this document is up to you, it will grow during the project and should contain a living description of your architecture, with diagrams and explanation texts. In addition, the content of that folder should be taged withtag_[weeknumber]with[weeknumber]the two-digit number of the week of the Wednesday of the delivery, as can be checked on this website.
Schedule of deliveries, and feedback on the deliverables can be found here
- Next delivery: Wednesday, Oct 10th at midnight. Component diagram, roadmap
- Nov 2nd: POC ready, oral defense
- March 1st, 2019: final demo, oral defense
- March 1st, 2019: delivery of video
-
Week #1: Overview, Organisation, Case Study, Project
-
Week #2: Build the Right system
-
Week #3: Build the system Right
-
Week #4: Architectural Approach
-
Week #5: Architecture Types, Architecture Evolution
-
2017 mid-term evaluation
-
Week #2.1: Organisation bimestre 2
-
Industrial presentation #1: Greencom Networks
-
Industrial presentation #2: Apera
-
Industrial presentation #3: MyCoach