Comments for The Federal Architect http://www.federalarchitect.com News & Advice for the Federal Enterprise, System, and Solutions Architecture Community Fri, 19 Mar 2010 20:59:28 +0000 http://wordpress.org/?v=2.7 hourly 1 Comment on Cloud Computing: DISA’s Operational Perspective by JMMED2008 http://www.federalarchitect.com/2009/03/08/cloud-computing-disas-operational-perspective/comment-page-1/#comment-19 JMMED2008 Wed, 13 Jan 2010 17:39:42 +0000 http://www.federalarchitect.com/?p=65#comment-19 Where can this presentation be viewed? Where can this presentation be viewed?

]]> Comment on Effectively and Securely Using the Cloud Computing Paradigm by JMMED2008 http://www.federalarchitect.com/2009/03/19/effectively-and-securely-using-the-cloud-computing-paradigm/comment-page-1/#comment-18 JMMED2008 Wed, 13 Jan 2010 17:38:52 +0000 http://www.federalarchitect.com/?p=69#comment-18 Will NIST provide official guidance on securely using Cloud Computing in the future, especially since there are some organizations within DoD that have already implemented Cloud Computing. Will NIST provide official guidance on securely using Cloud Computing in the future, especially since there are some organizations within DoD that have already implemented Cloud Computing.

]]> Comment on Security Guidance for Critical Areas of Focus in Cloud Computing by JMMED2008 http://www.federalarchitect.com/2009/05/07/security-guidance-for-critical-areas-of-focus-in-cloud-computing/comment-page-1/#comment-17 JMMED2008 Wed, 13 Jan 2010 17:37:07 +0000 http://www.federalarchitect.com/?p=81#comment-17 What are considered the critical areas of focus within cloud computing? What are considered the critical areas of focus within cloud computing?

]]> Comment on Managing FISMA compliance with OpenFISMA tool by SpenceII http://www.federalarchitect.com/2009/05/04/managing-fisma-compliance-with-openfisma-tool/comment-page-1/#comment-16 SpenceII Fri, 04 Dec 2009 16:36:31 +0000 http://www.federalarchitect.com/2009/05/04/managing-fisma-compliance-with-openfisma-tool/#comment-16 As the official sponsor of the OpenFISMA Open Source initiative, Endeavor Systems (which I am a part of), always appreciates a shout out. Currently led by a team of four federal agencies, The OpenFISMA initiative is a collaborative, inter-agency, open source development project. We have had extraordinary success using OpenFISMA to streamline vulnerability management & FISMA reporting. We're always eager for additional partners, and would love to hear your thoughts. Thanks! Spence Witten Endeavor Systems As the official sponsor of the OpenFISMA Open Source initiative, Endeavor Systems (which I am a part of), always appreciates a shout out.

Currently led by a team of four federal agencies, The OpenFISMA initiative is a collaborative, inter-agency, open source development project. We have had extraordinary success using OpenFISMA to streamline vulnerability management & FISMA reporting. We’re always eager for additional partners, and would love to hear your thoughts.

Thanks!
Spence Witten
Endeavor Systems

]]> Comment on PKI (HSPD-12) for controlling access to your web applications by One Stop Portal » Moving to two-factor authentication in healthcare apps http://www.federalarchitect.com/2009/05/01/pki-hspd-12-for-controlling-access-to-your-web-applications/comment-page-1/#comment-14 One Stop Portal » Moving to two-factor authentication in healthcare apps Sun, 07 Jun 2009 19:57:27 +0000 http://www.federalarchitect.com/?p=75#comment-14 [...] expensive or difficult to implement. As I wrote in my recent Federal Architecture blog posting, the open source PKI Framework and WebCullis projects are changing that. It’s worth a [...] [...] expensive or difficult to implement. As I wrote in my recent Federal Architecture blog posting, the open source PKI Framework and WebCullis projects are changing that. It’s worth a [...]

]]> Comment on The value of architecture artifacts by cliffbdf http://www.federalarchitect.com/2008/08/29/the-value-of-architecture-artifacts/comment-page-1/#comment-10 cliffbdf Wed, 25 Feb 2009 01:05:44 +0000 http://www.federalarchitect.com/2008/08/29/the-value-of-architecture-artifacts/#comment-10 kpburk3's discussion of quality attributes is right on. As I point out in my book Value-Driven IT, most of the difficult issues in architecture have to do with non-functional requirements. Yet, so much effort goes into functional architecture. This is why one hears so often about data synchronization problems between systems, scalability problems, and so on. kpburk3’s discussion of quality attributes is right on. As I point out in my book Value-Driven IT, most of the difficult issues in architecture have to do with non-functional requirements. Yet, so much effort goes into functional architecture. This is why one hears so often about data synchronization problems between systems, scalability problems, and so on.

]]> Comment on The value of architecture artifacts by Carnival of Enterprise Architecture #12 - October 1, 2008 | Project Management Resources, Templates, Books, Tools, News :: PMToolbox http://www.federalarchitect.com/2008/08/29/the-value-of-architecture-artifacts/comment-page-1/#comment-7 Carnival of Enterprise Architecture #12 - October 1, 2008 | Project Management Resources, Templates, Books, Tools, News :: PMToolbox Sun, 05 Oct 2008 08:15:32 +0000 http://www.federalarchitect.com/2008/08/29/the-value-of-architecture-artifacts/#comment-7 [...] N­. Shah pr­es­en­ts­ The v­alue of­ architecture artif­acts­ post­ed at­ T­he­ Fe­de­ral­ [...] [...] N­. Shah pr­es­en­ts­ The v­alue of­ architecture artif­acts­ post­ed at­ T­he­ Fe­de­ral­ [...]

]]> Comment on Web Oriented Architecture (WOA) succeeding SOA? by Shahid N. Shah http://www.federalarchitect.com/2008/09/04/web-oriented-architecture-woa-succeeding-soa/comment-page-1/#comment-6 Shahid N. Shah Thu, 04 Sep 2008 13:54:49 +0000 http://www.federalarchitect.com/2008/09/04/web-oriented-architecture-woa-succeeding-soa/#comment-6 Not really, Dave -- no big differences in my opinion. It's almost the same thing. In face check out this link for a guy who thinks we've gone too far with WOA: http://www.infoq.com/news/2008/06/whoa-woa :-) Not really, Dave — no big differences in my opinion. It’s almost the same thing. In face check out this link for a guy who thinks we’ve gone too far with WOA:

http://www.infoq.com/news/2008/06/whoa-woa

:-)

]]> Comment on Web Oriented Architecture (WOA) succeeding SOA? by DavidHarmon http://www.federalarchitect.com/2008/09/04/web-oriented-architecture-woa-succeeding-soa/comment-page-1/#comment-5 DavidHarmon Thu, 04 Sep 2008 13:51:23 +0000 http://www.federalarchitect.com/2008/09/04/web-oriented-architecture-woa-succeeding-soa/#comment-5 The authors of RESTful Web services (Leonard Richardson and Sam Ruby) have been calling the new approach ROA for Resource Oriented Architecture. Is there a difference between ROA and WOA? The authors of RESTful Web services (Leonard Richardson and Sam Ruby) have been calling the new approach ROA for Resource Oriented Architecture. Is there a difference between ROA and WOA?

]]> Comment on The value of architecture artifacts by kpburk3 http://www.federalarchitect.com/2008/08/29/the-value-of-architecture-artifacts/comment-page-1/#comment-4 kpburk3 Fri, 29 Aug 2008 18:53:55 +0000 http://www.federalarchitect.com/2008/08/29/the-value-of-architecture-artifacts/#comment-4 At the practitioner level (actually building a system), my experience has been that architecture products add little value. If fact they can be quite a tax in a DoD program environment if one is changed with maintaining them. However, from a programmatic perspective, architecture artifacts can, if done appropriately be of very high value in communicating with oversight officials (and that brings funding). They can also bridge interrelated programs toward interoperability. For example when I was in Army Medical IT business in 1999-2001, the Medical and Logistics DODAF architecture products provided substantial means of aligning both programs and technical architecture. These views provided a lexicon for several communities of practice to communicate, collaborate and develop plans. Mark Maier’s work “The Art of Systems Architecting “ is the best I have seen, I actually ref to it every six months or so One of the key concepts I remember from hearing Dr. Maier speak was that Architecture is not about “views” or “perspectives” as many EA proponents advocate. *** It is an identification and measurement of Quality Attributes. *** What are the Quality Attributes of the system or enterprise under consideration, and how can we measure them? Architecture efforts must be able to address these questions. http://www.amazon.com/Art-Systems-Architecting-Second/dp/0849304407 At the practitioner level (actually building a system), my experience has been that architecture products add little value. If fact they can be quite a tax in a DoD program environment if one is changed with maintaining them. However, from a programmatic perspective, architecture artifacts can, if done appropriately be of very high value in communicating with oversight officials (and that brings funding). They can also bridge interrelated programs toward interoperability. For example when I was in Army Medical IT business in 1999-2001, the Medical and Logistics DODAF architecture products provided substantial means of aligning both programs and technical architecture. These views provided a lexicon for several communities of practice to communicate, collaborate and develop plans.

Mark Maier’s work “The Art of Systems Architecting “ is the best I have seen, I actually ref to it every six months or so

One of the key concepts I remember from hearing Dr. Maier speak was that Architecture is not about “views” or “perspectives” as many EA proponents advocate. *** It is an identification and measurement of Quality Attributes. *** What are the Quality Attributes of the system or enterprise under consideration, and how can we measure them? Architecture efforts must be able to address these questions.

http://www.amazon.com/Art-Systems-Architecting-Second/dp/0849304407

]]>