Software Quality Assurance (SQA)

-

Jaminan kualitas perangkat lunak (SQA) secara sistematis menemukan pola dan tindakan yang diperlukan untuk meningkatkan siklus pengembangan. Menemukan dan memperbaiki kesalahan pengkodean dapat membawa konsekuensi yang tidak diinginkan; adalah mungkin untuk memperbaiki satu hal, namun merusak fitur dan fungsi lainnya pada saat yang bersamaan.


SQA telah menjadi penting bagi pengembang sebagai sarana untuk menghindari kesalahan sebelum terjadi, menghemat waktu dan biaya pengembangan. Bahkan dengan proses SQA di tempat, pembaruan perangkat lunak dapat merusak fitur lain dan menyebabkan cacat -- umumnya dikenal sebagai bug .


Ada banyak strategi SQA. Misalnya, Integrasi Model Kematangan Kemampuan ( CMMI ) adalah model SQA yang berfokus pada peningkatan kinerja. CMMI bekerja dengan memberi peringkat tingkat kematangan area dalam suatu organisasi, dan mengidentifikasi pengoptimalan yang dapat digunakan untuk perbaikan. Tingkat peringkat berkisar dari tidak terorganisir hingga sepenuhnya optimal.


Metodologi pengembangan perangkat lunak telah berkembang dari waktu ke waktu yang mengandalkan SQA, seperti Waterfall, Agile dan Scrum. Setiap proses pengembangan berupaya mengoptimalkan efisiensi kerja.

  • Waterfall adalah pendekatan linier tradisional untuk pengembangan perangkat lunak. Ini adalah proses langkah-demi-langkah yang biasanya melibatkan pengumpulan persyaratan, memformalkan desain, mengimplementasikan kode, pengujian kode dan perbaikan dan rilis. Hal ini sering dianggap terlalu lambat, itulah sebabnya metode pengembangan alternatif dibangun.
  • Agile adalah metodologi pengembangan perangkat lunak berorientasi tim di mana setiap langkah dalam proses kerja didekati sebagai sprint. Pengembangan perangkat lunak tangkas sangat adaptif, tetapi kurang dapat diprediksi karena ruang lingkup proyek dapat dengan mudah berubah.
  • Scrum adalah kombinasi dari kedua proses di mana pengembang dibagi menjadi beberapa tim untuk menangani tugas-tugas tertentu, dan setiap tugas dipisahkan menjadi beberapa sprint.


Untuk menerapkan sistem QA, pertama-tama tetapkan tujuan untuk standar. Pertimbangkan keuntungan dan pengorbanan dari setiap pendekatan, seperti memaksimalkan kemanjuran, mengurangi biaya atau meminimalkan kesalahan. Manajemen harus bersedia menerapkan perubahan proses dan bekerja sama untuk mendukung sistem QA dan menetapkan standar kualitas. 

Comments

Post a Comment

Popular posts from this blog

Agile v Waterfall - Which Is The More Risky?

-
  I still find it strange that companies unfamiliar with Agile automatically view it as being a methodology that pays no heed to process or ensuring quality of output. From my experience the quality is actually a lot better, the timescales set are achieved more readily and everyone involved has a much greater understanding of the product and its development status at any one time. At present I´m working on a project where I´ve had to split the test team into two due to several companies working to build a complex product together. One team is performing agile QA in a sprint team, the other is working ´the old way´. It´s very interesting to note that all the worry and uncertainty is coming from the team working with the traditional model due to the fact that timeframes having been guesstimated months ago about environments, data and functionality that no-one knew about then. As time marches on we appear to be spending more time in meetings discussing what we once thought was gospel,...
Read more

What are the Educational Requirements and How to train for the job of Quality Assurance?

-
  The position of a quality assurance job requires a certain set of educational qualifications which would help the professional to carry out the technical and administrative operations given to him as part of his job role in the organization. Following are the educational requirements to obtain a post in the quality assurance job field: Educational Requirements: The minimum educational requirement to enter into the field of quality assurance is a bachelor’s degree in the field of computer science any other related field. This study must include subjects of Java, C++, and Python etc. A further master’s degree in the field of business administration majoring in any of the related subjects would prove beneficial in acquiring a post in the quality assurance job. However, the educational requirements differ with industry. Like for example, a candidate who wants to work in the quality assurance department in the aviation industry would require a high school diploma combined with an aero...
Read more

To Assume is To Doubt - Eliminating Doubt to Ensure Quality

-
To Assume is To Doubt - Eliminating Doubt to Ensure Quality  Recently I was reflecting on the many different occasions on projects where I’d witnessed assumptions being made regarding test and project strategies as an acceptable practice. Situations such as the following :- 1) Maintaining test environments with unmonitored and, as a result, unknown and unrepeatable data, under the assumption that it is the functionality of the application that is important and the data it is fed is immaterial. 2) Testing end user sessions on a different platform, under the assumption that there will be very little difference in functionality (”Firefox on Ubuntu is the same as on Windows”) 3) Pointing new-starters to a wiki-page, under the assumption that anything else they need to know shall be relayed by ‘asking around’ 4) Arranging development teams such that each person only has deep understanding of one part of the system, under the assumption that all issues that arise will be easily solved by...
Read more