Relating Software Requirements and Architectures

ยท ยท ยท ยท
ยท Springer Science & Business Media
เบ›เบถเป‰เบกเบญเบตเบšเบธเบ
387
เปœเป‰เบฒ

เบเปˆเบฝเบงเบเบฑเบšเบ›เบถเป‰เบก e-book เบ™เบตเป‰

Why have a book about the relation between requirements and software architecture? Understanding the relation between requirements and architecture is important because the requirements, be they explicit or implicit, represent the function, whereas the architecture determines the form. While changes to a set of requirements may impact on the realization of the architecture, choices made for an architectural solution may impact on requirements, e.g., in terms of revising functional or non-functional requirements that cannot actually be met.

Although research in both requirements engineering and software architecture is quite active, it is in their combination that understanding is most needed and actively sought. Presenting the current state of the art is the purpose of this book. The editors have divided the contributions into four parts: Part 1 โ€œTheoretical Underpinnings and Reviewsโ€ addresses the issue of requirements change management in architectural design through traceability and reasoning. Part 2 โ€œTools and Techniquesโ€ presents approaches, tools, and techniques for bridging the gap between software requirements and architecture. Part 3 โ€œIndustrial Case Studiesโ€ then reports industrial experiences, while part 4 on โ€œEmerging Issuesโ€ details advanced topics such as synthesizing architecture from requirements or the role of middleware in architecting for non-functional requirements. The final chapter is a conclusions chapter identifying key contributions and outstanding areas for future research and improvement of practice.

The book is targeted at academic and industrial researchers in requirements engineering or software architecture. Graduate students specializing in these areas as well as advanced professionals in software development will also benefit from the results and experiences presented in thisvolume.

เบเปˆเบฝเบงเบเบฑเบšเบœเบนเป‰เบ‚เบฝเบ™

Paris Avgeriou is Professor of Software Engineering at the University of Groningen, The Netherlands, where he has led the software engineering research group since September 2006. He has published more than 90 peer-reviewed articles in international journals, conference proceedings, and books. His research interests lie in the area of software architecture, with a strong emphasis on architecture modeling, knowledge, evolution, and patterns.

John Grundy is Professor of Software Engineering at Swinburne University of Technology, Australia. He has published over 200 refereed papers and has made numerous contributions to the fields of collaborative software engineering, software architecture, and software visualization.

Jon G. Hall is Senior Lecturer at The Open University, UK. Jon has published widely on numerous subjects including formal methods, software architectures, and requirements engineering. His current research mission is to provide new thoughts and tools for sophisticated problem solving.

Patricia Lago is Associate Professor at the VU University Amsterdam, The Netherlands. Her research interests are in software and service-oriented architecture, architectural knowledge management, green IT, and sustainable software engineering. She has published over 100 peer-reviewed articles in international journals, conference proceedings, and books.

Ivan Mistrรญk is an independent consultant and researcher in software-reliant systems engineering with more than forty yearsโ€™ experience, working at R&D institutions in the USA and Germany and consulting on a variety of large international projects sponsored by ESA, EU, NASA, NATO, and UN.

เปƒเบซเป‰เบ„เบฐเปเบ™เบ™ e-book เบ™เบตเป‰

เบšเบญเบเบžเบงเบเป€เบฎเบปเบฒเบงเปˆเบฒเบ—เปˆเบฒเบ™เบ„เบดเบ”เปเบ™เบงเปƒเบ”.

เบญเปˆเบฒเบ™โ€‹เบ‚เปเป‰โ€‹เบกเบนเบ™โ€‹เบ‚เปˆเบฒเบงโ€‹เบชเบฒเบ™

เบชเบฐเบกเบฒเบ”เป‚เบŸเบ™ เปเบฅเบฐ เปเบ—เบฑเบšเป€เบฅเบฑเบ”
เบ•เบดเบ”เบ•เบฑเป‰เบ‡ เปเบญเบฑเบš Google Play Books เบชเบณเบฅเบฑเบš Android เปเบฅเบฐ iPad/iPhone. เบกเบฑเบ™เบŠเบดเป‰เบ‡เบ‚เปเป‰เบกเบนเบ™เป‚เบ”เบเบญเบฑเบ”เบ•เบฐเป‚เบ™เบกเบฑเบ”เบเบฑเบšเบšเบฑเบ™เบŠเบตเบ‚เบญเบ‡เบ—เปˆเบฒเบ™ เปเบฅเบฐ เบญเบฐเบ™เบธเบเบฒเบ”เปƒเบซเป‰เบ—เปˆเบฒเบ™เบญเปˆเบฒเบ™เบ—เบฒเบ‡เบญเบญเบ™เบฅเบฒเบ เบซเบผเบท เปเบšเบšเบญเบญเบšเบฅเบฒเบเป„เบ”เป‰ เบšเปเปˆเบงเปˆเบฒเบ—เปˆเบฒเบ™เบˆเบฐเบขเบนเปˆเปƒเบช.
เปเบฅเบฑเบšเบ—เบฑเบญเบš เปเบฅเบฐ เบ„เบญเบกเบžเบดเบงเป€เบ•เบต
เบ—เปˆเบฒเบ™เบชเบฒเบกเบฒเบ”เบŸเบฑเบ‡เบ›เบถเป‰เบกเบชเบฝเบ‡เบ—เบตเปˆเบŠเบทเป‰เปƒเบ™ Google Play เป‚เบ”เบเปƒเบŠเป‰เป‚เบ›เบฃเปเบเบฃเบกเบ—เปˆเบญเบ‡เป€เบงเบฑเบšเบ‚เบญเบ‡เบ„เบญเบกเบžเบดเบงเป€เบ•เบตเบ‚เบญเบ‡เบ—เปˆเบฒเบ™เป„เบ”เป‰.
eReaders เปเบฅเบฐเบญเบธเบ›เบฐเบเบญเบ™เบญเบทเปˆเบ™เป†
เป€เบžเบทเปˆเบญเบญเปˆเบฒเบ™เปƒเบ™เบญเบธเบ›เบฐเบเบญเบ™ e-ink เป€เบŠเบฑเปˆเบ™: Kobo eReader, เบ—เปˆเบฒเบ™เบˆเบณเป€เบ›เบฑเบ™เบ•เป‰เบญเบ‡เบ”เบฒเบงเป‚เบซเบผเบ”เป„เบŸเบฅเปŒ เปเบฅเบฐ เป‚เบญเบ™เบเป‰เบฒเบเบกเบฑเบ™เป„เบ›เปƒเบชเปˆเบญเบธเบ›เบฐเบเบญเบ™เบ‚เบญเบ‡เบ—เปˆเบฒเบ™เบเปˆเบญเบ™. เบ›เบฐเบ•เบดเบšเบฑเบ”เบ•เบฒเบกเบ„เบณเปเบ™เบฐเบ™เบณเบฅเบฐเบญเบฝเบ”เบ‚เบญเบ‡ เบชเบนเบ™เบŠเปˆเบงเบเป€เบซเบผเบทเบญ เป€เบžเบทเปˆเบญเป‚เบญเบ™เบเป‰เบฒเบเป„เบŸเบฅเปŒเป„เปƒเบชเปˆ eReader เบ—เบตเปˆเบฎเบญเบ‡เบฎเบฑเบš.