* Affiliatelinks/Werbelinks
Links auf reinlesen.de sind sogenannte Affiliate-Links. Wenn du auf so einen Affiliate-Link klickst und über diesen Link einkaufst, bekommt reinlesen.de von dem betreffenden Online-Shop oder Anbieter eine Provision. Für dich verändert sich der Preis nicht.
Model-Driven Software Systems Development Using the Meta-Artifact Process
Wayne O'Brien
* Affiliatelinks/Werbelinks
Links auf reinlesen.de sind sogenannte Affiliate-Links. Wenn du auf so einen Affiliate-Link klickst und über diesen Link einkaufst, bekommt reinlesen.de von dem betreffenden Online-Shop oder Anbieter eine Provision. Für dich verändert sich der Preis nicht.
Naturwissenschaften, Medizin, Informatik, Technik / Wärme-, Energie- und Kraftwerktechnik
Beschreibung
The importance of architecture for software systems is widely accepted, but the role of architecture in the overall development process is not so clear. Presenting an architecture-centric process, Model-Driven Software Systems Development Using the Meta-Artifact Process makes the role of architecture clear. At its core, this book is about developing software systems and, more specifically, software code. It describes three major innovations for making software, which are combined with five widely used enabling technologies, to provide a complete, hypothesis-driven software development process known as Meta-Artifact Process (MAP). Having complete requirements is essential for making good software and supports the hypothesis-driven MAP.
MAP offers properties, qualities, and capabilities that help stakeholders and developers understand and reason about a domain and target systems of interest. MAP, through the central role of the Meta-Artifact and incorporating the view that a computer program is a hypothesis about the requirements, offers new ways to look at systems and their development, even changing the roles of developers and stakeholders.
Recommending agile methods wherever appropriate while supporting the OMG Essence standard and working within an overarching architecture, MAP presents ways to ensure that the requirements are complete and correct. It helps to identify likely points during development to form alternative hypotheses about them. Because MAP requires an underlying software development process, it can provide that clarity to existing processes in which the organization’s developers are already proficient.
This book provides concrete examples from two broad but diverse areas—Accounting Information Systems in the commercial area and a military command and control system—to show the wide applicability of MAP in both commercial and defense domains.
