Figure 5.1 Hardware development process and information usage. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data.

Slides:



Advertisements
Similar presentations
Note: Third Party Brands and Trademarks are Property of Their Respective Owners. ACPI Overview.
Advertisements

Making the System Operational
ECOE 560 Design Methodologies and Tools for Software/Hardware Systems Spring 2004 Serdar Taşıran.
Kellan Hilscher. Definition Different perspectives on the components, behavioral specifications, and interactions that make up a software system Importance.
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
1 Software Testing and Quality Assurance Lecture 13 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
Object-Oriented Analysis and Design
PRJ270: Essentials of Rational Unified Process
Software Configuration Management Speaker: Jerry Gao Ph.D. San Jose State University URL:
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
CMPUT Software Process & QualityProcess Categories - slide# 1©P. Sorenson Engineering Process Category  Processes that specify, implement, or maintain.
Development Processes and Product Planning
CSE Senior Design II Test Planning Mike O’Dell Based on an earlier presentation by Mike O’Dell, UTA.
Configuration Management
Software Configuration Management CSC-532 Chandra Shekar Kandi Chandra Shekar Kandi.
Web Development Process Description
RUP Fundamentals - Instructor Notes
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Software Configuration Management
RUP Implementation and Testing
Rational Unified Process Fundamentals Module 4: Disciplines II.
Figure 8.1 The eight phases of Sun’s structured process. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management.
Configuration Management (CM)
Business Solutions: business rules, principles, and best practices Applications: configuration management document management product configurators collaboration.
Software Engineering Management Lecture 1 The Software Process.
Plant Modeling for Powertrain Control Design Modelica Automotive Workshop Dearborn, MI November 19, 2002 Dr. Larry Michaels GM Powertrain Controls Engineering.
Software Costs Hardware Costs Total Costs % Figure 1.1 Software and hardware development costs in the industrial robots.
Project Life Cycles.
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
Figure 7.1 The entire process divided in several phases with documentation delivered. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating.
Chapter SIX Implementation, Testing and Pragmatics Making it a reality.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
Figure 10.1 Development process managed by AllFusion Harvest Change Manager. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Figure 9.1 Different management tools and PDM systems. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management.
Figure 6.1 PDM and SCM integration—Common API and common repositories. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product.
CASE1 Computer-Aided Software Engineering Advanced Software Engineering COM360 University of Sunderland © 2000.
Figure 3.1 Basic version control. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration.
Figure 11.1 The overlap of DMS and PDM functions. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and.
Configuration Management CSCI 5801: Software Engineering.
The principles of an object oriented software development process Week 04 1.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Draft for discussion1 OSLC PLM roadmap discussion Aug 30 th 2011 Rainer Ersch Gray Bachelor V0.4 updated at meeting Aug 30th.
OSLC PLM Reference model February Summary of the OSLC PLM Reference Model V0.2 February 22 nd 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
Software Configuration Management
Software Configuration Management CSC-532
Software Engineering Management
How Systems are Developed
MANAGEMENT OF STATISTICAL PRODUCTION PROCESS METADATA IN ISIS
A Simulation Framework For Storage System Proposal
The Process of Object Modeling
Overview of System Engineering
BSA 376 AID Lessons in Excellence-- bsa376aid.com.
Object Oriented Analysis and Design
Rational Unified Process
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
Documenting an Architecture
Software Development Process
Patterns.
Chapter 11: Software Configuration Management
Wide Area Workload Management Work Package DATAGRID project
System Reengineering Restructuring or rewriting part or all of a system without changing its functionality Applicable when some (but not all) subsystems.
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Presentation transcript:

Figure 5.1 Hardware development process and information usage. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Concept Development System-Level Design Detail Design Testing and Refinement Production Ramp-Up Create/ change Read Requirements Functions & Features Product Architecture Subsystems & Components Tooling Prototypes Manufacturing process

Figure 5.2 Software design process and information usage. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Requirements Analysis Design Imple- mentation Integra- tion Test Create/ change Read System requirements System architecture Functional description Source Code Executables Release

Figure 5.3 An example of processes and information storage for hardware development. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Define Business Opportunity Define Product Content Verify Product Exhibit Product in Operation Specify Detailed Contents Design & Test Business Cases Requirements Design base or reuse System Architecture Initial product structure Interface specs Function specs Change requests Delivery Structure Product Revision Info TR Refined product structure Design of hardware products Block/Unit description Diagrams Net lists Test cases Test simulators CR and TR Production data Design Archive CAD/CAM Design Archive CAD/CAM Design Archive CAD/CAM Design Archive CAD/CAM Design Archive CAD/CAM Design Archive CAD/CAM RM CR PDM CR/TR RM PDM

Figure 5.4 An example of processes and information storage for software development. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” Release Note Product Revision Info TR Define Business Opportunity Define Product Content Verify Product Exhibit Product in Operation Specify Detailed Contents Design & Test Business Cases Requirements Design base or reuse System Architecture Interface specs Function specs CR Source code Build of Executables Block/Unit description Use cases User documentation Test cases Test simulators CR and TR Production data RM CR SCM CR/TR RM PDM SCM

Figure 5.5 Product development configurations. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” a) Hardware products c) Complex products with software and hardware components System level MechanicASICElectronic b) Software products System level Software comp. A Software comp. B Software comp. C System level Mechanic ASICSoftware

Figure 5.6 Complex PLC. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management”

Figure 5.7 Function overlap in PDM and SCM. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data Management and Software Configuration Management” PDM SCM Build Management Concurrent Development Workspace Mgmt... Classification Production Parts, Assemblies Context Configuration Efficiency Document Mgmt. Costs of components Vendors/Supplier Delivery Process Identification, Process Mgmt Change Mgmt, Meta Data Version/Revision & Storage Configuration Mgmt, Release Mgmt,Variants, History Management Product structure Relations CM