PPT and video are due no later than February 15, 2019

Slides:



Advertisements
Similar presentations
Software Architecture Design Chapter 12 Part of Design Analysis Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Advertisements

A component- and message-based architectural style for GUI software
The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.
Design Creative Process of transferring the problem into a solution
Designing the system Conceptual design and technical design
1 SYSTEM and MODULE DESIGN Elements and Definitions.
SE 555 Software Requirements & Specification Beyond Requirements Based on Weigers Chapter17.
CH05: Designing the System To design a system is to determine a set of components and inter-component interfaces that satisfy a specified set of requirements.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 system design 1 what is systems design? preparation of the system’s specifications with.
Software Waterfall Life Cycle Requirements Construction Design Testing Delivery and Installation Operations and Maintenance Concept Exploration Prototype.
Chapter 2 The process Process, Methods, and Tools
Software Design Refinement Using Design Patterns Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Styles.
10 Software Architecture CSCU 411 Software Engineering.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Software Engineering Principles. SE Principles Principles are statements describing desirable properties of the product and process.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Conceptual design Tells the customer what the system will do Tells the customer what the system will do Answers: Answers: Where will the data come from?
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Chapter 7 Software Engineering © 2007 Pearson Addison-Wesley. All rights reserved.
CS223: Software Engineering Lecture 14: Architectural Patterns.
CS 160 and CMPE/SE 131 Software Engineering May 12 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
Software Engineering 2007/2008 Chapter 5 Designing the System.
Chapter 2 Object-Oriented Paradigm Overview
Chapter 7: Software Engineering
Software Design.
Software architecture
Software Design Refinement Using Design Patterns
Chapter ? Quality Assessment
Lecture 9- Design Concepts and Principles
Instructor: Dr. Hany H. Ammar
Part 3 Design What does design mean in different fields?
Software Quality Engineering
CHAPTER 3 Architectures for Distributed Systems
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Introduction to Computer Graphics
Introduction to Computer Graphics
PPT and video are due: no later than November 16, 5:00 PM
Introduction to Computer Graphics
PPT9: Asserting expectations
Architectural Design.
PPT1: How failures come to be
PPT6: Scientific debugging
Lecture 9- Design Concepts and Principles
Software Engineering with Reusable Components
Software Design Lecture : 8
Chapter 7 Software Engineering.
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
PPT1: Basics of software engineering
4+1 View Model of Software Architecture
PPT4: Rational B-spline Curves and Surfaces
PPT12: Shape Modification Tools
PPT3: Project planning and management
PPT3: B-spline Curves and Surfaces
PPT6: Advanced Geometric Algorithms
PPT9: Global and local interpolation
PPT7: Conics and Circles
PPT2: B-spline Basics Functions
PPT4: Requirement analysis
4+1 View Model of Software Architecture
PPT8: Common Surfaces as NURBS
PPT6: Object-oriented design
PPT and video are due no later than March 1, 2019
PPT and video are due no later than March 22, 2019
PPT11: Advanced Surface Construction Techniques
PPT and video are due no later than March 29, 2019
PPT11: System maintenance
PPT10: Global and local approximation
PPT5: Fundamental Geometric Algorithms
Presentation transcript:

PPT and video are due no later than February 15, 2019 CEN 4020 Software Engineering PPT5: System design PPT and video are due no later than February 15, 2019 Submit to: lpiegl@gmail.com This template file is just an outline of the presentation that you need to complete. Additional pages will be necessary to fully explore the topic above. Each page should contain adequate text as well as illustrations. You are free to use all publicly available information (text as well as graphics) as long as the sources are properly acknowledged.

Team members’ contributions Member [name]:

What is design? Content outline: What is design? Conceptual and technical designs

What is design? Content outline: Good conceptual design Good technical design

Decomposition Content outline: Wasserman’s model Levels of decomposition Each module must be well defined

Architecture styles Content outline: Levels of design Representation of top-down design

Architecture styles Content outline: Pipes and filters Object-oriented design Implicit invocation Layering Repositories Interpreters Process control

Design issues: modularity and abstraction Content outline: Levels of abstraction

Design issues: modularity and abstraction Content outline: Modularity

Design issues: collaborative design Content outline: Team-based design

Design issues: collaborative design Content outline: Distributed development Communication

Design issues: user interface Content outline: Issues must be addressed Cultures and preferences

Design issues: concurrency Content outline: Synchronization Mutual exclusion

Design issues: concurrency Content outline: Process priority Methods of concurrency

Component independence Content outline: Coupling Forms of coupling

Component independence Content outline: Types of coupling: from most to least desirable Charts and explanations

Component independence Content outline: Cohesion Types of cohesion Examples of cohesion

Exception handling Content outline: What is exception handling Typical exceptions and the way to handle them

Control issues Content outline: Scope of effect

Control issues Content outline: Scope of component

Control issues Content outline: Fan-in and fan-out components

Fault prevention and tolerance Content outline: Fault vs Failure Fault detection

Fault prevention and tolerance Content outline: Fault correction Fault tolerance

Reducing complexity Content outline: Reducing complexity Tools to reduce complexity

Improving design Content outline: Design by contract

Improving design Content outline: Prototyping design

Improving design Content outline: Fault tree analysis

Design evaluation and validation Content outline: Mathematical validation

Design evaluation and validation Content outline: Measuring design quality

Design evaluation and validation Content outline: Comparing designs Design reviews

Design documentation Content outline: Documentation for customers and developers Major components