WAVV
Requirement Form
Date: 3/31/2010 Requirement #: WAVV201012
Title: (Paraphrase problem in a
single statement)MONDCSS is too small as
shipped
Detailed
Problem Description: (Description of what you want changed - 400 character entry limit)
The shipped DCSS defined for
monitor data is often too small for modern configurations. The default size
should accommodate the architectural maximum.
Priority: (Select one: Urgent
- High - Medium - Low)
Medium
Requested
Completion Date: (When? Examples: 3 months, 1 year,
Next Release) next release
Requirement
Type: (Select one:
Acceptability - Compatibility/Migration - Ease of Use - Feature/Function - Performance - Reliability/Availability/Serviceability
- Packaging - Interoperability)
Feature/Function
Business
Justification: (Why? Non-technical
business case description. Do not reword Detailed Problem
Description from above. What are the benefits to be gained by your
company, and the vendor and others?
Quantify: run time, dollars, manpower, etc. Why should the vendor do this for the customer?)
Customers have sufficient storage, but few have
time or expertise to calculate the proper DCSS size for a particular configuration.
Shipping the default DCSS to accommodate the architectural maximums is a simple
way to improve usability for PerfKit and other performance monitors -- one less
thing to have to worry about.
Solution: (Optional)(Desired/undesired elements Note: Making a suggestion may limit a
vendors ability to deliver a solution)
Define the default MONDCSS size to accommodate
the architectural maximum size for I/O configurations in a VM system
Impact: (Optional) (How
will your company’s business be affected if a solution is not delivered?)
We'll continue to do it ourselves.
Author Name: David
Boyes Author Title: Chief Technologist
Company Name: Sine
Nomine Associates
&
Address: 43596 Blacksmith Square
Ashburn, VA, 20147
Author E-mail: dboyes@sinenomine.net
Telephone:
US/Canada (703) 723-6673 Extension: 1233