About the Talk (slides)

Many organizations today, not only software companies, but also organizations such as banks, insurance companies, manufacturing organizations, etc., recognize that the software and system engineering has become an important part of achieving their business goals.

SPI (Software Process Improvement) methodology has its own history and is based on the basic concepts of process improvements developed by Walter Shewhart, W. Edwards Deming, Philip Crosby, Joseph Juran, Watts Humphrey.

According to the objectives of SPI, the process must be predictable, under statistical control and should be continuously improved. The life cycle of process improvement includes assessment of the current level of process capability, determining the target level of process capability, prioritization of the process improvement, as well as the implementation, monitoring and evaluation of these improvements.

CMMI (Capability Maturity Model Integration) and SPICE (Software Process Improvement and Capability Determination) (ISO/IEC 15504-5:2006) are important SPI models in today’s practice. Concept of these models are based on the two dimensional reference model for describing processes and process capability used in a process assessment. The reference model defines a set of processes (key process areas), defined in terms of their domain, purpose, outcomes and a framework for evaluating the capability of the processes through capability levels (0=incomplete; 1=performed; 2=managed; 3=defined;4=quant.managed; 5=optimizing).

Process Assessment Model (PAM) must be compatible with this reference model including assessment indicators. Accordingly, the process assessment requires the documented process for conducting assessment, the compatible assessment model(s) as well as the supporting assessment tools and adequate competence of the assessors.

The benefits arising from the use of these models include:

• for acquirers: an ability to determine the capability of a supplier’s software processes;
• for suppliers: an ability to determine the capability of their own software processes and an ability to define areas and priorities for software process improvement;
• for assessors: a framework for conducting assessments.

The benefits of SPI are numerous. Major benefits include increased customer satisfaction, productivity,quality, cost savings, and cycle time reduction. SPI methodology is developed in order to achieve these goals and features not only for the production of software, but also other disciplines (complex IT systems, hardware systems, IT services, etc.). SPI models can be combined with other methods and standards such as Six Sigma, statistical process control, ISO/IEC 9000; ITIL, ISO/IEC 20000, ISO/IEC 12207, ISO/IEC 15288, etc.

About the Speaker

Melita Kozina is an assistant professor at the Faculty of Organization and Informatics, Croatia; Titles: Ph.D in information sciences from the University of Zagreb, Faculty of Organization and Informatics, Croatia. Her field of research interests include : IT Management, Business Process Management, Quality Management, SPI (Software Process Improvement), ITSM (IT Service Management). She is working on the scientific project titled: developing the ICT management method (project code: 016-0161199-1718; The Ministry of Science, Education and Sports in the Republic of Croatia).

Links

foi.hr/djelatnici/melita.kozina

About the Talk

Forms are still one of the main user interface paradigms used today. They are most prominent on the web and lately with mobile devices. However, many desktop-based apps still rely heavily on forms.

In this presentation I will go through best practices for forms experience from the perspective of usability testing, customer support, e-commerce and overall user experience.

This is going to be highly practical presentation with brief introduction followed by numerous best forms design practices.

About the Speaker (from linkedin.com/in/vibor)

Skilled UX design and development professional with strong development and project management background. Top notch professional and experienced with Expression Studio (Blend, Web, Design, Encoder & Media) tools and technologies like WPF and Silverlight.

Highly skilled and experienced building and designing Windows Phone applications. Supporting partner for the official phone launch in 2010.

Passionate about all things user experience, usability, rapid and hi-fi prototyping and information architecture. Especially skilled with analytics and SEO (thanks to physics / science background).

Active blogger and speaker.

Book author – first book about building great UI and UX for Silverlight. Title: Silverlight 4 User Interface Cookbook (PACKT Publishing, Aug 2010)

Links

UXPassion.com
linkedin.com/in/vibor
twitter.com/viborc

About the Talk (slides)

Functional Testing is the process by which expected behavior of an application can be tested. Implementing functional test for your application early in the software development cycle speeds up development, improves quality and reduces risks towards the end of the cycle.
Most software undergo changes over a period of time. These changes may occur during the course of a single release, or across multiple releases. Any change to the software increases the chance of errors or bugs being introduced that breaks existing functionality. So we must test the software to ensure known existing behavior or functionality is not broken.
Writing web application tests by hand without tool support is exhausting and almost impossible at lager scale. Automating this task is both challenging, but when done right, very awarding. To test the Ericsson Mobile Health user interface we used Selenium, by which we create automatic tests and so ensure a quick and complete testing.
In this talk I want to present how we automated testing of EMH user interface, introduce the used tools, potential problems with automated testing and their possible solutions and show the benefits and goals achieved by this type of testing.

About the Speaker

Angelina Gavran is a fifth year student at the Faculty of Electrical Engineering and Computing in Zagreb, Croatia. She has participated in the Ericsson Nikola Tesla Summer Camp 2010 on projectEMH application testing. Since then she has worked on automatedtesting of the EMH user interface. She has been working for a year in T-HT company in Network Managementand Customer Service departmenton network Monitoring, detecting and removing failures. She is currently working on her graduation thesis, Stress testing of EMH application, in Ericsson Nikola Tesla Company.

About the Talk (slides)

As part of the round table this short talk will cover the used terminology and best practices of software verification and validation (V & V). Software V & V activities play an important role in the whole life cycle of a software product. The purpose of these activities is not just to “control” or “evaluate” the quality of the software throughout the life cycle. When properly planned and applied from the beginning, V & V will help to build quality into the software product and establish confidence that the product is fit for purpose.

Software verification is intended to confirm that design output conforms with design input requirements/specifications (i.e. are we building the product right?). Software validation is intended to develop a level of confidence that the software conforms with customer needs (i.e. are we building the right product?).

We will talk about the following V & V best practices: application of software V & V early in the software development process, appropriate selection of software V & V techniques, manual versus automated testing, proper documentation of software V & V activities including problem tracking, training of personnel on software V & V, setting up an effective testing team, and continuous process improvement. The participants will also gain a first-hand insight into the different approaches to integrate software V & V activities throughout the software life cycle.

About the Speaker

Nadica Hrgarek is a Software Quality Engineer at an innovative hearing implant company in Austria. Hrgarek received a B.Sc. and a M.Sc. in information sciences from the University of Zagreb, Faculty of Organization and Informatics, Croatia.

Her current research interests include quality management, process improvement, software process modeling, software metrics, and agile methodologies. She holds the ISO 9000 internal and lead auditor, ISTQB Certified Tester Full Advanced Level (Test Manager, Technical Tester and Functional Tester), IREB Certified Professional for Requirements Engineering and iSQI Certified Professional for Project Management Foundation Level certificates.

She is a member of the German association for software quality and training.

Links

linkedin.com/in/nhrgarek

About the Talk (slides)

Web browsers are some of the most complex pieces of software we have on our computers. From relatively sparse beginnings, the web has evolved to become one of the most sophisticated and widely-adapted technologies of our age. The challenges of establishing the web as the next application platform also poses new demands on quality assurance of the web stack; from the browser itself to the tools and testing strategies themselves.

In this talk I will introduce you to how web browsers actually work, and why testing them is hard. I will demonstrate some testing strategies we use, and also give a practical introduction to some of the tools we’ve written. The talk will give you a broad introduction to testing in a complex environment that should be applicable and useful also in other contexts. Finally, I will argue why emulating actual user behaviour is quintessential to the success of your testing, and conversely, why asking humans to do a machine’s job is a bad idea.

About the Speaker

Andreas Tolf Tolfsen does browser automation at Opera Software, where he is a contributor on the OperaWatir and OperaDriver projects. He has a background as a browser tester and web developer, and has previously given talks on browser automation with WebDriver and Watir at various conferences in San Francisco and Oslo. He holds a BA in Musicology from the University of Oslo.

Links

home.e-tjenesten.org/~ato
twitter.com/tolfsen
linkedin.com/pub/andreas-tolf-tolfsen

About the Talk (slides)

‘How can you improve if you don’t measure?’ – it is heard more and more this days. Running ICT in efficient way requires well designed service processes and supporting organization. Sometimes reinventing the wheel is not an option. It takes both – money and time. What is the best practice when we speak about IT Service Management. Worldwide industry recognize it within IT Service Management Forum or better known within „IT Infrastructure Library“, ITIL for short.

What is ITIL? How it is related with Good Testing Practice? What Service Management processes support testing and validation activities? This are only a few questions that will be answered during this presentation.

About the Speaker

William Bello, achieved B. Sc. of Applied Mathematics Science at University of Zagreb 1981, run IT department at Pliva as member of the Board of directors, designed information system for INA-OKI, 1993 founded IT networking company, run Network Managed Services operations center and today is senior business consultant specialized for IT service management process implementation and optimization. Has broad knowledge of business process IT service requirements and IT technology.

Links

linkedin.com/pub/william-bello

A few people from FOI (Fakultet organizacije i informatike) have proposed a round table titled Importance of quality (systems) for the IT profession:

• prof. dr. sc. Zdravko Krakar: Quality and maturity of the IT profession, and different IT views (IT as practice; IT in business systems; IT in Croatia) – 30 minutes
• doc. dr. sc. Melita Kozina: SPI (Software Process Improvement) in software development process – 20 minutes
• doc. dr. sc. Valentina Kirinić: Software quality norms – 20 minutes
• mr. sc. Nadica Hrgarek: Software verification and validation best practices – 20 minutes
• prof. dr. sc. Zdravko Krakar (chair): Discussion – 30 minutes

More information on speakers and topics coming soon.

Update: Slides are available.

About the Talk

Important part of non-functional testing is security for sure. We will start by writing security related non-functional application requirements and answer the question how to write security related requirements that make sense.

The second question that we will answer is how to help developers in fulfilling those requirements, and how to later check if the requirements are fulfilled. We will cover everything form white box to black box testing, including penetration testing, and code inspection/review. Of course, we will cover the most important free documents and tools available that can help you define and test security requirements.

About the Speaker

Vlatko Košturjak works as a information security consultant for Europe, Middle East and Africa (EMEA) where he helps clients in reaching desired security level. Vlatko specialized and certified in security and “ethical hacking” or penetration testing, business continuity, increasing information systems security levels, and development and monitoring ISMS according to international standards including ISO/IEC 27001. He is also authorized by PCI SSC to perform PCI QSA security audits of organizations processing credit card information conforming to PCI DSS.

Vlatko have experience in security for more than a decade. He is author of many papers and tools in security field, active member of OWASP (open global organization for application security) and author of OWASP projects. Vlatko also actively develops and contributes to open source software. For example, Snort, Nessus, nmap, w3af, Metasploit and OpenVAS contain code written by his hands. And for those believing only in certificates, here is a few abbreviations:
CISSP, CISA, C|EH, MBCI, Security+…

Links

twitter.com/k0st
linkedin.com/in/vlatko