Objektorienteret Netværkskommunikation (ONK1)

 TilbageATB Intranet IHA

Opgaver

 

 

Background:

You need practice in order to learn anything. In ONK1 we have two kinds of practical assignemnts: the short, non-required assignment (often only an advanced HelloWorld), and the two required written reports.

The non-required assignments will primarely take place in the EIT labs or, if you are so lucky as to have one, in your group room. You may choose not to solve the non-required assignments, as these are not essential for passing the exam. The assignments will, hower, help you in completing the two required  written reports, as well as gain a better and broader understanding of the subject. One more detail worth noting is, that I will only reluctantly provide help for the reports, if you have not solved the non-required assignments.

Division into groups:

You are required to form groups of 5-6. You will do this by creating a Campusnet group, and inviting me as a guest member. Those who can not themselves find a group may use the ONK1 Campusnet discussion forum for finding a group. All posted here who can not find a group to join, may either be formed into a new group, or placed in existing groups at my discretion. Failure to either be part of a group withing the first 14 days OR having joined the Campusnet discussion forum may result severe punishment.

Subject of assignment 1 and 2:

Thermo Surveillance System:
Design of system for monitoring temperature in a brewery’s fermentation tanks

Own idea:
If your group can come up with an exiting idea, I am open to suggestions
Needs to use same technologies and solve roughly the same requirements as the Thermo Surveillance System
 

Requirements:

Capabilities of the system:
Thermo Surveillance System (TTS) must be able to
- read and collect the temperature from a random number of distributed temperature reading stations
- administrator must be able to attach a name and an alarm level to each reading station
- other users of the system must be able to survey all reading stations present stations on a PC (PC Survey Program)
- A reading station that exceeds its alarm level must be marked clearly (e.g. in a red color) on the users PC Survey - Program (PSP) temperature readings must be performed every 30 seconds
- Last hour of temperature readings must be available for inspection in the PC Survey Program (could be on a different screen)
- Must work without Thermistors attached (simulation mode)
- VERY NICE TO HAVE: a mobile client (J2ME or Pocket PC)
 

Use of UML for design
- Using OOA/OOD techniques, UML and OO Middleware is a requirement for the assignment
- Only single Class Diagram and Use Case overview required – no need for a lengthy report!
- All nicely OO please!

Which technologies to use:
- SOAP is a requirement for assignment 1 including SOAP and WSDL
- Heterogeneity is required (more than one programming language) recommended is using AXIS/SOAP for Server side and Visual Studio C++ on client side – but other combinations is allowed!
- You would benefit from trying to use a database (OR-mapping), MySQL, MS Access
- The PC platform is required for server TTS and client PSP
- Temperature Reading Stations (TRS) will be a PC using the PICO TH-03 Thermistor Converter with RS-232 serial port access
- Other platforms may be used as well for TRS and PSP – J2ME, Pocket PC, ?
- For assignment 2, replace the infrastructure with Java RMI. You may keep any SOAP mobile client (Pocket PC or Mobile Phone) made in assignment 1

Report structure and size:
Should include the following chapters:
- Synopsis (max. 1/3 page) + illustrations
- Use Case overview (strictly graphical)
- Design considerations (max. 2 pages) + illustrations
- which technologies to use and how to design
- Class diagram (strictly graphical)
- Reflection and discussion (max. 1 page) + illustrations
- List of used literature
(all pages are excluding use of graphics and figures, Use Cases and Classes MAY be documented as Appendix)
- Should include references to used literature
 

Presentation:
After the product is finished each group will present the product (assignment 1) on class:
- Present the idea of the project (Synopsis)
- Present a working project
- Present design considerations, as written in the assignment
- Have a short discussion of the constructed system
- Around 2o min. time pr. group + 1o min. for questions/discussion
 

Reuse:
- You may reuse the use-case and some of the design considerations from assignment 1 in assignment 2
- You may reuse the entire persistence structure, and (depending on the quality of your oo) even reuse most classes and their designs
- You may keep any SOAP mobile client (Pocket PC or Mobile Phone) made in assignment 1

Evaluation:
- All group members will be evaluated individually
- Therefore: make sure that all gets to participate in the presentation!!!
- The result of Assignment one may influence your grade