Communiquez avec les autres et partagez vos connaissances professionnelles

Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.

Suivre

In your experience, what are the most common causes of software quality problems? How should teams proactively mitigate these risks?

user-image
Question ajoutée par Salauddin Mohammad , Sr. Manager, Software Development , Aspen Technology Inc
Date de publication: 2014/07/16
Jose Miguel Lucas Martins
par Jose Miguel Lucas Martins , IT Director - Robotic Process Automation (RPA) , Novo Banco

1. Lack of comunication between stakeholders

2. Bad requirement specification

3. Bad specification of acceptance criteria

 

Manmohan Singh jhunjhun
par Manmohan Singh jhunjhun , Software Engineer , G D Udyog

The main cause are at the time of selecting the technology whenever you choose a wrong technology for a wrong domain later on it causes the serious problems while in SDLC process...Just imagine your small business organization doesn't need a high fi software technology and you are implementing a large scale usable technology. How can you get the support from the Developers.

 

Gayasuddin Mohammed
par Gayasuddin Mohammed , Advocate , Practicing Law before High Court at Hyderabad

Requirements are not gathered correctly and the software was developed without following the due procedure of the SDLC, etc.

Can rectify many problems by verifying business requirements and specifications and have clear understanding about the requirements by interviewing and confirming the requirements gathered from the end user. Also doing code review at development stage. Unit test and proper flows of testing is ensured in testing phase. Finally integration testing is also very important where your full systems integration testing will be done carefully for the implementation of the system for live in production environment.

Ali Sayam
par Ali Sayam , Senior Software Quality Assurance Engineer , Punjab Information Technology Board

1- Lack of communication between stakeholders

2. Bad requirement specification

3. No proper unit testing at developer's level

4- No proper execution of test cases.

These are actually based on requirement elicitation. If there would be lack of communication with clients/stakeholders then there will be  strong chances of occurring software quality problems.

 

Abd El Rahman Badwy
par Abd El Rahman Badwy , Software Quality Control Engineer , taya it

Bad requirement specification

Kapil Jayant Sathe
par Kapil Jayant Sathe , Sr. Manager.(Customer Support) , Progen ERP Systems (P) Ltd

Not getting properly communicated about the requirement. If this is tackled properly, there would be less quality problems

Avez-vous besoin d'aide pour créer un CV ayant les mots-clés recherchés par les employeurs?