﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <pubDate>Wed, 19 Aug 2009 12:00:00 GMT</pubDate>
    <lastBuildDate>Wed, 19 Aug 2009 12:00:00 GMT</lastBuildDate>
    <title>Architecture Journal - Call for Papers</title>
    <description>Microsoft’s Architecture Journal is a quarterly magazine, providing a world-class forum for the publication of unique articles on how good architecture can help create great implementations.</description>
    <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
    <copyright>Copyright(c) 2007-2009, Microsoft</copyright>
    <language>en-us</language>
    <item>
      <title>The Architecture Journal Issue 22 - Call For Papers</title>
      <description>&lt;div&gt; We are pleased to announce the call for papers for the &lt;strong&gt;22nd Microsoft Architecture Journal&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt; Information is at the core of a business’s ability to make effective decisions. Architecture initiatives that increase the quality, timeliness, and usefulness of information have a direct correlation to increased revenue and competitiveness. As a result, &lt;strong&gt;Business Intelligence&lt;/strong&gt; is top of mind for business and technology leaders.&lt;br /&gt;&lt;br /&gt; For this edition of the Microsoft Architecture Journal, we are looking for interesting, thought-provoking, and insightful articles about effective architecture and &lt;strong&gt;Business Intelligence&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt; Some suggestions for &lt;strong&gt;Business Intelligence focus areas&lt;/strong&gt; include (but are not limited to):&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Enterprise Business Intelligence strategy and architecture&lt;/strong&gt;: Effectively reconciling the explosion of data across Operational Data Stores (ODS) and Data Warehouses (DW), building BI solutions that consolidate and work across heterogeneous data sources, successfully leveraging MOLAP, ROLAP and HOLAP for analysis, and integrating enterprise data with integration services, and Information As A Service (IaaS) across on-premises and cloud models.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Embedding business insights into your applications&lt;/strong&gt;: How to embed reports and analysis capabilities into your custom and line of business applications.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Infrastructure and performance&lt;/strong&gt;: Architectural considerations for BI &amp;amp; data warehouse solutions with high-volume, low-latency, low-cost access to data.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;End-user and self-service Business Intelligence&lt;/strong&gt;: Empowering end users to build BI solutions with little to no dependence on IT while enabling IT to maintain monitoring &amp;amp; management of end user built solutions. Helping people access, visualize and model disparate data to improve their ability to quickly make decisions and take action.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Delivering an effective Business Intelligence project&lt;/strong&gt;: Structuring an effective BI project, including building an effective team, requirements gathering, change management, customer-connected engineering, success criteria, etc.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;&lt;br /&gt; If you like to share your wisdom and experience with &lt;strong&gt;Business Intelligence&lt;/strong&gt; with the architecture community, this is your chance. To submit your proposal, please send the following &lt;strong&gt;before September 11, 2009&lt;/strong&gt;:&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;ul&gt;&lt;li&gt;An &lt;strong&gt;abstract&lt;/strong&gt; of between two and four paragraphs.&lt;/li&gt;&lt;li&gt;A short list (2-3 items) of &lt;strong&gt;reader's takeaways&lt;/strong&gt; from business and technical perspectives. This determines the relevance of your value proposition.&lt;/li&gt;&lt;li&gt;A short &lt;strong&gt;bio&lt;/strong&gt; (1-2 paragraphs).&lt;/li&gt;&lt;li&gt;A list of previously &lt;strong&gt;published articles&lt;/strong&gt;, if any.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;&lt;br /&gt; Submissions must be made to &lt;a href="mailto:archjrnl@microsoft.com"&gt;archjrnl@microsoft.com&lt;/a&gt; (we receive many submissions for each issue, so we encourage you to put time and thought into yours).&lt;br /&gt;  &lt;br /&gt; After the call for articles has ended, everyone who has submitted an idea will be notified via e-mail as to whether their submission was accepted or not. If it is accepted, your article must follow this schedule:&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;September 18&lt;/strong&gt;. Acceptance notified.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;October 8&lt;/strong&gt;. A first draft (possibly unfinished) is due.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;October 22&lt;/strong&gt;. Final draft is due.*&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Mid December&lt;/strong&gt;. The Journal containing your article is ready and published.&lt;/li&gt;&lt;/ul&gt;&lt;div&gt;&lt;br /&gt;&lt;br /&gt; * We recommend that articles be between 2,500 and 3,500 words in length.&lt;/div&gt;&lt;p&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;Send us your proposal or questions to &lt;a href="mailto:archjrnl@microsoft.com"&gt;archjrnl@microsoft.com&lt;/a&gt;. Good luck! &lt;/p&gt;&lt;p/&gt;&lt;p/&gt;&lt;p&gt;&lt;b&gt;Where can I get more information?&lt;/b&gt;&lt;/p&gt;&lt;p&gt;Check out &lt;a href="http://msdn.microsoft.com/en-us/architecture/bb219087.aspx"&gt;this link&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>Wed, 19 Aug 2009 12:00:00 GMT</pubDate>
      <link>http://msdn.microsoft.com/en-us/architecture/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>The Architecture Journal Issue 21 - Call For Papers</title>
      <description>&lt;p&gt;The 21st issue of the Architecture Journal will be devoted to &lt;strong&gt;SOA Keys for Success&lt;/strong&gt;.&lt;br /&gt;&lt;br /&gt;While Cloud, Utility, and Green Computing trends emerge as probable candidates for the top of the enterprise IT agenda for the next decade, SOA undoubtedly has been the priority during this decade, and particularly during these five last years.&lt;br /&gt;&lt;br /&gt;The initial appeal of SOA came when the industry acknowledged how standards such as XML Web Services easily achieved decoupled levels of integration that were unseen on previous, complex attempts such as CORBA or COM.&lt;br /&gt;&lt;br /&gt;Then came the SOA rush, and a growing number of companies embarked on SOA projects while Web Services standards continued to evolve in order to close the gap in security, reliable messaging, and transactional integrity.&lt;br /&gt;&lt;br /&gt;Some years later, we can confirm that SOA has accomplished its promise of interoperability. But where SOA practitioners probably will disagree is on the total cost of ownership of this kind of project. We might find as many successful stories (on time, on budget, and straightforward) as not-so-successful stories (more expensive than projected, unforeseeable complexity, and so on).&lt;br /&gt;&lt;br /&gt; What are the factors that make the difference? We are calling for articles on:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;SOA practices&lt;/strong&gt;. Which ones determine the success—or failure—of a project?&lt;/li&gt;&lt;li&gt;&lt;strong&gt;SOA governance&lt;/strong&gt;. Running, monitoring, versioning: How better to serve services?&lt;/li&gt;&lt;li&gt;&lt;strong&gt;To ESB or not to ESB&lt;/strong&gt;. Angel or demon? When to consider it a fundamental piece? What about it should you get rid of?&lt;/li&gt;&lt;li&gt;&lt;strong&gt;From object to services&lt;/strong&gt;. Considerations to guarantee separation of concerns after shifting paradigms.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Enhanced SOA&lt;/strong&gt;. How alternative, complementary approaches such as Event-Driven Architecture (EDA), REST protocols, service virtualization, and others are helping SOA traverse the last mile of integration.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;SOA and The Cloud&lt;/strong&gt;. What SaaS, S+S, and related emerging delivery models have to offer to an in-house SOA investment.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;If you have ideas on these topics that you would like to share with the architecture community, this is your chance! To submit an idea for an article, please send the following by &lt;strong&gt;June 11, 2009&lt;/strong&gt;:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;An abstract of between two and four paragraphs that explains what the reader will get from your article with regard to the "&lt;strong&gt;SOA Keys for Success&lt;/strong&gt;" theme of the issue. If you like, you may submit on an alternative topic; we have published out-of-theme articles in the past. However, your chances of being selected might be lower.&lt;/li&gt;&lt;li&gt;A bio of between one and two paragraphs.&lt;/li&gt;&lt;li&gt;A list of your previously published articles, if any. &lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;/p&gt;&lt;p&gt;Submissions should be made via e-mail to &lt;a href="mailto:archjrnl@microsoft.com"&gt;archjrnl@microsoft.com&lt;/a&gt; (we receive many submissions for each issue, so we encourage you to put time and thought into your submission).&lt;br /&gt;&lt;br /&gt;After the call for articles has ended, everyone who has submitted an idea will be notified via e-mail as to whether their submission was successful or not. If it is accepted, your article must follow this schedule:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;June 17&lt;/strong&gt;. Acceptance notified.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;July 8&lt;/strong&gt;. First draft (possibly unfinished) is due.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;July 22&lt;/strong&gt;. Final draft is due.*&lt;/li&gt;&lt;li&gt;&lt;strong&gt;September 5&lt;/strong&gt;. Your article and the Journal are ready and published.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&lt;br /&gt; * We recommend that articles be between 2,500 and 3,500 words in length. We will ask you to sign a release form that gives Microsoft permission to reprint the article, although ownership of the article will remain with you.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;Send us your proposal, or contact us at &lt;a href="mailto:archjrnl@microsoft"&gt;archjrnl@microsoft&lt;/a&gt;.com if you have any questions. Good luck! &lt;/p&gt;

&lt;p&gt;&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Where can I get more information?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Check out &lt;a href="http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx"&gt;this link&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 20 May 2009 12:00:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>Microsoft Architecture Journal Issue 20 - Call For Papers</title>
      <description>&lt;p&gt;The 20th issue of The Architecture Journal will provide insights into &lt;strong&gt;how turbulent times affect architects and the new and challenging solutions they will need to create&lt;/strong&gt;. This issue will examine how Software and Infrastructure Architects can add value back to their business units through business alignment, IT optimization, externalization of services, and consolidation of redundant or obsolete solutions. &lt;/p&gt;

&lt;p&gt;&amp;#160;&lt;/p&gt;

&lt;p&gt;How can the IT architects help keep business alignment and efficiency in such scenario? We are looking for real world ideas such as:&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;Optimizing&amp;#160; software development and delivery (i.e. via enterprise agile process implementation or any other strategy)&lt;/li&gt;

  &lt;li&gt;Optimized deployment to low-cost desktop infrastructure (thru virtualization or any other technique)&lt;/li&gt;

  &lt;li&gt;What IT Operations consolidation strategies Infrastructure Architects should know about&lt;/li&gt;

  &lt;li&gt;Efficient communication between distributed teams (IT, users, etc)&lt;/li&gt;

  &lt;li&gt;Any other original idea based on past, local crisis contexts &lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&amp;#160;&lt;/p&gt;

&lt;p&gt;If you have ideas that you would like to share with the architect community on this topic, here is your chance! Follow the instructions below to send an abstract before the cut-off date and you could see your thoughts and ideas shared with over 62,000 readers, translated in several languages, and distributed at multiple conferences around the world! &lt;/p&gt;

&lt;p&gt;The cut-off date for abstracts for the next issue is &lt;b&gt;March 18th 2009&lt;/b&gt;.&amp;#160; If you are interested in making a submission, here are the details: &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;How do I make a submission?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;To submit an idea for a paper, please send the following: &lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;A 2 – 4 paragraph abstract explaining how your paper fits the &lt;b&gt;&amp;quot;Architecture in Uncertain Times&amp;quot;&lt;/b&gt; theme of the magazine &lt;/li&gt;

  &lt;li&gt;A 1 – 2 paragraph bio &lt;/li&gt;

  &lt;li&gt;A list of previously published articles &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Submissions should be made via Email to &lt;a href="mailto:archjrnl@microsoft.com"&gt;archjrnl@microsoft.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We receive many submissions for each issue, so we encourage you to put time and thought into the submission. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;When will I know whether my submission is accepted?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;After the call for papers has ended, you will be notified via Email as to whether your submission was successful or not. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;What happens if my submission is accepted?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;If accepted, you’ll have between 6 weeks to submit two drafts and a final version of your paper. These dates will be clearly communicated. Your first draft will be reviewed by an editorial board to ensure it is on message for the magazine. Your second draft and final version will be subject to both technical and copy editing. &lt;/p&gt;

&lt;p&gt;The magazine is generally available in print and online 4 weeks after final drafts are submitted. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;What are the guidelines for papers printed in the Architecture Journal?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;We recommend that papers are between 3,500 and 4,500 words in length – although we have accepted shorter and longer papers in the past. The article should be submitted using Microsoft Word. Diagrams should be submitted in either Microsoft Visio or Microsoft PowerPoint, and will be reformatted for the magazine. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Do I still own the work?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Yes. We ask you to sign a release form that gives Microsoft permission to reprint the article, but ownership of the paper remains with you, the author. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Will I get paid for writing?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;We do not currently reimburse authors for contributing to the Architecture Journal. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Will I get copies of the magazine as an author?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;After printing you’ll be sent 10 copies of the Journal for your own use.&amp;#160; Additional copies can be requested. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Where can I get more information?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Check out &lt;a href="http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx"&gt;this link&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 25 Feb 2009 12:00:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>Microsoft Architecture Journal Issue 18 - Call For Papers</title>
      <description>&lt;p&gt;The 18th issue of The Architecture Journal will be focused on &lt;b&gt;Green Computing&lt;/b&gt;. The ubiquity of technology services is leading to significant energy waste, in a world where increasing energy costs and the need to reduce carbon footprints are becoming an imperative.&lt;/p&gt;

&lt;p&gt;&amp;#160;&lt;/p&gt;

&lt;p&gt;We are looking for practitioner experiences and ideas on sustainable&amp;#160; IT environments and solutions, addressing issues such as the following:&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;What are, beyond theory, the actual green technology big bets?&lt;/li&gt;

  &lt;li&gt;What considerations must be taken when building a physical data-center? &lt;/li&gt;

  &lt;li&gt;How do environmental regulations impact architectural decisions?&lt;/li&gt;

  &lt;li&gt;What could you say about Green Business Intelligence? Do you have some pattern for collecting, managing, and enacting environmental data? What are the best BI and data practices for analyzing environmental metrics?&lt;/li&gt;

  &lt;li&gt;From a solution architecture perspective, what are the best practices for reducing environmental impact on business, employees, partners, and customers?&lt;/li&gt;

  &lt;li&gt;Last but not least, are we ready to talk about green application development best practices? Do you know real strategies, patterns to use fewer resources and improve efficiency?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&amp;#160;&lt;/p&gt;

&lt;p&gt;If you have opinions that you would like to share with the architect community on sustainable architectures, here is your chance! Follow the instructions below to send an abstract before the cut-off date and you could see your thoughts and ideas shared with over 62,000 readers, translated in 5 languages, and distributed at multiple conferences around the world! &lt;/p&gt;

&lt;p&gt;The cut-off date for abstracts for the next issue is &lt;b&gt;September 10th 2008&lt;/b&gt;.&amp;#160; If you are interested in making a submission, here are the details: &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;How do I make a submission?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;To submit an idea for a paper, please send the following: &lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;A 2 &amp;#8211; 4 paragraph abstract explaining how your paper fits the &lt;b&gt;&amp;quot;Green Computing&amp;quot;&lt;/b&gt; theme of the magazine &lt;/li&gt;

  &lt;li&gt;A 1 &amp;#8211; 2 paragraph bio &lt;/li&gt;

  &lt;li&gt;A list of previously published articles &lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Submissions should be made via Email to &lt;a href="mailto:editors@architecturejournal.net"&gt;editors@architecturejournal.net&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We receive many submissions for each issue, so we encourage you to put time and thought into the submission. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;When will I know whether my submission is accepted?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;After the call for papers has ended, you will be notified via Email as to whether your submission was successful or not. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;What happens if my submission is accepted?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;If accepted, you&amp;#8217;ll have between 6 weeks to submit two drafts and a final version of your paper. These dates will be clearly communicated. Your first draft will be reviewed by an editorial board to ensure it is on message for the magazine. Your second draft and final version will be subject to both technical and copy editing. &lt;/p&gt;

&lt;p&gt;The magazine is generally available in print and online 4 weeks after final drafts are submitted. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;What are the guidelines for papers printed in the Architecture Journal?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;We recommend that papers are between 3,500 and 4,500 words in length &amp;#8211; although we have accepted shorter and longer papers in the past. The article should be submitted using Microsoft Word. Diagrams should be submitted in either Microsoft Visio or Microsoft PowerPoint, and will be reformatted for the magazine. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Do I still own the work?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Yes. We ask you to sign a release form that gives Microsoft permission to reprint the article, but ownership of the paper remains with you, the author. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Will I get paid for writing?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;We do not currently reimburse authors for contributing to the Architecture Journal. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Will I get copies of the magazine as an author?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;After printing you&amp;#8217;ll be sent 10 copies of the Journal for your own use.&amp;#160; Additional copies can be requested. &lt;/p&gt;

&lt;p&gt;&lt;b&gt;&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Where can I get more information?&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;Check out &lt;a href="http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx"&gt;this link&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 20 Aug 2008 12:00:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>Microsoft Architecture Journal Issue 17 - Call For Papers</title>
      <description>&lt;p&gt;The next issue of the Architecture Journal will focus on &lt;strong&gt;Distributed Computing&lt;/strong&gt;. We are approaching an inflection point with today’s hardware and technologies where a vision from only a few years ago is becoming reality –from deploying applications on microscopic devices in our environment through to football-sized datacenters offering applications in the cloud. Whether small or large, distribution and concurrency of multiple services can introduce a number of challenges – the focus of this issue is to understand what these challenges are, and how they can be overcome.&lt;/p&gt;
&lt;p&gt;If you have opinions that you would like to share with the architect community on distributed computing, here is your chance! Follow the instructions below to send an abstract before the cut-off date and you could see your thoughts and ideas shared with over 60,000 readers, translated in 5 languages, and distributed at multiple conferences around the world! &lt;/p&gt;
&lt;p&gt;The cut-off date for abstracts for the next issue is &lt;strong&gt;July 28th 2008&lt;/strong&gt;.&amp;nbsp; If you are interested in making a submission, here are the details: 
&lt;p&gt;&lt;strong&gt;How do I make a submission?&lt;/strong&gt;
&lt;p&gt;To submit an idea for a paper, please send the following: 
&lt;ul&gt;
&lt;li&gt;A 2 – 4 paragraph abstract explaining how your paper fits the &lt;strong&gt;"Distributed Computing"&lt;/strong&gt; theme of the magazine 
&lt;li&gt;A 1 – 2 paragraph bio 
&lt;li&gt;A list of previously published articles &lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;Submissions should be made via Email to &lt;a href="mailto:editors@architecturejournal.net"&gt;editors@architecturejournal.net&lt;/a&gt;
&lt;p&gt;We receive many submissions for each issue, so we encourage you to put time and thought into the submission. 
&lt;p&gt;&lt;strong&gt;When will I know whether my submission is accepted?&lt;/strong&gt;
&lt;p&gt;After the call for papers has ended, you will be notified via Email as to whether your submission was successful or not. 
&lt;p&gt;&lt;strong&gt;What happens if my submission is accepted?&lt;/strong&gt;
&lt;p&gt;If accepted, you’ll have between 6 weeks to submit two drafts and a final version of your paper. These dates will be clearly communicated. Your first draft will be reviewed by an editorial board to ensure it is on message for the magazine. Your second draft and final version will be subject to both technical and copy editing. 
&lt;p&gt;The magazine is generally available in print and online 4 weeks after final drafts are submitted. 
&lt;p&gt;&lt;strong&gt;What are the guidelines for papers printed in the Architecture Journal?&lt;/strong&gt;
&lt;p&gt;We recommend that papers are between 3,500 and 4,500 words in length – although we have accepted shorter and longer papers in the past. The article should be submitted using Microsoft Word. Diagrams should be submitted in either Microsoft Visio or Microsoft PowerPoint, and will be reformatted for the magazine. 
&lt;p&gt;&lt;strong&gt;Do I still own the work?&lt;/strong&gt;
&lt;p&gt;Yes. We ask you to sign a release form that gives Microsoft permission to reprint the article, but ownership of the paper remains with you, the author. 
&lt;p&gt;&lt;strong&gt;Will I get paid for writing?&lt;/strong&gt;
&lt;p&gt;We do not currently reimburse authors for contributing to the Architecture Journal. 
&lt;p&gt;&lt;strong&gt;Will I get copies of the magazine as an author?&lt;/strong&gt;
&lt;p&gt;After printing you’ll be sent 10 copies of the Journal for your own use.&amp;nbsp; Additional copies can be requested. 
&lt;p&gt;&lt;strong&gt;Where can I get more information?&lt;/strong&gt;
&lt;p&gt;Check out &lt;a href="http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx"&gt;this link&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Fri, 11 Jul 2008 12:00:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>Microsoft Architecture Journal Issue 16 - Call For Papers</title>
      <description>&lt;p&gt;The next issue of the Architecture Journal will be focused on &lt;strong&gt;Identity Architectures&lt;/strong&gt;. As more organizations embrace a services based infrastructure, the need to manage the identities of users in an organization becomes more and more important. Issues that have been easy to manage in traditional environments need now to be considered from the perspective of services moving to the “&lt;em&gt;cloud&lt;/em&gt;”. 
&lt;p&gt;This can include fundamental issues that you may even be facing now, such as internal authorization strategies; not only for employees, but how do you include partners and customers?&amp;nbsp; More complex issues may include tiered access; what data is relevant to each user or user group?&amp;nbsp; How do you secure that data?&amp;nbsp; Is all identity data relevant in any circumstance or does it depend on the role of the user at any given time? How do directories compare to claims based authentication? What happens with multipart, distributed transactions? What about auditing in various contexts? 
&lt;p&gt;If you have opinions that you would like to share with the architect community on identity management, here is your chance! Follow the instructions below to send an abstract before the cut-off date and you could see your thoughts and ideas shared with over 60,000 readers, translated in 5 languages, and distributed at multiple conferences around the world! 
&lt;p&gt;The cut-off date for abstracts for the next issue is &lt;strong&gt;April 21st 2008&lt;/strong&gt;.&amp;nbsp; If you are interested in making a submission, here are the details: 
&lt;p&gt;&lt;strong&gt;How do I make a submission?&lt;/strong&gt;
&lt;p&gt;To submit an idea for a paper, please send the following: 
&lt;ul&gt;
&lt;li&gt;A 2 – 4 paragraph abstract explaining how your paper fits the &lt;strong&gt;"Identity Architectures"&lt;/strong&gt; theme of the magazine 
&lt;li&gt;A 1 – 2 paragraph bio 
&lt;li&gt;A list of previously published articles &lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;Submissions should be made via Email to &lt;a href="mailto:editors@architecturejournal.net"&gt;editors@architecturejournal.net&lt;/a&gt;
&lt;p&gt;We receive many submissions for each issue, so we encourage you to put time and thought into the submission. 
&lt;p&gt;&lt;strong&gt;When will I know whether my submission is accepted?&lt;/strong&gt;
&lt;p&gt;After the call for papers has ended, you will be notified via Email as to whether your submission was successful or not. 
&lt;p&gt;&lt;strong&gt;What happens if my submission is accepted?&lt;/strong&gt;
&lt;p&gt;If accepted, you’ll have between 6 weeks to submit two drafts and a final version of your paper. These dates will be clearly communicated. Your first draft will be reviewed by an editorial board to ensure it is on message for the magazine. Your second draft and final version will be subject to both technical and copy editing. 
&lt;p&gt;The magazine is generally available in print and online 4 weeks after final drafts are submitted. 
&lt;p&gt;&lt;strong&gt;What are the guidelines for papers printed in the Architecture Journal?&lt;/strong&gt;
&lt;p&gt;We recommend that papers are between 3,500 and 4,500 words in length – although we have accepted shorter and longer papers in the past. The article should be submitted using Microsoft Word. Diagrams should be submitted in either Microsoft Visio or Microsoft PowerPoint, and will be reformatted for the magazine. 
&lt;p&gt;&lt;strong&gt;Do I still own the work?&lt;/strong&gt;
&lt;p&gt;Yes. We ask you to sign a release form that gives Microsoft permission to reprint the article, but ownership of the paper remains with you, the author. 
&lt;p&gt;&lt;strong&gt;Will I get paid for writing?&lt;/strong&gt;
&lt;p&gt;We do not currently reimburse authors for contributing to the Architecture Journal. 
&lt;p&gt;&lt;strong&gt;Will I get copies of the magazine as an author?&lt;/strong&gt;
&lt;p&gt;After printing you’ll be sent 10 copies of the Journal for your own use.&amp;nbsp; Additional copies can be requested. 
&lt;p&gt;&lt;strong&gt;Where can I get more information?&lt;/strong&gt;
&lt;p&gt;Check out &lt;a href="http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx"&gt;this link&lt;/a&gt;.</description>
      <pubDate>04 Apr 2008 12:00:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>TechEd 2008 Call For Sessions: Deadline Is Just Few Days Away!!</title>
      <description>&lt;p&gt;The call for sessions tool is now open for the Architecture track at the &lt;a href="http://www.microsoft.com/events/teched2007/teched2008faq.mspx#developers" target="_blank"&gt;TechEd Developers conference&lt;/a&gt; (3-6 June 2008). If you are interested in being part of the Architecture track this year, please submit a proposal &lt;strong&gt;&lt;font color="#ff0000"&gt;before December 31st 11:59 PM PST&lt;/font&gt;&lt;/strong&gt;.&lt;/p&gt;</description>
      <pubDate>13 Dec 2007 17:02:00 GMT</pubDate>
      <link>http://simonguest.com/blogs/smguest/archive/2007/11/29/Speak-at-the-TechEd-US-Developers-Conference_2100_.aspx</link>
    </item>
    <item>
      <title>Microsoft Architecture Journal Issue 15 - Call For Papers</title>
      <description>&lt;p&gt;We've just put the final touches on Issue 14 of the&amp;nbsp;&lt;b&gt;Microsoft Architecture Journal&lt;/b&gt;, which goes to print later this month. As we head into the New Year, the theme of the next issue will be around &lt;b&gt;The Role of an Architect&lt;/b&gt;. This is the first time that we are going to&amp;nbsp;look at&amp;nbsp;the role and our profession,&amp;nbsp;and I'm excited to hear more about how you work, certification, career path choices, and the future of IT Architecture. &lt;p&gt;If you think you could write a great article for the Journal, here is your chance!&amp;nbsp;Follow the instructions below to send an abstract before the cut-off date and you could see your thoughts and ideas shared with over 60,000 readers, translated in 5 languages, and distributed at multiple conferences around the world!  &lt;p&gt;The cut-off date for abstracts for the next issue is&amp;nbsp;&lt;strong&gt;January 14th 2008&lt;/strong&gt;.&amp;nbsp; If you are interested in making a submission, here are the details:  &lt;p&gt;&lt;strong&gt;How do I make a submission?&lt;/strong&gt; &lt;p&gt;To submit an idea for a paper, please send the following:  &lt;ul&gt; &lt;li&gt;A 2 – 4 paragraph abstract explaining how your paper fits the &lt;strong&gt;Role of an Architect &lt;/strong&gt;theme of the magazine  &lt;li&gt;A 1 – 2 paragraph bio  &lt;li&gt;A list of previously published articles &lt;/li&gt;&lt;/ul&gt; &lt;p&gt;Submissions should be made via Email to &lt;a href="mailto:editors@architecturejournal.net"&gt;editors@architecturejournal.net&lt;/a&gt; &lt;p&gt;We receive&amp;nbsp;many submissions for each issue, so we encourage you to put time and thought into the submission.  &lt;p&gt;&lt;strong&gt;When will I know whether my submission is accepted?&lt;/strong&gt; &lt;p&gt;After the call for papers has ended, you will be notified via Email as to whether your submission was successful or not.  &lt;p&gt;&lt;strong&gt;What happens if my submission is accepted?&lt;/strong&gt; &lt;p&gt;If accepted, you’ll have between 6 weeks to submit two drafts and a final version of your paper. These dates will be clearly communicated. Your first draft will be reviewed by an editorial board to ensure it is on message for the magazine. Your second draft and final version will be subject to both technical and copy editing.  &lt;p&gt;The magazine is generally available in print and online 4 weeks after final drafts are submitted.  &lt;p&gt;&lt;strong&gt;What are the guidelines for papers printed in the Architecture Journal?&lt;/strong&gt; &lt;p&gt;We recommend that papers are between 3,500 and 4,500 words in length – although we have accepted shorter and longer papers in the past. The article should be submitted using Microsoft Word. Diagrams should be submitted in either Microsoft Visio or Microsoft PowerPoint, and will be reformatted for the magazine.  &lt;p&gt;&lt;strong&gt;Do I still own the work?&lt;/strong&gt; &lt;p&gt;Yes. We ask you to sign a release form that gives Microsoft permission to reprint the article, but ownership of the paper remains with you, the author.  &lt;p&gt;&lt;strong&gt;Will I get paid for writing?&lt;/strong&gt; &lt;p&gt;We do not currently reimburse authors for contributing to the Architecture Journal.  &lt;p&gt;&lt;strong&gt;Will I get copies of the magazine as an author?&lt;/strong&gt; &lt;p&gt;After printing you’ll be sent 10 copies of the Journal for your own use.&amp;nbsp; Additional copies can be requested.  &lt;p&gt;&lt;strong&gt;Where can I get more information?&lt;/strong&gt; &lt;p&gt;Check out &lt;a href="http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx"&gt;this link&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>11 Dec 2007 00:37:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>Just Released: Architecture Journal Reader (Beta)</title>
      <description>&lt;p&gt;Demonstrating many of the UX principles highlighted in recent issues, this reader is a locally installed application that enables you to take every issue of the Journal into a searchable, immersive, and easy-to-read experience. The application synchronizes with our content management services so that you'll automatically have access to the latest Journal issues without needing to download PDF files or checking online.&lt;/p&gt;</description>
      <pubDate>27 Nov 2007 12:00:00 GMT</pubDate>
      <link>http://www.microsoft.com/downloads/details.aspx?FamilyID=dd466bbb-1b7d-438e-9f9a-954ce2058f15&amp;displaylang=en</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>Microsoft Architecture Journal - Call for Case Studies</title>
      <description>&lt;p&gt;&lt;img style="border-right:0px;border-top:0px;margin:0px 15px 0px 0px;border-left:0px;border-bottom:0px;" alt="journal" src="http://simonguest.com/images/ArchitectureJournalCallforCaseStudies_CEE9/journal_thumb.jpg" align="left" border="0"&gt; Starting with Issue 14, the Architecture Journal will feature architecture case studies in each issue.&amp;nbsp; We will dedicate one or two pages in each issue to some of the most intriguing architecture projects worldwide, the lessons learned, what worked, what didn't, and so on.&amp;nbsp; We feel that this is a great way of both highlighting the work that you do, and enlightening readers about best practices in our industry. &lt;p&gt; &lt;p&gt;If you have a project that you would like to have featured in the next issue, please submit a short abstract (1 or 2 paragraphs) of the project to &lt;a href="mailto:editors@architecturejournal.net"&gt;editors@architecturejournal.net&lt;/a&gt;.&amp;nbsp; The abstract should contain an overview of the project, a description of what was so good (or bad!) about it, your bio and a summary of your role in the project.&amp;nbsp; We are looking for architecturally relevant cases, so the project does not have to be based solely on Microsoft technology. The submission deadline for Issue 14 case studies is October 1st.&amp;nbsp;  &lt;p&gt; &lt;p&gt;If selected, you will have around 4 weeks to write up the short article.&amp;nbsp; The maximum length of the article is 1,500 words, and diagrams that support the case study are recommended.&amp;nbsp; You will need to obtain permission from your company in advance and you will own the rights to the article, although you will be asked to sign a release form that gives us permission to print the case study in the Journal.&lt;/p&gt;</description>
      <pubDate>19 Sep 2007 12:00:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
    <item>
      <title>Microsoft Architecture Journal - Issue 14 Call for Papers</title>
      <description>&lt;p&gt;It’s been a crazy few weeks here, wrapping up the current issue of the &lt;b&gt;Microsoft Architecture Journal&lt;/b&gt;, which goes to print later this month. Due to popular request, the theme of the next issue (Issue #14) is going to be focused on &lt;b&gt;Mobile Architecture&lt;/b&gt;. I know that many of you are doing a lot of work in this area, and I’m looking forward to showcasing best practices, recommendations, and patterns for systems and designs that enable mobile connectivity.
&lt;p&gt;If you think you could write a great article for the Journal, here is your chance!&amp;nbsp;Follow the instructions below to send an abstract before the cut-off date and you could see your thoughts and ideas shared with over 55,000 subscribers, translated in 5 languages, and distributed at multiple conferences across the globe! 
&lt;p&gt;The cut-off date for abstracts for the next issue is&amp;nbsp;&lt;b&gt;Sep 7th&lt;/b&gt;.&amp;nbsp; If you are interested in making a submission, here are the details: 
&lt;p&gt;&lt;b&gt;How do I make a submission?&lt;/b&gt;
&lt;p&gt;To submit an idea for a paper, please send the following: 
&lt;ul&gt;
&lt;li&gt;A 2 – 4 paragraph abstract explaining how your paper fits the &lt;b&gt;Mobile Architecture&lt;/b&gt; theme of the magazine 
&lt;li&gt;A 1 – 2 paragraph bio 
&lt;li&gt;A list of previously published articles &lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;Submissions should be made via Email to &lt;a href="mailto:editors@architecturejournal.net"&gt;editors@architecturejournal.net&lt;/a&gt;
&lt;p&gt;We receive&amp;nbsp;many submissions for each issue, so we encourage you to put time and thought into the submission. 
&lt;p&gt;&lt;b&gt;When will I know whether my submission is accepted?&lt;/b&gt;
&lt;p&gt;After the call for papers has ended, you will be notified via Email as to whether your submission was successful or not. 
&lt;p&gt;&lt;b&gt;What happens if my submission is accepted?&lt;/b&gt;
&lt;p&gt;If accepted, you’ll have around 6 weeks to submit two drafts and a final version of your paper. These dates will be clearly communicated. Your first draft will be reviewed by an editorial board to ensure it is on message for the magazine. Your second draft and final version will be subject to both technical and copy editing. 
&lt;p&gt;The magazine is generally available in print and online 4 weeks after final drafts are submitted. 
&lt;p&gt;&lt;b&gt;What are the guidelines for papers printed in the Architecture Journal?&lt;/b&gt;
&lt;p&gt;We recommend that papers are between 3,500 and 4,500 words in length – although we have accepted shorter and longer papers in the past. The article should be submitted using Microsoft Word. Diagrams should be submitted in either Microsoft Visio or Microsoft PowerPoint, and will be reformatted for the magazine. 
&lt;p&gt;&lt;b&gt;Do I still own the work?&lt;/b&gt;
&lt;p&gt;Yes. We ask you to sign a release form that gives Microsoft permission to reprint the article, but ownership of the paper remains with you, the author. 
&lt;p&gt;&lt;b&gt;Will I get paid for writing?&lt;/b&gt;
&lt;p&gt;We do not currently reimburse authors for contributing to the Architecture Journal. 
&lt;p&gt;&lt;b&gt;Will I get copies of the magazine as an author?&lt;/b&gt;
&lt;p&gt;After printing you’ll be sent 10 copies of the Journal for your own use.&amp;nbsp; Additional copies can be requested. 
&lt;p&gt;&lt;b&gt;Where can I get more information?&lt;/b&gt;
&lt;p&gt;Check out &lt;a href="http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx"&gt;this link&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>15 Aug 2007 12:00:00 GMT</pubDate>
      <link>http://msdn2.microsoft.com/en-us/arcjournal/bb219087.aspx</link>
      <author>archjrnl@microsoft.com</author>
    </item>
  </channel>
</rss>