Bøker av Paul Clements

This book excavates the depths of creative purpose and meaning-making, and the extent to which artist autonomy and authenticity in art is a struggle against psychological conditioning, controlling cultural institutions and markets, key to which is representation.The chapters are underpinned by examples from the arts and the narrative weaves a trail through a range of conceptualizations that are applied to various aspects of visual culture, from mainstream canonical arts to avant-garde, community and public art; social and political art to commercial art; ethereal art to the popular, edgy and kitsch. The book is wide-ranging and employs various aesthetic, cultural, philosophical, political, psycho-social and sociological debates to highlight the problems and contradictions that an encounter with the arts and creativity engenders.The book will be of interest to scholars working in art history, museum studies, arts management, cultural policy, cultural studies and cultural theory.

In August 1939 the Irish travel writer Richard Hayward set out on a road trip to explore the Shannon region. Eighty years on, inspired by his work, Paul Clements retraces Hayward's journey along the river. Clements paints a compelling portrait of twenty-first century Ireland, mingling travel and anecdote with an eye for the natural world.

"This new edition is brighter, shinier, more complete, more pragmatic, more focused than the previous one, and I wouldn't have thought it possible to improve on the original. As the field of software architecture has grown over these past decades, there is much more to be said, much more that we know, and much more that we can reflect upon of what's worked and what hasn't-and the authors here do all that, and more." -From the Foreword by Grady Booch, IBM Fellow Software architecture-the conceptual glue that holds every phase of a project together for its many stakeholders-is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system's architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated-in other words, is not well documented-the project cannot be deemed a complete success. This revision of Documenting Software Architectures provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully use, maintain, and build a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition: Coverage of documentation for new architectural styles, such as service-oriented architectures, multi-tier architectures, and architectures for aspect-oriented systems Guidance oriented to documentation in an Agile development environment Deeper treatment of the systematic rationale, reflecting best industrial practices Improved templates, reflecting years of use and feedback, and more documentation layout options A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system