In this IEEE article, authors talks about how a codesign methodology using modeling can benefit exascale computing systems with improved performance, power efficiency, and reliability. The five factors discussed in the codesign process are algorithms, application, programming model, runtime system, and hardware architecture.
BigLever, one of the few companies focusing on product line engineering, has recently appointed Dr. Paul Clements Vice President of Customer Success. Clements is well-known as one of the pioneers of software architecture in general and product line engineering in particular.
Behavior Driven Development (BDD) is being increasingly seen as an alternative way to approach Test Driven Development. SpecFlow and NSpec are popular frameworks for BDD in .NET. They help create test specifications that are easy to read even for non-programmers and allow the design of the software to be driven by it’s purpose.
Testing is an important means to obtain information about implementations. Likewise, code reviews help to keep the code quality high. What is very common for code, gets sometimes neglected for software architecture. But how can a project team test the architecture itself? Software architecture assessment represents an effective approach for introspecting and assessing software design.
It is four months since the SOA manifesto was announced; InfoQ interviewed the original author’s and in some cases pulled in their comments on the manifesto from the web to get a broad understanding of the manifesto, as well as provide insight into the goals of the participants, individually and as a whole, and provide transparency to the mechanics involved in putting together such an initiative.
David J. Anderson explains how to use predictability, measurement and change management to balance the factors of observed capability, staffing, and delivery targets to achieve predictable outcomes.
David Nolen critiques the tools, languages and methodologies used today from the perspective of solving the “mapping dilemma”, introducing match, a pattern matching library for Clojure.
Linda Rising talks about patterns and interacting with customers, the need for a better interaction between developers and customers, how she arrived at these patterns, teaching others how to teach.
In this interview Amr Elssamadisy talks about the practice of Agile software development and why it works. Elssamadisy said Agile processes work because developers are able to learn from their successes. Indeed, Elssamadisy said developers learn from both their mistakes/failures, as well as from their successes. Moreover, developers need to learn how to work with teams and to handle confrontation.
Scrum, arguably the fastest-growing Agile methodology, is well described in the original Scrum books, which tend to be read once and put aside. Scrum is a framework with simple rules. This Scrum Checklist will help you to remember these simple rules in the heat of daily work and stress. It enable you to create an enjoyable and productive work environment with your Scrum-Team.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.
Domain Driven Design is a vision and approach for designing a domain model that reflects a deep understanding of the business domain. This book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums.
