development, and learn rom their past successes and ailures so that theymay implement more e cient and intelligent processes.Key components o the Devest approach to knowledge managementinclude a centralized knowledge base, instant access to quality reports, andtools or communicating inormation relevant to individual test cases andthe project as a whole.
Managing Project Knowledge
In Devest, all testers may access a centralized repository o inormationrom within the Devest client. Te Devest knowledge view, powered byechExcel KnowledgeWise, provides development and QA organizations with a tool or collecting and organizing the ideas that drive productdevelopment and testing. All ideas, both ormal and inormal are collectedand managed in the same, centralized knowledge base.echExcel KnowledgeWise is a key component in the echExcelDevSuite o application lie cycle management products. KnowledgeWise provides project managers, designers, developers, testing groups, andsales and marketing departments with a secure repository or all projectdocuments— the project plan, business requirements, unctional andtechnical specications, risk management documents, and corporatestandards and guidelines may be managed in one knowledge base that isshared by the entire business.A centralized knowledge base increases e ciency, prevents the losso inormation, helps to reduce system and maintenance costs, andacilitates collaboration by distributed teams.Access to knowledge items is protected by privilege-based accesscontrols. Te ability o project members to view, edit, lock, checkout, and check in protected les is dened by their role in the project.Built-in version control tools ensure that all project developmentand testing teams (no matter where they are in world) always haveaccess to the most up-to-date documents.
Leveraging Control Documents
A common knowledge base ensures that the QA organization always hasaccess to the latest project control documents —business requirements,unctional and technical specications— and enables them to leverage thisinormation to plan and organize their test plans early in the development processes.In Devest, QA organizations may access project control documents assoon as those documents are uploaded to the knowledge base—at the same•••time they are available to the developers themselves. Access enables the QAorganization to jump-start test planning and develop testing strategies andtest cases in parallel with the implementation o the designs.Using these control documents, testing groups may estimate the scope o the project, allocate resources, and plan appropriate strategies or testing the unctionality and perormance o those eatures.esting groups need not wait or all o the control documents to beapproved beore they begin their test planning. Tey can create test casesand build test planning structures in a piecemeal ashion as the designed product is realized in the knowledge base. With each new controldocument that is added to the knowledge base they can create appropriatetest cases.Ideally, project control documents are complete and approved at thebeginning o the test planning stage. However, the specications anddesigns that are approved at the beginning o the development process maybe sketchy, inadequate, or change signicantly over time due to changes inthe marketplace, technical problems, or time constraints. Devest providestesting groups with the exibility they need to adjust to changes in designor schedule.QA organizations may take an evolutionary approach to test planning.By organizing their test cases by product eatures, they can readilyadjust to changes in product design or changes to the schedule. Teymay create appropriate structures and test cases as the requirements andspecications are completed and update the list to accommodate changesto the application. Devest planning structures and test cases may be easilyedited and updated so that QA organizations need not pay the penalty orchanges in design.
Facilitating Task-level Communication
By placing knowledge management at the core o all development processes, Devest acilitates all project-level and task-level communication. Just as the centralized knowledge base ensures that all stakeholders haveaccess to project inormation, the complete history o every test case andall background inormation is always right at hand. All communication isrecorded and tracked with the test case so that test task itsel is the vehicleor communication. Key inormation cannot be lost in e-mail exchanges orburied in user inboxes.Good notes rom the prior testing enables test team members to pick uptesting where others have lef o. Any testing team member may pick upthe work o another tester, and with a little research understand the test inits entirety.