Hi Raydhitya,
First of all, thanks for your efforts.
Session Invitation, Use Case 2: One time you speak of "more than one" and
another time of "two projects". That should be consistent. Furthermore, it is
not possible (from the GUI) to accept one out of two incoming projects. But
since these use cases are meant as a specification, that won't pose a problem.
Our GUI simply does not require any changes to fulfill this spec.
Project Invitation: There are two things, that are not/should not be true.
(1) "Another user cannot be added to the session" - No, there is no reason
to prevent changes to the set of participating users. New users may join,
others may leave without interrupting the rest of the session. The questions
remains, how new users should be invited, once the session is started. For
technical reasons, it's much easier to let the host do the invitation (non-host
invitations were disabled a few months ago). Basically, non-host invitations
can be useful and convenient, but technically that should always fall in the
responsibilities of the host - the other user may get the possibility to "tell"
the host, to invite a certain additional user.
(2) "all users of the session can add any project to the session" - From the
user's perspective that would be convenient, but the same technical reasons
that make non-host invitation difficult and error-prone also hold for adding
new projects: It's much safer to let the host do these things. Again, any user
might trigger that process, but only by sending the required data to the host,
who then distributes it to the other participants.
Currently, we only support a Session invitation that comes along with a Project
invitation. But basically, one could separate these two - and so should you
(the first four use cases cover both areas). Futhermore, if you formulate the
rule "there can be multiple projects in a session, every user shares all of
them" once, there is no need for your differentiation and your use cases would
become simpler and fewer.
Best Regards,
Franz
From: Raydhitya Yoseph [mailto:raydhitya.yos...@gmail.com]
Sent: Monday, July 08, 2013 4:48 PM
To: dpp-devel@lists.sourceforge.net
Subject: [DPP-Devel] Invitation Policy
I'm posting this so all developers can know how invitation and cancellation
work.
There are two invitations. The first one is session and the second one is
project.
Session Invitation
A session can be started if one user share one or more than one projects to one
or more than one users.
1. One project and one user is the simplest use case. Alice invites Bob to
share a project. Bob can accept the project to start a session with Alice. If
Bob rejects, no session started.
2. More than one project and one user. Alice invites Bob to share two projects.
Bob can accept all projects to start a session with Alice. If Bob rejects one
project, no session started.
3. One project and more than one users. Alice invites Bob and Carl to share a
project. Bob and Carl must accept the project to start a session with the three
of them. If only Bob accept the project, Bob starts a session with Alice.
Likewise if only Carl accept the project, Carl starts a session with Alice. If
both Bob and Carl reject the project, no session started.
4. More than one project and more than one users. Alice invites Bob and Carl to
share two projects. Bob and Carl must accept all projects to start a session
with the three of them. If only Bob accepts all projects, Bob starts a session
with Alice. Likewise if only Carl accept all projects, Carl starts a session
with Alice. If both Bob and Carl reject the project, no session started.
Project Invitation in a Session
In a session all users share all project of the session. Another user cannot be
added to the session, but all users of the session can add any project to the
session.
1. One project. One of the user add one project to the session. All users of
the session must accept the project to allow the project to be added to the
session. If one user rejects the project, it is not added to the session.
2. More than one project. One of the user add two projects to the session. All
users of the session must accept all projects to allow all projects to be added
to the session. If one user rejects one project, all projects are not added to
the session.
Are all use cases correct?
--
Raydhitya Yoseph
Informatics Engineering
Institut Teknologi Bandung
http://raydhityayoseph.blogspot.com
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
