Professional Documents
Culture Documents
Software Quality Assurance (SS17) - Exam Protocol
Software Quality Assurance (SS17) - Exam Protocol
Software Quality Assurance (SS17) - Exam Protocol
Preparation
approx. 1 week (summarizing all slides, going through the excercises (with solutions))
Literature:
Lecture Slides
Atmosphere: relaxed
Observer-Pattern
Q: Assume the Observable's API changes frequently so pulling changes would require constant modi-
cations in all Observers. Solution?
A: push variant.
Q: How would this look like for push?
A: The change would be passed to the update() method so the Observer does not need to know the
Observables API.
This could be lots of Data. Not good if connection is e.g. via a network.
Statechart inheritance
Q: If I now add this edge (see g. 2), how does the situation change?
A:
Still invocable
Not observable. After deleting unknown commands there could be multiple turn ons after
another. This would be impossible with TV.
Q: If I now take a modenTV in state standby and use it as a TV. Would this work?
A: No. You can use a modernTV as a TV, but then you are restricted to TV's methods.
Consider the trim() method of java.lang.String. (Returns a copy of the string, with leading and trailing
whitespace omitted.) Its signature is: String trim()
You don't need to write lots of if (a==null) code and can just use the objects which leads to
cleaner code.
Q: But you could just wrap all code in one big try-catch block.
A: Thats very bad practice since you should catch errors close to where they happen.
We the following model: Like in Java-programming we have packages that contain classes. Each package
corresponds to a folder, each class corresponds to a le.
Q: Is it possible to create two classes that link to the same le or the other way round?
A: No. Each created class creates a new le and a new le leads to a new class.
Q: Can you add rules so that those cases become possible?
A: see gs. 4 and 5