Software Engineering with Reusable ComponentsSpringer Science & Business Media, 19/06/1997 - 272 من الصفحات Software is rarely built completely from scratch. To a great extent, existing software documents (source code, design documents, etc.) are copied and adapted to fit new requirements. Yet we are far from the goal of making reuse the standard approach to software development. Software reuse is the process of creating software systems from existing software rather than building them from scratch. Software reuse is still an emerging discipline. It appears in many different forms from ad-hoc reuse to systematic reuse, and from white-box reuse to black-box reuse. Many different products for reuse range from ideas and algorithms to any documents that are created during the software life cycle. Source code is most commonly reused; thus many people misconceive software reuse as the reuse of source code alone. Recently source code and design reuse have become popular with (object-oriented) class libraries, application frameworks, and design patterns. Software components provide a vehicle for planned and systematic reuse. The software community does not yet agree on what a software component is exactly. Nowadays, the term component is used as a synonym for object most of the time, but it also stands for module or function. Recently the term component-based or component-oriented software development has be come popular. In this context components are defined as objects plus some thing. What something is exactly, or has to be for effective software develop ment, remains yet to be seen. However, systems and models are emerging to support that notion. |
المحتوى
1 | |
11 Software Components | 2 |
12 Software Reuse | 4 |
13 Structure of Book | 5 |
Software Reuse | 7 |
9 | |
22 Benefits of Software Reuse | 11 |
23 Obstacles to Software Reuse | 15 |
112 Software Specification | 145 |
114 Software Implementation | 146 |
115 Software Testing | 147 |
116 Software Maintenance | 148 |
117 Summary | 149 |
151 | |
122 Exploratory Model | 153 |
123 Prototyping Model | 155 |
24 Summary | 18 |
21 | |
31 Reuse Facets | 22 |
33 Reuse Scopes | 23 |
34 Reuse Techniques | 24 |
35 Reuse Intentions | 28 |
36 Reuse Products | 31 |
37 Summary | 35 |
37 | |
41 Legal Issues | 38 |
42 Economic Issues | 39 |
43 Organizational Issues | 40 |
44 Measurement Issues | 48 |
45 Summary | 52 |
55 | |
52 Management Commitment | 58 |
53 Reuse Motivation | 59 |
54 ThirdParty Components | 61 |
55 Summary | 63 |
Software Components | 65 |
67 | |
61 Component Definition | 68 |
62 Component Interfaces | 71 |
63 Component Platforms | 76 |
64 Summary | 82 |
83 | |
72 Forms of Interoperation | 98 |
73 Composition Mismatches | 102 |
74 Summary | 105 |
107 | |
82 Interactivity | 108 |
83 Interaction | 110 |
85 Distribution | 111 |
86 Forms of Adaptation | 113 |
88 Summary | 114 |
117 | |
92 Related Work | 122 |
93 Summary | 128 |
129 | |
Reuse on the WorldWide Web | 131 |
Reuse based on ASCII Pipes | 133 |
Reuse of a Desktop Publishing Application | 135 |
Reuse in a Programming Environment | 136 |
106 Summary | 138 |
Software Engineering | 141 |
143 | |
124 Spiral Model | 156 |
125 Twin Life Cycle | 157 |
126 Summary | 158 |
159 | |
131 Domain Analysis | 160 |
132 Domain Analysis Activities | 163 |
133 Domain Analysis Methods | 166 |
135 Domain Implementation | 168 |
171 | |
142 Component Generalization | 173 |
143 Component Certification | 174 |
144 Component Repositories | 178 |
145 Component Classification | 179 |
146 Summary | 184 |
185 | |
152 ComponentBased Life Cycle | 188 |
153 Domain Analysis and the Software Life Cycle | 192 |
154 Summary | 193 |
Software Documentation | 195 |
197 | |
162 User Documentation | 198 |
163 System Documentation | 199 |
164 Process Documentation | 200 |
203 | |
172 Reuse Manual | 206 |
173 Summary | 209 |
211 | |
182 Tool Support | 212 |
183 Acceptance | 214 |
184 Reuse Considerations | 215 |
217 | |
192 Line and Word Runs | 218 |
193 Case Study | 220 |
194 Summary | 224 |
225 | |
202 Source Code Inheritance | 226 |
203 Documentation Inheritance | 227 |
204 Summary | 231 |
Closing | 233 |
235 | |
212 Limits of Component Reuse | 237 |
213 Prospects | 239 |
References | 241 |
Glossary | 251 |
263 | |
طبعات أخرى - عرض جميع المقتطفات
Software Engineering with Reusable Components <span dir=ltr>Johannes Sametinger</span> لا تتوفر معاينة - 2014 |
Software Engineering with Reusable Components <span dir=ltr>Johannes Sametinger</span> لا تتوفر معاينة - 2010 |
عبارات ومصطلحات مألوفة
abstraction activities adaptation algorithms and/or application frameworks application group architecture Chapter class libraries classification clients component reuse component's computing context Corba costs data structures defined described design patterns domain analysis domain engineering evaluation example execution existing components faceted classification FrameMaker functions graphical user interfaces implementation inheritance input integration interaction interoperation Java line and word literate programming macros MetaFont modifications modules needed nents object-oriented programming OpenDoc operating system organizational output platforms ponents productivity programming language prototype repository requirements retrieval reusable components reuse maturity reuse of components reuse percentage reuse program reuse reuse reuse see Section reused components reusers software development Software Engineering software life cycle software reuse software systems source code source code components specific spiral model standards subsystems system documentation systematic reuse taxonomy textual tion Unix filters various waterfall model white-box reuse
مقاطع مشهورة
الصفحة 159 - Neighbors [Neighbors 84] was one of the first researchers to define domain analysis as being "the activity of identifying the objects and operations of a class of similar systems in a particular problem domain.