Project Requirement Document
| ID | Feature | Targeted for | Priority(1-high, 2-middle, 3-low) | Risk | Feature Description |
|---|---|---|---|---|---|
| 1 | Solaris Command Search | Solaris Book | 1 | User can search the Solaris commands | |
| 2 | Auto correction | Commands | 2 | Auto correction for invalid Solaris commands | |
| 3 | Reverse matching | All | 1 | concept/topic to commands used within the section | |
| 4 | Context | All | 1 | Provide a short description for each search result | |
| 5 | Availability | Commands | 2 | show availability to point to the IPS package repository, so users are prompted to get pkgs from repo | |
| 6 | Sponsored Link | All | 2 | point to trainings, service subscriptions | |
| 7 | Multi-language support | All | 1 | Users can search in their language, and get in their language. On-demand translation can be requested | |
| 8 | Information classification tab | All | 1 | Products can customize the CA (command assistant) by providing the classification categories. (see page-6 of the Slides (3rd rev)). CA works as users type keys, and it is always possible more than one commands can match. The page-6 is meaningful only when it narrows down to just one command. (can we do this by binding TAB key to narrow complete the match?) | |
| 9 | manpages | Commands | 1 | Utilize manpage source. E.g., get the "NAME" section from manpage. | |
| 10 | !SunAlert | Commands | 2 | Can we parse !SunAlert, and match with strings like gtar(1)? | |
| 11 | !Patch | Commands | 2 | Can we parse !Patch README, and match with the list under "Files included in this patch"? | |
| 12 | !Customization | Commands | 2 | Users can narrow down the information domain (e.g., "interested in only ZFS" | |
| 13 | !Personalization | Commands | 2 | Users can personalize the command assistant. For example, they can store bookmarks (or some equivalent) so they can always go back to important pages easily. |
Sign up or Log in to add a comment or watch this page.