A Modular Approach to Development Process

  • Date: June 9, 2010 from 4:00PM to 5:15PM
  • Day 3
  • ARC201
  • Speakers: Juval Lowy
  • Avg Rating: 0

  • 1,452 Views

Embed code for this video

Copy the code above to embed our video on your website/blog.

Close

Video format

Note: These selections will fall back to the next best format depending upon browser capability.

Close

Download

Right click “Save as…”

Slides (view online)
Architects always strive for modularity to achieve extensibility, maintainability, and reuse – the technology for the modules, the glue, changes over time, from objects, to .NET to WCF. And yet, all of these introduce inherit complexity. When you design a highly modular system, it would be naive of you to expect that the things you will do differently will be limited to design and technology. The development process itself needs to be modular, accommodating the complexity of the modules as a system. In this intense session, Juval shares his original techniques, metrics, and ideas, all practiced in real life, allowing for a module-oriented development process. This talk presents a battle-hardened development process that you can immediately apply to achieve robust applications, manage requirements, and ensure faster time to market. Also, see how the various team members – the architect, the project manager and developers – should work in concert, and their respective tasks and responsibilities towards the modules.

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.