bookmarks (hide)983
- Writing papers, giving research talks, and writing research proposals are key skills, but they aren't easy. This page describes how I approach each of these three challenges, in the hope that they may be useful to you.
- Yesterday, one of the JAXB users sent me an e-mail, asking for how to solve the problem he faced. The scenario was like this; you have a client and a server, and you want a client to send an XML document to a server (through a good ol' TCP socket), then a server sends back an XML document. A very simple use case that should just work. The problem he had is that unless the client sends the "EOS" (end of stream) signal to the server, the server keeps blocked. When he modified his code to send EOS by partial-closing the TCP socket (Socket.shutdownOutput), the server somehow won't be able to send back the response saying the socket is closed.
- So far in this series (click here for an index of the complete series, as well as supporting screencasts), I have illustrated how to develop both a LO-REST, AJAX-Friendly service, as well as HI-REST services adhering to the unified API of HTTP. In the very first post, I touched on some aspects of REST, but I haven’t spent much time on the benefits of following a RESTful architectural style. I made mention of the fact that RESTful services follow the "way of the web". As it turns out, this proves to be quite powerful.
- As the name implies, AMDD is the agile version of Model Driven Development (MDD). MDD is an approach to software development where extensive models are created before source code is written. A primary example of MDD is the Object Management Group (OMG)’s Model Driven Architecture (MDA) standard. With MDD a serial approach to development is often taken, MDD is quite popular with traditionalists, although as the RUP/EUP shows it is possible to take an iterative approach with MDD. The difference with AMDD is that instead of creating extensive models before writing source code you instead create agile models which are just barely good enough that drive your overall development efforts. AMDD is a critical strategy for scaling agile software development beyond the small, co-located team approach that we saw during the first stage of agile adoption.
publications (hide)199
- (2014)
- MS-CIS-90-47. Department of Computer and Information Science, University of Pennsylvania, (1990)
- (2010)
- (2009)
- (2010)
- (Dec 18, 2012)
- (2013)
- (1998)
- (2013)
- (2014)
- (2012)
- (2012)
- (2007)
- (September 2008)
- (2012)
- (2010)
- (2011)
- (2014)
- (2014)
- (2014)
