Case studies

The proposed syllabus currently uses two case studies:

the main one (Seminar organization), that is used throughout the lectures and in some assignments 
Preliminary Requirements Specification v 3.0
Preliminary Requirements Specification v 2.3
Requirements Specification v 3.0
Requirements Specification v 2.3
Implementation in Java (Novi Sad)
Implementation in Java (Berlin), Documents, Developer version (with sources)
the additional one (XCTL control system), that is partially used during the lecture and in some assignments. XCTL is also ideal for independent seminar works or student projects.

Behavioral specification (requirements) of XCTL-Control program. Function: Manual Adjustment of Sample and Collimator

Besides these two, there are also the following case studies that may be used in assignments or to replace above-mentioned main and/or additional case studies.

Encounter role-playing game, taken from the book by E. Braude, “Software Engineering - An Object Oriented Perspective”, John Wiley and sons, 2001, and adapted by Živana Komlenov  (Novi Sad). All documents are written according to IEEE standards and recommendations. Slight deviations from these standards are enumerated in documents.
Software requirements specification
Software design document for role-playing game framework
Software design document for Encounter (role-playing game)
Implementation in Java (unpack keeping folder names intact, and then execute "runit.bat'. Java-runtime is needed for execution).  
  Software for multi-level sales, produced as a result of an undergraduate "Requrements engineering" course. In Serbian.
Requirements specification (in Serbian)
A possible use of this specification in Topic 5 of JCSE (Results of the "Analysis and definiton" phase)

The document 'How to contribute to the joint course by case studies' (pdf, 5.20 Mb) lists the activities that should be done in order to completely exchange the main case study with the alternative one.

[December 6, 2013]