-
Ukraine
-
Kiev
-
Kharkiv
-
Dnipropetrovsk
-
Donetsk
-
Lviv
Master Class Dmitry Efimenko "Method" of objectives "in risk management software"
26 February 2012
Ukraine Kiev
Date: February 26, 2012
Place: Kiev, 40th anniversary of the October 70, m "Goloseevskaya" hotel "Mir", a large conference room.
Dmitry Efimenko, the head office Unitecsys (Uniteller) in Kharkov, Ukraine. In software development for over 13 years. For a long time worked in the custom design - from developer to technical director and head direction, to implement different methodologies, formed teams and worked on projects of all sizes, in different regions and with varying degrees of success :)
Since the year 2008 - in product development in the areas of Internet acquiring (payment by credit card over the Internet) and self (payment by bank cards in terminals and kiosks, self).
In his spare time, work and family seminars and workshops devoted to the requirements, design, testing, risk management and actively participates in conferences.
Purpose:
- To convey their attitudes and practices of software development through the solution of practical problems
- To compete in the management requirements and risk management, design and programming
Features: Master Class is designed for analysts, architects and developers, and consists of theoretical and practical parts. The practical part includes a competition for fans of software development (analysis - design - implementation - testing - delivery). If you do not want to just be a spectator at the implementation stage - bring a laptop with a familiar development environment and an environment for the language that you like :)
The plan of the master class
The theoretical part:
- Agree on the terminology and concepts
- Problems with the requirements of
- Review of practice coping with the challenges of working with the requirements in the various methodologies
- Basic principles of the method "on purpose" in the management of requirements and design and its rationale
- Translation of the principles of the method "on purpose" at all stages of software
- Analysis of strengths and weaknesses of the method
Practical part:
will
- To apply the method of "the goals"
- To determine the behavior scenarios and reveal the risks
- To engage in an abstract design
- Implementation of the design in your favorite programming language
- To write and debug code
- Justify and apply various engineering practices
- Designed to test
- Present the application
- Summarize and identify the winners
More: www.smartme.com.ua / ...workshop-riski
