Pokazywanie postów oznaczonych etykietą book review. Pokaż wszystkie posty
Pokazywanie postów oznaczonych etykietą book review. Pokaż wszystkie posty

wtorek, 22 stycznia 2008

Surely You're Joking, Mr. Feynman! - Book review

Mood: Lack of sleep

There is a question, somewhere deep in my head: Is it possible that Leonardo da Vinci has bored just once per whole civilization? Is there truely no place nowadays for real "renaissance person", who has some achievement in more than two,three disciplines? The book is the answer for the question: definitely there is at least one such a person - Mr. Feynman.
The book describes the incredible life of open-minded person, who can during one life do the following:
  • learn to repair radio as a thirtenn years old child
  • how to learnd italian quickly :D
  • take a part in Manhattan project (atom bomb) - surprisngly he writes the most about how the life in Los Alamos looked like, than about his real work. It seemes like he worked more in nearby factory in Oak Ridge, than in Los Alamos ;)
  • open locker, wardrobes and safes (I need to remember 25-0-25 and 50-25-50)
  • how to make impression on women in bars (do not pay for them silly)
  • how to earn money in Las Vegas
  • how to be friend of big fish in Las Vegas
  • try to repair Brazilian schollar system
  • play on pandeiro and frigideira (whatever it is) and took a part in Carnival celebration as the samba school member. Hotel boy screaming - "O PROFESSOR!"
  • learn why you should not earn too much
  • paint
  • why to be in touch with people from other disciplines and not to go for the interdisciplinar conferences discussing general topics
  • get Nobel prize (it sounded like the ceremony was the worest challenge)go through the hell of scroing US school books
  • how to play hald-professionaly on the drum for the ballet

So when you read the list there may be the following feelings in your head.

  • Did he really do these things? Yes.
  • Is he a megaloman? A little.
  • Why I hear the surname for the first time? I was surprised as well :)

As you can see making the extract from the book, which is the extract from such a rich life, like the Feymann's one, gives the odd results. Nevertheless what was the most inspring in this all - Feynman has always very pratical approach and even when he speaks about VERY complicated things (including philosophy), everything is served in straightforward way (without a single formula).

  • You can not be the professor Mr. Feynman.
  • Why?
  • Because I understand everything what you are saying.

On the other hand the book is simply SMART. It contains plenty of tips&tricks including not only "uncommon integration" (how you can gain from possesing the other toolkit), but also "how to cut massive number of string beans" or "how to deal wit a women". What is truely inspring it desribes the things AS-THEY-ARE and not with rounded words, so you can find even once a crossword on f, when he speaks about the government :D

He was also the one, who reminded me that if you want to achieve something in long term, you need to be honest in front of yourself and when you present the results of your work you must present ups and downs.

And at least, but not at last - the book is hilarious, so you enjoy reading it. It will be definitely well spent 11$.

Score: 6/6 (very good)

piątek, 5 października 2007

Advanced Project Management- Herold Kerzner

Mood: Sick
Soundtrack: Relax and take it easy (video clip is horrible, so this is why I prefer to display just cover :))

The book is definitely the must to read for any manager or leader in middle size or big organization (not only from IT sector). It is very visible, that the author put the strong effort in collecting the experiences from big number of companies. It is a pity that number of companies did approve publishing, but the list of contributors is very impressive anyway and it includes the brands like Sun, CA (all their procedures are published in appendix D! p733), HP, Nortel, Erricson and ABB. Sometimes the author allows treating the pages of his book as the free commercial for these companies, but usually the valuable information is passed including even some sample forms. Each chapter is full of samples from real life of the company with sweat and pain scenarios (the second one usually under the cover) – that type of approach gives that book a special, unique taste. Usually that type of book is saying you in rounded words what should be done, but this book says you also how. It covers a very wide angle of topics starting from the document flow systems, organization structures and finishing at some aspects of corporate politic.

When you start to cooperate with some organization, your first step should be formal or informal analysis of the situation. There are some samples of self-surveys (p653) and strong input for preparation employee survey - case 5, appendix I (p787), but the most interesting is the 2nd chapter defining the 5 levels of project management culture:
• Embryonic
• Accepted by directorate
• Accepted by managers
• Growing
• Adult
There is number of samples, definitions and methodologies, but the most useful will be the appendix B and C, giving you ready to use surveys to find out, on what level your organization is. If you need some guidelines in the area, the part 5.14 (p.248) contains some auto commercial about the Kerzner tools used for such The Growing and Adult stage are also broken into the pieces within 5 levels of Project Management Maturity Model (p239)
• Common language
• Common processes
• One methodology
• Competitors analysis
• Constant improvement (nice checklist in chapter 14.7 – p. 600)

Chapter 4 is giving you number of interesting samples from various companies, which worked out their own methodologies basing often on PMBoK. Prince2 is mentioned much more rarely and it seems like just Sun use it (p676). It was also interesting to read that Sun created originally RUP methodology. Anyway, there are not many books, which are brave enough to say that there is no golden rule and each company must create their own methodology. The IT fellow will find some well-known spots like Microsoft’s MSF methodology (p160), but most of the samples are quite fresh. The CIGNA sample (p138) was very good showing very well the linkage between the process and project plan. Intel (p147) enlists in details how the magic happens in real life, focusing on the document management. The list of critical aspects, when creating the methodology (p146) is also very valuable, but the best is the DePICT methodology from Exel (p153). It was the only company brave enough to publish their own document templates. Bravo!

Except strict project management the book covers also the general organization management issues including the Project Portfolio Management in chapter 7. The most interesting were the processes of choosing the projects for realization and two matrixes at drawings 7.6 and 7.7 (p308).

The 8th chapter is about the Project Management Office. I must admit, it was the first time I see so good PMO portraiture. Definitely, each organization has different understanding of PMOs and it is presented in part 8.4, but list of duties (p.334) seems to be common for most of them. Again, the chapter shows the real life situations starting from project approval mechanism like the 3 level recommendation mechanism (p354), closing at the sample template of document, which closes the project (p340) and set of sample postmortem questions (p360). Unfortunately, the implementation of documents management systems, which is in PMO duties, is not covered. The only things, which can be found, are some general drawings in chapter 16 (16.4 p647 and 16.5 p648), which shows document libraries structures on intranet sites. It would be great to see more in the area.

Very often, the risk management is neglected and that is probably why the author creates the whole chapter 9 just about that. He treats it in the complex and process way (checklist at p402), gives great ABB potential risk list (p413) and Motorola’s risk management system (p428) plus focus strongly on change management (p418).

I mentioned about the politic at the beginning, even if the book does not mention the word. That is known, however that half of success is to know what to do and the other half is to find a way to implement the change. The book give you a lot of tips how to fight with the resistance against the change, which exists often in big companies. The book mentions the interesting change management preparation list (p 243) and cool “basket team” scenario (p443), which shows that there will be always the person, whom you will not be able to change. The whole chapter 11 is discussing how to win the directorate attention. The sponsor or sponsor committee institution seems to be the best for it and chapter 11.2 contains some nice proves for it (p483).

To avoid accusation for being paid for this review, I must also to say a couple of bad things about the book. In some moments the author is trying to prove that some periods in history was about some particular stages in organizations grow. It went too far and drawings like 1.3 (p23) saying e.g. that the year 1994 was about “Cost analysis of live cycle” is simply funny. This is invalid tone, which can be heard through the whole book. Luckily, it is not in the mainstream and it can be ignored. The other disadvantage is, that there are some moments where the book is just the flood of words like the chapter 12 treating about trainings. The book would be as good as it is without this chapter.

On the other hand, the book shows definitely how wide the topic is and sometimes the mechanisms are just mentioned without further description:
• Statement Of Work (p196) – part of scope management
• Work Breakdown Structure (p196) – tasks management
• S curve (p196) – cost management
• Responsibility Assignment Matrix (p197) – responsibility management
As book has already over 1000 pretty well used pages, there is no space for blaming the author. See just for a second how often have I used the words sample and “in practice” – it describes the best the content of the book.

Score: 5.5/6 (very good)

The numbers of pages are based on polish translation of the book and they may be different in english version.

piątek, 17 sierpnia 2007

Understanding Public-Key Infrastructure - Carlisle Adams, Steve Lloyd

Introduction
The book is one of not too many, complex publication about PKI. It starts from explaining the asymmetric encryption idea and why such a solution is better than a symmetric encryption; this part includes also the general description of the most popular algorithms for both symmetric and asymmetric method. Then it describes quite clearly what kind of infrastructure is necessary to provide such solution and how it works. There are also mentioned the most popular services, issues and decisions linked with the PKI.

The content
The very strong positive aspect of the book is the practical approach. On page 59 it describes in details the full range of services within the PKI Infrastructure (Table 5.1), but there are also 4 other variants, where just the subset is implemented.

The chapter VII describes in details all the procedures implemented by the PKI like the Initiation, issuing, revocation plus renewing and archiving. It discuss also the communication with CA (Certificate Authority) and eventual use of RC (Registration Center). It covers also the transportation issues of public key where following solutions are possible:
· Publication out-of-band via the external channels
· To and from the public storages and databases, which provides them on the request and update in real time
· Network transport with communication protocols like secured email (S/MIME)

Chapter VIII on page 107 starts discussion about the various CRL implementations including distributed, delta CRLs and CRT tree. The description includes enlisting the benefits comparing to the basic solutions. The chapter describe also the OCSP solution, which provides the on-line and real-time solution on the top of CRL.

Chapter IX contains the interesting review of trust models. At looks like the unnecessary topic, but in fact it provides the input for quite important decisions about the shape of CA tree. Tree is in fact just the first considered model, where the next ones are based in general on cross-trust mechanisms (distributed trust).

The chapter X contains interesting discussion about the necessity of use number of key pairs for various applications and it mention SEIS (Secured Electronic Information in Society) regulations suggesting three of them:
· For encrypting and decrypting
· For signing and verification of users identity for general purpose
· For signing and verification of users identity where uniqueness of identity is the must
And it also covers the options about the storages for certificates, where LDAP is the most popular.

Chapter XXI will be great help if you need to convince decision maker about the necessity of using PKI. The most popular applications are described right there. When you start to implement the solution XXII will be at great help as all the major questions are there enlisted.

Conclusion
The book explains in details how the PKI works. I must say, that understanding the asymmetric idea, I still had a problem with understanding what for exactly the private and public key are used and how the whole thing works. There is no too many publication which explains in details and in practice how the infrastructure works – the book does it. It is a great starter for anybody involved within the PKI project as a user, project manager, programmer, supporter or team mate.

Also most of the topics around are covered including the legal issue (however it says just about US legislations).

It also shows the biggest problems linked with PKI solution putting a stress especially on decisions flexibility versus security. Number of problems may be solved with usage of the solution, but there is no golden rules and must to follow procedures. Most of things mentioned in the book must be customized per particular company and application.

Score: 4 (good) /6

poniedziałek, 6 sierpnia 2007

"Leadership the challenge" - book review

Mood: Relaxed
Soundtrack: I am easy like Sunday morning

Introduction

The book tries to be the ready to use recipe for the success by being the superior leader. The whole story is based on the axis of 5 practices and 10 commitments enlisted on page 22:
  • Model the way – Find your inner voice, Be the example of the shared values
  • Inspire a Shared Vision – Envision, enlist others in a common vision
  • Challenge the Process – seek for innovations, search for constant small improvements
  • Enable Others to Act – promote cooperative goals and building the trust, strengthen others
  • Encourage the Heart – appreciate individual experience, celebrate the values and victories
Each of these things are described in details in the following chapters with big number of real stories and examples.

The body

The 5 practises, seems to be a little bit pumped up and the best part of the books are actually short stories and tactics rather than “way of living”. The book says in number of places, as on the page 99, that leading by the story telling is very useful and practical technique. Page 381 mentions the David Amstrong’s book, which contains the collection of
“285 stories […] organized around the themes such as “stories that kick start
urgency”, “stories to make people brave and wise”, “stories about core values”,
“stories to inspire innovation””!
The book tries to be something more, but in fact, it seems that is the competitor of that book.

Instead of describe each practice or commitment, I will describe the best stories and tactics. The stories will be scored:
1 is I need to mention it, but nothing else
3 is I need to remember it
5 is Good story
7 is Very good story
9 is Excellent story

The stories

Lindsay’s story about the customer service – page 5; score 5
Lindsay highly improved the customer service in repair vehicles sector (women manager in man world) – couple of weeks after reading the book I remember the sample of the worker who drove hundreds of kilometers to pass the repaired car to the customer. Oh Lord, how much I would love to be their customer! The morale of the story is quite trivial: “it is always about the people”… way it is still forgotten?

Szwarzkopf’s story about the team-building – page 87; score 6
The story is about the new recruits coming into the base. The experienced officer “looking like from Olympics”, run with his team much more than the recruiters used to. The effect is that recruiters run much behind the leader. Szwarzkopf takes the officer on a side and explains him how the new soldiers feels like – they are first day in a new place, first morning run, they try to do us much as they can, then they try more, then they try even harder and they their lungs can not keep the tempo… Their leader, their officer does not even look behind. Where is the team spirit? Where is the unit cohesion? Of course, Szwarzkopf is successful in his couching action and he can see “the light dawned on the captain’s face”. He knew also that “the episode would get talked about around the base”. Ehhh… soldiers :)

Treyz’s Disney story about baking the client – page 88; score 8
Treyz speaks about the ABC-Disney negotiations. Negotiations were hard and long. What unique has happened in here was the personalized customer treatment. During on-going negotiations, Walt Disney (the president) took the Treyz’s wife Janet for whole-day-long personal tour guide to the Disneyland and after the amazing day, he provided Treyz’s kids the personalized gifts (among others Pinochio). The whole effort paid back triple during the on-going ABC-Disney negotiations (Janet convinced the husband to do the deal), couple of years later during the next and the next deal. The power of the personalized customer treatment is proved as nowhere else.

Geof Yang’s story “Vision for the leader is like the vision for the driver” – page 113; score 7
“Imagine you are driving along the Pacific Coast High-way heading south from San Franciso on a bright, sunny day. The hills are on your left; the ocean, on your right. On some curves, the cliffs plunge several hundred feet to the water. You can see for miles and miles” – you have vision, “you are cruising along at the speed limit”.
“Suddenly, without warning, you come around a bend in the road and there’s blanket of fog as thick as you’ve ever seen it”. What do you do? […] I slow way down” – well, you would be stupid to drive fast if you have no vision.
Delicious!

Janus effect – page 119; score 6
When drawing the vision, if you look first on your rear-view mirror you feel much more confident about the future predictions. There is a table 5.1 giving you some hard numbers for it – people asked about prediction gave you on average 3.2 years timeframe instead of to 1.8 years. Before making any vision, think for a while how the previous, similar project in the company or somewhere else looked like!

King’s speech “I have a dream” quoted at page 146; score 7
The whole speech is quoted. Before reading it, I though it is the exaggeration, but during and after… It is truly a great speech.

Ritz’s daily lineup meeting at page 180; score 5
Quick 15 minutes meeting is one of the key points for the agile methodologies. It is funny thing to see it in the Ritz chain across the whole glob. Funny and teaching… and making you to remember to keep the routine done, wherever you are and regardless from the size of your team.

Physicians story about listening more than speaking at page 187; score 9
“The Journal of the American Medical Associations reported on a five-year investigation of why some doctors were sued, and the others not, by parents who had all experienced the same tragedy (the death of their child during childbirth). […] “Physicians who had been sued frequently were perceived by their parents as unavailable, rushed, unconcerned, and poor communicators, while physicians with no malpractice claims were perceived as most available, interested, through, and willing to provide the information and answer questions fully.” Clearly, listening deeply makes a difference.”
If the kid asks why the man has two ears and one mouth, it is the answer. If you are not sure if you keep the proper listen/talk ratio ask somebody about noting it, during some longer meeting.

Urban’s ski story “you must fail to learn” at page 215; score 10
It was the first day of skiing classes. I skied all day
long, and I didn’t fall down once. […] I skied up to the ski instructor, and I
told him of my great day. […] He told me, “Personally, Urban, I think you had a
lousy day […] If you are not falling, you are not learning
Desmond Tutu incremental approach at page 228; score 3
“You can’t eat the elephant with one bite” and if you count 100 cards it seem to take much more effort comparing to counting 10 times 10 cards.

Axelrod strategy at page 254; score 10
“Two parties (individual or groups) are confronted […] they must decide whether or not to cooperate […] There are two basic strategies -cooperate or compete - and four possible outcomes based on the choices players make-win-lose, lose-win, lose-lose, win-win […] The long term winner was the simplest of all strategies submitted: Cooperate on the first move and then do whatever the other players did on the previous move.” – that is truly the first strategy which seems to may work within the rat-race!

Elliot Aronson Jigsaw groups at page 270; score 3
That is about the academic experiment, which have been divided into 5-6 groups of 5-6 students. Each group is working of some sub-part of the whole topic and then it shares the gathered knowledge with the others. “The results are dramatic […] All students do as well or better in their knowledge, the lowest-performing students do significantly better […] the levels of cooperation, self-esteem, compassion, and tolerance increase.”

Joseph Sensenbrenner’s story “It is their duty” at page 289; score 4
In big organization there is often the big bureaucracy problem. The story is about “the fleet with 440 different types, makes, models, and years of equipment”. That happens because the purchase department bought the cheapest vehicles, which were not the cheapest in maintenance, but parts manager could not change it because “[…]controller wouldn’t let us do it” And the controller?” says it is about the attorney… who says it is not a problem if you make strong and clear specification. Joseph changed the flawed system involving the frontline employees and 24 steps purchasing policy was cut to three. Everything would be truly a cool story, unless the whole thing had to be done by the mayor and none first-line employee including the controller could do the thing.

John H. Stanford story about the key to the success at page 399; score 4
Stay in love
The tactics

Other key things, which are something more that just well rounded sentences:
  1. Provide, improve and maintain the two-way communication (page 283), including some practical implementations:
    · a 360 degree feedback mentioned at page 85 and 103 – unfortunately it is just mentioned; no word how to realize it in details (the routines, sample set of questions etc.)
    · the collaboration audit (the only template of the form in the whole book!) form presented at page 267.
    · Passion-compassion game mentioned at page 375; where one person’s role is to speak in passioned way and second’s person role is to listen compassion.
  2. People want leaders who are honest, forward-looking, competent and inspiring (page 111). It is trivial, but important thing is that these are these adjectives and not the others (e.g. funny, self-confident, generous etc.) - worth to remember.
  3. Engage others in planning and analysis (page 142) – it also seems trivial, but many people paid a lot for the lesson, that usually teamwork is better than single heroic effort. It is described well within the Chinese wisdom (page 182): “Tell me, I may listen. Teach me, I may remember. Involve me, I will do it.”
  4. There are some useful tips about how to make public speeches at page 184-185 and advices like:
    “don’t say try, say will and are”
    - Do presentation workshops (including video taping), if you feel it is your weak point – there is a lot of people who has a problem with it and you must not be ashamed if you do
    - You must be enthusiastic, emotional, expressive and personally excited
    - Speak clearly and quickly
    - Make eye contact
  5. “Challenge a process” at page 177 is the story, which I have heard from my colleague from Toyota Bank in Poland – amazing thing, they can achieve really high cost reduction, by making really small (even micro) changes on the production lines. Saving pennies at actions, which happens hundred times daily, can make you saving million bugs monthly and I found exactly the same story in the book (at page 228-229) side by number of the others practical samples:
    - “Pick one major project per quarter. Implement one smaller improvement every three weeks” – page 196.
    ”Eliminate the Dumb Things”. Go find what needs fixing in your organization.
    Wander around the plant, the store, the branch, the halls or the office. Look
    for things that don’t seem right. Ask questions. Probe.
  6. Routine paradox at page 189 – on one hand you want to have one big routine, the process and simple production line on the other hand you must to try making it better, make you and people having fun (page 198, 367; there is even a book “301 Ways to have fun at work” mentioned at page 367) when they work and do some innovative things to keep creativity (page 197). The balance is the best approach.
  7. Let ideas flowing from the outside” at page 193 is definitely a good approach.
  8. Treat every new assignment as a start-over” – page 185
  9. Add a new member or two to the group every couple of years. Rotate some people out and others in.” at page 201 – keep pumping the fresh blood into company’s veins.
  10. Gather the ideas and give the awards for the best ideas – page 202
  11. The weakest muscle in the body is the one between the ears” page 207 – do not let yourself to think that some limitations or beliefs are stronger than you; implement incremental approach in order to achieve the big things. Lu Ann Sullivan at Wells Fargo Bank (page 212) established individual weekly goals and in this way, he could achieve the big win at the end for the whole branch (managing by targets).
  12. Collect yeses” - page 232. Tring to find common point is actually kind of NLP method, which causes very quick connection line and improves the communication between persons.
  13. Conduct pre- and postmortems for every project” at page 234
  14. Rotate team meeting leadership so everyone gets a turn” at page 277; “rotate the chair responsibility” at page 307
  15. Personalize cubicles and award the best ones. It makes people more tied with the work plus the variety makes the workplace special – page 333. Google is quite well-known from doing it at their offices.
  16. Do ceremonies for successful people and make them recognizable – page 345. Make the public board, where you can put the public “award notes” for the employee of the month – page 373. Picking up “the employee of the month” is the challenge itself described at page 377 as looking for “extra mile heroes” by ALL the employees. This action causes the extra achievements histories spread across the organization loudly by the employees themselves.
  17. Be the cheer-manager, the cheerleader among your team – the person who is heating up the team for fight. Do not be afraid to say people thank you if they did a good job – page 345.

The Opinion

All the items mentioned above and number of quotations direct to the conclusion that the book is really cool and practical. Indeed there are fragments where it is, but unfortunately the major part of the book is simple the bubble talk like the one at the page 123 where you find out that you MUST (the word used very often in the book) to listen, read, smell, feel,taste etc. Well… of course you always must to use all of your 7 senses :)

There too many places where you, as a leader, has to be the kind of the saint Santa Claus, who share, cherish and take care of his team mates :) The truth is that the leadership is often about the sweet, stress and all the dirty things, which are not mentioned in the book at all. What about the rat race, which was the plague some time ago and there are still companies which focus on the brilliant individual and not on the team collaboration skills? The “clean laboratory environment” does not surprise actually, as the authors of the book are working for the Leavey School and not for some big corporation, where they could find all of these things. They interviewed number of people, but who washes dirty laundry publicly?

The other problem within the book is that number of sample stories applies to high executives. There is a fragment at the end of the book, which says that anyone can be the leader, but how does it go along with the Joseph Sensenbrenner’s story “It is their duty”. I do not believe that front line employee could change the change in the story. Unfortunately, many stories are told by the chairmen, CTOs and generals – they could do some of the big changes, because they had a power to do it.

The biggest concern is however that unlike “The 7 Habits of Highly Effective People” the book does not give the full and complex recipe. It seems like the authors collected the very rich set of samples, stories and tactics, but then they did not know what to do with it. Even the proposed way of cataloging them does not seem to work as the same thing is repeated often number of times in various places of the book. Unlike “The 7 Habits …” it does not say also anything about the private life. Can there be the successful professional leader, who is passive in private life?

The book is a big, lost chance to say something more than the bunch of good stories and interesting tactics.

Score: 4(good) /6

czwartek, 28 czerwca 2007

„Evaluating Software Architectures: Methods and Case Studiem” book review

Mood: In hurry

Introduction
The book describes three methodologies of reviewing system architectures:
ATAM – Architecture Tradeoff Analysis Method
SAAM – Software Architecture Analysis Method
ARID – Active Reviews for Intermediate Designs
It concentrates mainly on the first method and afterwards it describes the following two much more briefly (especially ARID) basing on previous material.

Content of book
The biggest advantage of the book is a very practical approach to the very abstract topic. It is a direct guide for a novice person showing step-by-step how to:

  • prepare for evaluation
  • make evaluation
  • collect feedback from architecture review process

It includes the detail break down of the methods into phases and stages including the suggestions about audience, meeting agenda, topics to cover and threads including the ways of managing them. The authors of the book show a lot of real samples from particular stages of the process and provide number of very useful tips.

Mentioned methodologies do not cover the 360-degree review of the software architecture in particular project, but they concentrate on defining the main bottlenecks of the projects and following deliverables:

  • Creating the usage attributes tree [drawing 3.4, page 72] with assigning priorities to them - ATAM
  • Defining the most critical, common usage scenarios - ATAM, SAAM, ARID
    Creating the real risks list - ATAM
  • Defining quality attributes [drawings 5.1-5.3, page 132; table 6.3, page 190] and quality targets - ATAM
  • Synchronizing the knowledge about project and project vision among key persons in project - ATAM, SAAM, ARID
  • Reviewing available project documentation and architecture - ATAM, SAAM, ARID

Chapter 9 and Table 9.1 [page 274] contains the detail comparison of all three methodologies.

ATAM
ATAM methodology is the precisely structured (into phases and stages) extension of SAAM method and it is the best fit for:

  • Review of existing project before creating its new version or reuse in other project
  • Formal review by external authority of started or existing software project (for example before taking some strategic decisions)
  • Taking over the on-going or existing project from one team to the other
  • ATAM focuses on big and medium software projects. Tables 2.1 and 2.2 [page 61] show the approximate cost of evaluation process (medium – 36 man days, small – 15 man days).

SAAM
SAAM methodology [Drawing 7.1, page 234] is more flexible approach to topics covered by ATAM. It is also applicable to big and medium projects, which are during realization or before creating the new version. The main difference between SAAM and ATAM are:
SAAM is focused mainly on functionality and extensibility of the project (ATAM covers wider set of attributes - also security, scalability and reliability)
Slightly smaller cost of the evaluation (minimum 2 days comparing to 3 days for ATAM)
More iterative way of creating the deliverables – agenda of meetings is the same each day and cover topics from all the stages, unlike ATAM, where each stage has different agenda

ARID
ARID is the only methodology mentioned, which is applicable during (and not after) the analysis phase. Like SAAM it is based on iterative approach, where agenda (for phase 2) is the same through the whole time of the evaluation process. Unfortunately, this methodology described in a very brief way, without a sample.

The cost of using this methodology is similar to SAAM (minimum 2 mandays).

ADR
The common point of described methodologies is the active approach to the review process (Active Design Reviews, ADR) and bringing back the real effects from the process. The main reason of doing it is to guide the evaluation process so it does not provide just junky type of reports “everything-goes-fine;don’t-worry”. The genesis for this approach is the article “Active Design Reviews: Principles and Practises” written by David Parnas and David Weiss described in details on page 261. It says among others about proper way of putting the questions (non-rhetorical, but focused on descriptive answer), what brings back much better answers and results from review process.

Other methodologies
The book mentions also the number of the other evaluations methodologies (in Chapter 9) like:

  • Quality Attribute Workshop (page 286)
  • Software Performance Engineering (SPE)
  • Survivable Network Analysis (SNA)
    Etc.

They are not described in details and book is just a good reference point for further readings about them.

Source of Document Templates
Book provides also number of good template for number of documents like usage scenarios, usage scenario analysis [table 6.4, page 196], architecture approach [drawing 3.6, page 81], quality attributes, architecture drawings etc.

Opinion
It seems like authors of the book WANTED to create the full review of all “architecture review” approaches and they started it, with the full and a very nice ATAM overview, but afterwards it seems like they did not have enough steam to do the same for the other methodologies doing shorter and shorter descriptions in following chapters. At the end of the road, instead of a nice encyclopedia type of the book, it is in fact the book about ATAM and similar methodologies. It concentrates just on a middle and big projects, which already has started and does not give a lot of support for analysis phase (except short description ARID), where the most of this type of work SHOULD be done. Unfortunately, it seems like the reason of such approach is quite simple – the authors are selling their service and support in ATAM area.

There is number of references to other methodologies, but there is a visible lack of connection to software designing approaches like Agile methodologies, RUP, MSF or project management methodologies like Prince2 or PMBoK. Such two chapters would show much better where these processes could be applied during software development process.

Despite of the criticism, the book is definitely worth of reading as it is VERY practical and it shows a unique point of view for project managers, software architects, stakeholders and other key players in software development process. It provides a VERY good starting point for preparing the evaluation process, giving a number of nice tips; among others it says how to convince the stakeholders that the whole evaluation process is necessary and how to build the review architects team.

Final score: 4 (good)/6

Annotation
References to pages may be slightly different in English version of the book as the article bases on polish translation of the book made by Helion.

 
web metrics