Xelleration Sharepoint Consulting Irvine
Site Map Products Downloads
 
Home
Company
Solutions
Client Experiences
Contact Us
  

 

Accelerated Value Method

Accelerated Value Method - We often see an inordinate focus on applications and infrastructure development, with too little attention on redesigning business processes, managing cultural change, and managing project dynamics.

  • Engagement Management
  • Transformation Management
  • Process Innovation
  • Collaborative Development
  • Enterprise Deployment

The Value Frame is a tool for evaluating business goals against costs. The first frame delivers obvious business value in the form of a prototype application. Successive Value Frames deliver increasingly mature functionality. Finally, each Value Frame involves a value assessment, which allows early and frequent adjustments to minimize costs.

Business users are key in the design process
In traditional information technology methods, consultants lock down requirements and rigidly measure against them. AVM, on the other hand, allows users to design their own systems and accommodates their evolving needs. When users are an integral part of the design process, they understand the real potential of workflow technology. As a prototype matures, users help shape the emerging solution during intensive workshops held during design, development, and piloting. And progress toward business goals is always assessed based on the Value Frame.

Solutions Framework
Strategic alliances. Buyouts. New legislation. Global competitors. Shorter product cycles. No matter what challenges you're addressing with technology solutions, you'll need your technical and business goals in synch, on every project, from start to finish.

Without an effective process model in place, certain obstacles to success are predictable. Perhaps you've seen some of these symptoms in your own projects:

  • The project changed into something it wasn't designed to be.
  • The project is taking too long to develop and getting too expensive.
  • Every time you almost release it, someone adds more features.
  • You just discovered a major issue and have to start all over again.
  • The project is complete, on budget, but now you don't need it any more.

The model is comprised of six clearly defined roles. Unrestricted communication is critical:

  • Product Management
  • Program Management
  • Development
  • Testing
  • User education
  • Logistics 


Xelleration & Java Design Patterns

Xelleration has delivered a number of projects involving all layers of the J2EE application development model. We have experience with most of the popular design patterns like Struts, EAD4J, Java Blueprints, Session facades, Business Interfaces and others.

The following is a short overview of the Struts framework which we use for presentation layer modules.

Overview of Struts Framework 1.1

Struts is part of the Apache project, a set of tools to make dynamic Web Pages. It is a framework that brings together JSP or Java Server Pages, Taglibs or html like keywords with access to library calls and JSTL or the Java Standard Tag Library. Struts combine the above visual elements with a way to navigate through a set of mostly dynamically written web pages. This logical part of Struts is controlled by the Action class of Struts.

Struts is based on an MVC architecture

The aim of MVC architecture is to separate the business logic and data of the application from the presentation of data to the user. Following is the small description of each of the components in MVC architecture:

Model
The model represents the data of an application. Anything that an application will persist becomes a part of model. The model also defines the way of accessing this data (the business logic of application) for manipulation. It knows nothing about the way the data will be displayed by the application. It just provides service to access the data and modify it.

View
The view represents the presentation of the application. The view queries the model for its content and renders it. The way the model will be rendered is defined by the view. The view is not dependent on data or application logic changes and remains same even if the business logic undergoes modification. The view forwards its requests to the controller which then forwards the request to the appropriate Action.

Controller
All the user requests to the application go through the controller. The controller intercepts the requests from view and passes it to the model for appropriate action. Based on the result of the action on data, the controller directs the user to the subsequent view. Action is an implementation of an Action Class.