Architecture Description Languages Book

As with some other posts on this shelf, I have not read the entire volume. In this case, only selected chapters were included in the special edition made for the Drexel class.

This was a much more technical, and therefore challenging and interesting, book than the Experiencing MIS text for the first half of class. Again, the authors know they are writing a textbook and address the students as such. Again, the target student bady does not match with the cadre in an MLIS class - this text is aimed at students expected to become system analysts and go on to serve in IT departments at various businesses, not the proto-librarians I'm in class with. Because of this, the text occasionally assumes a level of programming knowledge that I didn't have (nor did any of my class-mates). But the authors didn't depend on that knowledge, instead trying hard to downplay the role of programmeds and application developers in favor business process analysis and revision.

There is something very strange about how much of business process management has been effectively ceded to technology divisions in modern corporations. An organization doesn't need to have computers to have a need for clear and consistant procedures. A database does not need to be electronic either - you'd think the librarians and records managers of the world would know this having created so many of the filing systems and search logics that allows computers to be invented in the first place