DOC PREVIEW
DREXEL CS 451 - Design Models

This preview shows page 1-2-3-26-27-28 out of 28 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 28 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CS 451 Software Engineering Design Models UML Component DiagramComponent DesignModel a componentModel a component’s interfacesModel a component’s relationshipInterface DesignThe Component and Interface Design of TheraWiiComponent Diagram Example in UML 1.4Another Example using UML 1.4Component Diagram Example in UML 2Beyond the BasicsDeployment DiagramArchitecture DesignDeployment DiagramDeployment Diagram ExampleUML Deployment Diagram ExampleConcise UML 2 Deployment DiagramDeployment DiagramData ModelsData Model DesignData Modeling ConceptsData Modeling using ClassesDatabase Scheme DesignNetwork DiagramsSoftware Design DocumentSlide Number 28Drexel University CS 451 Software Engineering 1 Yuanfang Cai Room 104, University Crossings 215.895.0298 [email protected] University Design Models  Data Flow Diagram  Class Diagram  Sequence Diagram  State Diagram  Component Diagram  Deployment Diagram  Data Models 2Drexel University UML Component Diagram 3Drexel University Component Design 4  Displays the high level packaged structure of the code itself.  Dependencies among components are shown  Source code components  Binary code components  Executable components.  Some components exist at compile time, at link time, at run times well as at more than one time.Drexel University Model a component 5  Illustrates the pieces of software, embedded controllers and such that make up a system, and their organization and dependencies.  A component is implemented by one or more Classes (or Objects) at runtime.Drexel University Model a component’s interfaces 6 Provided Interfaces Required InterfacesDrexel University Model a component’s relationship 7Drexel University Interface Design  Why interface design is needed?  Task parallelism  Performance analysis  Different types of Interface Design  Graphical interface design  Boundary class design  Database interface design  File storage interface design  Hardware interface design  More… 8Drexel University The Component and Interface Design of TheraWii 9Drexel University Component Diagram Example in UML 1.4Drexel University Another Example using UML 1.4 11Drexel University Component Diagram Example in UML 2Drexel University Beyond the Basics  Display a component's internal structure.Drexel University Deployment Diagram 14Drexel University Architecture Design 15  Models the configuration of run-time processing elements and the software components, processes, and objects that live on them.  Software component instances represent run-time manifestations of code units.  The relation between software and hardware  The ambiguity of the definition of “architecture design”  Sometimes it is used to represent component diagram  Sometime it means components and conectorsDrexel University Deployment Diagram 16Drexel University Deployment Diagram ExampleDrexel University UML Deployment Diagram Example Drexel University Concise UML 2 Deployment DiagramDrexel University Deployment Diagram 20Drexel University Data Models 21Drexel University Data Model Design  Why Data Model Design is needed?  Performance consideration  Interface consideration  Adaptability consideration  Different types of Data Design  In-memory data structure  Input-output file format  Database scheme  Classes attributes  Principles: abstraction and modularization 22Drexel University Data Modeling Concepts Data objects can then be represented as tables: 23Drexel University Data Modeling using Classes 24  The Data Model Design of TheraWiiDrexel University Database Scheme Design  Entity Relation Diagram  The Database Design of Vodka 25Drexel University Network Diagrams  Network diagrams are often drawn using software-based drawing tools (figure below was drawn using Microsoft Visio)Drexel University Software Design Document  Syntax  Component Diagram  High-level Component Diagrams  Detailed Component Diagrams (Classes and relations within a Component)  Interface Design (Boundary Class)  Data Model /Data Storage Design (Entity Classes), data attributes have to be specified  Optional  Deployment Diagram  Algorithm Explanation 27Drexel University Please refer to the design document rubric


View Full Document

DREXEL CS 451 - Design Models

Download Design Models
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Design Models and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Design Models 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?