| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-kw2vYHKDkWv2tZrDMrBPNA" |
| name="new_checklist,_Vael8CGMEdu3VKXZx45D3A" guid="-kw2vYHKDkWv2tZrDMrBPNA" version="1.0.0"> |
| <sections xmi:id="_kTZiACGMEdu3VKXZx45D3A" name="Global functional requirements have been captured and validated" |
| guid="_kTZiACGMEdu3VKXZx45D3A"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Are functional requirements that affect multiple use cases identified? For example, all use cases may be subject to
 |
| access control, audit trails, general responses to abnormal situations (overflow, communication facilities, error
 |
| handling and recovery and so on).
 |
| </li>
 |
| <li>
 |
| For each of these requirements, are they behavioral and could be better captured in a common use case?
 |
| </li>
 |
| <li>
 |
| For each of these functions, is it clear how input and shared data generate output and shared data?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_-eJXoCGMEdu5QMD9IAHRNg" name="Usability requirements have been captured and validated" |
| guid="_-eJXoCGMEdu5QMD9IAHRNg"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have the efficiency and usability factors of user tasks been considered?&nbsp;
 |
| </li>
 |
| <li>
 |
| Are the requirements specified in a way that is verifiable, including metrics and target values?
 |
| </li>
 |
| <li>
 |
| Have&nbsp;novice as well as expert users been considered?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_QCbtwCGNEdubdKsr57an1g" name="Reliability requirements have been captured and validated" |
| guid="_QCbtwCGNEdubdKsr57an1g"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have reliability requirements been specified as measurable requirements or prioritized design goals?
 |
| </li>
 |
| <li>
 |
| Is error checking and recovery required?
 |
| </li>
 |
| <li>
 |
| Are undesired events considered and their required responses specified?
 |
| </li>
 |
| <li>
 |
| Are initial or special states considered (such as cold starts or abnormal termination)?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_e3pOgCGNEdubdKsr57an1g" name="Performance requirements have been captured and validated" |
| guid="_e3pOgCGNEdubdKsr57an1g"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have the resource and performance margin requirements been stated (for example speed, response time, recovery time
 |
| of various software functions)?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_l8CeUCGNEdubdKsr57an1g" name="Supportability requirements have been captured and validated" |
| guid="_l8CeUCGNEdubdKsr57an1g"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Are there any requirements that will enhance the supportability or maintainability of the system being built?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_wIttsCGNEdubdKsr57an1g" name="Constraints have been captured and validated" |
| guid="_wIttsCGNEdubdKsr57an1g"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Are there any required standards in effect, implementation language, policies for database integrity, resource
 |
| limits, operating environments, and so forth?
 |
| </li>
 |
| <li>
 |
| Has the use of inherited design or code or pre-selected tools been specified?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_5j6c0CGNEdubdKsr57an1g" name="External interfaces have been identified" |
| guid="_5j6c0CGNEdubdKsr57an1g"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Is it clear how the software interacts with people, the system's hardware, other hardware, and other software?
 |
| </li>
 |
| <li>
 |
| Have all critical data elements that cross system boundaries been identified for those scenarios that will be
 |
| implemented&nbsp;next?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_H052MCGOEdubdKsr57an1g" name="Business rules have been captured and validated" |
| guid="_H052MCGOEdubdKsr57an1g"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Are the rules relevant to the use cases identified (data validation rules, formulas, flow decisions)?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_NBM78CGOEdubdKsr57an1g" name="Applicable standards and regulatory compliance requirements have been identified" |
| guid="_NBM78CGOEdubdKsr57an1g"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have all requirements derived from existing standard and regulations been specified?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| </org.eclipse.epf.uma:ContentDescription> |
