Software Development

SOA

• Service Manifest
• Service Categorization
• SOA Hype Chart
• Laws of SOA
• Real SOA versus REST

Articles

• Same Old Architecture versus Services
• Business Intelligence (BI) and Enterprise Search in a Service Oriented Architecture Strategy

Governance

• Policy Advisory Board (PAB)

Master Data

• Master Data Management Service
• Enterprise Domain Repository
• Intro to Enterprise Domain Repository

Articles

• Business Intelligence (BI) and Enterprise Search in a Service Oriented Architecture Strategy

Test Grouping

• JigZaw - Agile Testing done Right
• How to use JUnit Categories to implement JigZaw

Rules, laws and design guidelines

• Laws for Organization Architects
• Laws of SOA
• Laws for Project Architects

Navigate space

Space Index

0-9 ... 0 A ... 5 B ... 2 C ... 8 D ... 5 E ... 1 F ... 0 G ... 1 H ... 5 I ... 1 J ... 0 K ... 1 L ... 3 M ... 3 N ... 1 O ... 0 P ... 23 Q ... 0 R ... 4 S ... 48 T ... 18 U ... 0 V ... 1 W ... 0 X ... 0 Y ... 0 Z ... 0 !@#$ ... 0
0-9	A a small note on Governance and cost.. small reflection on Governance and cost. If you think knowledge is expensive, have you tried the opposite? Misplace prudence eats up any benefit from economy of scale http://paulgraham.com/artistsship.html This is a typical cost curve for IT expenses.. !http://wiki.cantara.no ... A software architect is a part-time Archeologist Title says is all, really :) http://97things.neartime.net/forum/usercontributedaxioms/communityaxiomscontributenewaxioms/3209?page=11 A2A http://wiki.community.objectware.no/download/attachments/622610/a2asimple.png width=100px! Application 2 Application Services Application 2 Application Services is services which orchestrates services from several applications, typically asynchronous and workflowbacked. I.e. a Auction type request against ... Above all, do no harm People ethics for the architect Be wary of your influence: When you suggest a solution, it may get accepted without critical consideration. You remove responsibility from those who will actually execute the task, and limit their feeling of responsibility for the choice. Be humble ... ACS http://wiki.community.objectware.no/download/attachments/622610/acssimple.png width=100px! Aggregated Core Services Aggregated Core Services is extensions to Core Services CS. ACS is usually either contextspecializing (CustomerCustomer and VendorCustomer) or aggregations from several Core Services CS like ...
B building services the last 15+ years Some references from successful services strategies Jini, successful projects Project OpenWingz http://www.openwings.org Business Intelligence (BI) and Enterprise Search in a Service Oriented Architecture Strategy Executive Summary Today, we are experience a heavyweight fight to own the definition of the business objects within the enterprise. The contenders are Data warehouse products, Enterprise Search Platforms and Service Oriented Architecture strategies. Solutions based upon enterprise search are closing ...	C Clear and consistent responsibility powers all great architectures all architects learn, architecture is all about balancing tradeoffs, but there is one trade off which should never be broken; namely the clear and consistent responsibility throughout your system or system(s). !axiom1.jpg client technology Cache Static code (Processing, aggregation, transformations) Movable code (JavaScript, XML, Java) P2P Async writes Cloud Home Work in progress, feel free to add/complete information Definition of Cloud Computing: Cloud computing is a payperuse model for enabling available, convenient, ondemand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications ... combining a SOA strategy with enterprise search and BI DWH complex data complexity connectedness semistructure Consistent and balanced decisions main value a great architect provides is when the sum of the decisions keep strengthen each other to create balanced synergies throughout the project, system or organization. Because it is the perception of the receivers that matters here, decisions can only be said to be consistent if the receivers ... Cover Your Ass Governance CS http://wiki.community.objectware.no/download/attachments/622610/cssimple.png width=100px! Core Services Core Services is basically data services. Typically they evolve to become the master repository for the most important business objects in the enterprise. Typical examples are Customer and Product. You will also ...
D Data integration Slides (ppt) Data integration.ppt Data Warehouse (DW) and Business Intelligence (BI) context we are defining traditional Business intelligence as Data Warehouse (DW) and Business Intelligence (BI) to separate this form Business Intelligence referred to by search platforms Data Warehouse (DW) and Business Intelligence (BI) is currently implemented on one of several available ... Design-Time Governance Design-Time Governance - SOA Design Rules Policy rule Doc status H2A A2A ACS CS Last PAB discussion P1. A service shall have one named owner (x) () () () () (off) P2. A service shall provide documented business value (x) () () () () (off) P3 ... Design-Time Governance - SOA Design Rules FAQ Question still to be asked	E Enterprise Domain Repository How can we manage domain objects (coreentities) created with data from multiple backends? !edr.jpg! Notes from workshop at SOA Symposium Problem Most enterprises have several systems which own parts of a coreentity. The data from ...
F	G Governance - lessons, reflections and ramblings Executive summary Governance has been on top of Gartners HypeCycle for some time now, and people still seem very confused on the topic. This is why I'll try to explain some of my experiences and thoughts on the subject... (Why should I care ...
H H2A http://wiki.community.objectware.no/download/attachments/622610/h2asimple.png width=100px! Human 2 Application Services Human 2 Application Services is an implementation of a usecase/user story which implements one, and only one human actor Characteristics Workfloworiented Services ... high reads Read Random Sequential High reads in the middleware Case At newspaper A newspaper can have many readers and can have many rssclients polling it as well. How do we scale for the reader the enterprise way Put your reverse proxy with cache as the gate to your middleware. Behind this we ... high writes Write Appendonly Random process and forward: large datasets who needs to be aggregated How to use JUnit Categories to implement JigZaw last categories are possible to use in JUnit Since the 4.8 version Hope this will ease the implementation of using testgrouping :) Read more on testcategorization on JigZaw Agile Testing done Right http://wiki.community.objectware.no/display/smidigtonull/JigZaw Thanks to David Saff http ...	I Intro to Enterprise Domain Repository Table of Content: Short description Problem description What is EDR? What does EDR solve? Why use EDR? When to use EDR. Refrences? Should we cite refrences
J	K KPI wider perspective on KPI It's tempting when trying to be customercentric to focus on delivering lots of functionality quickly. Supposedly features win the race and can increase revenue, but is that all that matters? Evidence such as the troubles Twitter have had in the past and this anecdote from Google ...
L Laws for Organization Architects Thou shalt always revisit the architecture axiom Clear and consistent responsibilities powers all great architectures # Thou shalt be kept accountable for all architectural decisions # Above all, do no harm # Thou shalt strive to build a learning organization ... Laws for Project Architects Thou shalt never forget that your day is 80% communication and 20% technology # Thou shalt strive to create a learning culture # Thou shalt never default to silver bullets or magic # Thou shalt strive to find and understand your limitations ... Laws of SOA succssfully implement a service oriented architecture you should: 1. Forget WS and products SOA is design and architecture. The WS standards is not much more than candidate technology for decorating your service endpoints... 2. Establish service categories and service ...	M Master Data Management (MDM)- strategies and practices SOA Master Data Management Service Metadata Meta data in the context of search is about classifying and tagging information that is propagated to the search index.excerpt} Taxonomy is the practice and science of classification. (Wikipedia) Meta data can be added manually or detected by a search engine. A search engine should for example be able to automatically ... middleware Intro Some categories optimizing middleware building blocks something that dictates design&architecture Technologies Queues Cache App servers Proxy ESB EDA containers ToupleSpace Grids
N Notes from workshop at SOA Symposium Workshop with the SOA patterns commitee http://www.soapatterns.org/soacommittee.asp at the International SOA Symposium http://www.soasymposium.com/ Participants Sheperd: Ian Robinson, Thoughtworks http://www.thoughtworks.com/ Dr. Thomas Rischbeck, ipt www.ipt.ch Radovan Janecek, CA www.ca.com First impression ...	O
P P1. A service shall have one named owner Motivation Ensure that the service will be successful. Argumentation If you are unable to find an owner for a service, chances are high that the service is unimportant which is not a good metric for success. The closer to the business departments you find the owner, the better chances for a successful service. Exceptions ... P2. A service shall provide documented business value Motivation If the service does not provide business value, it will never be of any use/interest Discussion In establishing the business value of a service, we can easily add the Key Performance Indicator for the service, and automatically monitor the generated value against the target values ... P20. All services shall be in the service universe Motivation Give the enterprise an understanding of the available services. Argumentation We want to prevent duplication of services. A simple and consistent access to service documentation. Library documentation of already existing building blocks to ensure usage/reuse of existing investments. Exceptions ... P21. A service shall be categorized Motivation Improve the quality and consistency of communication between the services. Ensure correct implementation of the services. Argumentation Since the service requirements vary a lot, it makes sense to categorize the services from a technical perspective to be able to pinpoint and standardize necessary technology to ensure ... P22. A service shall have an "authentication, authorization, endpoint strategy" Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ P23. A service shall document its Service Level Agreement SLA (response time, availability++) Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ P3. A service shall do one only thing, and one thing well Motivation We want to prevent service rot and duplication of services Argumentation If a service does more than one thing, it will likely not do everything well. The success ratio of a service correlates nicely with the characteristics of reusable code, namely code which ... P30. A service shall have a versioning strategy (ACS, CS) Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ P31. A service shall provide for audit and monitoring of service usage Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ P32. A service shall document its Service Level Agreement SLA (response time=30ms, availability=99.995%) Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () () () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ P4. A H2A service (webpart or portlet) shall be an independent component Motivation We want the H2A services to be reusable building blocks. Argumentation WebParts and portlets shall be selfcontained components to be conform to the specification and to be reusable in different scenarios and contexts. It is also very important to be able to automatically test the service in isolation, which is almost ... P40. A service shall provide at least one Evolving Service Endpoint Motivation Argumentation Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS Last PAB discussion (/) () () (?) () 2007.06.08 PAB discussions DesignTime Governance SOA Design Rules FAQ P41. A service shall provide heartbeat and traffic monitoring Motivation We want to keep track of the business value the service generates. Argumentation understand which services which is used understand services which are candidates for change orders if a service is unused, it does not provide value to its owners/users locate ... P42. A Core service shall have orthogonal functionality Motivation Service behavior should be predictable and not produce bieffects in other services Argumentation Ensure that a services does its thing and not everything else.. Improved evolve ability of the service, as the impacts of change is understood. Exceptions/special cases Definitions If(!totto) Orthogonality ... P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services Motivation Argumentation It is the responsibility of the portlet framework/application to be the coordinating framework. If the H2A services start stepping on the toes of its surroundings, we end up with chaos. Exceptions/special cases Definitions Status Doc status H2A A2A ACS CS ... P6. A H2A service shall not have internal workflow Motivation H2A services are pieces. If the pieces includes a lot of internal workflow, they will loose their abillity for reuse, and are in all practical terms not services but applications. Argumentation We create a conflict of responsibility between services when the services start manipulating other services ... P7. Too generic webparts or portlets shall be avoided Motivation We want our H2A services to be easy to use and to give great service/value. Argumentation Too generic webparts or portlets just moves the complexity to the configuration and shall be avoided. Usually these services are just a very thin presentation layer ... P90. A service shall have a documented coupling to the contractual and requirement for service usage Motivation Argumentation Exceptions/special cases Definitions Producer Consumer requirement/contract Information requirements data quality (freshness, correctness, validness/timespan...) data usage rights (Licensing of data ) response time / availability usability o.l. peek (volume ... PAB Persistence strategies for the 21 century ED: Nice starting point? Writeup of data layer from last Geek Cruise and EDR strategies merged with OW Open Community Persistence content... ETA alfa version: May 17th Policy Advisory Board (PAB) Policy Advisory Board is a specialized Center of Excellence organ, focusing on the round trip of keeping the designtime governance policies aligned with the company goals, people and competences. See also Governance for more details on Governance. This content is build on content from http ... Presentations Presentations Some presentations which has not been converted to wiki knowledge yet productivity factor is 5-10 fold among developers original study that found huge variations in individual programming productivity was conducted in the late 1960s by Sackman, Erikson, and Grant (1968). They studied professional programmers with an average of 7 years' experience and found that the ratio of initial coding time between the best ...	Q
R re-introducing Business Objects as first-class citizens of the architecture Real SOA versus REST an interesting question. There are in fact one key similarity between Real SOA (unlike most other SOA strategies) and REST, and that is that Real SOA puts resources/business data as first class citizens of the architecture (ACS and CS category services ... Real Time Enterprise Attribution: This work started on wiki.community.objectware.no http://wiki.community.objectware.no Realtime enterprise.. Just a dream? !Realtimeenterprise.jpg responsible owner is vital Product owner responsible owner is vital du kan ikke sette en gjøk til å være ansvarlig for et system (etc) sterkt eierskap og stålkontroll på eget system er en undervurdert suksessfaktor synes ...	S Same Old Architecture versus Services Intro It has been almost 10 years since the term SOA was introduced as a strategy to build a better future for enterprises. Most people have learned that skyscrapers don't scale http://97things.neartime.net/wiki/talkaboutthearchbutseethescaffoldingbeneathit and was looking for a better way to create ... Scalability - where, what and how to scale details and process behind this, see Geek Cruise III 2009 Scalability in 2009 http://wiki.cantara.no/display/PE/GeekCruiseIII2009Scalabilityin2009 Legend H = high probability for successful scaling M = Medium probability for successful scaling L = Low probability for successful scaling ... scale complex data in the client scale complex data in the database layer Approaches Graph databases, search indexes Problems Social networks scale complex data in the infrastructure layer scale complex data in the middleware layer scale complex data in the os & cloud layer scale complex data in the server code layer scale high processing or high computational in database layer scale high processing or high computational in the client Case SETI search for patterns in massive datasets from observations. Approaches Compute: Add computational execution to the clients running in the background. Process: Add P2P aggregation/concentration into the client "mesh" Consequences Computational grid of undeterministic size and quality. Lots ... scale high processing or high computational in the infrastructure layer scale high processing or high computational in the os & cloud layer scale high processing or high computational in the server code layer scale high read in the client Example: Map client, spotify, iTunes. We create one user system with a 1.tier client. Caching on client and/or server. p2p if server wire is bottleneck. Movable code to fetch data async. Streaming from server. Default / Enterprise Caching ... scale high read in the database layer scale high read in the integration layer scale high read in the os & cloud layer scale high read in the server code layer scale high write in the client scale high write in the database layer scale high write in the infrastructure layer scale high write in the middleware layer scale high write in the os & cloud layer scale high write in the server code layer scale large data in the client scale large data in the database layer scale large data in the infrastructure layer Case: Web crawling Problem: Downloads teh intarwebs. Process teh intarwebs. Scenario: fat servers Reliable, expensive, highend servers => assume reliability => low fault tolerance Local disks, no RAID Partitioned by domain name part of URL ... scale large data in the middleware layer scale large data in the os & cloud layer scale large data in the server code layer Scaling high computation load wrt. the middleware Four paradigms: MapReduce/offline/batch for latency insensitive cases Shared caches for lowlatency computations naturally partitionable data Tuplespaces/Grid movable code (at least for JavaSpaces or LISPbased solutions), customizable logic etc. Traditional messaging systems for orderingsensitive ... Search-driven Business Intelligence Kort om Searchdriven Business Intelligence Key features 70% of key data is unstructured. Realtime data Realtime alerts/action Good support for unstructured data file formats Rich correlation Schematic !BITheNextGenerationtiny.jpg thumbnail! How to do data ... Service categorization Service Manifest servicemanifest.jpg! Explanations to the Service Manifest I shall do one thing and one thing well To be able to reuse a service, the service has to have a tightly defined responsibility. Just think in terms og building Legoblocks. Some bricks makes ... Service Template - A2A Design rules compliance Design rule Description of compliance Last PAB discussion P1. A service shall have one named owner (x) (off) P2. A service shall provide documented business value (x) (off) P3. A service ... Service Template - ACS Design rules compliance Design rule Description of compliance Last PAB discussion P1. A service shall have one named owner (x) (off) P2. A service shall provide documented business value (x) (off) P3. A service ... Service Template - CS Design rules compliance Design rule Description of compliance Last PAB discussion P1. A service shall have one named owner (x) (off) P2. A service shall provide documented business value (x) (off) P3. A service ... Service Template - H2A Design rules compliance Design rule Description of compliance Last PAB discussion P1. A service shall have one named owner (x) (off) P2. A service shall provide documented business value (x) (off) P3. A service ... Service template common Unique Name Owner P1 P1. A service shall have one named owner Business Value P2 P2. A service shall provide documented business value \\ (short statement of value proposition) Responsibility P3 P3. A service shall ... Service templates Templates for documentation of categorized services Service Template H2A Service Template A2A Service Template ACS Service Template CS SOA - Service Categorization SOAServiceCategorizationv2.jpg! H2A Human to Application Services Human 2 Application Services is an implementation of a usecase/user story Implements one, and only one human actor A2A Application to Application Services Orchestrates services from several applications, typically ... SOA - Service Categorization FAQ How does this service categorization relate to OW SOA? This categorization is rooted in the OW SOA service categorization and extended from feedback from multiple sources and projects. It tried to communicate the fine lines somewhat more explicit to make it easier to understand ... SOA - Services and service invocation Most developers and architects I meet tend to define service == protocol endpoint which is wrong. I thought I might open up some eyes by describing the myriad of service invocation options we might have in a service oriented ... SOA Hype Chart SOAhype.jpg SOA Master Data Management Service Attribution: This work started on wiki.community.objectware.no http://wiki.community.objectware.no EDRMDS a SOA Master Data Management Service To allow standard software to coexist nicely with SOA and to reach SOA Maturity Level 2, we need to master our Business Objects.‏ EDR ... SOA Maturity Models and EDR-MDS Attribution: This work started on wiki.community.objectware.no http://wiki.community.objectware.no !SOAMM.jpg Software Development home of the Knowledge Management space. SOA Service Manifest KM:Service Manifest Service Categorization KM:SOA Service Categorization SOA Hype Chart KM:SOA Hype Chart Laws of SOA KM:Laws of SOA Real SOA ... System Strategy You need to select one of these strategies: # InHouse development silo application. # Tradespecific standard application. # Supplierstrategy: A single supplier (eg IBM, SAP) solves all problems. # Integrationstrategy: A selected few application are integrated. Eg DBsynchronization or ETL. # Servicesstrategy ...
T The Champion, the Chief and the Manager Successful product development projects are often characterized by having an enthusiastic product champion with solid domain knowledge, a visible and proud chief engineer and a clever and supportive project manager, and of course, a group of exceptional developers. From an organizational point ... Thou shall always revisit the architecture axiom - Clear and consistent responsibilities powers all great architectures Clear and consistent responsibilities powers all great architectures http://wiki.community.objectware.no/display/OWSOA/Clearandconsistentresponsibilitypowersallgreatarchitectures Thou shalt always be ahead of the project and know the risks and challenges before they arrive You must never say "I´ll TRY to be ahead of the team." > Then you are already behind Thou shalt always revisit the architecture axiom - Clear and consistent responsibilities powers all great architectures always important to stop and look at the big picture and the best guideline to an architect is to look at how the responsibilities are handled within the organization. As long as this is clear and consistent, you are always in the position to handle changes and new requirements. If the responsibility is fragmented allover, you ... Thou shalt be hands on Eat your own dogfood Implementing your own decisions will open your eyes to the flaws of your design and improve developer satisfaction Keep yourself updated to the tools currently in use. Software development is in a constant state of change Related articles ... Thou shalt be kept accountable for all architectural decisions Problem Organizational architects often tend to make decisions, building the main structure of a given domain. When the structure is built, the architect moves on to the next project or organization. Left behind are the people implementing the structure as requested. When when the structural problems ... Thou shalt lead by example architect role, contains a significant/dominating component of leadership as opposed to management. This is closely related to creating a learning organization architecture:Learning organization, beeing an example KM:Thou shalt lead by example and communication KM:Thou shalt never ... Thou shalt make consistent and balanced decisions throughout the organization Thou shalt make consistent and balanced decisions throughout the project Thou shalt never default to silver bullets or magic Thou shalt never default to silver bullets or magic, but always ensure that you have several alternatives before making a decision. When making an architectural decision it is important that architects always consider several possible solutions and consider their consequences ... Thou shalt never forget that your day is 80% communication and 20% technology Most of all major faults in project is not due to lack in planning and structure, but in lack of communications Hands on (coding) is communication As an architech you are responsible for the flow of consistent communication both to and from you fellow teamworkers, and to and from your projectcontext Thou shalt never micromanage project decisions an organisation's architect it is important to restrict yourself to making decisions that have measurable impact across the whole organisation. For example, it is not the organisation architect's role to dictate what logging libraray should be used on a project. However, it could be the organisation architect's role ... Thou shalt revisit and evaluate previous decisions You can't know everything at any given point in time. Lean ideas: Postpone decisions to the least responsible moment. Good/bad? References Use uncertainty as a driver http://97things.neartime.net/wiki/Use%20uncertainty%20as%20a%20driver by Kevlin ... Thou shalt sit and work together with the team - Thou art an integrated part of the team Coordinating architects must work with all teams within the project, while teach leads should focus on a single team Thou shalt strive to build a learning organization and culture Intro Learning culture References: http://wiki.cantara.no/display/IASA/Mintideralleredeoppbrukt5greptilenenklerehverdagforarkitekter hvis du ikke har fått noen tilbakemelding, så må du stoppe opp Thou shalt strive to create a learning culture fine to make mistakes, but it is not fine to not learn (from them) Why? Background, and a intro to how to implement can be found on Learning circle architecture:Learning circle Resources for better understanding Misplace prudence eats up any benefit from economy ... Thou shalt strive to find and understand your limitations References: Thou shalt revisit and evaluate previous decisions If there Is Only One Solution, get a second opinion, Timothy High http://97things.neartime.net/wiki/ifthereisonlyonesolutiongetasecondopinion Software architect has only lowercase a's deal with it, Barry Hawkins http://97things.neartime.net/wiki ... Thou shalt support and maintain functional and business data building blocks and communicate these to projects an organisation architect you have a unique overview over all projects that exist, are in progress, or are on the horizon and how each of these projects relate to each other. With this overview it is the organisation architect's responsibility to identify crossproject concerns that could potentially become building ...	U
V Value Delivered - Business Cases Attribution: This work started on wiki.community.objectware.no http://wiki.community.objectware.no "State of the art Enterprise Portal delivering value built on an Service Oriented Integration strategy realized through Enterprise Domain Repositories" IT Strategy Established a modern, flexible Service Oriented Architecture ...	W
X	Y
Z	!@#$