1 SYSTEM and MODULE DESIGN Elements and Definitions.

Slides:



Advertisements
Similar presentations
Lecture 6: Software Design (Part I)
Advertisements

MAPPING DATA FLOW DIAGRAMS INTO STRUCTURE CHARTS
S Y S T E M S E N G I N E E R I N G.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Information Systems Analysis and Design
Design Phase What’s design?
Software Design Deriving a solution which satisfies software requirements.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Introduction To System Analysis and Design
1 STRUCTURE CHARTS Elements and Definitions. 2 Software System Design translates SRS into a ===> software system architecture: –system’s static structure.
Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.
1 SOFTWARE DESIGN QUALITY COHESION and COUPLING (Part I)
Design The goal is to design a modular solution, using the techniques of: Decomposition Abstraction Encapsulation In Object Oriented Programming this is.
Lecture 13 Revision IMS Systems Analysis and Design.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© 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.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 system design 1 what is systems design? preparation of the system’s specifications with.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
1/19 Component Design On-demand Learning Series Software Engineering of Web Application - Principles of Good Component Design Hunan University, Software.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
CSE 303 – Software Design and Architecture
CS 3610: Software Engineering – Spring 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
1 Life Cycle of Software Specification Design –Risk Analysis –Verification Coding Testing –Refining –Production Maintenance.
Design Concepts By Deepika Chaudhary.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
Lyra – A service-oriented and component-based method for the development of communicating systems (by Sari Leppänen, Nokia/NRC) Traditionally, the design,
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
The basics of the programming process The development of programming languages to improve software development Programming languages that the average user.
11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.
Software Design Process
© 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.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Introduction to Design. 2 Outline Basics of design Design approaches.
Designing Abstract Interfaces for Device Independency Designing Abstract Interfaces for Device Independency Review of A Procedure for Designing Abstract.
Systems Design.  Application Design  User Interface Design  Database Design.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Week 6: Software Design HNDIT Software Engineering Software Design Learning Outcomes  Understand the activities involved in the Design process.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
Design Concepts ch-8
Principles of Programming & Software Engineering
7. Modular and structured design
Cmpe 589 Spring 2006.
Chapter ? Quality Assessment
SDLC: System Development Life Cycle
System Design.
SDC – SDLC integration.
Principles of Programming and Software Engineering
Software Design Mr. Manoj Kumar Kar.
About the Presentations
Software Quality Engineering
Life Cycle Models PPT By :Dr. R. Mall.
Object-Oriented Design
Software Design CMSC 345, Version 1/11.
Analysis models and design models
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
CS 8532: Advanced Software Engineering
Requirements Document
Chapter 2. Problem Solving and Software Engineering
Information Systems Development (ISD) Systems Development Life Cycle
Presentation transcript:

1 SYSTEM and MODULE DESIGN Elements and Definitions

2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance SW System Design Documentation Module Design Documentation

3 Design is the process of applying various techniques and principles for the purpose of defining a device, a process or a system in sufficient detail to permit its physical realisation. (E.S. Taylor )

4 Typical Activities handling of constraints and alternatives (semi-) formal specification –graphical (tabular, etc.) notations identification of good modules application of heuristics completeness and consistency checking risk analysis and resolution (e.g. prototypes)

5 Who does system engineering? system engineer / designer requirements engineer software engineer hardware engineer telecom. engineer organisational expert programmer.....

6 Software System Design translates SRS into a ===> software system architecture: –system’s static structure modules (blackbox) module interfaces –dynamic behaviour (execution) –data structures –user interface design

7 Detailed Design refines the logical system architecture into an implementation oriented design of modules: –invocation structure (calls, rpc, message,...) –module interface realisation (parameters,...) –algorithms for each module –data structure and user interface solutions –if necessary, further decomposition

8 The Concept of Modular Design a module is a separately named component a system is decomposed into modules –stepwise refinement –“top down” modules are integrated to satisfy the requirements –module aggregation –“bottom-up” ===> aggregation/decomposition abstraction

9 The Concept of Information Hiding D.L. Parnas: –a module appears as a blackbox to other modules in the system –characterised only by its interface –hide internal design decisions/details ===> support reusability & maintainability ===> improve functional independence

10 Design Documentation (variation of R.S. Pressman) 1. Scope 1.1 System objectives 1.2 Interfaces (HW, SW, user) 1.3 Major software functions 1.4 Externally defined databases 1.5 Constraints, limitations 2. Reference Documents

11 Design Documentation 3. SW System Design - Software Architecture 3.1 System structure 3.2 Data structure 3.3 User interface 3.4 Dynamic behaviour 3.5 Rules, principles & guidelines

12 Design Documentation 4. Module Design (for each module) 4.1 Functional description (informal) 4.2 Interface specification Inputs Outputs 4.3 Processing (semi-formal) 4.4 Aggregation/decomposition relations 4.4 Constraints, remarks, etc.

13 Design Documentation 5. Database and File Structure 6. Requirements Cross References 7. Test Provisions 7.1 Test guidelines 7.2 Integration strategy 8. Appendices

14 End of Section 3a coming up: structure charts