功能与视觉的双重设计，beyond Object 推出创意手写笔 Align | 理想生活实验室 - 为更理想的生活
登录　注册
功能与视觉的双重设计，beyond Object 推出创意手写笔 Align
由 ShiKai Tseng 和 Hanhsi Chen 创立于英国伦敦的设计品牌 beyond Object，日前推出了一款极具设计感的笔 Align。它采用高档铝合金制成，笔身被分为相互错位的三个部分，而扭动中间的部分即可推出笔芯来使用。设计者表示，Align 的设计灵感来源于，目的是“直观地展现人类大脑是如何组织信息。”通过视频介绍来了解一下：这款笔已在 Kickstarter 上募集到 23986 英镑（约合人民币 25 万），投产后将会提供不同尺寸以满足用户需求，更多信息可以查看品牌。
理想生活实验室近期精华内容汇集，一起关注全球消费市场动向和各种最新玩法攻略。
请填写正确的邮件地址
&版权声明 This site is licensed under a Creative Commons
Attribution-NonCommercial 4.0 International License.Why Extend the UML Beyond Object and Component Technology?
For years I've written that the
, at least
from the point of view of business application
development, and that we therefore need to
extend it.
In fact, I believe that I was
the first one in the IT industry to argue this:
I can't remember which was physically published
first, but both the first edition of
and an article I wrote reviewing the initial
release of the UML published in Object Magazine
(the first such UML article they published) came
out within a few months of each other.
Both the book and the article pointed out the
need to include fairly obvious things such as
to the UML so
that we could actually model a business
application.
Since then I've expanded on
this idea in several publications, but what I've
never really done is written, at least in one
place, about why extending the UML beyond object
and component technology is so important to the
IT industry.
Until now.
By extending the
, we would:
Support the full
range of business
application development.
There's more to business
application development than
object/component technology.
There are user interfaces on
the front end and databases
on the back end.
now taking a
service-oriented
architecture (SOA) approach
with web services,
transaction processing (TP)
technologies (e.g. CICS),
and even stored procedures
that are used to wrap
database access.
me old fashioned, but I
think it's a good idea to
model the UI, the database,
and services (not to mention
a myriad of other aspects)
when it makes sense to do
Make it a truly
unified language.
The word &unified& is
wonderful marketing rhetoric
describing the consolidation
of major object-oriented (OO)
modeling languages in the
mid-1990s.
great start, but to have a
truly unified modeling
language I believe that it
should address the other
important aspects of
development too.
Break down
communication barriers.
A common language, with a
common notation and
semantics, promotes
communication between
We've seen
this work within the object
community, now it's time to
do so within the IT
community as a whole.
Break down cultural
having a common,
comprehensive modeling
language IT professionals
will come to understand the
issues that other
specialists have to deal
importantly, they may even
realize that being a
specialist reduces their
overall effectiveness and
that they should instead
strive to become a
Provide direction to
developers.
developers, if they choose
to take a formal approach to
modeling at all, will focus
on UML-based techniques
has shown)
but not other techniques.
I suspect that this is in
part due to the effective
marketing of the UML tool
vendors, in part due to OO
books which only cover
UML-based techniques, and in
part due to over
specialization within
organizations (e.g. you
don't need to learn how to
model data because the data
folks do that work).
By including
non-object/component
modeling techniques in the
UML they're at least put on
the radar scope of these
developers, increasing the
chance that they'd pick up
the requisite skills to
apply them effectively.
Provide guidance to
tool vendors. I often
see developers struggle to
use UML modeling tools
effectively.
their management has forced
them to use the modeling
tool but they haven't been
given adequate training to
Unfortunately
there's not much I can do
about that problem other
than to advise against it.
Other times, however, the
developers have the UML
skills, they have a good UML
tool, yet they still
struggle because the tool
doesn't fully reflect what
they need to do.
Often, the tool is either
limited to just the UML or
has includes a
less-than-stellar
implementation of non-UML
models (more on this in a
For example,
if the UML included a
tool vendors
(see my list of existing
be motivated to build
something that maps between
a standard class diagram and
a standard data model.
Right now, although there
are a lot of great O/R
mapping tools out there,
they're all pretty much
limited to a subset of
platforms.
There are several
significant challenges to
this approach:
The UML is
arguably too big already.
Although the breadth of
the UML is still a bit
challenged, the depth
proves to be quite
impressive.
UML exhibits such detail
due to the needs of the
which is great for them,
but most UML
practitioners neither
need nor want this
people are happy with
the 20% of the UML
notation that they
already use, struggle to
see the point of the
other 80%, and really
aren't all that
concerned about adding
to the UML.
Object purists
don't like the idea.
The original goal of the
UML was to define a
common approach to
modeling OO software.
That scope was later
expanded for
component-based
purists feel that the
scope of the UML is fine
the way that it is.
Non-object
purists don't like the
seems to be a problem
withing the data
community in particular,
although to be fair it's
really a problem with a
very small minority
within the data
community.
see modern technologies
and techniques, such as
agile software
development approaches
or object technology
itself, as a threat. And
you know what, they're
absolutely right: the
changes that have been
underway within the
application development
community since the
early 1990s are very
different that the
traditional data
management approaches
which some people within
the data community still
one aspect of the
unfortunate
between the
object and data
communities, a mismatch
that we've been trying
to address with the
and its surrounding
techniques.
Why I think we will
see the UML extended:
vendors are
extending the UML on
their own.
hard-pressed to find
a &UML modeling
tool& that simply
restricted itself to
&pure UML&, and
that's perfectly
vendors need to meet
the actual needs of
their clients, and
their clients are
trying to use their
tools to build
actual software.
This is why you see
companies such as
IBM, Oracle, and
Sybase selling CASE
tools which support
their own version of
&UML data modeling&
(respectively, these
Similarly, some UML
modeling tools
support UI modeling,
business process
modeling, and web
service modeling
using their own UML
methodologists are
extending the UML on
their own.
Many UML book
authors describe
their techniques for
UI, process, and
data modeling using
cover all three in
started writing
about all three in
continued to do so
Craig Larman covers
similar ground in
More specifically,
for UI modeling via
the UML, Mark
Harmelen's
process modeling,
there's Penker and
Eriksson's and
For UML data
modeling, we have
Robert Muller's
Naiberg and
Maksimchuk's
The OMG is
finally starting to
extend the UML.
They've brought the
their fold,
indicating movement
standardized
approach to process
modeling via the
also issued an
in December 2005,
which is the first
step to developing
an industry
Unfortunately, the
data community has
never gone to the
effort of defining
an industry standard
notation (not that
you can blame them,
it's a truly
thankless task) so there
isn't an existing
standards body to
work with, unlike
with BPMN.
In short, it's
already happening.
Share with friends:
Let Us Help
We actively work with clients around the world to improve their information technology (IT) practices,
typically in the role of mentor/coach, team lead, or trainer.
A full description of what we do, and how to contact us, can be found at .
Recommended Reading
This book,
describes the
(DAD) process decision framework.
The DAD framework is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and provides the foundation for
This book is particularly important for anyone who wants to understand how agile works from end-to-end within an enterprise setting.
Data professionals will find it interesting because it shows how agile modeling and agile database techniques fit into the overall solution delivery process.
Enterprise professionals will find it interesting beause it explicitly promotes the idea that disciplined agile teams should be enterprise aware and therefore work closely with enterprise teams.
Existing agile developers will find it interesting because it shows how to extend Scrum-based and Kanban-based strategies to provide a coherent, end-to-end streamlined delivery process.
is an important reference book for agile modelers,
describing how to develop 35
including all 13
Furthermore, this book describes the fundamental programming and testing techniques
for successful agile solution delivery.
The book also shows how to move from your
agile models to source code, how to succeed at implementation techniques such as
The Object Primer also includes a chapter overviewing the critical database development techniques (,
database access coding) from my award-winning
This site owned by