Showing posts with label Requirements Module. Show all posts
Showing posts with label Requirements Module. Show all posts

Thursday, February 17, 2011

HP QC Certification (HP0-M31) - Points to Remember


                                               IMPORTANT POINTS

1)  Quality Center Editions: The availability of each feature depends on your Quality Center edition — Starter, Enterprise or Premier.
2)     To download files to your machine, you must log in with administrator privileges. For more information on the minimum permissions required to install client components, refer to the HP Quality Center Installation Guide.
3)     If file downloads are prohibited through your browser, you can install these files from the HP Quality Center Client Side Setup Add-in on the HP Quality Center Add-in page. For more information on add-ins, refer to the HP Quality Center Installation Guide.
4)     Quality Center prompts you to install Microsoft .NET Framework 2.0 if it is not already installed on your machine. To perform the installation, follow the instructions in the Software Update Installation Wizard (if Windows Installer 3.1 is not installed) and the Microsoft .NET Framework 2.0 Setup.
5)     Resetting your password is unavailable in either of the following situations:
6)     It is deactivated by the PASSWORD_RESET_DISABLE Site Configuration
7)     Parameter or LDAP authentication is enabled.
8)     Available Quality Center functionality may depend on how your site or project administrator has configured your Quality Center project.
9)     Quality Center Editions: The availability of each module and feature depends on the Quality Center edition you have — Starter, Enterprise or Premier. For more information, see Appendix C, “Quality Center Editions”.
10) You can navigate between the modules using shortcut keys. For a list of shortcut keys, see Appendix B, “Quality Center Keyboard Shortcuts.”


(Lets Read More)

HP0-M31 Quality Center Certification Preparation 2 - Requirements Module

REQUIREMENTS

·         Requirements describe in detail what needs to be solved or achieved to meet the objectives of your application under development.
·         Not all fields and functionality in the Requirements module are available if you are working with the Starter Edition.
·         You use the requirements scope to determine the overall requirements for the application under development. You then define different groups of requirements based either on requirement type or functional area.  Requirement groups are recorded in the Requirements module by creating a requirements tree. The requirements tree is a graphical representation of your requirements specification, displaying the hierarchical relationship between different requirements.
·         For each requirement group, you create a list of detailed requirements in the requirements tree.
·         Each requirement in the tree is described in detail and can include any relevant attachments. You then assign the requirement a priority level which can be taken into consideration when creating the test plan.
·         After defining your requirements, you can add traceability between the requirements. When analyzing the impact of a change proposed in a specific requirement, traceability shows the other requirements that the change might affect.
(    Lets read more)

HP0-M31 QC Certification Preparation 1 - Releases Module

1)      The Releases module is available for Quality Center Enterprise Edition and Quality Center Premier Edition.
2)      The foundation of the Releases module is the releases tree. This tree enables the modeling of upcoming releases within a hierarchical tree structure.
3)      A release represents a group of changes in one or more applications that will be available for distribution at the same time. After defining the release, you define cycles.
4)      A cycle is a set of development and quality assurance efforts performed to achieve a common goal based on the release timeline.
5)      After defining the releases tree, you define and review the requirements in the Requirements module and assign them to releases and cycles.
6)      Requirements describe in detail your application needs.
7)      Requirements are used as a basis for the test plan in the Test Plan module. The tests you create during the test plan phase should cover these requirements.
8)      After assigning requirements to releases and cycles, you assign each test set folder in the Test Lab module to a cycle.
9)      A test set is a group of test instances in a Quality Center project designed to achieve specific test goals.
10)   If an application flaw is detected while running a test set, you can submit a defect. Quality Center automatically creates a link between the test run, associated release and cycle, and the new defect.
11)   While reviewing and deciding which new defects need to be fixed, they can be assigned to the appropriate target release and cycle.
(Let us read more)