We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byChaim Jaycox
Modified over 2 years ago
© Andrew IrelandSoftware Design F28SD2 Software Design: Summary Andrew Ireland School of Mathematical & Computer Sciences Heriot-Watt University Edinburgh
© Andrew IrelandSoftware Design F28SD2 Outline Nature of Software Design Architectural Design Function-oriented Design Object-oriented Design Software Reuse and Component-based Design Verification & Validation
© Andrew IrelandSoftware Design F28SD2 Architectural Design Systems structuring, i.e. identify the key subsystems and the way in which they will communicate –Repository, client-server, layered Control modelling, i.e. how is control managed between the subsystems? –Centralized vs event-based Subsystem decomposition
© Andrew IrelandSoftware Design F28SD2 Function-oriented Design Transaction based systems, minimal state Data flow Structure charts Detailed design
© Andrew IrelandSoftware Design F28SD2 Object-oriented Design Decentralized state, exploiting information hiding and hierarchies Many OOD methods, but common ingredients: –Identification of objects: CRCs; use cases; grammatical analysis –Identification of static perspective: class diagrams –Identification of dynamic perspective: sequence; communication; activity; state machine diagrams
© Andrew IrelandSoftware Design F28SD2 Component-based Design Promote software reuse Key ingredients: –Well defined service (functionality) –Well defined interface –Explicit dependencies –Standardization (component model), e.g. CORBA, EJB, COM (.NET) Compositionality trade-offs Predictability, trustworthiness & certification
© Andrew IrelandSoftware Design F28SD2 Verification & Validation Definitions Static & dynamic analysis Analysis & testing life-cycle Early phase analysis Planning for testing Exploiting design notations (UML) From unit to acceptance testing
© Andrew IrelandSoftware Design F28SD2 Typical Exam Questions Explain concepts and approaches using examples, e.g. “Using an example explain the role of CRCs with software design process” Be able to compare and contrast the relative merits of particular approaches, e.g. “Compare and contrast the trade-offs between component-based design vs designing a system from scratch.”
© Andrew IrelandSoftware Design F28SD2 Typical Exam Questions Given a scenario, be able to propose a software architecture together with a justification Given a scenario, apply a particular technique or approach, e.g. given English requirements develop: DFDs; structure charts; use cases; CRCs; class, sequence communication, activity, state machine diagrams. Alternatively, be able to answer questions on a given design OR extend the design OR compare it against given requirements
Presentation by Prabhjot Singh V-Model. Wikipedia ISTQB Exam Certification.com Resources.
Software Engineering 1 Provisional Revision Plan.
© Andrew IrelandSoftware Design F28SD2 Function-oriented Design Andrew Ireland School of Mathematical & Computer Sciences Heriot-Watt University Edinburgh.
Dale Roberts Object Oriented Programming using Java - Introduction Dale Roberts, Lecturer Computer Science, IUPUI Department.
© Andrew IrelandSoftware Design F28SD2 Architectural Design Andrew Ireland School of Mathematical & Computer Sciences Heriot-Watt University Edinburgh.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
1 / 26 CS 425/625 Software Engineering Architectural Design Based on Chapter 11 of the textbook [SE-8] Ian Sommerville, Software Engineering, 8t h Ed.,
1 Software Testing and Quality Assurance Lecture 16 - Test Analysis & Design Models (Chapter 4, A Practical Guide to Testing Object-Oriented Software)
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1 / 26 CS 425/625 Software Engineering Architectural Design Based on Chapter 10 of the textbook [Somm00] Ian Sommerville, Software Engineering, 6 th Ed.,
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Requirement Analysis Functional & Non-Functional Requirements Scenarios Use cases: – View Fixtures – Manage Tournament – Register Team – Report Discrepancy.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
1 Object orientation. 2 What benefits does OO give? Primarily –Encapsulation (Associates data & operations) –Types & specialisation –Software re-use.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
UHD::3320::CH121 DESIGN PHASE Chapter 12. UHD::3320::CH122 Design Phase Two Aspects –Actions which operate on data –Data on which actions operate Two.
Midterm Study Guide COP 4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of EE and Computer Science University of Central.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Toward product architecture oriented requirements analysis for product line development in systems engineering Kei Kurakawa Nara Institute of Science and.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Final Exam Study Guide COP 4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of EE and Computer Science University of.
Introduction to OOAD and the UML Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
1 UML Basic Training. UML Basic training2 Agenda Definitions: requirements, design Basics of Unified Modeling Language 1.4 SysML.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Component Software: A New Software Engineering Course H. Conrad Cunningham, Yi Liu, Pallavi Tadepalli, and Mingxian Fu Software Architecture Research Group.
Object-Oriented Design Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
Systems Analysis and Design in a Changing World, 6th Edition 1 Online Chapter B.
TAL7011 – Lecture 4 UML for Architecture Modeling.
1 CMPT 275 High Level Design Phase Modularization.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
Program Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS, INC. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
COMET Approach for UML Overview Chapter 6 Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
CSC480 Software Engineering Lecture 10 September 25, 2002.
7 Systems Analysis and Design in a Changing World, Fourth Edition.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
UML (Unified Modeling Language). 2 UML The static structure defines the kinds of the objects important to a system and to its implementation as well as.
Software Engineering I Object-Oriented Design Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 SWE Introduction to Software Engineering Lecture 20 – Architectural Design (Chapter 11)
Software Architecture Design Chapter 12 Part of Design Analysis Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
© 2017 SlidePlayer.com Inc. All rights reserved.