The project goal is to provide an environment and framework for students to get practical experience on real-life service development, going from the business idea of a new service through its design and implementation to actual launching the service in the Web. Development includes internal service audit, intra-group cross-validation and testing of the results during the whole lifecycle of the service development. The projects is designed for IMP WISE students, 2nd year of studies
Prerequisites are sufficient knowledge on theories and applications of: Semantic Web and Ontology Engineering Agent Technologies Cloud Computing Big Data Engineering
Mode of studies: Team work International teams 4 members in each team Joint report + demo + presentation Joint project defense Variety of skills – see bellow
Leadership – coordination Delegation ! ’Paper work’ – keeping record, writing report Negotiations - communications Presentations Creative design / visualization Development/implementation
Team leader Negotiator Speaker Archivarius Domain expert Platform developer Application developer Interface developer
To analyze own strength, weaknesses and preferences - IW To build the teams aiming for each and everyone to shine - TW To distribute the management roles - TW To chose the domain and service - TW To distribute the technological roles - TW Defense of the service idea - SW
IW – individual work TW – team work (fixed time & space) SW – supervised work (fixed time & space): - lectures, - public defenses, - seminars, - presentations, - consulting
To design the service ( by skeleton) - TW To defend own design if needed ? - SW Start to develop platform, application and interfaces – IW & TW Technology Consulting * – SW Service development - TW To negotiate Master Thesis topic – I&S W Final service defense * - SW
By topic – with certain expert By technological role – with certain team member By organizational role – with certain team member By team – each claim own input NB! – experts will only provide ’new’ knowledge
The final system should: Be a Semantic web service Expose an API Be deployed in the cloud Have some sort of pro-activeness (Push service) Have BI kind of analytics Consume multiple sources of information (services integration | aggregation) Have a human interface (as alternative) Include some form of user preferences It will be good idea to involve a reasoning (depending on the business case) – further research ?
Domain Ontology, MetaData Storage Platform Functionality – Domain- independent Application Functionality – Domain-specific Domain Expert, Knowledge Engineer Platform Developer Application Developer Technological Collaboration with other teams Interfaces Interface Developer Inter-Domain collaboration