Chapter 1 - 잘 설계된 프로그램이 세상을 뒤흔든다
SOFTWARE ENGINEERING/Object Oriented Programming 2011. 3. 16. 19:081. 고객이 원하는 기능을 하도록 하자
=> 요구사항을 수집 및 분석
2. 객체지향의 기본원리를 적용
=> 중복코드를 찾고 객체지향 방식을 제대로 적용했는지 확인하자
3. 유지보수와 재사용이 쉬운 디자인을 위해 노력하자
=> 디자인 패턴과 원리를 적용
UDDI (Universal Description, Discovery and Integration)
WSDL (Web Service Description Language)
SOAP (Simple Object Access Protocol)
SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) as its message format, and usually relies on other Application Layer protocols (most notably Remote Procedure Call (RPC) and HTTP) for message negotiation and transmission. SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built.
As a layman's example of how SOAP procedures can be used, a SOAP message could be sent to a web service enabled web site (for example, a house price database) with the parameters needed for a search. The site would then return an XML-formatted document with the resulting data (prices, location, features, etc). Because the data is returned in a standardized machine-parseable format, it could then be integrated directly into a third-party site.
The SOAP architecture consists of several layers of specifications for message format, message exchange patterns (MEP), underlying transport protocol bindings, message processing models, and protocol extensibility. SOAP is the successor of XML-RPC, though it borrows its transport and interaction neutrality and the envelope/header/body from elsewhere (probably from WDDX).[citation needed]