Yazılım Testi ve Test Süreçleri

testingKaliteli yazılımlar, kabul edilebilir düzeyde hatasız, planlanan bütçe ile zamanında bitirilip dağıtılabilen, gereksinimleri ve/veya beklentileri karşılayabilen ve sürdürülebilir özelliklere sahip yazılımlardır. Ancak, kalite terimi kişilere göre oldukça değişebilen bir terim olup müşterisinin kim olduğuna ve tasarımda hedeflenen unsurlara bağlı olarak farklılıklar gösterebilmektedir. Doğal olarak, her kişinin kalite hakkında bireysel eğilimleri veya tercihleri söz konusu olmasına karşın kaliteyi ortaya koyan nesnel yöntemler yansız değerlendirmeleri olanaklı kılmaktadır.

Test, bir sistemi manuel veya otomatik yollarla deneyerek veya değerlendirerek, belirlenmiş gereksinimleri karşıladığının doğrulanması veya beklenen ile gözlenen sonuçlar arasındaki farkların belirlenmesi sürecidir. Yazılım testi ise bir yazılımın sonsuz sayıdaki çalışma alanından, sınırlı sayıda ve uygun şekilde seçilmiş testler ile beklenen davranışlarını karşılamaya yönelik, dinamik olarak yapılan doğrulama faaliyetlerini kapsamaktadır.
Yazının devamını okumak için tıklayın..

2014 Türkiye Yazılım Geliştiricileri Anketi Sonuçları

Ankete katılan 1387 kişinin yalnızca yüzde 6‘sı, yani 88’i, cinsiyetini kadın olarak işaretlerken geçen seneyle kıyasladığımızda yüzde 2’lik bir artıştan söz etmek mümkün.

Diğer yandan yazılım geliştiricilerin yaş ortalaması 26,6 olurken lise ya da üniversite eğitimini bilgisayar bilimleriyle alakalı bir bölümde yapıyor olan/yapan kişilerin oranıysa yüzde 70. Bir başka deyişle yazılımcıların üçte birinin ‘alaylı’ olduğunu görüyoruz ki genel kanının üzerinde bir oran.

Eğitim durumu ve çalışılan şirket tipi gibi detaylarla beraber kişisel bilgilerin tamamına aşağıdaki görselden ulaşabilirsiniz.

Bir hosting macerası ve mutlu son

Boş zamanlarımda hobi olarak kod yazıyorum, böylece hem bir uğraşım oluyor, hem de yeni teknolojileri takip etme şansı buluyorum. Geçenlerde ASP.Net MVC framework denemeleri yaparken tamamladığım basit bir web sitesi projem vardı; aşağıdaki yazı, bu web sitesini barındırabileceğim bir hosting şirketi ararken yaşadığım gerçek bir hikayedir.

Web sitesine ait altyapı : ASP.Net 4.5, MVC 5, MS SQL Server

İçerik : Microsoft’un VS Express 2013 içerisinde gelen identity framework altyapısını kullanan ve çok fazla kodsal değişiklik içermeyen basit bir resim listeleme sitesi.

Bildiğiniz gibi MVC 5 yeni bir teknoloji, dolayısıya bu desteği veren hosting şirketi bulmak epey zor. Özellikle sunucuları Türkiye’de olan, kurumsal bir hosting firması istediğim için alternatifler çok fazla değildi, bir de yeni trend olan “sınırsız hosting” istediğim için, sayı neredeyse sıfıra yaklaşmıştı.

Firmalarla ilgili yazdıklarım subjektif yorum içermemektedir ve yalnızca yaşanılan deneyimlere dayanmaktadır.

Yazının devamını okumak için tıklayın..

SOA? ESB? What is all this?

Lots of nice articles have been published on the net on both Service Oriented Architecture (SOA) and Enterprise Server Bus (ESB). This topic is being discussed quite heavily for last few years but started gaining weight as ESBs started getting more and more matured. To start this series, I am planning to put together information which I found to be very useful when I started working on this project. Some of this information has come from other blogs, company websites (JBOSS, IBM, Cape Clear, BEA, Microsoft etc.). I am planning to add my experiences when we carried out performance analysis of one of the ESB implementations.

A Day in the life of an Enterprise Architect

Enterprise architecture has grown from being just a set of small pilots to being a fully sponsored and supported initiative within enterprises. With the growing demands to reduce costs, increase agility, and standardize IT environments, there has been a surge of enterprise architecture activity. According to Gartner and the MIT institute the growing complexities that span across process, information and software are among the three top CIO concerns. Additional pressures come from regulatory bodies that impose compliance guidelines on the industry (such as the Clinger-Cohen Act of 1996 or FFIEC Guidance). Compliance has been a catalyst for the formation of an enterprise architecture practice. This article will walk you through the daily challenges that an enterprise architect faces. By doing so, we hope to provide a unique perspective on this growing role in the IT industry.

A Comparison of the Top Four Enterprise-Architecture Methodologies

Twenty years ago, a new field was born that soon came to be known as enterprise architecture. The field initially began to address two problems:

  • System complexity—Organizations were spending more and more money building IT systems; and
  • Poor business alignment—Organizations were finding it more and more difficult to keep those increasingly expensive IT systems aligned with business need.

The bottom line: more cost, less value. These problems, first recognized 20 years ago, have today reached a crisis point. The cost and complexity of IT systems have exponentially increased, while the chances of deriving real value from those systems have dramatically decreased.

Today’s bottom line: even more cost, even less value. Large organizations can no longer afford to ignore these problems. The field of enterprise architecture that 20 years ago seemed quaintly quixotic today seems powerfully prophetic.

Many enterprise-architectural methodologies have come and gone in the last 20 years. At this point, perhaps 90 percent of the field use one of these four methodologies:

  • The Zachman Framework for Enterprise Architectures—Although self-described as a framework, is actually more accurately defined as a taxonomy
  • The Open Group Architectural Framework (TOGAF)—Although called a framework, is actually more accurately defined as a process
  • The Federal Enterprise Architecture—Can be viewed as either an implemented enterprise architecture or a proscriptive methodology for creating an enterprise architecture
  • The Gartner Methodology—Can be best described as an enterprise architectural practice

Three big reasons CRM initiatives fail

CRM failure rates have remained high during the last ten years, indicating that many organizations don’t receive full benefit from their CRM initiatives. Let’s examine important reasons for this unfortunate situation.

Although relatively few projects become complete write-offs, partial failure is common. Most often, a project delivers some expected benefit, but still leaves users unsatisfied and business sponsors wondering what went wrong.

This list describes three major pitfalls that plague many CRM initiatives. While not a comprehensive inventory of potential problems, many projects succumb to these big causes of failure.

Finding the Value in SOA

Confronted with the age old problems of agility and complexity, today’s CIOs are under more pressure than ever to improve the strategic value of IT to the business. At best, these challenges have increased costs, limited innovation and increased risk. At worst, they have reduced IT’s ability to respond to changing business needs in a timely fashion.

Yet, changes for business and IT are continuing to occur at an ever-increasing pace. To keep up, enterprises need to adopt an agile, flexible architecture style with a proven strategic approach to delivering IT to the business.

Enterprise Architect vs Solution Architect

What exactly is an Enterprise Architect versus a Solution Architect? I’d like to chat about the difference because I’m not confident everyone understands this well.

It’s actually quite simple. I propose that a Solution Architect is a project team role that is responsible for the system quality of the solution being delivered to the business. I also propose that an Enterprise Architect is a planning role that is responsible for identifying the future state of an organization’s IT environment and engage wherever and whomever necessary to help guide project team’s to deliver toward it. There are formal definitions out there but I thought I’d simplify it for the purposes of this blog post.

What is Kanban?

Kanban is a new technique for managing a software development process in a highly efficient way. Kanban underpins Toyota’s “just-in-time” (JIT) production system. Although producing software is a creative activity and therefore different to mass-producing cars, the underlying mechanism for managing the production line can still be applied.