principles   6343

« earlier     later »

Service-oriented architecture - Wikipedia
These services and their corresponding consumers communicate with each other by passing data in a well-defined, shared format, or by coordinating an activity between two or more services.[8]

A manifesto was published for service-oriented architecture in October, 2009. This came up with six core values which are listed as follows:[9]

Business value is given more importance than technical strategy.
Strategic goals are given more importance than project-specific benefits.
Intrinsic inter-operability is given more importance than custom integration.
Shared services are given more importance than specific-purpose implementations.
Flexibility is given more importance than optimization.
Evolutionary refinement is given more importance than pursuit of initial perfection.
SOA can be seen as part of the continuum which ranges from the older concept of distributed computing[7][10] and modular programming, through SOA, and on to current practices of mashups, SaaS, and cloud computing (which some see as the offspring of SOA).[11]

There are no industry standards relating to the exact composition of a service-oriented architecture, although many industry sources have published their own principles. Some of these[12][13][14][15] include the following:

Standardized service contract
Services adhere to a standard communications agreements, as defined collectively by one or more service-description documents within a given set of services.
Service reference autonomy (an aspect of loose coupling)
The relationship between services is minimized to the level that they are only aware of their existence.
Service location transparency (an aspect of loose coupling)
Services can be called from anywhere within the network that it is located no matter where it is present.
Service longevity
Services should be designed to be long lived. Where possible services should avoid forcing consumers to change if they do not require new features, if you call a service today you should be able to call the same service tomorrow.
Service abstraction
The services act as black boxes, that is their inner logic is hidden from the consumers.
Service autonomy
Services are independent and control the functionality they encapsulate, from a Design-time and a run-time perspective.
Service statelessness
Services are stateless, that is either return the requested value or give an exception hence minimizing resource use.
Service granularity
A principle to ensure services have an adequate size and scope. The functionality provided by the service to the user must be relevant.
Service normalization
Services are decomposed or consolidated (normalized) to minimize redundancy. In some, this may not be done, These are the cases where performance optimization, access, and aggregation are required.[16]
Service composability
Services can be used to compose other services.
Service discovery
Services are supplemented with communicative meta data by which they can be effectively discovered and interpreted.
Service reusability
Logic is divided into various services, to promote reuse of code.
Service encapsulation
Many services which were not initially planned under SOA, may get encapsulated or become a part of SOA.
soa  patterns  apis  principles 
4 weeks ago by earth2marsh
Home | Laws of UX
Laws of UX is a collection of the maxims and principles that designers can consider when building user interfaces. It was created by <a href=''>Jon Yablonski</a>.
ux  ui  laws  !great  resource  reference  design  inspiration  interface  law  principles  psychology 
4 weeks ago by alexmc
Designing for Interaction Modes · An A List Apart Article
But why is it still so hard (on most of the internet) to avoid uphill struggles? Often, for example, a quality reading experience is only fully available via a hack, using Safari’s reader view or a browser plug-in. I use Instapaper to send articles to my Kindle—a device that’s devoted to reading mode—because reading is not just about getting the job done. The experience itself is also important.

The best experiences result from designers matching the way the computer behaves with the way our users are thinking, feeling, and interacting. This is what user experience design is all about. And yet, because of pressures, competing priorities, and industry trends, interaction modes are often an afterthought.
design  development  principles 
4 weeks ago by tamouse
HDC LIBRARY - Tilden's Tips
Provoke: attention, curiosity and interest.
Relate: to the everyday life of your visitors.
Reveal: the main concept or theme through some creative or unusual viewpoint.
Address the Whole: make sure your program relates to your main Project THEME.
Message unity: use the correct supporting elements in your program to illustrate your theme or main concept.
Interpretation  principles 
4 weeks ago by stacker
Heritage interpretation - Wikipedia ("Tilden's principles" of interpretation)
Any interpretation that does not somehow relate what is being displayed or described to something within the personality or experience of the visitor will be sterile.
Information, as such, is not Interpretation. Interpretation is revelation based upon information. But they are entirely different things. However all interpretation includes information.
Interpretation is an art, which combines many arts, whether the materials presented are scientific, historical or architectural. Any art is in some degree teachable.
The chief aim of Interpretation is not instruction, but provocation.
Interpretation should aim to present a whole rather than a part, and must address itself to the whole man rather than any phase.
Interpretation addressed to children (say up to the age of twelve) should not be a dilution of the presentation to adults, but should follow a fundamentally different approach. To be at its best it will require a separate program.
principles  Interpretation 
4 weeks ago by stacker
The Anchoring Principle
By Therese Fessenden - Dec 9, 2018
articles  UI  psychology  principles 
4 weeks ago by mycotn

« earlier    later »

related tags

!great  12  advice  ai  algorithms  amazon  amzn  animation  apis  app  architecture  article  articles  artificial_intelligence  at  authentication  aws  betting  bias  business  career  charts  code  coding  color  community  concepts  content  cookies  culture  cyber  design  designprinciples  development  dieter-rams  disney  documentation  education  engagement  engineering  ethics  examples  explain  explained  facebook  finance  forms  forwork  frameworks  good-design  google  group  guide  guidelines  harvard  hasn't  hbs  hourofcode  howto  ibm  ideology  in  inclusion  inclusive  infographic  inperson  inspiration  institutions  interaction  interface  interpretation  interview  interviewing  job  jobs  kids  kiss  law  laws  layout  leadership  life  links  list  management  mobile  motion  navigation  notifications  odds  outreach  paciello  parenting  patterns  pdf  persistence  person  phone  prep  preparation  prepare  preparing  process  processes  product  productdesign  productmanagement  programming  psychology  python  rams  reference  research  resource  responsibilities  review  roles  rules  sandberg  scala  sen  signed  soa  software  strategy  teaching  teams  technology  to_revisit  tog  togaf  transparency  tutorial  u.s.  ui  usability  ux-laws  ux  valuefirst  values  videos  visualization  voice  voiceui  vui  work  working  workshop  writing  yet  zuckerberg   

Copy this bookmark: