MAS Tomasz Pieciukiewicz Rafa Hryniw Main Topics Rules

MAS Tomasz Pieciukiewicz Rafał Hryniów

Main Topics Rules u Presentations u Project u Tests u

Rules No final exam u Every student has to prepare and deliver a presentation u Every student has to prepare a project u Student can be absent up to 3 times u

Rules u Final mark will be based on: • Tests results • Final project quality (docs and implementation) • Presentation results • Participation

Presentations u Presentation 1 : • Mapping the following inheritance variations from UML to Java: Disjoint u Overlapping u Complete u Incomplete u Multi-Inheritance u Multi-Aspect u Dynamic u

Presentations u Presentation 2: • Implementation of class extension using: Static array (class attribute and array with size determined during compilation) u Collections+ u • Implementation of class extension using a separate class (Employee -> Employees)

Presentations u Presentation 3: • Mapping associations with and without attributes using: References (reference collections) u Association arrays u u Presentation 4: • Mapping aggregations and composite objects (remember about operation propagation) • Mapping qualified associations (association arrays) • Mapping N-ary associations • Mapping constraints

Presentations u Presentation 5: • Statechart diagrams u Presentation 6: • Activity diagrams u Presentation 7: • Interaction diagrams u Additionally: • One of those presentations may include collaboration diagrams for extra bonus.

Presentations u u First four presentations should include code examples (WORKING) All presentations should include examples, tasks for students etc. Students that do not prepare enough tasks and examples won’t receive FINAL mark higher than 3. Students should deliver their presentation in a proper manner (standing, with visual aids, speaking NOT reading etc. )

Project Continuation of PRI project u Final delivery should include: u • Old docs (PRI) • New docs • Implementation

Project u New docs: • Use case diagram, with DETAILED specification of ONE NON-TRIVIAL use case. Specification should include both natural language description and activity diagrams. • User interface design based on that use case.

Project u New docs: • Dynamic analysis of that use case using interaction and statechart diagrams. • Class diagram, including results of dynamic analysis such as new attributes, associations, methods etc. • Detailed description of dynamic analysis results.

Project u New docs: • Final (implementation) class diagram along with detailed description of design decisions (chosen mappings etc). Reasons for and consequences of those decisions should be described. u I need final version of docs ONE MONTH (class 12) before the end of semester.

Project u Implementation: • Class structure • Methods required to implement specified use case • User interface required for use case presentation • Java. Docs. u Additional features (extra credit) • Regression tests (using JUnit of similar software) • Interactive test scenario for specified use case

Tests u Test one (class 6): • Presentations 1 -4. Simple requirements (four – six classes). Class diagram in „basic” and implementation version, Java implementation. u Test two (class 13): • Presentations 5 -7. Simple requirements (four – six classes). Class diagram in „basic” version and dynamic analysis.

Thank you for your attention Questions?