Software Engineering Design : Theory and Practice
Software Engineering Design : Theory and Practice
Click to enlarge
Author(s): Otero, Carlos
Otero, Carlos E.
ISBN No.: 9781439851685
Pages: 368
Year: 201210
Format: Trade Cloth (Hard Cover)
Price: $ 142.62
Dispatch delay: Dispatched between 7 to 15 days
Status: Available (On Demand)

Introduction to Software Engineering Design Engineering Design Engineering Problem Solving Initial State Operational State Thinking about the Problem Problem Solution Goal State Software Engineering Design Why Study Software Engineering Design? Reasons for Studying Software Design in Product Development Reasons for Studying Software Design in Project Management Software Design Challenges Design Challenge 1: Requirements Volatility Design Challenge 2: Process Design Challenge 3: Technology Design Challenge 4: Ethical and Professional Practices Design Challenge 5: Managing Design Influences Stakeholders Development Organization''s Structure Context of Software Design Software Design Process Software Architecture Detailed Design Interface Design Component Design Construction Design Human-Computer Interface Design Software Design Documentation Software Design Management Roles of the Software Designer Systems Engineer Software Architect Component Designer Software Design Fundamentals General Software Design Principles Modularization Abstraction Encapsulation Coupling Cohesion Separation of Interface and Implementation Completeness and Sufficiency Practical Software Design Considerations Design for Minimizing Complexity Design for Change Software Design Strategies Structured Design Object-Oriented Design Software Design with Unified Modeling Language What Is UML? Why Study UML? The UML''s Fundamentals Structural Modeling Component Diagrams Logical versus Physical Components Class Diagrams Classes Name Compartment Attribute Compartment Operation Compartment Relationships Dependency Association Aggregation Composition Generalization Realization Deployment Diagrams Behavioral Modeling Use Case Diagrams Interaction Diagrams Communication Diagrams Sequence Diagrams Concurrency in Interaction Diagrams Principles of Software Architecture What Is Software Architecture? Why Study Software Architecture? Key Tasks in Architectural Design Identifying Stakeholders'' Concerns Identifying Appropriate Architectural Views Identifying Architectural Styles and Patterns Identifying System Interfaces Identifying Impact of Architectural Decisions in Organization Impact on Customer Base Impact on Budget and Schedule Impact from Resource Availability Identifying the System''s Major Components and Interfaces Evaluating and Validating the Architecture Introducing Policies for Design Synchronicity Problem Solving in Software Architecture Inputs Constrainrements Volatility Design Challenge 2: Process Design Challenge 3: Technology Design Challenge 4: Ethical and Professional Practices Design Challenge 5: Managing Design Influences Stakeholders Development Organization''s Structure Context of Software Design Software Design Process Software Architecture Detailed Design Interface Design Component Design Construction Design Human-Computer Interface Design Software Design Documentation Software Design Management Roles of the Software Designer Systems Engineer Software Architect Component Designer Software Design Fundamentals General Software Design Principles Modularization Abstraction Encapsulation Coupling Cohesion Separation of Interface and Implementation Completeness and Sufficiency Practical Software Design Considerations Design for Minimizing Complexity Design for Change Software Design Strategies Structured Design Object-Oriented Design Software Design with Unified Modeling Language What Is UML? Why Study UML? The UML''s Fundamentals Structural Modeling Component Diagrams Logical versus Physical Components Class Diagrams Classes Name Compartment Attribute Compartment Operation Compartment Relationships Dependency Association Aggregation Composition Generalization Realization Deployment Diagrams Behavioral Modeling Use Case Diagrams Interaction Diagrams Communication Diagrams Sequence Diagrams Concurrency in Interaction Diagrams Principles of Software Architecture What Is Software Architecture? Why Study Software Architecture? Key Tasks in Architectural Design Identifying Stakeholders'' Concerns Identifying Appropriate Architectural Views Identifying Architectural Styles and Patterns Identifying System Interfaces Identifying Impact of Architectural Decisions in Organization Impact on Customer Base Impact on Budget and Schedule Impact from Resource Availability Identifying the System''s Major Components and Interfaces Evaluating and Validating the Architecture Introducing Policies for Design Synchronicity Problem Solving in Software Architecture Inputs Constrain Component Design Construction Design Human-Computer Interface Design Software Design Documentation Software Design Management Roles of the Software Designer Systems Engineer Software Architect Component Designer Software Design Fundamentals General Software Design Principles Modularization &n.


To be able to view the table of contents for this publication then please subscribe by clicking the button below...
To be able to view the full description for this publication then please subscribe by clicking the button below...