2nd iteration presentation
|The presentation will be in front of the whole staff and all of the groups. This supersedes any previous message regarding the presentation. Each presentation will be about an hour long.|
The focus of the presentation is to show your actual running application. No slide show is required. In fact, if you choose to use a slide show (e.g. power point), please limit yourself to the minimum number of slides, and plan for no more than 5 minutes of a slide show. Get as fast as possible to running the application. You may return to the slides if needed (and if your 5 minutes aren’t up). Please prepare ahead of time and present *meaningful and realistic* scenarios (for example: load info into the database ahead of time). When presenting a scenario, make it clear what type of end user you are simulating (if you have more than one type). Prepare enough scenarios for about half an hour.
Please begin your presentation by explaining what your project is (to people that have never heard of it). It is very helpful to present the vision of the project, but please focus on what you actually developed. Make sure to make it clear what features are actually available, and what were the changes from the first iteration. Clearly explain who the end users are supposed to be, and any other information needed to understand and appreciate your work. It would be wise to use this opportunity to explicitly note any difficult implementation issues (e.g. technologies used) and smart design decisions you have made.
Be ready to also present your code/tests/test-coverage, and to answer questions regarding your design and other aspects of your project. You are encouraged to present any experiments you conducted, if any.
Regarding the submission, in addition to the updated version of everything you submitted last time (known bugs, workload balance, etc), please also make a list of 3rd party resources: tools, libraries, code from other sources, technologies, etc.
The course staff
2nd Iteration Submission
|The submission date is Tue the 29th, 12:30 (this supersedes any previous messages)|
Each group must pick one (and only one) time slot when all (or most) of the group can present your project.
Please use the following link to reserve the slot you want:
The submission and presentation will be similar to the previous iteration (the version you wish to submit in trac and in Git is now "V1.1").
The key differences are that now all the staff will check each group (room 235), and the offline check will be more thorough.
In addition, on Tue the 29th 14:30-16:30 (usual class hours), groups that are not presenting their project to the staff will present their project to the other groups.
This is so you can see what the others have been working on, and to show off your work to the others.
***EDIT: All presentations will be in front of all of the groups.
|Details regarding the final submission for this semester will be published in a few days. For now assume it will be similar to the previous iteration.|
Regarding the personal roles - please continue with the same roles. We want to see more of everything, namely:
- more unit test coverage (use EclEmma) - please make sure the coverage is meaningful
- more system/acceptance tests (define as soon as possible)
- more usability: use the heuristics or/and user evaluation to improve your UX
- give a high priority to fixing known bugs from the previous iteration (create tests where relevant)
Reminder: the version for the second iteration is "V1.1"
|Next week is the submission of this iteration. Afterwards you’ll have about one week to plan the next iteration (update the design, create “V1.1” tickets in trac).|
We will meet with each group for about 1 hour, in which you’ll start by presenting your application, with meaningful scenarios (or acceptance tests), followed by showing us your tests and code, and answering our questions (be ready to explain the choices you made).
On Sunday, we’ll meet in class for about 15 minutes, followed by the iteration exams:
~14:45 groups 2 and 5
~15:35 groups 4 and 6
On Tuesday we will meet in class, and after that we will continue the exams:
~15:30 groups 1 and 3
Please have everything you need to present your project ahead of time. You can use your machines or the lab computers for the presentation.
Remember: the submission time and date is the start of class on Sunday, for everyone. Make sure you do not change your submission after that point.
The course staff
Upcoming iteration submission
|The iteration ends Dec-30, 12:30PM (start of class).|
We will meet with each group that week, and you will present your application on your machines (have it installed ahead of time).
The submission will include:
- Tagging the code in Git with "V1.0"
- A list of known bugs
- If applicable, a list of features that were moved to the next iteration (after the iteration started)
- Workload balance: A single document with one paragraph for each member, describing the work you did.
- And of course, all relevant tickets in trac are with version "V1.0" and properly closed.
|On Tuesday, we'll have the GAE lecture. |
Following that, we'd like to check the IAVA unit and system tests.
We'll be meeting with groups in the SSDL. People that have moved groups, please make sure to rejoin with your original group for the purpose of this meeting.
15:00-15:30 Group 6
15:30-16:00 Groups 1 and 3
16:00-16:30 Groups 5 and 4
Meanwhile, Yossi will continue checking the code with you.
We will continue the checks next week for the rest of the groups.
Reminder: NO class or meeting tomorow
|There is no mandatory meeting tomorrow, however, each group must still have a meeting (online if necessary).|
|To all groups: please make sure that by Sunday 9:30 all IAVA tickets have their version set to "V0", and all of this iteration's tickets have their version set to "V1.0".|
Groups that have not finished designing and distributing the workload (via trac) for this iteration, please do so ASAP and begin development.
Each and every student is responsible for accepting meaningful non-trivial development tasks.
Please make sure with the supervisor of your group that you have shared the workload properly, and that you have taken on enough tasks.
Remember, since you didn't have much time for gathering requirements, research, or design, it is expected that your tasks will be updated throughout the iteration. Try and make sure that at least for the first two weeks of the development, everybody has enough work.
Please make use of your personal roles to make your project a success and to train your managing skills.
The iteration ends Dec-30, 12:30PM (start of class).
Next lectures and submissions
|Sun 2-Dec: We will present the personal roles (each one of you will get a role within your group)|
Tue 4-Dec: Tickets in trac are due
Finish your high-level design as soon as possible.
Pay attention to the major parts of your system, and especially to the interfaces between them.
GUI sketches are very useful.
Do the minimum amount of work needed to divide the system between you.
Each of you will then further design the part assigned to you.
Come back together and draw tasks from the design and enter them into trac.
- Read the trac presentation again to make sure you use it correctly.
- Each task includes learning and unit testing.
- When you accept a task, you are responsible for the estimated time.
- Each developer should do around 8 hours of work a week (no more than 10, or 15 in the week before the submission)
Make sure that after you finish the planning stage (i.e. accepting the tickets in trac),
that each of you knows what they should code for the entire iteration, but especially for the first two weeks.
Note: For people who have moved to a new group, please ask someone in your new group to give you access to the group trac via the admin tab.
Lecture on 27-Nov (Tomorrow)
|Tomorrow we'll have a very interesting and relevant guest lecture:|
Title: Application Life-cycle Management.
Learn how to be in control of your development process.
Speaker: Ariel Kogan.
As always attendance in mandatory.
Dates and submissions
|Tue 20-Nov: Python workshop|
Sun 25-Nov: present your project idea*
Sun 30-Dec: first iteration submission deadline
Mon 30-Jan: second iteration submission deadline
Tue 31-Jan: project presentation
* Note: For groups without an idea, or if your idea is not accepted, the default project is IAVA.
For groups choosing to do the Android App for cancer patients:
1. The pdf presented in class can be found under the course material, in the lectures and tutorials section ("ProjectA").
2. This will be first-come-first-serve, so please email ASAP if you wish to do this project
After your group is assigned a project, we will likely also assign one supervisor (TA or Yossi) to your group.
To present a project idea (if you wish to), you need to have done enough work as to know what similar applications already exist, and just enough written material so that you can immediately begin designing your system. Also, try and (roughly) prioritize the features you suggest.
Details about the iterations/submissions will be given soon.
|For the IAVA project, you need: Java 7, eclipse 4.2, and the OS needs to be 64 bit.|
For code coverage, please use EclEmma.
Please remember that:
- Deadlines are not moved, so you submit what you have when the time comes.
- Problems are taken into consideration, so let us know if there are things that you won't be able to finish on time (e.g. the extensions). Please specify the problems (technical problems, reserve duty, etc).
- As a rule, prefer quality over quantity. Try not to submit half done tasks.
Please do not lose sleep over this 0th-iteration, one of the main goals is to get started and to weed out technical problems.
For groups that have finished all of the requirements: there's no need to do more than required, even if you wish to continue with the IAVA project.
Please use the general-forum ( ) to ask questions, but also to answer questions of other students. We won't always give you the solutions you want, but it is vitaly important that any complaints/suggestions are done in writing, via the forum (or mail, if it's personal).
Soon you will be asked if you wish to continue with the IAVA project or take on a new one. It would be wise to discuss this within your group, especially if you wish to suggest an idea (we will provide new ideas of our own). The course staff will eventually decide which group does what, but we wish to hear your ideas and accommodate your preferences as much as possible.
IAVA First Task
|Details of the IAVA first task are available in the general group.|
Git and trac
|To access trac, follow the link: https://ssdl-svn.cs.technion.ac.il/cs234311-trac/yp2012-gX|
Where X is your group number.
The Git server is on the same lab server (ssdl-svn.cs.technion.ac.il)
You can check your quota here: http://ssdl-svn.cs.technion.ac.il/quota.htm
For technical help, please mail Shahar at
המלצה על קורס
|לכל הסטודנטים בפרוייקט השנתי. בסמסטר זה ניתן פרוייקט בתכנות אג'ילי על ידי מומחים מהתעשיה. |
ד"ר רונן בר נהור, וגב' רוני תמרי.
נושאים מתקדמים 5: 236605
השעה אולי מעט לא נוחה, יום א' בין 930 ל 1230 אבל הקורס מומלץ מאוד,
שכן אנו נעבוד בשיטה הזו בפרוייקט
הקורס זכה להמלצות חמות מסטודנטים שהשתתפו בו בשנה שעברה
Please search under "Course Material" & More
|A. Please search under "Course Material". You will find there a copy of the project you should start from.|
B. The GIT and TRAC accounts should be opened today; you will receive a separate notification.
C. On Tuesday, the first hour would be a lecture on the trac. On the second hour, you will conduct a group meeting. (Attendance is not optional in each of these)
D. A Google group for general course discussion is opened under https://groups.google.com/forum/#%21forum/yp-general-forum
please post discussions regarding: assignments, material, schedule, etc.
E. Irena went on maternal leave. Please do not send email to her. All course related questions are to be directed to " " rather than any staff member.
Upcoming lectures + staff email
|Sunday 28-Oct: ** class is canceled **|
Tuesday 30-Oct: Trac
Sunday 4-Nov: Meeting
Tuesday 6-Nov: Python
Sunday 11-Nov: Meeting
Tuesday 13-Nov: Python
Please send all mails to
and not to specific TAs
|החלוקה האחרונה לקבוצות נמצאת כאן:|
אם כתובת הדואר שמופיעה שם היא הכתובת הטכניונית שלך, מצויין.
אם לא, המידע שמופיע אצלנו אינו מספיק כדי לפתוח חשבונות
כדי שהחשבון שלך על ה
שבפקולטה יפתח, עלכך לשלוח דואר ל
ולציין בו גם את הדואר שמופיע שם, וגם כתובת הדואר הטכניונית
ולציין שם את כתובת הדואר האלקטרוני שלכם
Reminder: First meeting is today at 14:30!
|The first meeting is today 14:30-16:30, the attendance in the meeting is mandatory!|
Reminder: Establishing Teams
|The deadline is 23/10/12 12:00 noon.|
requests of the size 4,5 are not accepted.
( See previous announcement )
Our goal is to group you in teams of 6. To this end, follow these instructions:
Students who can form a team of exactly 6 members, should send email (one per the whole team) containing id's and mails of the team members.
Otherwise, you can send us groups of size 3 or 2, (again, one mail per group) we'll try to treat these small groups as building blocks for the complete teams.
All other students, should not send mail, and will be distributed among emerging teams by the course staff.
Please send emails to: