Assessment:

• Regular attendance:
  • Attendance will be monitored since the third week.
  • 1 non-excused absences during the semester (since the third week).
• Set of appointed UML models:
  • In general, models will focus on the application of software patterns in software life cycle as well as component-based system development.
  • Concrete models required for successful assessment will be specified during the semester

Project:

Masaryk University has developed a great information system referred to as IS MU. This system consists of many modules covering wide range of university activities, from complete study agenda through classroom management to e-shop etc. In our project, we will suppose that the development of IS MU reached maintenance limits. Every change in the code produces may errors in unrelated parts of the system which makes the system maintenance very complicated. This is obvious situation after continuous long time adaptation of the system to changing user requirements. Our goal is therefore to refactor the system in the way that the new architecture will strictly adopt component-based design preserving current functionality.

Refactoring will comprise several phases. During the first phase, that has been already done, initial use case model has been outlined. This model comes from current IS MU services and  represents the top-level overview to the most important modules. Another phases, e.g. analysis, design of selected components, components assembly, etc., will follow.

This lecture tasks:

• Appoint couples.
• Go through the use case model in order to understand the problem domain. Find possible inconsistencies with the behavior of the real IS MU.  Discuss uncertain aspects of the system.
• Write short documentation for every use case in the model (can be in Czech):
  • Right-click on the use case then open "Specification -> General Tab".
  • 1-3 sentences describing crucial aspects of the use case (e.g. key services).
• Homework:
  • Read the specification of the Ollie's Order Centre (see link bellow), pages 31-33. This demo system will be used in next lessons to demonstrate the application of analysis and design patterns.

Feedback to the initial use case model (remarks, questions and accepted changes):

• Q/R: Active MU members can also apply for new study. Shouldn't the Active MU member associate the Electronic Application use case?
  • A: When active MU member is applying for a new study then he/she is in the role Guest User at this moment. Therefore no changes to use case diagram are needed.
• Q/R: Alumni and employees of the Office of Studies have also embedded e-mail client as well as external services available.
  • A: Correct, accepted.
• Q/R: Students can also manage their publications.
  • A: Correct, accepted.
• Q/R: Why Discussion Group inherits from Noticeboard?
  • A: These functionalities look very similar. Discussion group can be seen as a noticeboard with extended functions, at least at this stage of analysis.
• Q/R: Noticeboard should be available to Guest Users as well as to employees of the Office of Studies.
  • A: Correct, accepted.
• Q/R: Why is the Supervisor agenda available to students?
  • A: At least PhD students can supervise thesis.
• Q/R: Why is the Schoolmates agenda available for teachers which are not alumni of MU?
  • A: In fact, "schoolmates" is not the best name for this use case because this agenda is more general, including services to "meet people", etc.
• Note: A new MU member actor in the second version of the project (see links bellow) has been added to simplify communication relationships.

Tasks:

• Discuss changes in refined use case model.
• Teacher will explain basic Fowler's analysis patterns and demonstrate their application on a case study. Patterns that seems to be valuable for IS MU project:
  • Party + Accountability
  • Quantity + Conversion Ratio + Individual Instance Method (?)
  • Identification scheme
  • Proposed and Implemented Action + Completed and Abandoned Actions + [Suspension + Plan]
• Students will deeply study selected patterns. In the next lesson they will apply them to the problem domain model of the IS MU project.

Tasks:

• Teacher will explain problem domain model (initial class diagram) of the project. He/she will describe relationship with use case model.
• Students will apply selected analysis patterns.

Features of IS MU to be taken into consideration for analysis model:

• Organizational structure of MU and faculties is very complex:
  • Basic organizational hierarchy: university, faculties/institutions, departments.
  • Management of MU and faculties/institutions: senior management, dean's council.
  • Academic boards: academic senate, scientific board, ...
  • ...
• Three classification schemes (or units if you like):
  • A = 1 = excellent
  • B = 1.5 = very good
  • C = 2 = good
  • D = 2.5 = acceptable
  • E = 3 = satisfactory
  • F = 4 = unsatisfactory
  • Z = accepted
  • N = rejected
• It would be useful to monitor changes in number of students enrolled in study fields/programs.
• It would be even more useful to monitor transfers of student between study fields.
• Each lecture is planned and realized for every single semester (registration, enrollment, cancellation, teaching, closure, ...)

Tasks:

• Students will continue with the application of selected analysis patterns.
• Feedback from teacher. Students must adapt their models according to teacher's recommendations.
• Presentation of good, bad or interesting models. Discussion.

Tasks:

• Introduction to design patterns.
• Teacher will demonstrate application of design patterns on case study.
• Students will deeply study selected design patterns. In the next two lessons they will apply them to selected part of the project.

Tasks:

• Students will apply design patterns to selected parts of the project.

Note: Monday is a free day

Tasks:

• Students will continue with the application of design patterns.
• Feedback from teacher. Students must adapt their models according to teacher's recommendations.
• Preparation for Milestone (project defense):
  • Every group (couple) will present and explain their models next week (10 min presentation + 10 min discussion)

Milestone instructions for groups 01 and 02 (supervisor R. Ošlejšek):

• Project has to contain at least one analysis pattern in addition to 4 already proofred patterns. Presentation will focus on the explanation of the pattern properties and its application in problem domain model. 4 proofred patterns will be omitted.
• Project has to contain at least 4 GoF patterns. Presentation will focus on the general explanation of their properties and the explanation of their usage.
• Visual Paradigm PDF report (with use case diagram, analytic model and design model) and PDF presentation will be stored in IS MU -> Homework Vaults -> 8th week. Every group will create its own subdirectory (its name doesn't matter) where both the PDF files will be stored.

Tasks:

• Every group (couple) will present and explain their models.
• 10 min presentation + 10 min discussion

Wednesday is a free day.

Notes:

• To run PCM in B116 select "Eclipse Palladio (incl. path to java)"
• To open the MediaStore Example:
  • Download and unpack the .zip file (link bellow)
  • In PCM select "File->Import->General->Existing Projects into Workspace"
  • Open the unpaked directory

Wednesday is a free day.