This is a preliminary schedule of the Course on Software Engineering 2 (02162) in
autumn 2020 including a list of all deliverables (submissions and releases). Unless
stated otherwise for a deliverable, the deadline is Friday, 1200 (noon).
The plan also indicates, at which times there will be lectures, tutorials,
group meetings, work sessions, and presentation sessions. Normally, the
material for the lectures and tutorials will be made available shortly before
or after the resp. lecture or tutorial. Some of the topics of the lectures
and tutorials will be announced later ("TBA").
Please note that this is still a preliminary schedule and the exact time slots for
lectures and tutorials and their contents are subject to change. Please check regularly
for changes and updates on this page, and the added material. To make it easier for you
to track the changes, there is a page on which
the changes are logged (after Sept. 4 on).
The group meetings on Friday from 15-17, however, are fixed for the complete
lecturing time. The group meetings will held in building
210 in the following rooms:
Some important work and discussions on the project will also be
discussed in the Tuesday (10-12) or Friday (13-15) plenum sessions with
all students (such as the status reports from the
groups on Friday).
| Wk |
Tue 8-10 |
Tue 10-12 |
Fri 13-15 |
Fri 15-17 |
Deliverables (releases) |
| |
303A/45 |
303A/45 |
303A/45 |
group rooms |
|
| 1 (36) |
L: Introduction
(SE2-L01.pdf, ,
blackboard notes) |
P:
P: Forming of groups
|
P/T: Project details, technology overview & organisation
(SE2-Project2020.pdf and SE2-Project2020-Source-code-overview.pdf)
|
Group meeting
(see SE2-GroupMeeting.pdf and
slides 22-25 of SE2-Project2020.pdf) |
|
| 2 (37) |
L: Agile development
(SE2-L02.pdf,
blackboard notes)
|
P: Project discussion (SE2-Project2020-2.pdf and
SE2-Project2020-Source code overview-Docker-Installation.pdf)
P: Work on project
|
T: Technology discussion
(SE2-T01.pdf)
P: Project discussion
|
Group meeting |
|
| 3 (38) |
L: Giving talks (SE2-L03.pdf)
|
P: Project discussion (SE2-Project2020-3.pdf),
P: Installation of software on VM
P: Work on project
|
P: Status reports (SRs) (software running on groups server)
P: Project vision (SE2-Project2020-4-ProjectVision.pdf)
|
Group meeting
|
|
| 4 (39) |
L: Working together, version management
(SE2-L04.pdf)
|
P: Project discussion
P: Work on project
|
P: Group Presentation 1: Project vision, demo of release 0 and ideas for user stories for release 1
|
Group meeting including planning game (PG release 1)
|
Submission of project vision and user stories for first release.
Demo of working Release 0 (during presentation). Here are some examples of
earlier project definitions (for two different non-agile projects): Example 1, Example 2.
The submission is via Campus Net.
|
| 5 (40) |
L: Modelling (1) (SE2-L05.pdf)
|
P: Models in the project (discussion)
P: Work on project
|
L: Modelling (2)
|
Group meeting |
|
| 6 (41) |
L: Specifying systems and writing documents (SE2-L06.pdf,
Example)
|
P: Work on project
|
P: Status reports (SRs) (including a demo of running software)
|
Group meeting |
|
| (42) |
Autumn holidays |
| 7 (43) |
L: Specifying systems and writing documents (cntd. SE2-L06.pdf)
|
P: Work on project
|
Group presentation 2:
Oral presentation of system specification (incl. requirements) and demo of release 1.
User Story X for release 2 (SE2-Project2020-5.pdf)
|
Group meeting including PG for release 2 |
Release 1: Features agreed under planning game for release 1.
The submission is via Campus Net.
|
| 8 (44) |
L: Quality Management (SE2-L07.pdf)
|
P: Systems Specification (discussion, SE2-L06b.pdf)
P: Work on project
|
P: Walk-through the code of release 1 individually with groups (also in group meetings).
|
Group meeting |
|
| 9 (45) |
L: Management (SE2-L08.pdf)
|
P: Info on the final presentation (see here)
and the final submission (see here).
P: Work on project
|
L: Writing Handbook (SE2-L09.pdf)
|
Group meeting |
Systems Specification (of planned final version including requirements). You will
find an example
here (see also lecture notes).
The submission is via Campus Net.
|
| 10 (46) |
P: Work on project
|
P: Status reports (Release 2)
P: Discussion of systems specifications
|
Group meeting (including PG for release 3) |
Release 2: Features agreed under planning game for release 2.
|
| 11 (47) |
P: Discussion of Systems Specifications and Release 2 individually with groups
(schedule will be announced via Campus Net)!
P: Work on project
|
L: Agile development (2) (SE2-L10.pdf)
|
Group meeting |
|
| 12 (48) |
L: Guest lecture by netcompany (slides via CampusNet/Inside)
|
P: Work on project
|
L: Outlook, Summary and Conclusion (SE2-L11.pdf)
|
Group meeting
|
|
| 13 (49) |
P: Work on project
|
Final presentations (optional/early): Presentation of final product with slides (technical and sales talk)
including a demo of release 3 (see
here for schedule and more information)
|
Group meeting (including planning game for final release) |
Release 3: Features agreed under planning game and
Handbook
|
| Examination period |
| (50-51) |
In this period, the groups can finalize their projects.
Groups can chose to do their final presentation early on Friday, Dec. 4 (see above) or to do
their final presentation on Monday, Dec. 14. A detailed schedule will be announced later, once
the groups have made their decisions.
You will find more information on the schedule and what is expected from the
final presentation here.
|
Final submission: Tuesday, December 22., 23:59
Final software, test documents, running installation, updated systems specification.
Note that the submission will consist of two parts: the group submissions and a brief
individual submission from each student.
More information on the final submission and a checklist
can be found here.
|
