Difference between revisions of "EMU"
m |
|||
| Line 27: | Line 27: | ||
* interface for IDE and server | * interface for IDE and server | ||
* modular / independent of IDE-integration | * modular / independent of IDE-integration | ||
| − | |||
===EMU-IDE integration=== | ===EMU-IDE integration=== | ||
* minimal change to existing ES-classes and features. | * minimal change to existing ES-classes and features. | ||
* modular integration: activatable and removable / hideable | * modular integration: activatable and removable / hideable | ||
| + | |||
==User Requirements== | ==User Requirements== | ||
| Line 39: | Line 39: | ||
* minimal extra work (less total work) | * minimal extra work (less total work) | ||
* better efficiency | * better efficiency | ||
| + | |||
Revision as of 12:38, 24 April 2006
Contents
Overview
Eiffel Multi User: The aim of this project is to integrate a repository functionality into EiffelStudio.
Software Requirements Specification
The Parts
- EMU-Protocol
- EMU-Server
- EMU-Client
- EMU-IDE integration
Developer Requirements
EMU-Protocol
defines Client/Server communication with
- client/server states
- available messages
- client/server actions
EMU-Server
- stores and manages code-repository
- synchronizes code of clients
- manages Locking-System
EMU-Client
- interface for IDE and server
- modular / independent of IDE-integration
EMU-IDE integration
- minimal change to existing ES-classes and features.
- modular integration: activatable and removable / hideable
User Requirements
- easy to use
- target is a small project group of up to 20 developers.
- code synchronisation process mostly hidden from user
- minimal extra work (less total work)
- better efficiency
Milestones
M1: April 25th
- set up mailinglist es-emu@origo.ethz.ch (Bernd)
- wiki page up to date
- everyone managed to compile Eiffelstudio
M2: May ???
- To be completed by the team
Team
Everyone intrested in this project is welcome to join our mailinglist es-emu@origo.ethz.ch
