What people are saying - Write a review
We haven't found any reviews in the usual places.
addition alternative features application engineering application testing approach architecture aspects asset version graph CAVG Chapter classiﬁcation composition language conceptual product line conﬁguration management constraints construction artifacts construction speciﬁcation construction workﬂow model contains content component model content conﬁguration core asset version create SQL created creation database DB Modeling DB-Introduction deﬁned deﬁnition diﬀerent diﬃcult digital artifacts digital information products digital products domain analysis domain design domain engineering domain testing e-learning eﬀort example execution feasible feature models ﬁrst ﬁxed foreign key helper programs Introduction to DB layout Lines for Digital marking graph metadata modules node notation oﬀered overview document package parameters Petri Nets PLANT Powerpoi 1.0 PPT Powerpoint ﬁles predeﬁned product line model product map template product-based view QX nets Relational Model Repository reusable reuse SCORM Sect software product lines strategy technical tion transition update variability variants Workflow Management
Page 10 - Kotler (1984:463) offers a useful definition: a product is 'anything that can be offered to a market for attention, acquisition, use, or consumption that might satisfy a want or need. It includes physical objects, services, persons, places, organizations, and ideas'.
Page 44 - More formally, a software product line is "a set of software-intensive systems sharing a common, managed set of features that satisfy the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way
Page 36 - A software component is a unit of composition with contractually specified interfaces and explicit context dependencies only.
Page 43 - A product line is a group of products that are closely related either because they satisfy a class of need, are used together, are sold to the same customer groups, are marketed through the same types of outlets, or fall within given price ranges.
Page 28 - Glossary (2003), e-learning covers a wide set of applications and processes, such as Web-based learning, computer-based learning, virtual classrooms, and digital collaboration. It includes the delivery of content via Internet, intranet-extranet (LAN/WAN), audio- and videotape, satellite broadcast, interactive TV, and CDROM.
Page 201 - Workflow Patterns: On the Expressive Power of (Petri-net-based) Workflow Languages. In K. Jensen, editor, Proceedings of the Fourth Workshop on the Practical Use of Coloured Petri Nets and CPN Tools (CPN 2002), volume 560 of DAIMI, pages 1-20, Aarhus, Denmark, August 2002.
Page 43 - More specifically, an architectural style defines a vocabulary of components and connector types, and a set of constraints on how they can be combined.
Page 57 - An activity in which a system or component is executed under specified conditions, the results are observed or recorded and an evaluation is made of some aspect of the system or component.
Page 205 - W. Reisig. Place/Transition Petri Nets. In Lectures on Petri nets I: Basic Models, LNCS 1491, pp.