Welcome to Informatik III!
I look forward to getting to know you!
My schedules are usually tentative anyway, but this is going to be another crazy semester. We are supposed to be in presence, but I understand that many of you may have issues that prevent you from attending. One will be if you are not vaccinated. I have grandchildren I do not want to infect. If you are not vaccinated, I kindly request that you attend only at a distance. I will be offering the course in a hybrid manner. This means that the sessions will be held at the HTW but also broadcast via Zoom. It will be difficult to keep the students from a distance involved in the discussions, but I will try my best. I also have many of the lectures from the first Corona semester on the Mediathek of the HTW. I'll link to them in the Moodle room. I have a number of new topics this semester, and of course I always link all sorts of current events (= software failures) into the topics we will be covering, so attending in person is probably more fun :)
My goal is to introduce you to the field of modern software engineering, which has a lot in common with the production of complex media. When we produce media we sometimes speak of Media Engineering. Engineers plan something, make sure it gets done, and measure that they actually implemented what they were trying to afterwards. We will be looking at various methods of planning, doing, and measuring and learn how many things go into creating a software product that is above and beyond simple coding.
You can get an idea about what we will be doing by watching this short (7 min) video by the author of our textbook, Ian Sommerville, with 10 Questions on Software Engineering.
This handout describes some of the general information that you will need to know about the course. It also includes course policies that I will expect you to abide by during this term. You should read through this handout and make sure that you understand its contents. You will probably also want to save the link for future reference. This handout—as well as other course information—is available on the web via the course web page, http://people.f4.htw-berlin.de/~weberwu/info3/site.
Learning Objectives
In this course you will learn
Course Contents
We will be discussing the following topics, among others:
Course Basics
|
Teacher
|
|
Contacting Prof. Weber-Wulff I am best reached by email. Make sure you use a good subject line, a professional email address, sign your full name, and give me a bit of context. I get hundreds of emails a day. If you are contacting me by Zoom or Skype, let me know who exactly you are, don't use the default text. I block bizarre incoming names. |
|
Venues We will be using a Moodle
collaboration room for the course. It is planned for us to meet
for lectures
The labs are also on Mondays
There are Zoom-Rooms for those who are unable to attend the lectures: Monday - Thursday |
Course Materials
There are a number of books that can be useful for this course. The first one is the book I will be using as a basis for much of the course material.
[10th edition]. Prentice Hall. Ian has now made a
number of videos on various topics from the book or on supplementary
topics. They will be very useful for you, so have a look around at http://iansommerville.com/software-engineering-book/videos/software-engineering/During the term, there will be 9 exercises which will be posted on the web page. Lab reports are due the evening before the next lab by 23:59, but may of course be handed in early.
There will be a 2-hour examination on or about July 28, 2022. The examination will cover conceptual understanding in ways that may be difficult to assess during the laboratory sessions. The examination will probably not be online, as you will have to be drawing pictures. No "cheat sheets" will be permitted!
There are 9 exercises worth a total of 70 lab points. You must submit at least 7 exercises on time in order to be admitted to the exam. The following number of points are possible for each lab session:
Missing a lab report will automatically result in 0 points for the lab.
Your grade in Info 3 will be a weighted mixture of the following elements of the course:
Yes, I know that this makes 105 %. I don't like to discuss points I take off, so I always have a bit more :)
Laboratory sessions are an essential part of the course. The laboratory assignments will be posted on the home page. The first two exercises will be in randomly assigned groups so that you get to know each other (in person!) better. Then you are to form a team, a group of three or four, who will work together. You will learn to use the different kinds of UML diagrams to design an application. Then we will mess with some nasty legacy code stuff before setting up a project plan and a risk analysis for your app.
I expect you to work together and not to do every other exercise alone. All lab work must be turned in on time and be labelled with the names of the students who did the work. I shouldn't have to say this, but you MUST write in complete sentences, in English or in German. Each student submits their own copy of their report to Moodle, using the naming convention: Ex<exercise number as a digit>_<Your last names no umlauts>.pdf - and yes, I will only accept pdf. Every member of the group hands in their own copy of the same PDF.
Handing in any kind of plagiarized exercise (from the Internet, from other students) will result in an automatic failure (5,0) with a notice of cheating put on your permanent record! You are here to learn, don't cheat.
The examination will be diagnostic in nature. You are expected to do your own work here—any cheating will result in an automatic 5.0. Questions will tend to be similar to the questions in the Sommerville chapters. I will expect you to answer in complete sentences, German or English, giving your arguments for something. Don't mix languages in one answer, but you can switch between questions if you need to. I will be giving you paper if this is not going to be an online exam, you will only need a pen. You may use a dictionary, but there must not be writing in the dictionary. Please don't bring complete meals to the exam, but a bottle of water or a cup of coffee is fine.
You are responsible for all material covered in each lecture unless otherwise indicated. This material may not be covered elsewhere, so if you miss a meeting, you are responsible for getting notes from a friend or otherwise making up the material. Old versions of the lectures can be found in the Mediathek. Handouts will not be distributed on paper, but will be made available on the course web site.
I encourage attendance at the laboratory, however, this semester involves many special circumstances. It is important that you communicate with your group partners. If someone in your group is not communicating, please contact me as soon as possible. If you have special problems that arise (and the situation seems to be changing on a daily basis), please contact me as soon as possible.
This section details the general course collaboration policy. Certain assignments require different kinds of, or restrictions on, collaboration. When the collaboration policy differs from that described here, it will be specified in the laboratory assignment.
I encourage you to work together on the exercises. They are designed for working in small groups, allowing you to help each other learn and to balance your knowledge and strengths. Note that collaboration extends to discussion and problem-solving, but not to write-ups. I expect that any written work you turn in will be done by one of the authors of the exercise reports, though it may reflect group preparation.
Experimental work is a complex topic. It is often useful to discuss your models with peers or with me, and I strongly encourage this. It is particularly useful to do so as a means of debugging your models. Reading models written by others and having others critique yours are good ways to improve your modelling style. However, it is of no benefit to you or to anyone else to have someone else actually do your work. I expect that the default assumption (i.e., unless specified otherwise) is that assignments are your own work, but may reflect input from others just as an essay edited by friends might. You should be the one who wrote the models you turn in.
In each piece of work that you turn in, you must specify everyone with whom you have collaborated and each person's role in the collaboration. Failure to specify such collaboration will be interpreted as a statement that you have not collaborated with others in your work. While this is acceptable under course policy, it is probably ill-advised. (Really. I want you to work together and to learn from each other!).
Note that there are no "right" answers for this course. You will need to explain why you chose to model your solutions as you did. A convincing explanation will always serve you well.
Reports should not use any copyrighted material (pictures or other media) without the express written consent of the copyright holder or be material under a free license.
Our Moodle room has a chat attached, and there is a forum for general comments and discussion. Make use of this as you need. If you need to have any other kind of communication tool, please let me know. Moodle has a ton of extras that can be installed easily.
Examinations are diagnostic in nature and as a consequence should represent independent work.
Of course, copying of the work of others is entirely unacceptable and will result in the lab in question being marked as missed, or for especially severe cases in failure for the course.