|The appeals of the final grade will be allowed until 31/7.|
If you feel that your work has been evaluated differently than what it deserves, you may hand in a PRINTED appeal with the following *mandatory* items:
1. Your name, ID, and hand signature at the bottom.
2. The details of your work PER WEEK of semester, with relevant issues numbers to support it.
3. The grade you received, and the grade you believe you deserve.
Be advised, after your appeal, your work will be reviewed very carefully as it appears in GitHub. Your grade may be raised, lowered, or unchanged.
The printed appeal should be placed in Tom Palny's mailbox number 208 on the 5th floor.
Please also send the appeal as a PDF to Tom's email tpalny@cs
(Appeals that are not printed will not be accepted)
Final grades published
The final grades have been published. The protocol for appeals will follow soon.
Delay in grades publishing
Due to reserve duty of one of the supervisors we cannot publish yet the final grades. Please be patient.
Room for final presentation on Sunday & Monday is 235
|Room 235 will be used for the meetings.|
Reminder, *all* members of the team are expected to be present.
End of Semester Presentation
|It has come to the staff's attention that some students have exams starting earlier than July 4th, and therefore it will be unfair to request work to be done on the projects during that time. |
Therefore, the final presentations will be done as following:
On Sunday and Monday, 24-25/6, between 14:30-16:30
1. The three project supervisors will hold a *private* meeting with each group (all the group members are requested to be present), each project's meeting will take 30 minutes.
2. In those meetings the supervisors will use the WIKI installation instructions as well as the WIKI for the "user manual" to understand the project and test all the different features.
3. We do not need a PowerPoint slideshow for this meeting.
4. Code Freeze will be slightly before each project's meeting with the staff. There will be no development allowed after that.
The grade for this will be 20 points.
The sign-up sheet for the private meetings' time slots: https://docs.google.com/document/d/1vGHsCaNFIEuuGCs-OziEit44b3WfPEyafQmZqO_H-F4/edit?usp=sharing
EVENT CHANGED, SEE NEWER MESSAGE (End of semester "Client Challenge")
The end of semester is nigh, and with it the end of semester's presentation.
This semester, the final presentation will be replaced by a different type of event, which will be called from now on "The Client Challenge".
In this challenge, during the 4 hours total of the regular course hours, 2 hours on Sunday the 24th, and 2 hours on Monday the 25th, from 14:30 to 16:30 you will all be checking, as a user (aka "Client") a project OTHER than your own.
The exact project which you will check and the room to be seated in will be known to you on Sunday the 24th.
This means that the WIKI with the installation instructions for the user and the WIKI with the User manual explaining what are the different features of your project and how to use them, should be perfectly written and ready by that date.
In this challenge you will be required to:
1. Check the most important aspects of a program, i.e. smooth installation, usability and user input error handling and communicating, graceful recovery from errors, and of course, find any bugs, unexpected behavior and crashes.
2. Open an issue for each problem you encounter in the GitHub repository of the project you are checking describing IN DETAIL exactly what problem you found (also regarding the installation process, in case it is not successful). Include screenshots in the issue to help make the problem clear to the developers. Label those issues with "Client Test Day".
3. Write a separate issue in that project's repository with the title "Client Test Log", detailing what was the procedure of your testing, what features you tested, and the bugs and problems you found. In (the very unlikely) case you didn't find any problems, this log will be your "proof of work" during those 4 hours.
4. Deal with and try as best as you can to resolve in the frame of those 4 hours the newly opened issues others found in your own project.
The "code freeze" date is July 4th, which means you have slightly more than a week after the "Client Challenge" to resolve all the issues that were found during those 4 hours.
This challenge will be a total of 30 points from your final grade, from which you will receive 10 points individually for the testing you did during those 4 hours (as documented by the "Client Test Log" and the issues you opened, if any), and 20 points as a group, for successfully resolving the issues that were opened for you by the testers.
(Issues that will be opened without justification will cause points to be reduced from the grade of the student who opened them)
Guest Lecture 11.6, Monday, Taub 5, 14:30
Next week, on Monday, 11.6, at Taub 5 starting at 14:30 we will have our final (mandatory) guest lecture.
The lecture will be given by Eyal Bar Lev, head of the software dev. group in Advanced Airborne Graphics in Elbit.
He will be talking about Soft. Eng. in Agile dev. environments.
This should not be missed by any Software Engineering student, let alone the current ones in the Yearly Project.
See you there
Project Fair on 26.6
At the end of the semester, on Tuesday, 26.6, between 16:30-18:30 a "Project Fair" will take place in Taub lobby and 1st floor. All projects will be presenting their work.
The fair is open to students from other departments, Dean and faculty of CS, and Public Relations of The Technion.
Those of you who have classes at that time will be excused for the duration of the fair, but at least 3 representatives from each group are expected to be there.
You will find a poster template under the course material section for you to download and edit with information regarding your project.
Please prepare and export to PDF the file, and send it to Tom not after 5.6.
POC Presentation requirements
The POC Presentation is in a little less than two weeks.
In the presentation we want you to go over the following things:
1. A ONE MINUTE reminder of the project you are working on.
2. Talk about the progress (aka, diff) from the end of previous semester. What progress you have made, new features you have implemented, changes to design, and technologies you are using.
Go in DETAIL regarding the design of your project: we need to see, much like an investor, that you know what you are doing, why you are using the tools and technologies you are using and how they solve the problem you are trying to solve.
3. Azure cloud usage: how you are/will be using it, how it gives any added value to the project, difficulties along the way
4. Planned features: what are the remaining features you are working on which will be *included and tested* in the final product.
5. Live demo: here you are required to show a live demo of WORKING FEATURES ONLY. Optional: Azure usage, Logger in the project. If for some *very good reason* you cannot show a live demo, a video will be accepted as substitute.
In the live demo part, we are aware that some features might be buggy. We will allow ONE crash/error in the demo. Any more will result in reduced grade.
Following the demo, will be a short QA session from the supervisors.
POC Sign-up form
|Below please find the link to the time slot sign-up form for the POC presentation on 27-28.5.18|
Detailed instructions regarding the presentation will follow soon.
Guest Lecture next week moved to 11.6 (original date)
|Please note, next week the guest lecture planned on Monday will NOT take place.|
Instead, it will be on Monday, 11.6. (exact time TBD).
Guest Lecture Changed Date: Next Week 30.4
|Our guest lecture from 11.6 has changed the date to NEXT WEEK, Monday, 30.4, from 14:30 to 15:30, at Taub 5. |
Anyone who has a problem attending, please contact Tom by email or Telegram with reason why.
The lecture will be talking about OpenSource and how it is implemented and used inside Elbit and the change it is causing the industry.
Reminder: Tomorrow Mandatory Guest Lecture
|The MANDATORY lecture will be tomorrow, Tuesday, in room Taub 3 at 12:30 about Azure.|
(Student names in attendance will be checked)
Course Time Conflicts V2.1
|Students taking course 214909: same attendance requirements as 236698, with the exception that **you need to bring a signed note from the TA that you attended the tutorial**.|
You ARE excused from the guest lectures on 21.05 and 11.06. It is your responsibility to prove you attended the other course lecture/tutorial on these dates.
You are NOT excused from attending mid & end semester project presentations and thus you'll have to miss 2 tutorials of the other course.
You must attend the guest lecture on 10.04. If you have a problem with that date, please talk to you supervisor.
Course Time Conflicts V2.0
|We would like to clarify the course rules regarding mandatory attendance and the issue of the course hours conflicting with other courses.|
The mandatory attendance dates this semester are:
Three guest lectures from which you can choose to attend just two: 10.04, 21.05, 11.06
Mid and end semester projects presentations: 27-28.05, 24-25.06
For students taking one of the MANDATORY ATTENDANCE courses which collide with our course hours: 236698 - Software Quality Assurance
You ARE excused from the guest lectures on 21.05 and 11.06. It is your responsibility to prove you attended the 236698 lecture on these dates, by signing with Tanya at the lecture.
You are NOT excused from attending mid & end semester project presentations and thus you'll have to miss 2 lectures of 236698.
You must attend the guest lecture on 10.04. If you have a problem with that date, resolve it with your supervisor.
For students taking colliding courses that DO NOT require mandatory attendance:
בעיות במדעי המחשב 2 - 214909
פרוטוקולי רשת עמידים בתקלות -
You are NOT excused from any of the mandatory attendance dates.
Course Time Conflicts
|If you have a time conflict between our course and another course THAT HAS MANDATORY ATTENDANCE POLICY, so that you are prevented from attending 2 out of 3 guest lectures or the mid-semester or end-of-semester presentations, follow the link below and write your information.|
Those taking "Software Quality Assurance" course number 236698 are required to sign attendance with Tanya at the course lecture.
Next week is our first official week of the course.
Our first meeting will be a lecture, *** Attendance is Mandatory ***, Sunday, 25/3, from 14:30-16:30 in Taub 3.
We wish you all a great semester, and may all your projects be robust, intricate, and well implemented!