We are pleased to announce the call for papers for the 22nd Microsoft Architecture Journal.
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, Business Intelligence is top of mind for business and technology leaders.
For this edition of the Microsoft Architecture Journal, we are looking for interesting, thought-provoking, and insightful articles about effective architecture and Business Intelligence.
Some suggestions for Business Intelligence focus areas include (but are not limited to):
- Enterprise Business Intelligence strategy and architecture: 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.
- Embedding business insights into your applications: How to embed reports and analysis capabilities into your custom and line of business applications.
- Infrastructure and performance: Architectural considerations for BI & data warehouse solutions with high-volume, low-latency, low-cost access to data.
- End-user and self-service Business Intelligence: Empowering end users to build BI solutions with little to no dependence on IT while enabling IT to maintain monitoring & 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.
- Delivering an effective Business Intelligence project: Structuring an effective BI project, including building an effective team, requirements gathering, change management, customer-connected engineering, success criteria, etc.
If you like to share your wisdom and experience with Business Intelligence with the architecture community, this is your chance. To submit your proposal, please send the following before September 11, 2009:
- An abstract of between two and four paragraphs.
- A short list (2-3 items) of reader's takeaways from business and technical perspectives. This determines the relevance of your value proposition.
- A short bio (1-2 paragraphs).
- A list of previously published articles, if any.
Submissions must be made to
archjrnl@microsoft.com (we receive many submissions for each issue, so we encourage you to put time and thought into yours).
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:
- September 18. Acceptance notified.
- October 8. A first draft (possibly unfinished) is due.
- October 22. Final draft is due.*
- Mid December. The Journal containing your article is ready and published.
* We recommend that articles be between 2,500 and 3,500 words in length.
Send us your proposal or questions to archjrnl@microsoft.com. Good luck!
Do you accept submissions outside the “call for papers” period?
If you already have an idea for an abstract, we recommend that you wait for the next call before making a submission, subscribing this RSS feed or, better, the Architecture Newsletter.
Will I get paid for writing?
We do not currently pay authors for contributing to the Architecture Journal.
What are the guidelines for papers printed in the Architecture Journal?
We recommend that papers are between 2,500 and 3,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.
In case I contribute, who owns the article?
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.