Advertisement

05.12.2006 at 06:00AM PDT, ID: 21848144
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.6

From Requirements Specification to Feature list

Asked by Razzie_ in Software/Systems Design

Tags: , ,

Hello all,

I was wondering if there is a 'best-practice' to go from your System Requirements Specifications to a 'feature list', which is used imho primarily if you're building COTS software and want to sell it. First you specify what the system must be able to DO, but when it is built, you want to show the world what your software CAN. The difference between the two is therefore, in my opinion, small. The typical requirements in a SRS are stated in phrases like:

'The system shall...'
'The system must be able to...'

and I imagine a system feature list / manual to provide information like:

'Our system can...'
'Our system is able to...'

Though there are enough templates for SRS (IEEE, Volere) I was wondering if there are any 'best-practice' ways to translate your SRS to a manual / feature list to sell your system. I hope my question is clear :)

Regards,
RazzieStart Free Trial
 
Loading Advertisement...
 
[+][-]05.12.2006 at 09:30AM PDT, ID: 16668986

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: Software/Systems Design
Tags: specification, requirement, software
Sign Up Now!
Solution Provided By: Jenn3
Participating Experts: 1
Solution Grade: A
 
 
[+][-]06.04.2006 at 09:32AM PDT, ID: 16827622

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
[+][-]06.04.2006 at 01:46PM PDT, ID: 16828630

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32