Ticket #144 (closed planned_task: obsolete)
PRO_LIB_CORE_MISUSE_DETECTION_R0
Reported by: | Astea | Owned by: | peko |
---|---|---|---|
Priority: | 3 | Milestone: | M03_PRE3 |
Component: | PRO_LIB_CORE | Version: | 2.0 |
Keywords: | Cc: | ||
Category: | BASE | Effort: | 1 |
Importance: | 30 | Ticket_group: | |
Estimated Number of Hours: | Add Hours to Ticket: | ||
Billable?: | Total Hours: | ||
Analysis_owners: | niki | Design_owners: | peko |
Imp._owners: | peko | Test_owners: | |
Analysis_reviewers: | boyan, peko | Changelog: | |
Design_reviewers: | orliin | Imp._reviewers: | |
Test_reviewers: | Analysis_score: | 3.5 | |
Design_score: | 3 | Imp._score: | 0 |
Test_score: | 0 |
Description
wiki page: PRO_LIB_CORE_MISUSE_DETECTION_R0 - effort: 1d
Change History
comment:1 Changed 16 years ago by deyan
- Category set to BASE
- Design_score set to 0
- Imp._score set to 0
- Test_score set to 0
- Analysis_score set to 0
comment:3 Changed 16 years ago by niki
- Owner changed from Astea to niki
- Status changed from new to s1a_analysis_started
- Analysis_owners set to niki
taken
comment:4 Changed 16 years ago by niki
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:5 Changed 16 years ago by boyan
- Status changed from s1b_analysis_finished to new
- Analysis_reviewers set to boyan
- Analysis_score changed from 0 to 2
- Are you sure there are at least 5 misuses?
- You should try to be more specific in the task requirements - "something else" does not sound good.
- Every method has an attached JavaDoc so documentation is not such a big issue.
- The implementation idea is not very clear - it should state how you will approach identifying misuses and fixing them.
- The main goal of this task is writing checks and assertions that prevent misuse so you should focus on that.
- The How to demo section should be more descriptive, for example: "Show unit tests" or "Explain the misuses to the team".
comment:7 Changed 16 years ago by niki
- Status changed from s1a_analysis_started to s1b_analysis_finished
comment:8 Changed 16 years ago by peko
- Status changed from s1b_analysis_finished to s1c_analysis_ok
- Analysis_reviewers changed from boyan to boyan, peko
- Analysis_score changed from 2 to 3.5
I think the analysis is pretty good. May be there are a lot of things stated to be done for just 1d but it is OK as a whole.
comment:9 Changed 16 years ago by peko
- Design_owners set to peko
- Owner changed from niki to peko
- Status changed from s1c_analysis_ok to s2a_design_started
comment:10 Changed 16 years ago by peko
- Status changed from s2a_design_started to s2b_design_finished
comment:11 Changed 16 years ago by orliin
- Status changed from s2b_design_finished to s2c_design_ok
- Design_score changed from 0 to 3
- Design_reviewers set to orliin
- avoid using words like things and try to name these things
- if it is impossible to make tests before the implementation, you should at least give the method of testing to make shure that the testing will not be adapted to implementation in order to just pass
comment:12 Changed 16 years ago by peko
- Status changed from s2c_design_ok to s3a_implementation_started
- Imp._owners set to peko
comment:13 Changed 16 years ago by peko
- Status changed from s3a_implementation_started to s3b_implementation_finished
comment:14 Changed 16 years ago by jani
- Status changed from s3b_implementation_finished to s2c_design_ok
- Imp._score changed from 0 to 2
- Imp._reviewers set to jani
- A test is failing in the unit test.
- You should also mention the detection of improper use of @own annotation in the wiki page.
- Always use ctrl+shift+f to format your code.
comment:15 Changed 16 years ago by peko
- Status changed from s2c_design_ok to s3a_implementation_started
comment:16 Changed 16 years ago by peko
- Status changed from s3a_implementation_started to s3b_implementation_finished
comment:17 Changed 16 years ago by peko
- Status changed from s3b_implementation_finished to s2c_design_ok
comment:18 Changed 15 years ago by deyan
- Status changed from s2c_design_ok to closed
- Resolution set to obsolete
Batch update from file query-obsoleted.csv
Note: See
TracTickets for help on using
tickets.
Adding category