Good morning all,
Welcome to our February 8 Link Roundup. Here are some notable posts from other software engineering blogs that you may have missed this past week:
NServiceBus 2.0 Release Candidate 2 Available, by Udi Dahan at the Software Simplist. Udi’s post about the new release of NServiceBus details its major features, which include the ability to integrate transactional messaging into applications.
Most inane customer service #fail ever, by Phil Wainewright at Software as Services. Phil’s unfortunate experience with TeleWest provides some great guidance about service providers shouldn’t do.
Conversational Stories, by Martin Fowler at his own blog. Martin takes on some common misconceptions about Agile method.
California Needs the Cloud, by Ryan Nichols at CIO Blog. Ryan makes a call to action to the state of California to investigate using cloud computing for their check-processing systems, and provides examples of how other types of public agencies have used cloud computing to achieve great things.
Categories: SATURN Network
Registration is now open for the sixth annual SEI Architecture Technology User Network (SATURN) Conference, presented in collaboration with IEEE Software magazine in Minneapolis, Minn., from May 17 to 21.
The SATURN Conference is held every year to bring together experts from around the world to exchange best architecture-centric practices in developing, acquiring, and maintaining software-intensive systems.
Register for the conference and view the preliminary program at the SATURN 2010 website. SEI Members and subscribers of IEEE Software magazine get 15% off conference and tutorial fees.
Categories: SATURN Conference
Tagged: SATURN 2010, SATURN Conference, SATURN Network, SEI, software architecture
In a recent paper, Peter Feiler, technical lead and author of the Architecture Analysis and Design Language (AADL) industry standard notation, points out that more than 160 publications in refereed conferences and journals have been published about the standard since it was published in 2004 by SAE International. An updated version was published in 2009. In his research brief, Peter provides detail on the development of AADL and on MetaH, a precursor to the standard.
Categories: Architecture-Centric Engineering · Architecture-Centric Practices
Tagged: architecture analysis, model-based engineering, software architecture, system architecture
“SOA met its demise on January 1, 2009.”
That announcement in a Burton Group Application Platform blog is the starting place for many comments in the past year on the health of service-oriented architecture (SOA).
“The blog headline does say ‘SOA is dead,’ which is wrong. But the part of the headline that few people note is ‘long live services,’” according to Grace Lewis, a senior researcher at the Carnegie Mellon Software Engineering Institute (SEI). Lewis and others have developed a research agenda for SOA (View a presentation on the agenda.)
While wrong in writing off SOA, the obituary does point out something important for the future. “We need to move away from considering SOA as a set of technologies to embrace service-orientation as a way to design, implement and deploy systems,” Grace says.
Grace points out that these “pillars of SOA adoption” are essential for success with SOA:
- alignment with mission and business goals
- instantiation of principles of SOA governance
- evaluation of relevant technologies for SOA implementation
- recognition that SOA requires a different mindset than traditional development
All in all, “The technologies to implement SOA will most probably change over time, but the concepts will remain,” Grace predicts.
Categories: Service-Oriented Architecture
Tagged: Service-Oriented Architecture, SOA
I am working with Bursatec, the technology company of the Mexican stock exchange on the architecture design for a new system. Bursatec is using the SEI’s Attribute-Driven Design (ADD) method embedded in a Team Software Process (TSP) environment for designing the new system. They also use the tool “Enterprise Architect” for documenting the system’s software architecture.
Last week, when working with Bursatec’s architecture team, they showed a nice little rule they implemented for using the design tool. Since I believe that many architects have the same problem when using a design tool, I thought it would be worthwhile sharing their solution. Keep reading →
Categories: Architecture and Agile · Architecture-Centric Engineering · Architecture-Centric Practices
Tagged: software architecture, ADD, attribute-driven design, UML, SEI, documentation, software design
January 15, 2010 · 1 Comment
Research discussed at WEUSE V: The 5th Workshop on End-User Software Engineering indicates that, in the US, there are about four times as many people who do programming at work (12 million) as there are professional programmers (3 million). Add in another 55 million of us who use spreadsheets and databases (and thus may also be considered to be doing programming) on the job, and that means there’s probably a lot of undependable, error-riddled software being created. As workshop participants noted: “When the software that end users create is not dependable, the people whose retirement funds, credit histories, e-business revenues, and even health and safety rely on decisions made using that software can face serious consequences.”
The workshop participants discussed end-user programming with a specific focus on the software engineering that is required to make it a more disciplined process, while still hiding the complexities of greater discipline from the end user. Proceedings from the workshop are available in a report at http://www.sei.cmu.edu/library/abstracts/reports/09sr015.cfm.
One approach reported on in the workshop: distributed cognition, advanced by Margaret Burnett et al. From the SEI report: “Thus, instead of trying to build systems that solve this type of problem: ‘What can the system figure out automatically so that users need not think too hard?’, [the] distributed cognition perspective is that the problem statement becomes: ‘How can end-user software engineering tools help end users think?’ “
Categories: Architecture and Agile
Tagged: Agile Alliance, end user programming, software engineering
Good morning all,
Welcome to our January 11 Link Roundup. Here are some notable posts from other software engineering blogs that you may have missed this past week:
Architecture for a New Decade, by Peter Cripps at Software Architecture Zen. Peter notes that three of the top ten strategic technologies for 2010 include cloud computing, advanced analytics, and social computing.
Tips from 2009 for a Prosperous 2010, by Phil Wainewright at Software as Services. Phil reflects on viral marketing, predictable and diversified revenue streams, as well as the importance of a strategy that includes real business value for both investors and consumers.
Trends for 2010, by J.D. Meier at J.D. Meier’s Blog: Software Engineering, Project Management, and Effectiveness. J.D. outlines a roadmap of software engineering for 2010 and beyond.
REST: Tying AJAX to the Cloud, by Martin Heller at Strategic Developer. Martin sees 2010 as the year of AJAX and REST services, and examines the difference between the “cloud” and the “server.”
Categories: Architecture-Centric Engineering · Service-Oriented Architecture
Tagged: cloud computing, software engineering
