Masayuki Otoshi

I wrote in my previous article, "Interactive Storyboarding with JSP," that interactive storyboarding is an effective way to define better requirements by eliciting actual business user needs. And I proposed to describe the requirements inJSPs with the J-CASE tag library, which enables business to experience conceptual pages to get a better understanding of the proposed system. As a next step, this article proposes to create a storyboard library that can be reused among projects. This article also shows that aspect weaving makes customization of the library easier to describe application-specific requirements. Storyboarding with J-CASE Before discussing requirements reuse, I will briefly explain how J-CASE creates storyboards. It's very hard for business users and engineers to clearly recognize all the requirements early on. Even if we carefully define use cases, we ... (more)

J-CASE Tag Library - Interactive Storyboarding with JSP

A lot of rework still happens in projects applying UML techniques because of conflicts and omissions in requirements. To reduce rework, interactive storyboarding is effective, but it seems that projects using the technique are limited because of the few tools available. To improve this situation, this article introduces the J-CASE open source Tag Library that lets us describe storyboards on JSPs based on use cases, and explains how to generate documents and UML diagrams from the JSPs. To reduce the rework and improve quality of the requirements, we should carefully realize the use... (more)