Sistema Bibliotecario de la Universidad de Quintana Roo

Opening -- The Triptych Paradigm -- Documents -- Conceptual Framework -- Methods and Methodology -- Models and Modelling -- Descriptions: Theory and Practice -- Phenomena and Concepts -- On Defining and on Definitions -- Jacksons Description Principles -- Domain Engineering -- Overview of Domain Engineering -- Domain Stakeholders -- Domain Attributes -- Domain Facets -- Domain Acquisition -- Domain Analysis and Concept Formation -- Domain Verification and Validation -- Towards Domain Theories -- The Domain Engineering Process Model -- Requirements Engineering -- Overview of Requirements Engineering -- Requirements Stakeholders -- Requirements Facets -- Requirements Acquisition -- Requirements Analysis and Concept Formation -- Requirements Verification and Validation -- Requirements Satisfiability and Feasibility -- The Requirements Engineering Process Model -- Computing Systems Design -- Hardware/Software Codesign -- Software Architecture Design -- A Case Study in Component Design -- Domain-Specific Architectures -- Etcetera: Coding and All That! -- The Computing Systems Design Process Model -- Closing -- The Triptych Development Process Model -- Finale.

The art, craft, discipline, logic, practice, and science of developing large-scale software products needs a believable, professional base. The textbooks in this three-volume set combine informal, engineeringly sound practice with the rigour of formal, mathematics-based approaches. Volume 3 is based on the maxim: "Before software can be designed its requirements must be well understood, and before the requirements can be expressed properly the domain of the application must be well understood." This book covers the process from the development of domain descriptions, via the derivation of requirements prescriptions from domain models, to the refinement of requirements into software designs, i.e., architectures and component design. Emphasis is placed on what goes into proper domain descriptions and requirements prescriptions, how one acquires and analyses the domain knowledge and requirements expectations, and how one validates and verifies domain and requirements models. The reader can take an informal route through Vol. 3, and this would be suitable for undergraduate courses on software engineering. Advanced students, lecturers, and researchers may instead follow the formal route through Vol. 3, and in this case Vol. 1 is a prerequisite text. Lecturers will be supported with a comprehensive guide to designing modules based on the textbooks, with solutions to many of the exercises presented, and with a complete set of lecture slides.

ZDB-2-SCS