1. MAS 2007 Rafał Hryniów rhryniow@pjwstk.edu.pl

2. Main Topics  Rules  Presentations  Project  Tests

3. Rules  No final exam  Every student has to prepare a project and a mini-project  Student can be absent up to 3 times

4. Rules  Final mark will be based on: Tests resultsTests results Mini-project resultsMini-project results Final project quality (docs and implementation)Final project quality (docs and implementation) ParticipationParticipation

5. Project  Deadline – class 14  Continuation of PRI project  Final delivery should include: Old docs (PRI)Old docs (PRI) New docsNew docs ImplementationImplementation

6. Project  New docs: Use case diagram, with DETAILED specification of ONE NON-TRIVIAL use case. Specification should include both natural language description and activity diagrams.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.User interface design based on that use case.

7. Project  New docs: Dynamic analysis of that use case using interaction and statechart diagrams.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.Class diagram, including results of dynamic analysis such as new attributes, associations, methods etc. Detailed description of dynamic analysis results.Detailed description of dynamic analysis results.

8. Project  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.Final (implementation) class diagram along with detailed description of design decisions (chosen mappings etc). Reasons for and consequences of those decisions should be described.

9. Project  Implementation: Class structureClass structure Methods required to implement specified use caseMethods required to implement specified use case User interface required for use case presentationUser interface required for use case presentation JavaDocs.JavaDocs. Persistent data (files, databases)Persistent data (files, databases)  Additional features (extra credit) Regression tests (using JUnit of similar software)Regression tests (using JUnit of similar software) Interactive test scenario for specified use caseInteractive test scenario for specified use case

10. Test & Mini-project  Test (class 4): Class diagram in „basic” version and dynamic analysis.Class diagram in „basic” version and dynamic analysis.  Mini-project (deadline class 11) Implementation of all elements that can be found in class diagram. Should be a base for a main project. No GUI, access to databases etc.Implementation of all elements that can be found in class diagram. Should be a base for a main project. No GUI, access to databases etc.

12. Thank you for your attention Questions?