The different perspectives are discussed between service designer and business architect, and the skills are documented which makes both of these roles successful.
Several very important concepts around transactions are explored, including that transactions exchange value and require a decision. The idea that a transaction comprises a request and response is introduced, and a number of examples are provided. Chapter 3 covers the concept of patterns, from Stonehenge to modern operational transactions.The six types of data are discussed, along with their interdependences. This chapter talks about the history of the transaction from ancient Sumer over 10,000 years ago to modern day computer systems. Chapter 2 has a title that I bet is unique to every business or technical book written over the last 2000 years: “Trading Sheep in Sumer”.There are some fantastic insights into Agile in this section, including the dangers of producing a ‘minimum viable product’. My favorite part of this chapter is the section titled the “Requirements Black Hole”. Chapter 1 introduces the challenges with turning requirements into applications.
Here is a quick summary of what’s inside the book: For example, the Request of a customer to purchase a product followed by the Response of assessing the customer’s eligibility to purchase, is very similar to the Request for a claimant to make a claim for an insured loss followed by the Response of assessing the claimant’s eligibility. A Transaction Pattern quoted from the book is “a generic combination of work tasks, grouped into phases, by which a transaction is initiated and processed.” One of the main ideas in the book is that if we can represent business transactions in the more generic form of a Request and a Response, we can build more flexible and useful applications.
#Age of rebellion books series
Agile isn’t making things any better, despite the many promises of quick delivery.Įmily, in working with a data architect, identifies a series of Transaction Patterns. There seems to be constant friction between those who need better applications and those that need to build and support those applications. Similar to what Chris Potts did with IT strategy and enterprise architecture with the FruITion trilogy, Lloyd and Graham did with Transaction Patterns in the new book, Emily’s Rebellion.Įmily is a business analyst who becomes frustrated with the current approach taken by IT and the business to develop applications. A great way to take a technical or business topic and make it an exciting read is to turn it into a story.
0 kommentar(er)
