Service Construction is the phase where the service is actually programmed. Artifacts from the design phase (WSDL, or other interfaces) are passed to the development teams along with the Service and Operation Cases. Together, these artifacts act as the specification for development. 

In the Service Design phase, we created Service Test Cases. These cases will be used by the development teams to verify quality deliverables. However, these cases do not replace the need for general purpose Unit Tests. 

From a work pattern perspective, service developers will be able to develop and release one operation at a time. The development teams do not need to wait until the entire service is developed. By releasing operations early, consumption and integration teams can begin testing the software and providing feedback. 

Service Builds need to focus on "The service as the unit of deployment". This means that they have to design services to be autonomously deployable units of work. In the past, organizations have built 'run on services', where large applications were service enabled but due to coupling in the code base were not able to be deployed as autonomous units. 

The final build needs to be well documented and published. If a service is designed properly, it is likely that the service will live for a long time. It must be easy to maintain by people other than the original development team.