Lecture 5
Lecture 5
Information Technology
Web Technologies II
Lecture#5
●Design Process
●Workflow Design
●Data Design
Design Process
Web application design can be summarized as
follows:
* Understand the issues related to the technical
environment on which the software will operate
* Understand and create a model of requirements for
individual modules and subsystems.
* Capture the major interfaces between subsystems. As
we will see, in some design methods these are
captured in a so-called Web software architecture.
* Use as much as possible a common notation
for the design within a team
* Decide on an appropriate design abstraction
so that the implementation is a more or less
straightforward refinement of the design
without significant change of structure.
Workflow Design
The workflow design is a follow-up refinement of a
business process model described from an
organizational perspective during requirements
analysis.
In fact, a workflow is a special kind of
business process that is case- and
order-based.
This characteristics allow us to define the
exact work product of such a business
process (a case) and also where such a
business process starts and how it
proceeds (the activity order).
The first step in a workflow design is to
determine which of the activities in the
business process will be implemented by the
Web application.
We adopt UML activity diagrams to illustrate the
workflow design. Other notations exist and are
used, such as the Business Process Modeling
Notation and Petri Nets
We will use here as example an online
magazine Web application and expand on
it in the following sections. Our scenario is
based on a simplified workflow for ordering
magazines, where the application supports
the retrieval and selection of articles
As can be seen from the above
example, the workflow design models
are good at mapping user activities,
tasks, and processes to the tasks
that a Web application must perform.
Sequence Diagrams
Sequence diagrams are one of two types of interaction diagrams. They
illustrate the objects that participate in a use case and the messages that pass
between them over time for one use case.