Saturday, July 7, 2012
How is Configuration management (CM) process applied in software testing?
Posted by
Sunflower
at
7/07/2012 01:27:00 PM
0
comments
Labels: Application, Attributes, Changes, Configuration, Configuration management, Control, Crisis, Information, Network, Quality, Software configuration management, software engineering, Software System, Testing, Tests
|
| Subscribe by Email |
|
Monday, June 25, 2012
What is the relation between installation testing and configuration management?
- Upgrading of installation and
un- installation process.
- Partial installation and un-
installation process.
- Full installation and un-
installation process.
What is Configuration Management?
- Maintaining software trace-ability throughout the software development life cycle.
- Maintaining software
integrity throughout the software development life cycle.
Relation between Installation Testing and Configuration Management
Posted by
Sunflower
at
6/25/2012 11:56:00 PM
0
comments
Labels: Application, Attributes, Configuration, Configuration management, Customers, Focus, Functionality, Installation, Installation testing, Quality, Software, software engineering, Software System, Test engineer
|
| Subscribe by Email |
|
Monday, July 26, 2010
High-level Best Practice One(1) in Software Configuration Management
Software configuration management (SCM) is a set of activities that are designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling changes that are imposed, and auditing and reporting on the changes that are made.
Software Configuration Management Best Practices are the techniques, policies and procedures for ensuring the integrity, reliability and reproducibility of developing software products.
When implementing SCM tools and processes, you must define what practices and policies to employ to avoid common configuration problems and maximize team productivity. There are six areas of SCM deployment, and some coarse-grained
best practices within each of those areas.
- Workspaces: It is the area where the engineers edit source files, build the software components they’re working on, and test and debug what they have built. The best practices for workspaces include:
. Don’t share workspaces.
· Don’t work outside of managed workspaces.
· Don’t use jello views: A file in your workspace should not change unless you
explicitly cause the change. A “jello view” is a workspace where file changes are
caused by external events beyond your control.
· Stay in sync with the code line.
· Check in often: Integrating your development work with other peoples’ work also
requires you to check in your changes as soon as they are ready.
Posted by
Sunflower
at
7/26/2010 04:50:00 PM
0
comments
Labels: Areas, Configuration management, High-level, Management, Practices, Processes, SCM, Software configuration management, Tools, Workspaces
|
| Subscribe by Email |
|
Monday, June 28, 2010
How are testing tools categorized ? - Part II
Embedded Software Testing Tools :
It is a very challenging task to test embedded software as the timing requirements for these applications are very stringent. The code has to be optimized so that it occupies the minimum memory. IBM Rational Test Real Time is the widely used test tool in this category.
Network Protocol Testing Tools :
Testing networking and communication software has attained a lot of importance in recent years as computer networks are becoming widespread. There are number of tools available for testing networking and communication protocols. ANVL(Automated Network Validation Library) is to test routers and other networking products. Agilent Technologies, Rhode and Schwartz etc supply protocol analyzers which generate the necessary protocols based on international standards such as ITU-T standards.
Configuration Management/Bug Tracking Tools
Configuration Management is a very important process. When test engineers report bugs, the managers have to track these bugs and ensure that all the bugs are removed. Bugzilla is an open source defect tracking system. Samba's Jitterbug is a freeware defect tracking system. IBM Rational Software's Clear DDTS is a change request management software. GNU's GNATS is a freeware bug tracking and change management software.
Software Testing Management Tools
These tools help in managing process oriented software testing. Using these tools, the QA manager can create a formal test plan, allocate resources, schedule unattended testing, track the status etc. AutoTester's AutoAdviser, Compuware's QA Director are such tools.
Posted by
Sunflower
at
6/28/2010 01:23:00 PM
0
comments
Labels: Automated Testing, Automation, Bugs, Categories, Configuration management, Embedded, Manual Testing, Network, Protocols, Software, software engineering, Testing tools, Tools
|
| Subscribe by Email |
|
Tuesday, April 27, 2010
Configuration Management (CM) and Decision Analysis and Resolution (DAR) process area in CMMi
The purpose of Configuration Management (CM) is to establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits. It is a support process area at Maturity Level 2.
Configuration management is normally not used or managed within the development process for a Level 1 organization.
Specific Practices by Goal
SG 1 Establish Baselines
- SP 1.1 Identify Configuration Items.
- SP 1.2 Establish a Configuration Management System.
- SP 1.3 Create or Release Baselines.
SG 2 Track and Control Changes
- SP 2.1 Track Change Requests.
- SP 2.2 Control Configuration Items.
SG 3 Establish Integrity
- SP 3.1 Establish Configuration Management Records.
- SP 3.2 Perform Configuration Audits.
Decision Analysis and Resolution (DAR)
It is a support process area at Maturity Level 3. The purpose of Decision Analysis and Resolution (DAR) is to analyze possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria.
Specific Practices by Goal
SG 1 Evaluate Alternatives
- SP 1.1 Establish Guidelines for Decision Analysis.
- SP 1.2 Establish Evaluation Criteria.
- SP 1.3 Identify Alternative Solutions.
- SP 1.4 Select Evaluation Methods.
- SP 1.5 Evaluate Alternatives.
- SP 1.6 Select Solutions.
Note : SP stands for Specific Practice and SG stands for Specific Goal.
Posted by
Sunflower
at
4/27/2010 11:02:00 AM
0
comments
Labels: Capability Maturity Model, CMM, CMMi, Configuration management, DAR, Decision Analysis and Resolution, Maturity levels, Models, process areas, Processes, Purpose, Specific goals, Specific practices
|
| Subscribe by Email |
|