in

ASP.NET Weblogs

.NET Brain Droppings

I'm a Microsoft Certified Architect (MCA)... Feel free to ask me about the program...

Long-Range Technical Plan Feedback

I'm currently working on our Long Range Technical Plan that maps out our group's long-term vision; out to 2008.  The audience is upper-management (so can't be super-technical), but it does need to provide a high-level roadmap of my groups technical vision.

I contributed to this document last year, but this is my first take at creating one, so I thought I would look to the community to help with ideas.  Anyone out there working on a long range plan similar to mine?  Anything I should include?  Below is a quick list of things that I've got so far:

2004-2006

  • WS-I compliance
  • Adherence of 4 (or 5) SOA tenets
  • Repeatability of development process (CMM level 2-3)
  • Department-wide data sharing strategy (web services, async messaging, replication)
  • SOA-based "Systems Integration" layer (and development strategy) for legacy applications
  • Async Service Communication Infrastructure (Federated Search, service discovery and selection, data transformation)
  • Single Sign On and unified security realm
  • Reusable client-side frameworks and glue
  • Indigo migration strategy

2007-2008

  • Longhorn migration strategy
  • This is where I need the most input!

Thanks for any ideas!

 

 

Published Mar 15 2004, 11:12 AM by dbrowning

Comments

 

Christian Romney said:

One suggestion. SOA tenets not tenants.
March 15, 2004 12:54 PM
 

Don said:

Damn Word spell checker... ;)
March 15, 2004 1:18 PM
 

Darrell said:

CMM Level 2 is Repeatable. CMM Level 3 is Defined. The difference is level 2 is on project management, and level 3 is on software engineering practices. Note that doing level 3 stuff (software engineering) before level 2 (project management) will not yield much benefit.

Repeatable. Basic project management processes are established to track cost, schedule, and functionality. The necessary process discipline is in place to repeat earlier successes on projects with similar applications.

Defined. The software process for both management and engineering activities is documented, standardized, and integrated into a standard software process for the organization. All projects use an approved, tailored version of the organization's standard software process for developing and maintaining software.
March 15, 2004 4:42 PM
 

Gabriel said:

Regarding the Longhorn roadmap, have a look at:
http://news.com.com/2100-7343_3-5211424.html?tag=nefd.top
May 13, 2004 7:11 PM

Leave a Comment

(required)  
(optional)
(required)  
Add
Terms of Use