Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

to identify 10 most critical defects in current version of SRS #8

Closed
yegor256 opened this issue Apr 21, 2013 · 8 comments
Closed

to identify 10 most critical defects in current version of SRS #8

yegor256 opened this issue Apr 21, 2013 · 8 comments
Assignees

Comments

@yegor256
Copy link
Owner

migrated from Trac, where originally posted by yegor256 on 8-Sep-2010 2:12pm

You should review the existing version of SRS and identify 10 most critical defects in it.

Preliminary version of site design/layout you can find here: http://linux.fazend.com/p/netbout/trunk (the same login/password as in Trac).

Please report each defect in its own ticket and assign them to the SRS component. I already set the budget for the ticket, if it's not enough, please let me know. If it's OK, please go ahead.

@ghost ghost assigned yegor256 Apr 21, 2013
@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 9-Sep-2010 11:27am

Yuri, please update me on this. Thanks!

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by y.vedenin on 15-Sep-2010 10:19am

Sorry for the delay.
It took me some time to read the SRS.
I created the following items within this ticket:
#22
#23
#24
#25
#26
#27
#28
#29
#30
#31
#32
#33
#34
#35
#36

Please, review them.

By the way, is there any ability to link SRS pars (use cases, steps of use cases and pages) with exact screens already created? It will help to understand the SRS better from my point of view.

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 16-Sep-2010 3:38pm

Good job, thanks! The defects are very specific and correct.

Let's wait while they are closed, I dispatched them all.

The idea to link SRS to implementation is good and bad at the same time. The idea of requirements specification is to make them separated from implementation. How they are implemented is a decision made by programmers. If we add links we will make requirements "biased" and will have problems in the future. Let's keep them as they are now.

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 21-Feb-2011 7:38am

Most of defects reported are already fixed. They are waiting for your response. Please, help us to close them finally. Thanks!

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by y.vedenin on 22-Feb-2011 11:51am

I'll review the tickets till Wednesday, February 23, 2011

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by y.vedenin on 15-Mar-2011 11:09am

I think this ticket can be closed if tickets #22 and #33 are completed from your point of view.

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 16-Mar-2011 6:03pm

Indeed, the ticket is closed. Thanks!

@yegor256
Copy link
Owner Author

migrated from Trac, where originally posted by yegor256 on 23-Nov-2011 9:06am

Milestone JUN11 deleted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant