
 |  | What are the quality process tools & methodologies used? |
|  | Requirements Analysis & documentation Requisite Pro.
Database design - ER Win, MS - Visio.
Testing - Defect Tracking System
Configuration Management - Visual Source Safe (VSS), (Should the customer have any specific needs whatsoever, we could make use of any specified tools and methodologies) |
|  |  |  |
| |
 |  | What are the software development estimation techniques used? | |  | Function Point Analysis. Lines of Code (LOC). Requirement Study (RS) Effort Method. Stage - Percentage Matrix. | |  |  |  | |
 |  | What are the software development Methodologies used? | |  | Advanced V Model is the basis SDLC model. SDLC is tailored based on Project Size & Technology. SDLC's are tailored from: Waterfall Model. Prototype Model. Spiral Model. RAD Model etc. | |  |  |  | | |
 |  | What are the software development testing techniques? | |  | Boundary Value Analysis Loop Test Conditional Checking | |  |  |  | |
 |  | How does Mindscape adopt customer's quality standards? | |  | It is a four-step process Customer quality standards are studied and reviewed by Project Manager and Quality Department.  Management Representative for Quality (MRQ) approves the deviation from Mindscape's quality process. The Customer standards to be followed are documented in the Project Plan, which is reviewed by Project Manager, Quality Department and approved by Management Representative for Quality (MRQ).  Project Team is trained on the Customer's quality standards. | |  |  |  | | |
 |  | What are the software development project metrics deployed by Mindscape? | |  | Customer Satisfaction Project Deliverables - Planned Vs. Actual Defects - Acceptance Testing Defect Leakage Index Test Efficiency Effort Work Product Audit - Planned Vs. Actual Defects · Review - Document , Code. Testing - Unit, Integration, System. Baseline Changes | |  |  |  | |
 |  | What are the risk management methodologies you deploy? | |  | Our risk management planning involves 3 stages and confirms to PMI's risk management methodology. The process tries to quantify the impact of each risk factor and creates risk management plans, contingency plans, parallel planning and reserves and even up to contractual obligations themselves Risk Identification Determining which risks are likely to affect Project (Could be opportunities or threats) Tools: Flowcharting, Interviews, checklists Outputs: Sources of risks (Part of PP) Potential risk Events (contains probability and frequency) Risk Symptoms Risk Quantification Evaluation of risks, risk weightage Tools: Expected Monetary Value (EMV), Decision Tree Outputs: Opportunities: Pursue/Ignore? Threats: accept/respond? Depends on periodic EMV value [EMV = Risk Event Probability * Risk Event Value] Risk Response Development Enhancement steps for opportunities Responses to threats Avoidance: By eliminating the cause Mitigation: Reducing the EMV Acceptance: Contingency Plan Tools: Contingency Planning, Alternative Strategies, Insurance, etc Output: Risk Management Plan, Contingency Plans, Reserves, Contractual agreements | |  |  |  | | |
 |  | What is the percentage of cost that your quality processes would have on the project cost? | |  | Needless to say, quality is very important for any project. It has been an area of thrust for us ever since inception and has been well received by our customers. The cost overhead that quality systems add to our developmental process is approximately about 10-15 percent. | |  |  |  | |