|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
A T T E N T I O N: To avoid duplication which could in-turn cause delays in response time to act on reported feedbacks, go to Button 2-Review Feedbacks-before submitting a new feedback.
The columns you find on the Review Feedback page will be pictured and explained, column by column, below under paragraph 3. Button 2 Review Feedbacks.
Each of us might name a possible improvement differently so take time to look closely at, not only the “Name” of the feedback, but also the full description and proposed correction of any existing feedbacks submitted and then and only then “Use” Button 1 to submit a new feedback.
COMMENTS
If you find that another user has already submitted a feedback covering your concern, add comments to their f/b. Your added comments will verify multiple concerns and may expedite the process. This can be done by scrolling to the bottom of the page and clicking on the Comments button. This will bring up the Comments page where you will find the same black ticker tape strip across the top, number of CCB feedback i.e. ID: 01.0028, the short description of the feedback, and an Add Comment button. If comments have already been added by another user, there will be two Add Comments boxes. You can use either one. Read previous comments and/or add your own. Two text boxes are available for your input.
Comment list- A text box for a brief description of
what you are adding to the larger box labeled:
Comment text- where you can
expound on the Comment list and on the feedback in general.
A box labeled Save Comment is
immediately under the Comment text and by clicking that you will be brought
back to the Feedback Comment page where you can review your added comment. Please proof-read your comments before
clicking on the Save Comment button or you will be unable to go back and
correct your comments. You can enter
another comment to amend it but even if you use the Back button and it appears
that you can correct your work, when you Save Comment again, it will only add
(not amend) your earlier work. Scroll
down (if necessary) to see all submitted comments. Ownership of the comments is included, date
and time written, as well as what stage the feedback was in when the comments
were added. Comments are in
chronological order with the newest, last. To add more comments, follow directions
above or to return to previous page, click on the “Back” button. You can click on “Return to Feedback Details”
hyperlink, to return to the Feedback Details page. To return to the complete list of feedbacks
either use the dropdown arrow next to the Back button
or use the tickertape hyperlink at the top of the page to navigate throughout
the WEBCCB site.
2. Button 1: Submit feedback This section is for detailed feedbacks of problems encountered during the operation of MMS WIN, suggestions for expanding services, and improvements to make MMS WIN more user friendly. These are generally known as bugs or enhancements. (NOTE) This is not for entering concerns about the operation of the WEBCCB. These should be addressed to jflood@romis.com or Patricia.L.Perez@navy.mil.
a. Using
your mouse to maneuver through the page, when you pass your cursor under the
words “Submit Feedback”, the I-beam will become a pointing hand. With the pointing hand on the “Submit
Feedback hyperlink, left click on your mouse and it will take you to the “Submit
Feedback” page.
The above display
is an example of the Feedback Details page you will be viewing:
1.
Submitter: Click dropdown arrow to select your name. If your name is not in the list contact the Configuration Manager
to have it added.
2.
Feedback Name: Please check current feedbacks before
submitting to ensure your concern hasn’t already been addressed by another
user. Use short concise keywords to
title the feedback.
3.
MMS Version Involved: Version being used at the time the f/b was
generated.
4. Description:
a. Be specific, thorough, and concise. The more details you can provide, such as what screen you were on, what functions you used leading up to the problem, the quicker your concern can be addressed. Don’t include your recommendation corrections until the section titled “Recommended Improvements” which follows.
b. Sometimes an error will only be generated if a specific chain of events has occurred. Your thoroughness in detailing this will assist greatly in a timely correction of the problem and avoid your f/b delays in More Information Required (MIRE) status.
c. State whether you feel the problem will be classified as a bug (glitch in the system that generates an error) or enhancement (need to rebuild, redirect or relocate data as MMS WIN evolves).
d. Include in comments low, medium or high for importance of correction and also the final date correction should be incorporated
5. Recommended Improvements: The more specific you can be, the quicker and more thoroughly the problem can be addressed. Be as thorough as possible and ensure your correct , address, email address and phone number are on the form to expedite processing if clarification is required.
To save the information you have just entered, click on the Save Feedback button. This action will take you to the same page with all your data entered. A comments button at the bottom allows you to enter any other pertinent data you feel might be relevant to the analysis of the feedback. (See “Comments” description above.)
3. Button 2: Review Feedbacks (FYI-Select submission date range below, Select Target Release Version, and Show Pending Only are not currently available).
a. Select a Submitter: If you wish to see all feedbacks scroll down the page to a complete list of all current and past feedbacks. If you wish to see only one specific user’s feedbacks, use this feature. Check the box to the left of “Select a Submitter”, then click the dropdown arrow to view the list of submitters.
i. Use your cursor to highlight the submitter of your choice and left click on that name.
ii. Click the ‘View Selected’ button and only that ‘selected’ submitter’s feedbacks will be displayed.
iii. When ready to exit, either click the “Back” button, or the “return to feedback details” prompt in lower right.
b. Review Feedbacks page example is pictured above.
c. Sort: Next to each column header is a small arrow which can be used to sort the display in numerical/alphabetical order or can be clicked a second time to reverse the order of any previously sorted columns.
d. Column names and uses from left to right:
i. ID*: Is in a format of two numbers (indicating the year feedback was written followed by a decimal/period then four digits indicating the unique number of f/b’s in the order submitted.
ii. Name*: Is the short title given to the f/b by the submitter. The name is hyperlinked and by passing the cursor under the name, the arrow will change to a hand and by left clicking with mouse, the full feedback will be displayed.
iii. Phase*: Is the current f/b phase in the process from Submitted to Released.
1. Submitted phase-initial phase when the f/b is added to the WEBCCB, alerting MMSWIN Users of a possible need for change.
2. Reviewed and Not Promoted-not found to be a valid concern, i.e. duplicate, already taken care of, already scheduled for a fix in a future version of MMS.
3. Pending Analysis phase-during this phase data is being gathered to evaluate cost, time, most feasible version for implementation.
4. Analysis-is the phase where a determination of cost/time involved to implement the enhancement, which version the update will be included in and the impact on the MMS community.
5. Pending Vote phase-Analysis is complete and preparations are being made to distribute all applicable information concerning the f/b to voters prior to the actual vote being taken.
6. Voting phase (explained below in paragraph 4, Button 3-Voting)-a timed phase determined by the Configuration Manager in which all authorized voters are given to vote. Voters can either vote for, against, or abstain.
7. Rejected-means the vote did not carry and voters against the change outnumbered the voters for the change. The change will not take place at this time. Another vote can be called for at a later time and the issue brought up again for reconsideration.
8. Passed- means the vote carried and voters for the change outnumbered those against the change. Depending on money and resources, the change will be implemented in the future.
9. Pending Coding-is the phase before coding while waiting for funding of the enhancement.
10. Coding-phase during which programming is done to accommodate the change in all respects. In some cases, a major amount of adjustment is required to make what seems like a very minor change. Screens may have to be totally rebuilt and rearranged to permit the change to be made fully.
11. Pending Certification Testing-preparing for Cert Testing.
12. In Certification Testing-comprehensive investigation of the change in every conceivable application to ensure completeness and accuracy.
13. Failed Cert Testing-indicates the enhancement, when tested, did not do 100% of what it was designed to do. During this period, a decision will be made as to the feasibility of rebuilding or reorganizing to bring the enhancement up to full use.
14. Cert Tested and Verified-indicates that the implementation is ready for use. All that remains if for the enhancement to be included in the version of MMSWIN determined by the Configuration Manager.
15. Released-indicates that this feedback has successfully gone through all phases and is now implemented fully into MMSWIN’s current version.
iv. Status*: There are eight status codes as follows:
1. CANC-status is cancelled and the feedback request will not be filled
2. DEFR-deferred status, may be on hold for funding, etc.
3. UM-submitted do to user misunderstanding
4. DUP-duplicate feedback
5. MIRE-more information required
6. bug fix-means the change can be done with the minimum amount of time and funding and possibly without a vote required.
7. NMCI-Navy Marine Corps Internet use only
8. None-self explanatory
v. Sub Date*: Date submitted
vi. Last Mod Date: Final date modifications were made
vii. Vote Status*: Five possible presentations available
-majority
of voters are abstaining 
-no votes have been
entered
|
|
|
|
|
|
|
|
NOTE: If the status is blank, the f/b has not been designated for a vote
viii. Voting close: last available date to vote on this issue
ix. Code: Project code-as in N/C, REP, WH, dept. #, etc.
x. Cost: Estimated total cost of building, testing and releasing bug/enhancement
xi. Target Release*: Expected version in which the f/b will be incorporated
xii. Orig FB Num*: If this f/b was documented in an earlier release or refers to a previous f/b, that number would be posted here
*-available to WEBCCB personnel with submitter (SUB)access only.
4. Button 3: Voting: When a feedback requires an enhancement affecting the MMS community, a voting criteria may be met and the Configuration Manager may call for a vote by the CCB voters.
|
VOTING |
|||||||||
|
If authorized to vote, user can click on any f/b Name
in the Review Feedbacks page with a status of ‘Voting’ and when the voting box
at right appears, enabling the user to see the time remaining to submit
their vote. Read the Review
Feedback description, and any comments attached. If unclear exactly how the f/b involves
MMS, contact the submitter and ask for amplification from them. Then prior to the end of the voting
period, enter one of the choices in the box to the right. Voting will help determine the
criticality and user’s desire in regards to the present issue. Radio buttons allow a choice of three
inputs, Approve, Reject or Abstain.
After making your choice, click the ‘Submit Vote’ button.
|
|||||||||
|
|
VOTING |
|
|
|
|
|
The voting box on the left will appear next confirming
your vote and as shown, can be changed at any time prior to the close of voting
for that feedback. As a voter, you
can check the status of the voting by clicking on either the word ‘Vote’ in
the header in any screen or by clicking on the Voting hyperlink in the Home
page. All feedbacks that are
currently in a voting status will be displayed along with how you voted
under the ‘My Votes’ column (example below).
|
|
|
|
|
|
|
|
To close the WEBCCB site, use Logout at the top of the page or click on the ‘Back’ dropdown arrow and return to any page previously visited.
The CCB site is checked regularly and submissions are forwarded promptly for consideration.
This page is maintained by the ROMIS MMS Help Desk and be contacted with any constructive criticism at helpdesk@romis.com . Last updated 03/10/2008.