For organizations with five or more servers, SHEEP is a Systems Integration Project built on standard-based prefabricated modules.

SHEEP interconnects any java capable systems and transforms your existing Intranet and the Internet in a giant Service Oriented Web, so you don't need to define a Service Oriented Architecture from scratch. Use It from web browsers, automate it with scripts, wrap it in web or standalone applications and harness the immensity of available ambient resources.

Unlike other Systems Integration packages and frameworks, SHEEP allows this using your existing staff, skill sets and procedures; furthermore SHEEP is intentionally kept granular, so each component can be used by the right person within the organization for better governance.
Easily taught, learnt, installed and operated, SHEEP is not only an efficient System Integration project, it is also a way to interconnect team members and partners just as well as computers.

Acronyms
• SI Systems Integration
• EAI Enterprise Applications Integration
• A2A Application to Application
• B2B Business to Business
• SOA Service Oriented Architecture

Definitions
• SHEEP: Organization friendly SOA, EAI and B2B project
• Interconnect any computer and interface any application!
  Compomentis extends Loose-coupling to de-coupling.
• Easily publish or populate your databases and other business information using web services.
• SHEEP eases and reduces the cost of managing eBusiness and Enterprise applications and allows the rest-of-us to achieve in days what a team of architects may not deliver in months.
• Http based methodology for fast development and deployment of small to medium scale EAI or B2B projects aiming at no more than 10 million transactions per server/day.
• Designed with business governance in mind, SHEEP projects separate IT logs from transaction logs down to the individual request.
  Designed with project managers in mind, a SHEEP based architecture can be quickly designed and prototyped by business analysts and developers.
  Designed with IT governance in mind, SHEEP projects can be deployed, automated and controlled by operations staff using native operating system commands.
  Designed with IT directors in mind, SHEEP projects don’t require lengthy and costly training and specialization. Existing staff adapt in a matter of hours and all methods and procedures are identical regardless of the operating system.

Acronyms
• J2EE Java 2 Enterprise Edition
• OOP Object Oriented Programming
• UML Unified Modeling Language
• MQ Message Queuing (aka MB Message Broking)
• ‘has-a’ object usage as opposed to inheritance being ‘is-a’
• OR Operational Requirement (aka NFR non functional requirement)

Definitions
• SHEEP is a healthy reaction to SOAP and J2EE elitism and is
  designed to put an end to the analysis-paralysis.
• SHEEP is an open specification Systems Integration project hosted by Compomentis Pty Ltd in Australia.
• SHEEP aims at facilitating web services consumption.
  SHEEP web services mimic a web browser’s ability to send forms and leverages from the ability of a web server to process them.
• By rigorously applying segregation of concerns and communication model layering, SHEEP allows building simple, robust and efficient architectures, that business analysts can rely on to deliver on their ideas without blowing the budget.
• SHEEP components are Web services implemented as plain-old-java-objects (POJO) and accessible from a command line, java and web applications with the same parameters! On all operating systems! Now, that’s handy!
• IT is not an excuse for developers to get more money! It is an actual business discipline and most of it is not performed by coders. SHEEP acknowledges this and is designed with operations, compliance and quality in mind. Components can be validated independently, audited at the technical and transactional level independently and configured and deployed with developers.
• SHEEP projects achieve phenomenal throughputs (2 million transactions per hour on a desktop over a cheap DSL link) and only require 5 to 10 hours of standard coding to develop from go to wow!

• Command line interface.
  Each module is designed to be command line enabled using named arguments. This allows operators to write short yet powerful scripts. This also allows calls from non-java programs.
• Standard Java Objects.
  J2EE is great, so are UML, XML, XSLT, Hibernate, Spring…
  But altogether their tutorials amount for over 4,000 pages…
  So, think easy and get web services before you get your PhD.
• Java Runnable interface.
  For those who did learn the lot…How about adding a Thread Pool and boost performance even further?
• Interfaces alignment.
  Regardless of how you use the components, parameters and arguments have the same name and definition, this eases dialogue between team members.
• Easy to audit and manage logs.
  Each transaction receives a pseudo-random id at the time of the request, this id is used to name logs that are persisted to the file system following a simple host/service/file organization.
• Standalone usage.
  How about just using someone else’s web service?
  Automate your downloads or your uploads.
  If the service works with a browser, it will work with SHEEP.
• Multiple operating system support.
  Windows, Mac, Solaris, Linux, i5/OS, OS/400…
  If java runs on it, then SHEEP runs on it.
• Multiple java level support
  Components are available by default at java level 1.4.2, then at level 1.5. Java 1.6 will enter production mid 2008.
• Everything is a file or a value
  SHEEP allows exchanging discrete values as key=value pairs.
  It also allows exchanging very large binary files.
  This is because SHEEP relies on http standards, not on XML.
• It is really fast
  No xml parsing, no extra protocol, buffered exchanges.
  exchanges 250Mb per minute on a wireless LAN.

Acronyms
• ROI Return On Investment
• COO Cost of Ownership
• HR Human Resources
• TTM Time to Market

top ten benefits
• Simplified Recruitment.
  SHEEP adapts to essential key skills, rather than require specialist ones.
  It eases 'one-man-jobs' just as well as structured team work.
• Simplified Training
  SHEEP interfaces simplicity is one of its key design elements.
  It is primarily designed to be operated, not programmed.
  Interface design precedence is scripting, html applications, web applications, java applications.
  User precedence is therefore operators, users, web developpers, java developers.
• Simplified Partnering.
  Even the best organized IT operation is on the back foot went addressing a partner's IT.
  Most of an IT culture comes from the method and tools they use, SHEEP uses http as a federating agent to facilitate dialogue in B2B, A2A and eBusiness projects.
• Faster Architecture.
  SHEEP acknowledges than 95% of the needs are in essence identical.
  It separation of concerns lends itself to prefabricated modules.
  It allows stopping to reinvent the wheel and simply assemble them.
• Faster and better Functional Design.
  SHEEP is an operational project.
  As a result, the team spends less time and money on integration (typically around 25% of budget and time).
  This budget can then be redirected to what really matters, Business Analysis and Functional Requirements.
  With technical concerns reduced, business analysts can then receive results not excuses.
• Faster and better Quality Management.
  Only a discrete number of architectural modules need controlling to ensure quality.
  Modules being decoupled, they can be tested in isolation (as opposed to tightly or loosely coupled ones).
  The quality and validation effort can be directed towards the business solution.
• Faster and better Auditing.
  The logging and auditing is intentionally kept in the file system.
  As a result, very little hardware and software equipment is required to manage auditing.
• benefit 8
  title.
  description.
• benefit 9
  title.
  description.
• benefit 10
  title.
  description.