Track C: Test Management


Myroslav Palenychka

Myroslav Palenychka

CURRÍCULUM VITAE

Myroslav has joined Software Verification Team for Rational Modeling tools at IBM in January 2008. Prior to IBM, he worked as a Software Designer at Nortel after graduation from Carleton University in Ottawa, Canada with a Bachelor’s degree in Computer Science, Software Engineering Stream.

His fourth year honours project at university resulted in co-authoring a research paper titled “SMART: A Web-Based, Ontology-Driven, Semantic Web Query Answering Application” published in the 6th International Semantic Web Conference in Korea, summer 2007. While at university he has done two full-time work terms with the same team at IBM. Also Myroslav had various Software Development co-op positions at National Research Council of Canada, and Nortel. He has done presentations to different audience while in school and work and is confident in presenting to broad audience. Currently Myroslav is finishing his Master’s of Science in e-Business Technologies degree part-time at University of Ottawa, Canada.

Myroslav strengths are in UML modeling of software, teamwork process, and software verification testing.


ABSTRACT

Vertical approach in managing testing of software projects

Today’s software systems such as Enterprise Resource Planning and Networking solutions are very complex. Those systems often involve: large combinations of inter-dependent features, support for different platforms, and integration with other products to form end-to-end solutions. A typical software project involves stakeholders with the following roles: business analyst, project manager, software developer, and software verification and validation engineer. Projects are evaluated by three parameters: cost, quality and time. In order to improve cost, companies distribute project teams across different locations and time zones. There are many variations of how a team can be distributed. A common example is that business analysts are located close to clients whereas development teams can be split in cost efficient places such as Eastern Europe, India or China. This adds additional complexity to software projects where quality and time parameters can suffer due to poor communication between team members and time zone differences.

Back to the Programme