E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE D ESIGN C OPYRIGHT © 2011 DSR C ORPORATION.

Slides:



Advertisements
Similar presentations
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER T EST D ESIGN T ECHNIQUES C OPYRIGHT © 2012 DSR C ORPORATION.
Advertisements

E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER I NTRODUCTION TO Q UALITY A SSURANCE C OPYRIGHT © 2012 DSR C ORPORATION.
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Pfleeger and Atlee, Software Engineering: Theory and Practice CS499 Chapter 7 Writing the Programs Shari L. Pfleeger Joann M. Atlee 4 th Edition.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Software Testing and Quality Assurance
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Embedded Systems Software Training Center
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
1 The Teaching and Learning Strategy, including Projects Roy Crole Department of Computer Science University of Leicester.
Chapter 4 Capturing the Requirements 4th Edition Shari L. Pfleeger
Software Architecture. Agenda " Why architect? " What is architecture? " What does an architect do? " What principles guide the process of architecting?
Software Product Lines Krishna Anusha, Eturi. Introduction: A software product line is a set of software systems developed by a company that share a common.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Computer Science: An Overview Tenth Edition by J. Glenn Brookshear Chapter.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Tasks 1.Check you have the following posts: 1.Hardware and Software 2.Input and Output 3.Components of a Computer 2.ALL fonts should be a sensible size.
The Software Development Cycle Defining and understanding the problem.
Continuation From Chapter From Chapter 1
Guide to the Software Engineering Body of Knowledge Chapter 1 - Introduction.
The Guide to the Software Engineering Body of Knowledge
E MBEDDED S YSTEM S OFTWARE B ASICS D IAGRAMS E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER 1.
Overview of Software Testing 07/12/2013 WISTPC 2013 Peter Clarke.
SWE © Solomon Seifu CS425 Software Engineering Solomon Seifu Department of Computer Science Maharishi University of Management, Fairfield, IA.
Quality Management.  Quality management is becoming increasingly important to the leadership and management of all organisations. I  t is necessary.
ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue University – Fort Wayne Instructor – Dr. John Tanik.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER P ROJECT M ANAGEMENT P ROCESSES C OPYRIGHT © 2012 DSR C ORPORATION.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
IEEE CS SAB, Nov 2007 For Computer Society Internal Use Only 1 S2ESC Report Standards Activities Board Meeting November 6-7, 2007 Submitted by Paul Croll.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
1. The Requirements Process Requirements Input Example
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?
Chapter 7 Software Engineering © 2007 Pearson Addison-Wesley. All rights reserved.
DEVELOPING THE WORK PLAN
EMBEDDED SYSTEM SOFTWARE AND HARDWARE BASICS HOME TASK E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER 1.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
1.The following diagram illustrates the relationship among various hardware components. The arrows indicate the directions of data flow. Activity 1 Relationship.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Monica Gloudemans Ekaterina Schwartz Gloudemans/Schwartz ACS 560 CMAP.
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER T EST D ESIGN T ECHNIQUES C OPYRIGHT © 2012 DSR C ORPORATION.
A Comparative Survey of Enterprise Architecture Frameworks
SQA project process standards IEEE software engineering standards
Embedded Systems Software Training Center
Chapter 7: Software Engineering
Chapter 24: Architecture Competence
SQA project process standards IEEE software engineering standards
Software and Systems Engineering Standards Sponsor Committee Report
Lecture 17 ATAM Team Expertise
For Computer Society Internal Use Only
Lecture 9- Design Concepts and Principles
Quality Management Perfectqaservices.
A Comparative Survey of Enterprise Architecture Frameworks
Definitions.
تحليل وتصميم نظم المعلومات
Software Engineering Lecture #45
Lecture 9- Design Concepts and Principles
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
National University of Laos
Requirements Document
Presentation transcript:

E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE D ESIGN C OPYRIGHT © 2011 DSR C ORPORATION

Objectives  Understand what software design is  Understand the software design techniques and approaches C OPYRIGHT © 2011 DSR C ORPORATION 2

Agenda 1. What is Software Design? 2. Software Design Strategies 3. Software Design Techniques 4. Key Issues in Software Design 5. Software Architectural Styles and Patterns 6. Software Design Documentation 7. Software Design Quality C OPYRIGHT © 2011 DSR C ORPORATION 3

Coupling and Cohesion: Coupling C OPYRIGHT © 2011 DSR C ORPORATION Pfleeger and Atlee, Software Engineering: Theory and Practice, Chapter 5 4

Coupling and Cohesion: Coupling (cont.)  We can measure coupling along a range of dependence C OPYRIGHT © 2011 DSR C ORPORATION Pfleeger and Atlee, Software Engineering: Theory and Practice, Chapter 5 5

Coupling and Cohesion: Cohesion C OPYRIGHT © 2011 DSR C ORPORATION Pfleeger and Atlee, Software Engineering: Theory and Practice, Chapter 5 6

Coupling and Cohesion: Cohesion Examples C OPYRIGHT © 2011 DSR C ORPORATION Pfleeger and Atlee, Software Engineering: Theory and Practice, Chapter 5 7

Summary  Software Design is a crucial process of the software life cycle  It involves design strategies, techniques, styles, and patterns  Different aspects must be taken into consideration  Software Design Document must contain as much as possible the information necessary for implementation as well as the design flow  Design validation is one way to achieve good product quality C OPYRIGHT © 2011 DSR C ORPORATION 8

References 1.SWEBOK. Guide to the Software Engineering. Body of Knowledge Version / A project of the IEEE Computer Society Professional Practices Committee 2.Software Engineering: Theory and Practice / Shari Lawrence Pfleeger 3.IEEE Std , IEEE Standard Glossary of Software Engineering Terminology C OPYRIGHT © 2011 DSR C ORPORATION 9

Questions and exercises 1.What are the main and supplementary software design activities? What are the input and output for every activity? 2.What are the key software design strategies? Give the characteristic for every strategy. When it is used? What kind of the diagrams is used for its description? 3.What are the key software design techniques? Give the short characteristic for every technique. 4.What are coupling and cohesion? What software quality characteristic it influences the most? What the coupling among components depends on? Give the example of low cohesion and high cohesion. C OPYRIGHT © 2011 DSR C ORPORATION 10