Software engineering design : theory and practice /: theory and practice. (2012)
- Record Type:
- Book
- Title:
- Software engineering design : theory and practice /: theory and practice. (2012)
- Main Title:
- Software engineering design : theory and practice
- Further Information:
- Note: Carlos E. Otero.
- Other Names:
- Otero, Carlos E
- Contents:
- 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;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; Constraints; Outputs; Software Architecture Process; Understand and Evaluate Requirements; Elicitation; Requirement Sources; Elicitation Techniques; Analysis; Specification and Validation; Specific; Correct; Complete; Consistent; Attainable; Verifiable; Designing the Architecture; The 4 + 1 View Model; User View; Process View; Physical View; Development View; Logical View; Components and Connectors; Designing Logical Architectural Elements Using Data Flows; Designing Logical Architectural Elements Using Styles and Patterns; Designing the Process Architecture; Processes; Threads; Evaluating the Architecture; Patterns and Styles in Software Architecture; Architectural Styles and Patterns; History of Architectural Styles and Patterns; Architectural Pattern Classification; Data-Centered Systems; Blackboard Pattern; Data Flow Systems; &nbs … (more)
- Publisher Details:
- Place of publication not identified : Auerbach Publications
- Publication Date:
- 2012
- Extent:
- 1 online resource, illustrations
- Subjects:
- 005.1
Software engineering - Languages:
- English
- ISBNs:
- 9781466510159
1466510153 - Access Rights:
- Legal Deposit; Only available on premises controlled by the deposit library and to one user at any one time; The Legal Deposit Libraries (Non-Print Works) Regulations (UK).
- Access Usage:
- Restricted: Printing from this resource is governed by The Legal Deposit Libraries (Non-Print Works) Regulations (UK) and UK copyright law currently in force.
- View Content:
- Available online (eLD content is only available in our Reading Rooms) ↗
- Physical Locations:
- British Library HMNTS - ELD.DS.143439
- Ingest File:
- 02_032.xml