Comments (24)
migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 12:17pm
I agree with the defect. There is not enough information in the SRS about "login process".
from netbout.
migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 12:26pm
I think that there should be two mechanisms of "user authentication" (let's call it this way): explicit and implicit.
"Explicit authentication": user provides his credentials (email+password or id+password), the SUD validates them, and let him in.
"Implicit authentication": the SUD understands who is the user by HTTP cookie, validates the cookie, and let him in.
I don't see why we need "captcha" during authentication.
from netbout.
migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 12:26pm
The ticket is related to UC6 mostly.
from netbout.
migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 12:30pm
Marko, the ticket is for you. You should make changes to UC6 in order to make it non-ambiguous.
from netbout.
migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 1:37pm
duplicate in #39
from netbout.
migrated from Trac, where originally posted by marko_lipo on 23-Sep-2010 10:14pm
I would say that UC6 should describe how user identifies himself with ID and password, and in UC7 when he receives invitation in his e-mail, and clicks on the secured link in e-mail and registers to the NetBout. Do you agree?
In addition, I'm thinking of new entity called SearchRequest or BoutSearch that enables list of bouts belonging to the user, that user would create after he logs in. So draft of UC6 main flow would be:
UC6 where user identifies himself:
- ActorUser opens web site NetBout.com.
- „we offer login page“
- "ActorUser provides ID and passowrd"
- "we validate user ID and password"
- ActorUser creates BoutSearch
- SUD lists NetBouts-s of ActorUser
- ActorUser reads NetBout.
In UC7 where user accepts invitation, he is registering with e-mail.. Explained in ticket #30; and we need failure flows... Please feedback do you think this is right direction?
from netbout.
migrated from Trac, where originally posted by yegor256 on 26-Sep-2010 3:07pm
Yes, you're right about UC7.
We have to remember that functional requirements (use cases) should not say anything about their implementation. We should not say how exactly a user will find bouts, through searches or maybe somehow else. We just have to say what functions will our user be able to do with the system.
I think that we should rename UC6 to something like this:
UC6 where ActorVisitor (the visitor) turns into ActorUser (the user):
1. "The visitor provides ID and password through HTTP link".
2. "SUD validates ID and password".
UC6 1a) If "there are no ID or password in the link":
1. "SUD asks the visitor to provide ID or email, and password"
UC6 2a) If "credentials are invalid":
1. Failure "Access Denied".
What do you think?
from netbout.
migrated from Trac, where originally posted by marko_lipo on 27-Sep-2010 12:02am
Yes, I missed the point with describing searching in UC6, however do you think that this type SearchRequest would fit into UC8 for example?
I agree with your proposal for UC6 (I'll put it into SRS shortly), however it puzzles me regarding UC structure, as we put it so far. For example UC1 looks strange if in UC6 we describe how to turn visitor to user. We need to describe first how to create ActorUser first time, don't we?
from netbout.
migrated from Trac, where originally posted by yegor256 on 28-Sep-2010 6:46pm
Absolutely, we have to change UC1, UC2, and UC6. UC1 should start something like this:
UC1 where ActorVisitor (the visitor) turns into ActorUser (the user)
and communicates with others:
1. The visitor turns into the user and joins NetBout.
2. The user talks in NetBout.
...
UC2 where ActorVisitor (the visitor) turns into ActorUser (the user)
and joins NetBout (the bout):
1. The visitor turns into the user.
2. The user creates the bout.
...
UC6 where ActorVisitor (the visitor) turns into ActorUser (the user):
1. "The visitor provides ID and password through HTTP link".
...
Got the idea?
from netbout.
migrated from Trac, where originally posted by marko_lipo on 29-Sep-2010 11:10pm
Understood. Pls let me know - refering to this and other tickets that are close to the solution and editing in SRS: do I have to edit SRS as we agreed first and then ask Yuri approval about resolution of the ticket, or vice versa?
from netbout.
migrated from Trac, where originally posted by yegor256 on 4-Oct-2010 12:02pm
First, you make changes to the SRS. Then, you approve the changes. If for some reason your changes are not OK for anyone - we can rollback them in wiki. So, feel free to make changes as soon as you think it's appropriate.
from netbout.
migrated from Trac, where originally posted by marko_lipo on 5-Oct-2010 9:48pm
I tried to update SRS with new UC1 as we discussed, but I keep getting new 'syntax error' or 'statement ignored' warnings. I tried to change UC1 definition as we discussed:
UC1 where ActorVisitor (the visitor) turns into ActorUser (the user) and communicates with others:
1. The visitor turns into the user and joins Netbout.
So I didn't managed to go any further in descriptions...
Please advise.
from netbout.
migrated from Trac, where originally posted by yegor256 on 11-Oct-2010 8:20pm
The problem is that we can't use and
in UC signature, since it's a reserved word in RQDQL. Thus, a correct UC1 signature would look like:
UC1 where ActorVisitor (the visitor) turns into ActorUser (the user)
to communicate with others:
Try it.
from netbout.
migrated from Trac, where originally posted by marko_lipo on 12-Oct-2010 10:26pm
Thanks, it worked for UC1, but doesn't work for UC2.
I tried to insert for UC2:
UC2 where ActorVisitor (the visitor) turns into ActorUser (the user) who joins NetBout (the bout):
I got:
Warning: The Wiki page field '[wiki' is invalid: SRS]/9: "`1. The user joins NetBout.`" - `Signature '{user} joins {?}' is not recognized`
I tried with comma, or replacing 'who' word with 'to', 'thus' etc.. but error warding is always the same. Please help.
from netbout.
migrated from Trac, where originally posted by yegor256 on 24-Oct-2010 4:57pm
When it says that some "signature is not found" it means that the system can't understand your UC flow. It can't find any use case in wiki which will be related to this flow.
Every UC flow has to be either "quoted"
or formally linked to another use case. When you're getting a message about "signature not found" it means that it's not quoted and can't be linked. Makes sense?
from netbout.
migrated from Trac, where originally posted by marko_lipo on 27-Oct-2010 5:16pm
I understand the concept. However when trying to update UC2 as discussed, why is it OK to insert signature:
where ActorUser joins NetBout:
but when I insert as agreed:
where ActorVisitor (the visitor) turns into ActorUser (the user)
and joins NetBout (the bout):
then I get this (above mentioned) error?
In addition in UC2 first flow is:
1. ActorVisitor turns into the user.
but I don't see that in SRS first page it is recognised as UC6 signature.
Did I miss something again?
from netbout.
migrated from Trac, where originally posted by yegor256 on 12-Nov-2010 2:38pm
Don't use and
in signature, it is a reserved word. Try this signature instead:
where ActorVisitor (the visitor)
turns into ActorUser (the user)
joining NetBout (the bout):
I think that it should work. Later, everywhere you should use this exact signature, like:
1. ActorVisitor turns into the user joining the bout.
from netbout.
migrated from Trac, where originally posted by marko_lipo on 12-Nov-2010 11:11pm
OK, thanks it is fixed now.
from netbout.
migrated from Trac, where originally posted by yegor256 on 15-Nov-2010 6:35am
When you make a fix to some wiki page, please update the ticket with the following message (or something similar):
It is fixed in [wiki:UC2@11]
This message will tell everybody where exactly you just made changes, e.g. [wiki:UC2@11].
Yuri, please review the result.
from netbout.
migrated from Trac, where originally posted by yegor256 on 21-Feb-2011 7:33am
Yuri, any news here? Please update. If we have no answer in the next 7 days I will have to assign the ticket to someone else.
from netbout.
migrated from Trac, where originally posted by y.vedenin on 22-Feb-2011 11:56am
I'll update the ticket till Wednesday, February 23, 2011
from netbout.
migrated from Trac, where originally posted by y.vedenin on 25-Feb-2011 12:04am
It's ok from my point of view
from netbout.
migrated from Trac, where originally posted by yegor256 on 25-Feb-2011 7:20am
Closed, many thanks to all.
from netbout.
migrated from Trac, where originally posted by yegor256 on 23-Nov-2011 9:06am
Milestone JUN11 deleted
from netbout.
Related Issues (20)
- migrate to Dokku HOT 11
- Dependency conflicts on com.jcabi:jcabi-log, leading to inconsistent program behaviors HOT 3
- ruby release HOT 21
- Dependency Dashboard
- Testcontainers configuration for database bootstrapping HOT 2
- login fails due to lack of tests HOT 3
- simple search should work HOT 3
- Login does not work HOT 8
- search parsing
- permissions HOT 5
- extra restrictions HOT 3
- search doesn't work for flags and tags HOT 3
- login via token HOT 3
- token login is not tested well HOT 3
- JSON API is not tested well HOT 3
- more details in JSON API HOT 3
- Codecov check doesn't work HOT 1
- offset and limit don't work in search API HOT 6
- `absent` doesn't work HOT 6
- move to heroku HOT 18
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from netbout.