58310304 Seminar: Tool Interoperability and the Eclipse Framework in Global Software Engineering (3 cr) CANCELLED!
Teacher
Assistant Toni Ruokolainen (Toni.Ruokolainen(at)cs.Helsinki.FI)
News
Description
In future, an increasing portion of software development is done within
distributed and global software engineering teams. Software engineering projects
are based on multi-sourcing, where in-house development is done in collaboration
with out-sourced and off-shored development for optimizing the efficency and
cost of software development. Such a global software engineering scenario is
motivated by efficient utilization of resources, knowledge and core
competencies, as well as "green" values.
In such a context, distributed development teams use Internet for propagating
development and coordination mechanisms between team members. Software
engineering artefacts and processes are shared within the distributed
teams. Such collaborative and distributed (organizationally, geographically)
software engineering approach poses new kinds of demands for the tool-chains and
platforms used for facilitating the development activities.
Especially, means for tool interoperability and collaboration enactment are
needed for efficient utilization of distributed software development
teams. Since the teams and their members may use different tools and internal
processes in different software engineering phases, interoperability between the
different tools involved in a shared engineering process becomes a
problem. Facilities need to be provided for efficient collaboration between team
members; this includes real-time conversations, shared working areas, and
coordination mechanisms, for example.
This research seminar studies problems and possibilities in facilitating global
software engineering. The approach is a pragmatic one, although theoretical
issues can also be studied about interoperability in general, coordination
mechanisms, social factors in collaboration, for example. For providing a
"hands-on" experience on the subject, the seminar concentrates especially on
solutions for enhancing tool interoperability and collaboration that are based
on the Eclipse framework
(
http://www.eclipse.org).
Prerequisites
This study seminar is part of MSc studies. Thus, the completion of
bachelor-degree studies is required, especially the course for scientific
writing.
Structure
In this seminar the working language is English.
NOTE:
Please always put your name and date on every document you deliver. The abstract
and seminar paper should deal in a structured way with the following questions:
- What is the paper about?
- What is the problem under investigation?
- Why is that a problem?
- How is the problem addressed/tackled/solved?
- Why is the proposed remedy a good/better one for the problem?
Each seminar participant is expected to take the following steps:
- Extended abstract (work plan).
The work plan / extended abstract is a refinement of your seminar
topic. You may need to interact with the adviser to get the scope and
goalsetting of the paper right. The abstracts allow advisers and students
to "make a contract" about the content and schedule of the work.
The work plan / extended abstract serves also as the means of making it
visible for the rest of the group what kind of talk and paper you will
deliver and what your research question and viewpoint are in the
discussion. The length of the text is about two pages. The text also
includes the title (potentially refined from the original), list of
contents, list of main references. The abstracts are published during the
second seminar week.
- Seminar paper
The papers will be published at latest one week before the
presentation. The length of the paper is about 15-20 pages, counted with
font size of 12 pt, and 1.5 line spacing in one column format. The
structure and formatting of the paper conforms to the instructions given
on the scientific writing course (references, scientific argumentation
style etc). The paper is emailed in PDF format to the seminar teacher.
- Seminar presentation
Each session contains one presentation. You may use 60-70 minutes for your
presentation, leaving the final 30 minutes for discussion.
- Active participation into discussions and providing feedback for others.
Before each presentation, you must read the paper and prepare some
questions and comments about the topic. You may find additional viewpoints
for the topic area using the material related to your own presentation,
thus, widening the discussion from the original presentation scope.
At the end of each session, after the discussion, each participant spends
a few minutes writing down (anonymously or named) feedback notes for the
presenter, both about the paper and the presentation. Practice
constructive feedback, and bring out strengths and improvement
suggestions. The feedback goes directly to the presenter, who may choose
to share or not to share it with the adviser. After others have left, the
adviser stays with the presenter for 5-10 minutes analysis discussion.
Active participation is also measured in terms of sessions attended. You
can only pass the seminar if you have been present in all but 3 sessions.
The seminar grading takes into account the quality of the paper, success of the
presentation and constructive activity in discussions. Main emphasis is on the
paper and presentation.
Topics
- General issues and theory
- Tool interoperability
- Coordination facilities for distributed software engineering processes
- Method engineering for global software development processes
- Knowledge sharing in global software engineering
- Security, trust and privacy in global software engineering
- etc
- Related Eclipse based (or others as well) technologies
- Eclipse Communication Framework site
- Higgins - Open Source Identity Framework site
- STP - SOA Tools Platform site
- ModelBus - site
Material
Will be published in
the
intranet.
Some references on the topics
TBA
[an error occurred while processing this directive]
