Ticket #1540 (closed planned_task: obsolete)

Opened 14 years ago

Last modified 13 years ago

GLOBAL_SPEC_MANAGING_R3

Reported by: Astea Owned by: deyan
Priority: 3 Milestone: M05_PRE5
Component: GLOBAL_SPECIFICATION_ARTIFACTS Version: 2.0
Keywords: Cc:
Category: SUPPORT Effort: 2
Importance: 60 Ticket_group:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: Total Hours:
Analysis_owners: mitex,deyan Design_owners: deyan
Imp._owners: deyan Test_owners:
Analysis_reviewers: kyli Changelog:
Design_reviewers: todor Imp._reviewers: danvisel
Test_reviewers: Analysis_score: 3.5
Design_score: 3.5 Imp._score: 3
Test_score: 0

Description (last modified by deyan) (diff)

wiki page: GLOBAL_SPEC_MANAGING_R3 - effort: 2d

Change History

comment:1 Changed 14 years ago by deyan

  • Design_score set to 0
  • Milestone changed from M04_PRE4 to M05_PRE5
  • Imp._score set to 0
  • Test_score set to 0
  • Analysis_score set to 0

Moving to the next iteration

comment:2 Changed 14 years ago by mitex

  • Owner changed from Astea to mitex
  • Analysis_owners set to mitex

changed owner

comment:3 Changed 14 years ago by deyan

generating a visual elements tree will be useful. it contains all of the elements from the layout, their descriptions and specifications may be linked there. Splitting the object types (halos, huds, ..) may come handy, should be thinked of

comment:4 Changed 14 years ago by deyan

  • Owner changed from mitex to deyan
  • Status changed from new to s1a_analysis_started

done, same as r2

comment:5 Changed 14 years ago by deyan

  • Status changed from s1a_analysis_started to s1b_analysis_finished
  • Analysis_owners changed from mitex to mitex,deyan

done

comment:6 Changed 13 years ago by kyli

Revision 2 of this task is dedicated to revising and refactoring the specification diagrams we have. It is not implemented yet, and it probably would be good to make it together with this task.

comment:7 Changed 13 years ago by kyli

Also, the implementor of this task should be aware that changing the current specification could require changing the user documentation (for example, if you decide to have different keyboard shortcuts, the new ones must be pointed in the documentation).

comment:8 Changed 13 years ago by kyli

  • Status changed from s1b_analysis_finished to s1c_analysis_ok
  • Description modified (diff)
  • Analysis_reviewers set to kyli
  • Analysis_score changed from 0 to 3.5

3,5p. Good analysis, I just wrote a comment about the previous revision and added some "related" entries.

comment:9 Changed 13 years ago by deyan

  • Design_owners set to deyan
  • Status changed from s1c_analysis_ok to s2a_design_started

taken

comment:10 Changed 13 years ago by deyan

  • Description modified (diff)

comment:11 Changed 13 years ago by deyan

  • Status changed from s2a_design_started to s2b_design_finished

finished

comment:12 Changed 13 years ago by todor

  • Status changed from s2b_design_finished to s2c_design_ok
  • Design_score changed from 0 to 3.5
  • Design_reviewers set to todor

the formatting of the task page is inappropriate and a bit confusing, there are too many question marks (for example the diagram of the flaps, could be used in the section about tabs, because the tabs are presented there). it is not marked the effort spent on the design. aside from that the design is good enough.

comment:13 Changed 13 years ago by deyan

  • Status changed from s2c_design_ok to s3a_implementation_started
  • Imp._owners set to deyan

comment:14 Changed 13 years ago by deyan

  • Status changed from s3a_implementation_started to s3b_implementation_finished

Done.

comment:15 Changed 13 years ago by danvisel

  • Status changed from s3b_implementation_finished to s3c_implementation_ok
  • Imp._score changed from 0 to 3
  • Imp._reviewers set to danvisel

I think this seems pretty good. It might be useful to have a section in each report that links to user documentation of the task - maybe this can wait for a later revision of the ticket, but we do eventually want to cross-reference between the general spec and the user documentation to make sure that everything promised is actually included.

comment:16 Changed 13 years ago by deyan

  • Status changed from s3c_implementation_ok to closed
  • Resolution set to obsolete

Batch update from file query-obsoleted.csv

Note: See TracTickets for help on using tickets.