Comments for NVISIA

Comment on Lightweight Requirements Management with Confluence by links for 2010-06-17 « The Adventures of Geekgirl

links for 2010-06-17 « The Adventures of Geekgirl — Fri, 18 Jun 2010 02:03:09 +0000

[...] NVISIA – Lightweight Requirements Management with Confluence (tags: confluence requirements management howto templates atlassian nvisia) [...]

Comment on Final definition of “meaningful use”? by Final definition of “meaningful use”? | EMR Stimulus Package

Final definition of “meaningful use”? | EMR Stimulus Package — Mon, 07 Jun 2010 09:07:57 +0000

[...] Above article publish on http://nvisia.com/techs/?p=364 [...]

Comment on Lightweight Requirements Management with Confluence by Adriana B.

Adriana B. — Thu, 06 May 2010 19:30:41 +0000

Kevin, great job illustrating the use of a wiki to manage requirements. It complements very well my article on this subject at Bridging the Gap ( http://www.bridging-the-gap.com/wiki-requirements-management-benefits/ ).

Thanks for leaving the link in the comments there.

Comment on Lightweight Requirements Management with Confluence by Kevin

Kevin — Thu, 29 Apr 2010 10:55:04 +0000

Brad -
Glad to hear you thought this was useful. I had run across your blog a while ago, and remembered it mostly because of the great name!

Comment on Lightweight Requirements Management with Confluence by Kevin

Kevin — Thu, 29 Apr 2010 10:53:41 +0000

Matt - Thanks for the info about the new template bundle functionality in 3.2 - I hadn’t noticed that before. Being able to pre-install templates should address one of the main complaints I hear from Confluence users–that it’s difficult to enforce any sort of page-level standardization. I’m going to take a closer look at it.

Comment on Presenting GPetStore: a Groovy Pet Store in a single 500 line script by Brock Heinz

Brock Heinz — Wed, 28 Apr 2010 02:15:13 +0000

… how about releasing a version built using Groovy’s Swing Builder. The ‘desktop’ is the new ‘browser’

Comment on Lightweight Requirements Management with Confluence by Brad Rosenberg

Brad Rosenberg — Thu, 01 Apr 2010 02:34:42 +0000

Thanks for the incredible post! It’s always interesting to see how people are using Confluence in the wild. I’m the wiki coordinator at my software company and we use Confluence as a way to collaborate on projects and share knowledge. I’ll certainly share your recipe here for requirements management to our software team.

Would love to hear more about your practices in using Confluence.

Feel free to check out my Confluence blog, Conflatulence at http://conflatulence.blogspot.com/ where I share my experiences as well.

Comment on Lightweight Requirements Management with Confluence by Matt Hodges

Matt Hodges — Mon, 29 Mar 2010 17:13:34 +0000

Kevin, this is a great post. Good job.

With the release of Confluence 3.2 you are now able to import a bundle page templates into Confluence as a plugin. Perhaps you may like to share your templates on the Atlassian Plugin Exchange:

https://plugins.atlassian.com/search/category/20177

Learn how to package your templates as a plugin in our documentation:

http://confluence.atlassian.com/display/CONFDEV/Creating+A+Template+Bundle

Thanks Kevin.

Cheers,
Matt

Comment on Spring Roo by Neal Ravindran

Neal Ravindran — Tue, 09 Mar 2010 13:06:31 +0000

To test out, I used ROO to do one of my pet projects: CROW..course registration over the web(it is like a hello world with me since 1997 with any new framework or technology I encounter) Have to say! Roo is the next best thing to
Was very impressed.
Roo is Maven on steroids, in a way.
It was a snap making CROW this time around…15 mins..I had it running
i agree with you 100% regarding the thoughts that run thru one’s mind when starting a new project…been there a few times myself…

The bad thing is that some college kid with rudimentary java & db knowledge could replace me as a java developer with Roo..Time to retire, I reckon

Comment on Supporting Downtime in a Clinical Setting by Brock Heinz

Brock Heinz — Tue, 24 Nov 2009 02:56:28 +0000

… definitely a difficult scenario to plan for. From your post, it seems as though you are explaining how NVISIA solved the read-only part of the application. Interesting approach, but what about data capture?

One of the ways that we solved the data capture piece in our clinical environment was by developing data acquisition applications that were able to maintain more state on the client EDC (electronic data capture) system when needed. Once the client application determined that the server (or network for that matter) was not available, data was temporarily stored locally. Then, once it was determined that the server / network was back online, a synchronization with the server was able to occur. Grant it, this strategy will not work for the ‘Net at large (for public facing applications), but for highly controlled clinical environments, latency and the amount of data being captured per visit is predictable, and re-synchronizing isn’t that huge of a challenge. We were able to do this with a slightly thicker client (Java Web Start)… but for the web purists, I’m guessing there is some sort of slick JavaScript framework somewhere that will allow for acceptable levels of serialization in intranet environments.