Home improvement
http://reviews.cnet.com/televisions http://www.hdguru.com
http://gizmodo.com/5067130/giz-explains-how-to-buy-an-hdtv-like-a-pro
from here: http://bluxte.net/musings/2009/01/11/removing-hdmi-overscan-sony-hdtv
Connecting the PC to the TV with HDMI showed a good amount of overscan: the viewable resolution was something like 1820x1030 pixels when the native resolution of the TV is 1900x1080, causing the borders of the PC's desktop to be cut, and even worse, causing the display to be blurry because of some image resizing happening somewhere.
setting on the TV side: Go to "Settings / Set-up / Screen settings / Display Area" and select the "Full pixel" option.
120Hz/240Hz
Response time (5 ms)
contrast ratio: ?
http://en.wikipedia.org/wiki/HD_ready
HD Ready(1280x720) / Full HD(1920x1080) / HD Ready 1080p
http://www.ehow.com/how_4530941_make-printer-wireless.html
http://answers.yahoo.com/question/index?qid=20061126055208AAfbCYU
http://www.dlink.com/products/category.asp?cid=10
http://www.the-ebook.org/rus E-books
Amazon: Guardsman #385000 Furniture Touch Up Kit
Slipstick CB840 Large Castor Cup Gripper
Arm Chair
http://www.iasahome.org/web/home/skillset
http://www.bredemeyer.com/Architect/RoleOfTheArchitect.htm
http://www.enterpriseintegrationpatterns.com/index.html
http://www.soapatternsbook.com/
http://www.enterprise-architecture.info/
http://www.cio.gov/index.cfm?function=showdocs&category=3
http://msdn2.microsoft.com/en-us/arcjournal/default.aspx
http://msdn2.microsoft.com/en-us/architecture/default.aspx
http://forums.microsoft.com/MSDN/default.aspx?ForumGroupID=58&SiteID=1
http://www.mail-archive.com/service-orientated-architecture@yahoogroups.com/
http://service-architecture.blogspot.com
http://msdn2.microsoft.com/en-us/library/bb419307.aspx
http://www.royans.net/arch/library/
Software architecture is the collection of fundamental decisions about a software
product/solution designed to meet the project's quality attributes, or architectural requirements. The
architecture includes the main components, their main attributes, and their collaboration (i.e.
interactions and behavior) to meet the quality attributes. Architecture can and usually should be
expressed in several levels of abstraction, where the number of levels depends on the project's size.
In order for a system’s architecture to be intentional, rather than accidental, it should be
communicated. Architecture is communicated from multiple viewpoints to cater the needs of the
different stakeholders.
As for architectural styles - Simply put, an architectural style to architecture is what a design
pattern is for design. The Software Engineering Institute defines an architectural style as "A
specialization of element and relation types, together with a set of constraints on how they can be
used."
The abstraction used to deal with complexity is called an architecture. An architecture is a system design that specifies how the overall functionality of the design is to be decomposed into individual functional components and the way in which these components are to interact to provide the overall functionality of the system. The decomposition of the enterprise into manageable parts, the definition of those parts, and the orchestration of the interaction among those parts constitutes the enterprise architecture.
Service orientation is a means for integrating across diverse systems. Each IT resource, whether an application, system, or trading partner, can be accessed as a service. These capabilities are available through interfaces; complexity arises when service providers differ in their operating system or communication protocols, resulting in inoperability.
Service orientation uses standard protocols and conventional interfaces—usually Web services—to facilitate access to business logic and information among diverse services. Specifically, SOA allows the underlying service capabilities and interfaces to be composed into processes. Each process is itself a service, one that now offers up a new, aggregated capability. Because each new process is exposed through a standardized interface, the underlying implementation of the individual service providers is free to change without impacting how the service is consumed.
There are numerous misconceptions about what SOA is—that it is a product that can be purchased (it is not; it is a design philosophy that informs how the solution should be built); that the goal is to build a SOA (it is not; SOA is a means to an end); or that SOA requires a complete technological and business process overhaul (it doesn’t; SOA solutions should be incremental and built on current investments).
SOA is also often equated with Web services, and the terms used interchangeably. While it is true that SOA is made easier and more pervasive through the broad adoption of Web services–based standards and protocols, the two are distinct. SOA is an approach to designing systems—in effect the architectural drawings or blueprint—that directs how IT resources will be integrated and which services will be exposed for use. In contrast, Web services is an implementation methodology that uses specific standards and language protocols to execute on a SOA solution.
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
http://users.rcn.com/jcoplien/Patterns/Top10OrgPatterns.html