Appeals have been reviewed and grades updated
|The appeals have been reviewed. Please find the appeal reply at the secretaries' office (lobby floor). The grades of those whose appeals were accepted were updated in GR, and the UG will update in the next week or two.|
Further Grade Details, new Appeals date
|In order to be as transparent as possible, two columns were added to the grades detailing in finer resolution the remaining 55% of the final grade. The Column "Relative_Contribution", which is 25% of the grade, and "Software_Engineering", 30% of the grade.|
In the "Software_Engineering" grade two main components are weighed:
1. Your contribution of essential and meaningful code and issues, internal documentation and overall contribution to teamwork on the project in GitHub.
2. The project's Test runs and "HLD" & "Test Plan" documents.
The new Appeals deadline is 21.2.18
Final Presentation and Course Grades Published, Appeals
|Dear Students of the Yearly Project,|
The grades have been published for the Final Presentation and the Course Grade.
As mentioned before, the grades were comprised of 20% POC Presentation, 25% Final Presentation and 55% Work as detailed in previous post.
For those who wish to appeal, please find in the following link the form with instructions on how to appeal formally.
Please note: DO NOT contact your supervisor with questions about the grades. If you wish to appeal, the only way to do so is on paper, as detailed in the link.
We wish you all success in the rest of your exams!
Remainder Grading and instructions of project installation
|Dear Students, |
The remainder of the grade (55 points) in the course will be given by the staff of the course on the following (in descending order of importance):
1. Each student's work in GitHub
2. A number of test runs of the project at its current state of development by the project's supervisor
3. Internal documentation in code
4. The HLD and Test Plan documents written at the early stage of the project
Please provide by 22/1/18 simple documentation with installation instructions for the supervisor to run the project. Write the prerequisites needed in order for everything to be able to execute smoothly (what tools are necessary to have installed, any PATH variables that need to be added).
Treat this as "installation instructions for a new developer joining the team" scenario.
End of Semester "Live Demo" Presentation sign up sheet and info
Below please find the sign up sheet for the time slots of the "End of Semester Live Demo Presentation".
Attendance on both days is mandatory.
Please read the following CAREFULLY.
The presentation will need to include all of, but not limited to, the following points:
1. A Summary of the essence of your project - remind us about the problem you are solving, and the solution you are suggesting, and the tools you are using to solve it.
2. Testing - this is where you discuss "how you prove that your solution works". What are the tools you use (unit tests, continuous integration that shows build passing and run automatic tests, manual tests, other)
3. Error Handling - does your system keep a log, in case the user has any input errors, does your software communicate this to the user or simply crash, etc.
4. LIVE DEMO - this is, naturally, the core of your presentation. Here we need to see a working example that demonstrates how your system works. DO NOT waste time showing "login" or "sign up" screens,
we will assume they exist. **We want to be impressed with the features and the stability of the system** (meaning, crashes are not welcome in such a demo). DO show handling user errors and any "edge cases" or interesting cases you can think of.
5. Next Steps - this is where you talk about what is planned for the future, what features are left unimplemented, enhancements, expansions, technologies you may want to add, etc.
Notice that the time for the presentation is 20 minutes. The Live Demo part should take, at the very least, 10 minutes of those, and you have 10 minutes to prepare between presentations. (No "Mockups" this time!)
Grading: This presentation is more substantial in terms of depth and expectations than the mid-semester, and therefore will be a total of 25 points from your total grade.
The grading will be done in the same way as in the mid-semester presentation, meaning, the supervisors NOT directly in charge of the team will give a grade based on their impression from the presentation of the work ofthe team, the features implemented AND demonstrated and the complexity of the project in total relative to others.
The supervisor in charge of the team will give a grade that will be calculated with a lower weight into the total.
The presentation should be prepared and rehearsed to make sure that you communicate your ideas clearly to an audience that is not aware of the details and intricacies of your project.
Time yourself, and **use the FULL 20 minutes**. This will ensure that you are given enough time to do justice to your project and your team.
**Attendance Mandatory** in Proof of Concept Presentations on Both Days
|Clarification regarding the Presentations forum:|
The presentations will be given in the presence of the supervisors and **all students in the course**, on both days, without exception, during the course hours in our regular room, Taub 3.
Proof Of Concept Demo: Update and Grading policy
|As it is still an early stage in the progress of the semester, we've decided to replace the "live demo" part of the presentation with a different approach. |
The parts of the presentation are:
1. Project description: The students in the team, the problem you are trying to solve, your goals, and any other information you think is relevant to the project.
2. Features planned to be included in the project.
3. The goals for Sprint 1 (the presentation) and the goals for Sprint 2 (the end of semester) with details regarding the timetable to the end of the FIRST semester.
4. A mockup of the GUIs you will be using in the project: show what they should ultimately look like at the end of the project.
(Find a free online mockup tool, google keywords such as "free ui mockup wireframing prototyping")
5. Screenshots/video of the *working features* in your projects (if no features are currently working, expand on the previous sections)
Since we will not have a live demo, this means the presentation should be more substantial in terms of details.
The presentation will count towards your final grade in the semester a total of 20 points, all members of the team receive the same grade (unlike the semester grade, which is individual).
This means the presentation should do justice to the project: make sure to include *all* the planned features and explain them well.
The grade will be given based on the complexity of the project as presented relative to others, and based on the general level of the teamwork up to this point in the semester.
You have 20 minutes to present, no more, so time yourself when you prepare. Select the people in your team that will present the best (you can have multiple presenters).
Mid Semester Proof Of Concept Presentation
|Below you will find a link to the time slots document for the presentations that will take place on December 24-25. |
Please fill in your preferred presentation time.
Each group will have 20 minutes, 10 minutes for a Slideshow presentation, and 10 minutes for a Proof of Concept (POC) demonstration.
The slideshow should be NO MORE than 10 minutes in length (so time yourself before) and should include:
1. The general idea of the project (what is it about, your goals, etc.)
2. Sprint 1 objectives
3. Sprint 2 objectives
(You can choose who among your team presents best the slideshow, you don't all have to talk)
Following this, all the team will be on stage and you will demo what you have prepared as a POC.
Between each group's presentation you will have 10 minutes to set up. (first group, arrive at 12:20 to set up your presentation)
Guest Lecture TOMORROW 4/12 Taub 3 12:30 (Mandatory attendance)
Test Plan Template has been uploaded in "Course Material"
|Test Plan template should be filled in and handed next week to your project supervisor. |
Please go over the document carefully before asking questions. The features for which you are writing the test plan are the ones you have provided in the HLD document.
Guest Lecture next week 4/12 Taub 3 12:30 (Mandatory attendance)
HLD Template Uploaded to Course Material
|A High Level Design (HLD) Template page was added to the course material section. Please read the detailed description inside to help you in writing and understanding what an HLD means.|
The HLD is expected from each project to be handed in to the supervisor next week, or by a different date that the supervisor and the group agreed on.
You can now create new repositories in TechnionYearlyProject Organization in Github
|ONE MEMBER ONLY from each project will need to go to the "Yearly Project" organization in GitHub and click on "create a new repository". |
After that, all the other members in the team will be able to clone it into their local machine.
After Creating the new Project, Add your team members to the project and each one should test with a new commit. No need to create any issue for it yet.
Teams and Project Preference form
|In the following link, please write in any of the available columns the names of the 6 members in the team you are forming.|
Under those, please fill in your 4 preferred projects in descending order, according to the numbers that they are listed in the file.
Telegram & Github User Info
|Hello Yearly Project Students,|
In the following link, please fill in your information in each column after you've created your new accounts on Telegram and Github.
First Lecture in the course
|Hello and Welcome to the Yearly Project in Software Engineering !|
The first lecture in the course will take place on Monday, October 23rd, Taub 3 at 12:30- 14:30.
See you there