0% found this document useful (0 votes)
16 views

Lecture 5

Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views

Lecture 5

Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 22

College of Computer Science and

Information Technology

Web Technologies II

Lecture#5

Dr Mohammed Mohsin Al-Ebady


Headline

●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.

A sequence diagram is a dynamic model that shows the


explicit sequence of messages that are passed between objects in a defined
interaction. Because sequence diagrams emphasize the time-based ordering
of the activity that takes place among a set of objects, they are very helpful
for understanding real-time specifications and complex use cases.
The sequence diagram can be a generic sequence diagram that shows all
possible scenarios for a use case, but usually each analyst develops a set of
instance sequence diagrams, each of which depicts a single scenario within
the use case. If you are interested in understanding the flow of control of a
scenario by time, you should use a sequence diagram to depict this
information. The diagrams are used throughout the analysis and design
phases. However, the design diagrams are very implementation specific,
often including database objects or specific user interface components as
the objects.
Data Design
Data design is a well-established activity that is
fundamental especially for those Web
applications that need to manage a huge
amount of data. Data design produces a
refinement of the application domain model
identified during requirements engineering,
with the purpose of outlining how content will
be stored and processed by the Web
application.
The result is a data model that specifies
the structures used to store the data
underlying the entities and the
relationships previously identified in the
application domain model.
The data model may differ depending on the
data base management system (DBMS)
that is chosen for storing and processing
data
Data Model
A data model is a conceptual representation of the data
structures that are required by a database. The data
structures include the data objects, the associations
between data objects, and the rules which govern
operations on the objects. As the name implies, the
data model focuses on what data is required and how it
should be organized rather than what operations will be
performed on the data.
Relational Data Model Main Elements

In this section we will concentrate on the


relational data model, which is the leading
solution for the development of Web
applications. Its main elements are:
● Relation: a set of tuples, each one
representing a “fact” about a given concept
(an entity or a relationship of the application
domain).
● Attribute: the ordered pair <attribute name,
type name>.
● Constraints: properties that must be satisfied
for data items to be correct and consistent.
The most important constraints refer to the
definition of primary key and foreign key.
Thank You

You might also like