Internet: Workflow & User Interfaces

To define an effective internet computing solution, you must understand the implication of the workflow and the user interface.  End-users may be accustomed to traditional interfaces and applications in which, for example, the flow from screen to screen is predictable and fixed.  The internet environment changes this perception - the flow is no longer guaranteed.  To build an effective application, you must ensure that the requirements and the solution reflect the realities of the internet environment.  Specifically, consider:


·          workflow requirements,


·          continually refining the architecture with an emphasis on interface and workflow,


·          maintenance of the solution model,


·          navigation, transactions, and persistence.


Workflow Requirements


Architecture Consideration: In examining the requirements, consider how the work flows.  Consider whether the “success” of the transaction depends on the end-user being led through a series of steps.  Identify the areas of impact if such a flow is not maintained.  Identify areas that may not be supported by the new environment, for example, multiple screen input and updates with guaranteed integrity.


Exploration Approach: Because of the freedom of the end-user to leave screens in the middle of a sequence or to arrive (for example via a search) at a screen without the prerequisites, the internet computing solution may not fit the end-users views of applications.  Therefore it is important to further explore workflow.  Use storyboarding (see Functional Storyboarding) to identify requirements based on expected workflow(s) that may have to be altered.  Identify areas that may be difficult to accommodate, or that require specific support from the underlying tool set, such as transaction support.  Use the storyboards to convey the impact of revised workflow to end-users and to gain acceptance and understanding of the new application. 


Continually Refine the Architecture


Architecture Consideration: As the understanding of the application increases, as with other architectures, consider the impact of new detailed information on the architecture.  Again the focus is on interface and workflow so that differences and issues can be identified as early as possible and addressed.


Exploration Approach: As the application knowledge increases, explore alternate approaches using storyboards.  As Use Cases are defined, consider the implications of the proposed interactions with the end-user.  Ensure that the environmental constraints are reflected in the use cases and communicated to the end-users for acceptance.  Define prototypes, based on the use cases, to confirm that the solution assumptions about navigation (horizontal prototype) and functionality (vertical prototype) can be implemented.  Document in the architecture the middleware or custom functionality agreed upon to address requirements.


Maintain the Solution Models


Architecture Consideration: Remember that the storyboard (and the use cases) is not the model of the solution, but a mechanism to explore the interfaces and navigation that the solution must address, leading to concise statements of the requirements and a common understanding of the application. 


Exploration Approach:  Ensure that the identified requirements are reflected in the solution model (e.g., the object model).  For example, if it has been decided that the best approach to address functional requirements involves the development of custom "middleware" allowing access to legacy systems or providing interfaces between solution elements, ensure that this is part of the solution model.  Documenting specifics helps achieve acceptance and a common understanding of constraints and accurate reflection of the effort to develop the solution.


Navigation, Transactions, and Persistence


Architecture Consideration: Since the internet-based application often must change workflow or change the integrity requirements for multiple page (or multiple screen) transactions, consider the impact of the user interface and the screens or pages that define the navigational flow.


Exploration Approach: For web-based internet applications, examine the storyboards to a sufficiently detailed level to assess what information is gathered on each web page and what is output on each web page.  This information assists in the development of a strategy to address persistence for each grouping of information needed for update.  It also forces an understanding of the navigation and the transactional requirements.  Ensure that any constraints or changes to the end-users' expectations are accepted. 

Related Tags:
About the Author
4 Comments | Write Comment
Sign In to Post a Comment

very informative article..




its very useful who is working in SAP


Very true!
