I thought that this was a helpful overview:
The authors conclude:
... use RESTful services for tactical, ad hoc integration over the Web (à la Mashup) and to prefer WS-* Web services in professional enterprise application integration scenarios with a longer lifespan and advanced QoS requirements.
Without a master plan, an enterprise's architecture could end up like the
Sarah Winchester's house in the San Jose area.
When trying to committing document changes to TFS via TSWA (Team System Web Access), while uploading the revised changes, elect to overwrite.
The checkin-checkout mechnism of Tswa is slightly different from the Sharepoint portal. In order to do this:
- Checkout the file
- Download this file
- Make necessary changes and save
- Upload this file
- Check in
It is not possible to perform checkin, checkout operation within Word or Excel.
The undo \ redo MS Excel function is disabled for TFS tables. Haven’t found when this function will be added back in yet.
Two different friends are telling me the best water parks at the Wisconsin Dells are Great Wolf, Wilderness and Kalahari. Wilderness is a big and sprawling place with2-3 separate indoor parks. Kalahari is all under one roof and allows the public to pay for entry. Wilderness might now too. The kids prefer the game & play rooms at Wilderness – better & nicer hot tubs which go outside at Wilderness. Wilderness now has an outdoor tubing hill in winter.
How many gopher holes do you have? Will you choose to fill most of them up?
This is a great analogy for software development.
If an architectural review board was to be established, what would it do? Answer the following questions? (Paraphrased from
here.)
- Application Segment: Which segment is the application in?
- Emerging - New technology that may have a significant role in the organization, such as the latest trends in software development.
- Core - Technology that is core to the business, such as current standardized technologies that are mature and in wide use.
- Depreciate - Technologies that should not be used and existing implementations that should have a plan to remove.
- Banned - Forbidden technologies that should not be used.
- Identify relationships with other applications - consider operational aspects like information security, business continuity.
- Application modernization schedules - creating schedules around if and when applications should be reviewed.
- Standards - identification of the right and wrong standards used within.
- Project costs
- Quality attributes - consideration of non-functional attributes like security, risk, continuity, and performance.
- Impact on environment
- Resource requirements - gaps in technical ability? Gaps in what is supported versus what is not.
- Unique solution - Is there something similar already in the organization that can be re-purposed?
- Aligned with the build vs. buy processes and policies?
- Domains - Does this apply to the given domain only or multiple domains?