Software Development Best Practices Moscow 2007 (SDBP Moscow 2007)

Venue: Radisson SAS Slavianskaia Hotel

Location: Moscow, Russia

Event Date/Time: Apr 03, 2007 End Date/Time: Apr 04, 2007
Registration Date: Apr 01, 2007
Early Registration Date: Dec 31, 2006
Abstract Submission Date: Nov 30, 2006
Paper Submission Date: Nov 30, 2006
Report as Spam


Presented by Dr. Dobb’s and CMP Technology in conjunction with Fort-Ross and RUSSOFT Association, SD Best Practices Moscow will be held on April 3-4, 2007, and address the unique regional needs of software development professionals living and working in Russia, featuring content and contributions from the industry’s most recognized and respected luminaries and vendors.

SD Best Practices Moscow will offer comprehensive training and discussion on essential software development methodologies, ideas, management issues, tools and technologies related to the entire application development lifecycle—from architecture and design, to development and deployment, to project management, to product marketing and sales. The Conference Program Committee invites all interested and qualified parties to submit speaking proposals for one or both of the following content tracks:

Track 1: Design, Build, Test, Deploy
Track 2: People, Project and Teams

Speaker benefits
Conference structure
Selection guidelines
Selection criteria
Deadlines and requirements
Suggested speaking themes/topics
All speakers will get VIP Conference Badge that provides access to all special events at the conference.
All submitted papers will be published at the web site
All accepted papers will be published on the Dr.Dobb’s Journal web site ( ) in a special section devoted to SD Best Practices Moscow 2007.
The Program Committee will award a ‘Best Paper’ from the accepted pool of submissions. This paper will be recognized in the print version of Dr. Dobb’s Journal after the conference.

All proposals must be sent to the Program Committee Secretary ( by November 30, 2006!

During the 2-day conference, all topics will be addressed in 60 or 90-minute classes, case studies, roundtables or panel discussions.
All proposed classes should be 60 or 90 minutes in length, including time for Question & Answer.
Case Studies
Whether success stories or a learning experience, share your knowledge from the front-line during these 90-minute sessions. Note: Case Studies are *not* vendor presentations of software products or processes.
Roundtables are focused discussions on various topics, allowing for active discussion among participants after a brief introduction by the roundtable facilitator.
Panels, as opposed to roundtables, are more structured with less audience participation. Debate among panelists is welcome in this format and audience questions should be accounted for. Issues should be presented and placed in their proper historical context with an eye towards its future resolution.

Dr. Dobb's has a strong reputation for offering the highest quality technical training and content. The Program Committee is looking for:

Technically challenging presentations that will provide a better understanding of processes and technologies.
Topics that will appeal to a broad range of attendees.
Practical information that can be immediately put to use back in the work place.
Topics that stress processes and methodologies rather than products.
How-to classes to ease the development process.
Speakers with a desire to teach and share their technical expertise.
Working developers with several years of practical development experience.
Speakers with strong organizational and speaking skills and good presentation materials.

Each submission will be judged on the speaker’s credentials, as well as the proposal’s concept, depth and organization.

Concept: This is the basic idea of your proposal. Is it interesting? Is it relevant? Will it be beneficial for software development professionals?
Depth: Has the idea of the proposal been considered and fleshed out? To what extent will the audience gain insight? The more in-depth and concise the better.
Organization: Are your ideas organized in a fashion conducive to present in front of an audience? Will the Program Committee follow what you are trying to say?
Credentials: How do your credentials qualify you to speak on the topic you have proposed?

All proposals should be sent to the Program Committee Secretary ( by November 30, 2006.

The Program Committee Secretary will reply to you confirming receipt of your submission AND will contact you with a decision regarding your proposal no later than December 25, 2006.

Please be sure that each proposal submission includes:
Name of Speaker
Bio of Speaker (1000 characters + photo)
Track that you’re applying for: Design, Build, Test, Deploy or People, Projects & Teams
Title of presentation
Short abstract of the presentation (250-500 characters)

All abstracts should be sent in English. The presentation at the conference can be conducted in English or Russian, but all slides and written materials should be presented in English. Simultaneous translation will be available at the conference.

The chosen tracks at SD Best Practices Moscow 2007 reflect the Program Committee's desire to focus on both technical (Track 1: Design, Build, Test, Deploy) and management (Track 2: People, Projects & Teams) issues related to software development. Each track will address and bring to light the most relevant and timely issues affecting software development now and in the near future. The following list of speaking topics/themes/ideas may help you craft your proposal:
Java Programming
J2EE and the intricacies of the language, in particular, the powerful features and libraries that set Java apart from its predecessors
Modeling & Design
Information and best practices about UML, domain-specific models, model-driven architecture (MDA), agile modeling, business-process modeling, inclusive modeling, domain-driven design, software architecture, design patterns, security modeling and/or database design
.NET Development
+ C# 2.0/C# 3.0
+ .NET Framework
+ .NET Security
+ .NET System Programming
+ Windows Forms and Smart Clients
+ Visual Basic 2.0/3.0
+ Visual Studio codename "Orcas"
+ Visual Studio 2005
+ Windows Communication Foundation (WCF)
+ Windows Presentation Foundation (WPF)
+ Window Workflow Foundation (WF)
+ Windows CardSpace (WCS)
People, Process & Methods
The techniques, tools and group interactions that make for successful software development vary greatly, depending on the domain, technology and team involved.
Requirements & Analysis
Collaborative requirements gathering, agile modeling, use cases, business rules, business modeling, user/usage-centered analysis, usability and/or robustness analysis
Popular OO language, including Web application frameworks and programming best practices
Software security
Testing & Quality
Leading-edge testing and quality assurance techniques that you can use in real world situations
Web Development
Technologies covered could include:
+ Dynamic Languages (PHP, JavaScript, etc.)
+ Web Services consumption (Amazon, Google APIs, etc)
+ Web Services creation (Axis, for example)
+ Server-side toolkits (Atlas, JSF)
+ Ajax (Jaxson, Prototype toolkits)
+ Servlets
+ Trails
+ Mono
Web Services/SOA
Explain and explore concepts related to Web services and service-oriented architecture (SOA). Discuss core standards such as SOAP and WSDL, and practical implementations of Web services with related technologies (including REST, POX and JSON) and platforms (including J2EE, Apache Axis/Axis2, .NET and Windows Communication Foundation [WCF]).
XML Development
Topics of interest could include:
+ Schemas
+ XForms
+ Semantic Web
+ Native XML Databases
+ XQuery
+ Atom

All proposals will be accepted by the Program Committee Secretary ( until November 30, 2006!


Europe Square 2