Learn how to successfully implement trustworthy computing tasks using aspect-oriented programming <p> This landmark publication fills a gap in the literature by not only describing the basic concepts of trustworthy computing (TWC) and aspect-oriented programming (AOP), but also exploring their
Using aspect-oriented programming for trustworthy software development
β Scribed by Safonov, V. O
- Publisher
- Wiley-Interscience
- Year
- 2010
- Tongue
- English
- Leaves
- 352
- Series
- Quantitative Software Engineering Series
- Category
- Library
No coin nor oath required. For personal study only.
β¦ Synopsis
- Provides the necessary tools to complete trustworthy computing tasks more efficiently with AOP. * Includes practical information on a working AOP tool for .NET (Aspect.NET) and a number of working examples of how to use AOP for the purposes of TWC. * Solutions throughout the book include traditional software engineering metrics and comparisons to agile/xp programming and SCRUM. * Targets practical day to day TWC tasks and other needs of the software engineer.
β¦ Subjects
Aspect-oriented programming;Computer software--Development;Computer software--Reliability;Computer software -- Development;Computer software -- Reliability
π SIMILAR VOLUMES
"A refreshingly new approach toward improving use-case modeling by fortifying it with aspect orientation."<br /><br /><br /><br />--<b>Ramnivas Laddad,</b>author of<i>AspectJ in Action</i>"Since the 1980s, use cases have been a way to bring users into software design, but translating use cases into
Aspect-oriented programming (AOP) is a revolutionary new way to think about software engineering. AOP was introduced to address crosscutting concerns such as security, logging, persistence, debugging, tracing, distribution, performance monitoring, and exception handling in a more effective manner. U
"A refreshingly new approach toward improving use-case modeling by fortifying it with aspect orientation." --Ramnivas Laddad, author of AspectJ in Action "Since the 1980s, use cases have been a way to bring users into software design, but translating use cases into software has been an art, at best
xli, 755 p. : 24 cm