R.S. Pressman & Associates, Inc. For University Use Only
|
|
- Eileen Ward
- 6 years ago
- Views:
Transcription
1 Software Engineering: A Practitioner s Approach, 6/e Chapter 10 Architectural Design copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
2 Why Architecture? The architecture is not the operational software. Rather, it is a representation that enables a software engineer to: (1) analyze the effectiveness of the design in meeting its stated requirements, (2) consider architectural alternatives at a stage when making design changes is still relatively easy, and (3) reduce the risks associated with the construction of the software. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
3 Why is Architecture Important? communication between all parties (stakeholders) interested in the development of a computer-based system. highlights hli ht early design decisions i as important, on the ultimate success of the system as an operational entity. constitutes a relatively small, intellectually graspable model of how the system is structured and how its components work together [BAS03 03]. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
4 Data Design At the architectural level Design of one or more databases to support the application architecture Design of methods for mining the content of multiple databases navigate through existing databases in an attempt to extract appropriate business-level information Design of a dt data warehouse a a large, independent d database that t has access to the data that are stored in databases that serve the set of applications required by a business with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
5 Data Design At the component level refine data objects and develop a set of data abstractions implement data object attributes as one or more data structures review data structures to ensure that appropriate relationships have been established simplify data structures as required with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
6 Data Design Component Level Apply the systematic analysis principles like for function and behavior Representation of data flow and content, data objects All data structures and the operations to be performed on each should be identified. A data dictionary should be established and used to define both data and program design. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
7 Low level data design decisions should be deferred until late in the design process. (abstraction, step-wise refinement) The representation of data structure should be known only to those modules that must make direct use of the data contained within the structure. (information hiding) A library of useful data structures and the operations that may be applied to them should be developed. A software design and programming language should support the specification and realization of abstract data types. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
8 Architectural Styles Each style describes a system category that encompasses: (1) a set of components (e.g., a database, computational modules) that perform a function required by a system, (2) a set of connectors that enable communication, coordination and cooperation among components, (3) constraints that define how components can be integrated to form the system, and (4) semantic models that enable a designer to understand the overall properties of a system by analyzing the known properties of its constituent parts. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
9 Architectural Styles Data-centered architectures Data flow architectures t Call and return architectures Object-oriented architectures Layered architectures with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
10 Data-Centered Architecture A data store resides at the center, is accessed frequently by other components. Increase integratability (independent components) Blackboard: sends notifications to client software when data of its interest is changed. 10
11 Data Flow Architecture When input data are to be transformed through a series of computational or manipulative components into output data. Filters (components) work independently. 11
12 Call and Return Architecture Main program/subprogram (classic program structure) Remote procedure call (components are distributed across multiple computers) 12
13 Object-oriented Architecture Components of a system encapsulate data and the operations that must be applied to manipulate the data Communication and coordination between components is accomplished via message passing. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
14 Layered Architecture A number of different layers are defined, each accomplishing operations that progressively become closer to the machine instruction set. 14
15 Deriving Program Architecture Program Architecture with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
16 Partitioning the Architecture horizontal and vertical partitioning are required with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
17 Horizontal Partitioning define separate branches of the module hierarchy h for each major function use control modules to coordinate communication between functions function 1 function 3 function 2 with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
18 Vertical Partitioning: Factoring design so that decision making and work are stratified (classified) decision making modules should reside at the top of the architecture decision-makers workers with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
19 Structured Design objective: to derive a program architecture that is partitioned approach: the DFD is mapped into a program architecture the PSPEC and STD are used to indicate the content of each module notation: structure chart with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
20 Flow Characteristics Transform flow Transaction flow with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
21 General Mapping Approach isolate incoming and outgoing flow boundaries; for transaction flows, isolate the transaction center working from the boundary outward, map DFD transforms into corresponding modules add control modules as required refine the resultant program structure using effective modularity concepts with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
22 Transform Mapping a b d e f g h c data flow model i j x1 "Transform" mapping x2 x3 x4 b c d e f g i a h j with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
23 Factoring direction of increasing decision making typical "decision making" modules typical "worker" modules with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
24 First Level Factoring main program controller input controller processing controller output controller with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
25 Second Level Mapping D B C A A C control main B mapping from the flow boundary outward D with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
26 Transaction Flow incoming flow T action path with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
27 Transaction Example fixture setting fixture servos operator commands process operator commands report display screen robot control assembly record robot control software in reality, other commands would also be shown with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
28 Refining the Analysis s Model write an English language processing narrative for the level 01 flow model apply noun/verb parse to isolate processes, data items, store and entities develop level 02 and 03 flow models create corresponding data dictionary entries 5. refine flow models as appropriate p... now, we're ready to begin design! with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
29 noun-verb parse Deriving Level 1 Processing narrative for " process operator commands" Process operator command software reads operator commands from the cell operator. An error message is displayed for invalid commands. The command type is determined for valid commands and appropriate action is taken. When fixture commands are encountered, fixture status is analyzed and a fixture setting is output to the fixture servos. When a report is selected, the assembly record file is read and a report is generated and displayed on the operator display screen. When robot control switches are selected, control values are sent to the robot control system. Process operator command software reads operator commands from the cell operator. An error message is displayedfor invalid commands. The command type is determinedfor valid commands and appropriate action is taken. When fixture commands are encountered, fixture status is analyzed and a fixture setting is output to the fixture servos. When a report is selected, the assembly record file is read and a report is generated and displayed on the operator display screen. When robot control switches are selected, control values are sent to the robot control system. with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
30 Level 1 Data Flow Diagram operator commands read operator commands Error msg status valid command analyze fixture fixture status fixture servos fixture setting determine command type select report control robot generate report report display screen send control value robot control assembly record robot control system with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
31 Level 2 Data Flow Diagram command error msg read command produce error msg status t command invalid command validate command determine type read fixture status combined status determine setting format setting raw setting fixture setting robot control send control value read record record calculate output values values format report report assembly record start /stop with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
32 Transaction Mapping Principles isolate the incoming flow path define each of the action paths by looking for the "spokes of the wheel" assess the flow on each action path define the dispatch and control structure map each action path flow individually id with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
33 Transaction Mapping a b data a flow model x1 t l m d g n h e i j f k Mapping b a t x2 x3 x4 d e f g h x3.1 l m n i j with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001, k
34 Isolate Flow Paths command error msg read command produce error msg status command invalid command validate command determine type read fixture status combined status determine setting format setting raw setting fixture setting robot control send control value read record record calculate output values values format report report assembly record start /stop with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
35 Map the Flow Model process operator commands command input controller determine type read validate produce command command error message fixture report send status generation control controller controller value each of the action paths must be expanded further with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
36 Refining the Structure Chart process operator commands command input controller determine type read command validate command produce error message fixture status controller report generation controller send control value read fixture status determine setting format setting read record calculate output values format report with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001,
copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner s Approach, 6/e Chapter 10 Architectural Design copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student
More informationDesign Concepts and Principles
Design Concepts and Principles Analysis to Design Data Object Description Entity- Relationship Diagram Data Flow Diagram Process Specification (PSPEC) Component level design (or) procedural design Data
More informationCS485/540 Software Engineering Architecture and Component Design (Chs. 9,10)
CS485/540 Software Engineering Architecture and Component Design (Chs. 9,10) Cengiz Günay Dept. Math & CS, Emory University Fall 2013 Some slides courtesy of Joan Smith, Roger Pressman, Ian Sommerville,
More informationChapter : Analysis Modeling
Chapter : Analysis Modeling Requirements Analysis Requirements analysis Specifies software s operational characteristics Indicates software's interface with other system elements Establishes constraints
More informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS SOFTWARE ENGINEERING
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS 6403 - SOFTWARE ENGINEERING QUESTION BANK TWO MARKS UNIT I SOFTWARE PROCESS AND PROJECT MANAGEMENT 1. What is software engineering? Software engineering
More informationChapter 9 Design Engineering
Software Engineering: A Practitioner s s Approach, 6/e Chapter 9 Design Engineering copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student
More informationUNIT III. Software Design
UNIT III Software Design Design Specification Models Data design - created by transforming the analysis information model (data dictionary and ERD) into data structures required to implement the software
More informationDesign Concepts. Slide Set to accompany. Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman
Chapter 8 Design Concepts Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For non-profit educational
More informationFunctional Design of Web Applications. (partially, Chapter 7)
Functional Design of Web Applications (partially, Chapter 7) Functional Design: An Overview Users of modern WebApps expect that robust content will be coupled with sophisticated functionality The advanced
More information06. Analysis Modeling
06. Analysis Modeling Division of Computer Science, College of Computing Hanyang University ERICA Campus 1 st Semester 2017 Overview of Analysis Modeling 1 Requirement Analysis 2 Analysis Modeling Approaches
More informationDesign. Introduction
Design Introduction a meaningful engineering representation of some software product that is to be built. can be traced to the customer's requirements. can be assessed for quality against predefined criteria.
More information!"#$%&'()*+,-*,--)./00#'1)2)345"645"%()
!"#$%&'()*+,-*,--)./00#'1)2)345"645"%() Chapter 9!! Architectural Design! Slide Set to accompany Software Engineering: A Practitionerʼs Approach, 7/e # by Roger S. Pressman Slides copyright 1996, 2001,
More informationThe Nature of Software. Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger S. Pressman. For non-profit educational use only
Chapter 1 The Nature of Software Slide Set to accompany Software Engineering: A Practitioner s Approach, 8/e by Roger S. Pressman and Bruce R. Maxim Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger
More informationSoftware Architecture and Design I
Software Architecture and Design I Instructor: Yongjie Zheng February 23, 2017 CS 490MT/5555 Software Methods and Tools Outline What is software architecture? Why do we need software architecture? How
More informationDarshan Institute of Engineering & Technology Unit : 3
1) Explain design concepts. A set of fundamental software design concepts has evolved over the past four decades. Although the degree of interest in each concept has varied over the years, each has tood
More informationUser Interface Design. Slide Set to accompany. Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman
Chapter 11 User Interface Design Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For non-profit
More informationChapter 6 System Engineering. System Engineering
Software Engineering: A Practitioner s s Approach, 6/e Chapter 6 System Engineering copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student
More informationTesting Object-Oriented Applications. Slide Set to accompany. Software Engineering: A Practitioner s Approach, 7/e by Roger S.
Chapter 19 Testing Object-Oriented Applications Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman
More informationSlides copyright 1996, 2001, 2005, 2009, 2014 by Roger S. Pressman. For non-profit educational use only
Chapter 16 Pattern-Based Design Slide Set to accompany Software Engineering: A Practitioner s Approach, 8/e by Roger S. Pressman and Bruce R. Maxim Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger
More informationSE Notes Mr. D. K. Bhawnani, Lect (CSE) BIT
Unit 3 Design concepts and principles 1 Software Design 1. Software design deals with transforming the customer requirements, as described by the SRS document, into a form that is implementable using a
More informationArchitectural Design
Architectural Design Minsoo Ryu Hanyang University 1. Architecture 2. Architectural Styles 3. Architectural Design Contents 2 2 1. Architecture Architectural design is the initial design process of identifying
More informationSoftware Design. Software design is a blueprint or a plan for a computerbased solution for system
Software Design Software Design Software design is a blueprint or a plan for a computerbased solution for system Software design deals with transforming the customer requirements, as described by the SRS
More informationCHAPTER 9 DESIGN ENGINEERING. Overview
CHAPTER 9 DESIGN ENGINEERING Overview A software design is a meaningful engineering representation of some software product that is to be built. Designers must strive to acquire a repertoire of alternative
More informationChapter 12 (revised by JAS)
Chapter 12 (revised by JAS) Pattern-Based Design Slide Set to accompany Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman
More informationLecture 8: Chapter 8!
Lecture 8: Chapter 8! Design Concepts! Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For
More informationStructured Analysis and Structured Design
Structured Analysis and Structured Design - Introduction to SASD - Structured Analysis - Structured Design Ver. 1.5 Lecturer: JUNBEOM YOO jbyoo@konkuk.ac.kr http://dslab.konkuk.ac.kr References Modern
More informationSoftware Testing Strategies. Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger S. Pressman. For non-profit educational use only
Chapter 22 Software Testing Strategies Slide Set to accompany Software Engineering: A Practitioner s Approach, 8/e by Roger S. Pressman and Bruce R. Maxim Slides copyright 1996, 2001, 2005, 2009, 2014
More informationStructured Analysis and Design
1 st Cut - Creating... 14:10 A Actors... 2:11 Additional Notations... 11:17 Alternative Names for the System... 13:15 Analysis - Overview... 1:9 Analysis and Design - Goals... 1:6 Analysis and Design -
More informationcopyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner s Approach, 6/e Chapter 7 Requirements Engineering copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student
More informationRequirements Engineering. Contents. Functional requirements. What is a requirement?
Contents Ø Introduction 4 Ø Engineering Ø Project Management Ø Software Design Ø Detailed Design and Coding Ø Quality Assurance Engineering Ø What is a Requirement? Ø RE Activities Ø Documentation Ø RE
More informationinformation process modelling DFDs Process description
Process modelling IMS9300 IS/IM FUNDAMENTALS information process modelling DFDs Process description processes are the action part of businesses process modelling graphically represents the processes which
More informationTDWI Data Modeling. Data Analysis and Design for BI and Data Warehousing Systems
Data Analysis and Design for BI and Data Warehousing Systems Previews of TDWI course books offer an opportunity to see the quality of our material and help you to select the courses that best fit your
More informationTransformation of analysis model to design model
2010 International Conference on E-business, Management and Economics IPEDR vol.3 (2011) (2011) IACSIT Press, Hong Kong Transformation of analysis model to design model Lalji Prasad Truba College of Engineering
More informationSoftware design descriptions standard
Tuffley Computer Services Pty Ltd Quality Management System Software design descriptions standard Version: 2.0 Date: 09/05/11 Status: Approved Copy no.: Controlled Approved by: Approver s name: Approver
More informationVETRI VINAYAHA COLLEGE OF ENGINEERING AND TECHNOLOGY DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
VETRI VINAYAHA COLLEGE OF ENGINEERING AND TECHNOLOGY DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS6403 SOFTWARE ENGINEERING II year/ IV sem CSE (Regulation 2013) UNIT 1- SOFTWARE PROCESS AND PROJECT
More informationModelling as a Communication Tool: Introduction to Process Modelling. Modelling. Simplification in modelling. Representation in modelling
CSE104 - Information Systems 1 Modelling as a Communication Tool: Introduction to Process Modelling The requirements specification document Must be communicated to key stakeholders Should contain: Functions
More informationCS SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS 6403 - SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS 1. Explain iterative waterfall and spiral model for software life cycle and various activities
More informationUniversity of Calgary Department of Electrical and Computer Engineering. SENG : Object Oriented Analysis and Design Behrouz Homayoun Far
University of Calgary Department of Electrical and Computer Engineering SENG 609.23: Object Oriented Analysis and Design Behrouz Homayoun Far Evaluation Test () 20:00 20:30 PM Instructions: 1. This booklet
More informationRequirements Modeling (Ch. 6)
Requirements Modeling (Ch. 6) Cengiz Günay CS485/540 Software Engineering Fall 2014 Some slides courtesy of Joan Smith and Roger Pressman Günay (Emory MathCS) Requirements Modeling Fall 2014 1 / 8 (c)
More informationProcess Modelling. Data flow Diagrams. Process Modelling Data Flow Diagrams. CSE Information Systems 1
CSE104 - Information s 1 Process Modelling Data Flow Diagrams Process Modelling Process modelling aims to graphically represent the processes which capture, manipulate, store and distribute data. data
More informationTesting Object-Oriented Applications. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only
Chapter 19 Testing Object-Oriented Applications Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman
More informationPresentation-Abstraction-Control (PAC) Pattern. PAC Introduction
Presentation-Abstraction-Control (PAC) Pattern PAC Introduction The Presentation-Abstraction-Control architectural pattern (PAC) defines a structure for interactive software systems in the form of a hierarchy
More informationUNIT 1-SOFTWARE PROCESS AND PROJECT MANAGEMENT
PART A (2 MARKS) UNIT 1-SOFTWARE PROCESS AND PROJECT MANAGEMENT 1. What is software engineering? Software engineering is a discipline in which theories, methods and tools are applied to develop professional
More informationObjectives. Explain the purpose and objectives of objectoriented. Develop design class diagrams
Objectives Explain the purpose and objectives of objectoriented design Develop design class diagrams Develop interaction diagrams based on the principles of object responsibility and use case controllers
More information(Murlidhar Group of Institutions,Bhavnagar Road, Rajkot) by:-assit. Prof. Vijay Vora (SOOADM) MCA-III
Analysis Modeling What is Analysis Modeling? Analysis modeling uses a combination of text and diagrammatic forms to depict(represent) requirements for data, function, and behavior These text and diagrammatic
More informationSystem Models. Minsoo Ryu. Hanyang University. Real-Time Computing and Communications Lab., Hanyang University
System Models Minsoo Ryu Hanyang University 1. Context Models 2. Structural Model 3. Behavioural Models 4. Object Models Contents 2 2 Building a System Model User requirements should be written in natural
More informationMIGRATING COOL:TEAMWORK MODELS INTO MODERN CASE TOOLS
MIGRATING COOL:TEAMWORK MODELS INTO MODERN CASE TOOLS A UML/MOF METAMODEL FOR HATLEY-PIRBHAI SYSTEM SPECIFICATION By Colin Coates (Senior Consultant) Version 1.0 Tuesday, 13 October 2015 Table of Contents
More informationFundamentals of Health Workflow Process Analysis and Redesign
Fundamentals of Health Workflow Process Analysis and Redesign Unit 10.3d Process Mapping Gane-Sarson Notation Slide 1 Welcome to the Gane-Sarson Notation for Data Flow Diagrams Subunit. This is the third
More informationCS6403 SOFTWARE ENGINEERING Year / Sem : II / IV Sub. Code &Subject : CS6403 SOFTWARE ENGINEERING QUESTION BANKWITH ANSWERS
CS6403 SOFTWARE ENGINEERING Year / Sem : II / IV Sub. Code &Subject : CS6403 SOFTWARE ENGINEERING QUESTION BANKWITH ANSWERS UNIT 1-SOFTWARE PROCESS AND PROJECT MANAGEMENT 1. What is software engineering?
More informationCS485/540 Software Engineering Requirements Modeling (Ch. 6)
CS485/540 Software Engineering Requirements Modeling (Ch. 6) Cengiz Günay Dept. Math & CS, Emory University Fall 2013 Some slides courtesy of Joan Smith and Roger Pressman Günay (Emory) Requirements Modeling
More informationUser Interface Design. Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger S. Pressman. For non-profit educational use only
Chapter 15 User Interface Design Slide Set to accompany Software Engineering: A Practitioner s Approach, 8/e by Roger S. Pressman and Bruce R. Maxim Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger
More informationModeling. Slides by: Ms. Shree Jaswal. Slides by:ms. Shree Jaswal 1
Modeling Slides by: Ms. Shree Jaswal Slides by:ms. Shree Jaswal 1 Model What is a model? a model is a simplification of reality Why do we model? we build models so that we can better understand the system
More informationUnit II. (i) Computer Programming Languages
Unit II. (i) Computer Programming Languages Need of a computer programming language: A programming language is an artificial language designed to communicate instructions to a computer. Thousands of different
More informationPart 7 - Object Oriented Concepts Classes, Objects, Properties and Methods
Part 7 - Object Oriented Concepts Classes, Objects, Properties and Methods Object Orientated Paradigm... 2 Abstract Data Types (ADT) & Encapsulation... 3 Encapsulation... 5 Classes and Objects... 6 Methods
More informationcopyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner s Approach, 6/e Chapter 27 Change Management copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student
More informationDesigning Component-Based Architectures with Rational Rose RealTime
Designing Component-Based Architectures with Rational Rose RealTime by Reedy Feggins Senior System Engineer Rational Software Rose RealTime is a comprehensive visual development environment that delivers
More informationLecture 14: Chapter 18!
Lecture 14: Chapter 18! Testing Conventional Applications! Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e " by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by
More informationTesting Web Applications. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only
Chapter 20 Testing Web Applications Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For non-profit
More information(Team Name) (Project Title) Software Design Document. Student Name (s):
(Team Name) (Project Title) Software Design Document Student Name (s): TABLE OF CONTENTS 1. INTRODUCTION 2 1.1Purpose 2 1.2Scope 2 1.3Overview 2 1.4Reference Material 2 1.5Definitions and Acronyms 2 2.
More informationInformation Management Fundamentals by Dave Wells
Information Management Fundamentals by Dave Wells All rights reserved. Reproduction in whole or part prohibited except by written permission. Product and company names mentioned herein may be trademarks
More informationUML Fundamental. OutLine. NetFusion Tech. Co., Ltd. Jack Lee. Use-case diagram Class diagram Sequence diagram
UML Fundamental NetFusion Tech. Co., Ltd. Jack Lee 2008/4/7 1 Use-case diagram Class diagram Sequence diagram OutLine Communication diagram State machine Activity diagram 2 1 What is UML? Unified Modeling
More informationArchitectural Blueprint
IMPORTANT NOTICE TO STUDENTS These slides are NOT to be used as a replacement for student notes. These slides are sometimes vague and incomplete on purpose to spark a class discussion Architectural Blueprint
More informationBusiness Processes and Rules: Siebel Enterprise Application Integration. Siebel Innovation Pack 2013 Version 8.1/8.
Business Processes and Rules: Siebel Enterprise Application Integration Siebel Innovation Pack 2013 September 2013 Copyright 2005, 2013 Oracle and/or its affiliates. All rights reserved. This software
More informationSoftware Design Report
Software design is a process by which the software requirements are translated into a representation of software components, interfaces, and data necessary for the implementation phase. The SDD shows how
More informationSoftware Testing Strategies. Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman
Chapter 17 Software Testing Strategies Slide Set to accompany Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For
More informationCSEB233: Fundamentals of Software Engineering. Software Design
CSEB233: Fundamentals of Software Engineering Software Design Objectives Explain set of design principles, concepts, and practices Describe five design models complete design specification: required for
More informationUNIT-4 Behavioral Diagrams
UNIT-4 Behavioral Diagrams P. P. Mahale Behavioral Diagrams Use Case Diagram high-level behaviors of the system, user goals, external entities: actors Sequence Diagram focus on time ordering of messages
More informationA STUDY OF OBJECT ORIENTED ANALYSIS AND DESIGN
A STUDY OF OBJECT ORIENTED ANALYSIS AND DESIGN GARJE RAKESH RAMESHRAO RESEARCH SCHOLAR, DEPT. OF COMPUTER SCIENCE CMJ UNIVERSITY, SHILLONG, MEGHALAYA INTRODUCTION Object-oriented Analysis and Design is
More informationRequirements Engineering
Requirements Engineering Semi-Formal Specification: Structural Functional Requirements Structured Analysis Data Flow Diagrams SADT IDEF0 1 Back to the past GO/AO OO SA (DT) DFD SADT IDEF (Back to the future)
More informationComponent-Level Design. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only
Chapter 10 Component-Level Design Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For non-profit
More informationLecture Chapter 2 Software Development
Lecture Chapter 2 Software Development Large Software Projects Software Design o Team of programmers o Cost effective development Organization Communication Problem Solving Analysis of the problem Multiple
More informationMicrosoft. [MS20762]: Developing SQL Databases
[MS20762]: Developing SQL Databases Length : 5 Days Audience(s) : IT Professionals Level : 300 Technology : Microsoft SQL Server Delivery Method : Instructor-led (Classroom) Course Overview This five-day
More informationSE 1: Software Requirements Specification and Analysis
SE 1: Software Requirements Specification and Analysis Lecture 4: Basic Notations Nancy Day, Davor Svetinović http://www.student.cs.uwaterloo.ca/ cs445/winter2006 uw.cs.cs445 U Waterloo SE1 (Winter 2006)
More informationProcess Modeling. Wei-Tsong Wang 1 IIM, NCKU
Process Modeling Based on Chapter 9 of Whitten, Bentley, and Dittman: Systems Analysis and Design for the Global Enterprise (7th Ed). McGraw Hill. 2007 Wei-Tsong Wang 1 IIM, NCKU 2 Models: Logical and
More informationDarshan Institute of Engineering & Technology for Diploma Studies
REQUIREMENTS GATHERING AND ANALYSIS The analyst starts requirement gathering activity by collecting all information that could be useful to develop system. In practice it is very difficult to gather all
More informationUNIT III DESIGN CONCEPTS AND PRINCIPLES
UNIT III DESIGN CONCEPTS AND PRINCIPLES Design process and concepts modular design design heuristic design model and document. Architectural design software architecture data design architectural design
More informationSystem Analysis & design
Assiut University Faculty of Computers and Information System Analysis & design Year 2 Academic Year 2014/ 2015 Term (2) 5 A PICTURE IS WORTH A 1,000 WORDS A process model is a graphical way of representing
More informationDeveloping SQL Databases
Course 20762B: Developing SQL Databases Page 1 of 9 Developing SQL Databases Course 20762B: 4 days; Instructor-Led Introduction This four-day instructor-led course provides students with the knowledge
More informationSlides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only
Chapter 7 Requirements Modeling: Flow, Behavior, Patterns, and WebApps Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005,
More informationBasic Structural Modeling. Copyright Joey Paquet,
Basic Structural Modeling Copyright Joey Paquet, 2000 1 Part I Classes Copyright Joey Paquet, 2000 2 Classes Description of a set of objects sharing the same attributes, operations and semantics Abstraction
More informationChapter 13. Application Architecture and Modeling. McGraw-Hill/Irwin. Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 13 Application Architecture and Modeling McGraw-Hill/Irwin Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Objectives 13-2 Define an information system s architecture in
More informationSoftware Design Document (SDD) Template (summarized from IEEE STD 1016)
Software Design Document (SDD) Template (summarized from IEEE STD 1016) Software design is a process by which the software requirements are translated into a representation of software components, interfaces,
More informationLecture 16: (Architecture IV)
Lecture 16: (Architecture IV) Software System Design and Implementation ITCS/ITIS 6112/8112 091 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte Oct.
More informationCompuScholar, Inc. Alignment to Nevada "Computer Science" Course Standards
CompuScholar, Inc. Alignment to Nevada "Computer Science" Course Standards Nevada Course Details: Course Name: Computer Science Primary Cluster: Information and Media Technologies Standards Course Code(s):
More informationConfiguration Manager
Tivoli Management Solution for Microsoft SQL Configuration Manager Version 1.1 Tivoli Management Solution for Microsoft SQL Configuration Manager Version 1.1 Tivoli Management Solution for Microsoft SQL
More informationCourse on Database Design Carlo Batini University of Milano Bicocca
Course on Database Design Carlo Batini University of Milano Bicocca 1 Carlo Batini, 2015 This work is licensed under the Creative Commons Attribution NonCommercial NoDerivatives 4.0 International License.
More informationSoftware Modeling & Analysis. - Introduction to SASD - Structured Analysis. Lecturer: JUNBEOM YOO
Software Modeling & Analysis - Introduction to SASD - Structured Analysis Lecturer: JUNBEOM YOO jbyoo@konkuk.ac.kr References Modern Structured Analysis, Edward Yourdon, 1989. Introduction to System Analysis
More informationLesson 11. W.C.Udwela Department of Mathematics & Computer Science
Lesson 11 INTRODUCING UML W.C.Udwela Department of Mathematics & Computer Science Why we model? Central part of all the activities We build model to Communicate Visualize and control Better understand
More informationGuide to EPC Process Modelling
Guide to EPC Process Modelling Guideline to EPC Process Modelling Standard 1. PURPOSE The purpose of this document is to provide a guideline to the Event-Driven Process Chain (EPC) modelling notation used
More informationObject-Oriented Design
Object-Oriented Design Lecture 15: Refining Analysis Relationships Department of Computer Engineering Sharif University of Technology 1 Refining Analysis Relationships Relationships in analysis are converted
More informationTCP/IP Packet Identifier
Software Requirement Specification Requested by: Mr. Ken Swarner Systems Administrator Computer Science Department of Siena College TCP/IP Packet Identifier EdgeTech Development Always on the cutting edge
More informationSQL Server Development 20762: Developing SQL Databases in Microsoft SQL Server Upcoming Dates. Course Description.
SQL Server Development 20762: Developing SQL Databases in Microsoft SQL Server 2016 Learn how to design and Implement advanced SQL Server 2016 databases including working with tables, create optimized
More informationSE310 Analysis and Design of Software Systems
SE310 Analysis and Design of Software Systems Lecture 4, Part-2 Architectural Design January 28, 2019 Sam Siewert OOA/OOD vs. SA/SD Last Year s Consensus - 50% OO Helps, 50% Undecided Discussion of OOA
More informationVANCOUVER Chapter Study Group. BABOK Chapter 9 Techniques
VANCOUVER Chapter Study Group BABOK Chapter 9 Techniques May 27, 2015 David Ghotbi, CBAP Agenda Chapter 8 Review Pop Quiz Break Chapter 9 Review Pop Quiz Q & A 2 Chapter 9 Techniques Techniques: Alter
More informationSlides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only
Chapter 11 Requirements Modeling: Behavior, Patterns, and Web/Mobile Apps Slide Set to accompany Software Engineering: A Practitioner s Approach, 8/e by Roger S. Pressman Slides copyright 1996, 2001, 2005,
More informationSlides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman
Chapter 7 Requirements Modeling: Flow, Behavior, Patterns, and WebApps Slides in this presentation were taken from two sources: Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman
More informationB.H.GARDI COLLEGE OF MASTER OF COMPUTER APPLICATION. Ch. 1 :- Introduction Database Management System - 1
Basic Concepts :- 1. What is Data? Data is a collection of facts from which conclusion may be drawn. In computer science, data is anything in a form suitable for use with a computer. Data is often distinguished
More informationEnterprise Architect. User Guide Series. UML Models. Author: Sparx Systems. Date: 30/06/2017. Version: 1.0 CREATED WITH
Enterprise Architect User Guide Series UML Models Author: Sparx Systems Date: 30/06/2017 Version: 1.0 CREATED WITH Table of Contents UML Models UML Diagrams UML Structural Models Class Diagram Composite
More informationDesign and Information Hiding
Design and Information Hiding 15-214: Foundations of Software Engineering Jonathan Aldrich Related Reading: D. L. Parnas. On the Criteria To Be Used in Decomposing Systems into Modules. CACM 15(12):1053-1058,
More informationComparative Analysis of Architectural Views Based on UML
Electronic Notes in Theoretical Computer Science 65 No. 4 (2002) URL: http://www.elsevier.nl/locate/entcs/volume65.html 12 pages Comparative Analysis of Architectural Views Based on UML Lyrene Fernandes
More information