Software design methodology
Software design methodology has come a long way since the 1960's and 1970's when programmers were limited to Pascal/C and SA/SD to create systems. When creating information systems for today's world, many factors must be taken into consideration including globalization, the software l...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Amsterdam ; Boston :
Elsevier Butterworth-Heinemann
2005.
|
| Edición: | 1st edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627431006719 |
Tabla de Contenidos:
- Software Design Methodology; Contents; List of Figures; List of Tables; Preface; 1. Basic Concepts of Design; 1.1 INTRODUCTION; 1.2 CHARACTERISTICS OF DESIGN ACTIVITIES; 1.2.1 The input and start point of designs; 1.2.2 The outcome and results of designs; 1.2.3 Transformation of data; 1.2.4 Generation of new ideas; 1.2.5 Problem solving and decision making; 1.2.6 Satisfying and discovering constraints; 1.2.7 Evolution and optimisation in a solution space of diversity; 1.3 ESSENTIAL ELEMENTS OF DESIGNS; 1.3.1 Statement of design problem and objectives; 1.3.2 Constraints
- 1.3.3 Description of product 1.3.4 Rationale; 1.3.5 Plan of production; 1.3.6 Description of usage; 1.4 THE FACTORS THAT AFFECT DESIGNS; 2. Design Quality; 2.1 SOFTWARE QUALITY MODELS; 2.1.1 Hierarchical models; 2.1.2 Relational models; 2.2 THE EFFECT OF DESIGN ON SOFTWARE QUALITY; 2.2.1 Efficiency; 2.2.2 Correctness and reliability; 2.2.3 Portability; 2.2.4 Maintainability; 2.2.5 Reusability; 2.2.6 Interoperability; 2.3 QUALITY ATTRIBUTES OF SOFTWARE DESIGN; 2.3.3 Quality of development process; 3. Design Principles; 3.1 BASIC RULES OF SOFTWARE DESIGN; 3.1.1 Causes of difficulties
- 3.1.2 Vehicles to overcome difficulties 3.1.3 Basic rules of software design; 3.2 DESIGN PROCESSES; 3.2.1 The context of design in software development process; 3.2.2 Generic design process: descriptive models; 3.2.3 Design strategies: prescriptive models; 3.3 STRUCTURE OF SOFTWARE DESIGN METHODS; 4. Software Architecture; 4.1 THE NOTION OF ARCHITECTURE; 4.1.1 Architecture in the discipline of buildings; 4.1.2 Architecture in the discipline of computer hardware; 4.1.3 The general notion of architecture; 4.2 THE NOTION OF SOFTWARE ARCHITECTURE; 4.2.1 Prescriptive models
- 4.2.2 Descriptive models 4.2.3 Multiple view models; 4.2.4 The roles of architecture in software design; 4.3 SOFTWARE ARCHITECTURAL STYLE; 4.3.1 Introductory examples; 4.3.2 The notion of software architectural style; 5. Description of Software Architectures; 5.1 THE VISUAL NOTATION; 5.1.1 Active and passive elements; 5.1.2 Data and control; 5.1.3 Relationships; 5.1.4 Decomposition/composition of architectural elements; 5.2 EXAMPLE 1: WWW CLIENT-SERVER PAIR; 5.3 EXAMPLE 2: ROBOT SOCCER UNSW; 6. Typical Architectural Styles; 6.1 DATA FLOW; 6.1.1 The general data flow style
- 6.1.2 The pipe-and-filter sub-style 6.1.3 The batch sequential processing sub-style; 6.2 INDEPENDENT COMPONENTS; 6.2.1 The general independent components style; 6.2.2 The event based implicit invocation systems sub-style; 6.2.3 The communicating processes sub-style; 6.3 CALL AND RETURN; 6.3.1 The general call and return style; 6.3.2 The layered systems sub-style; 6.3.3 Data abstraction: the abstract data type and object-oriented sub-styles; 6.4 DATA-CENTRED; 6.5 VIRTUAL MACHINE; 7. Using Styles in Design; 7.1 CHOICES OF STYLES; 7.2 COMBINATIONS OF STYLES
- 7.2.1 Hierarchical heterogeneous styles
