Implementation Work Flow. CSC 532: Advanced Software Engineer Louisiana Tech University

Similar documents
Some Important Annoucement

Object-Oriented Design

Best Practices for Model-Based Systems Engineering

Week 9 Implementation

CHAPTER 5 CO:-Sketch component diagram using basic notations 5.1 Component Diagram (4M) Sample Component Diagram 5.2 Deployment Diagram (8M)

Rational Software White paper

ITEC420: Software Engineering Lecture 3: Recap OO/UML Requirement Workflow

What is Systems Engineering?

CSC Advanced Object Oriented Programming, Spring Overview

A Multifaceted Dependency Map of MySQL

index_ qxd 7/18/02 11:48 AM Page 259 Index

Architectural Blueprint

Object Oriented Model of Objectory Process

SE Assignment III. 1. List and explain primitive symbols used for constructing DFDs. Illustrate the use of these symbols with the help of an example.

Object Oriented Analysis and Design - Part2(Design)

Objectives. Explain the purpose and objectives of objectoriented. Develop design class diagrams

Software Architectures

UML Views of a System

Model Driven Development Unified Modeling Language (UML)

3rd Lecture Languages for information modeling

Presenter: Dong hyun Park

UML Modeling. Sumantra Sarkar. 29 th June CIS 8090 Managing Enterprise Architecture

Module 3. Overview of TOGAF 9.1 Architecture Development Method (ADM)

Guido Sandmann MathWorks GmbH. Michael Seibt Mentor Graphics GmbH ABSTRACT INTRODUCTION - WORKFLOW OVERVIEW

Component Design. Systems Engineering BSc Course. Budapest University of Technology and Economics Department of Measurement and Information Systems

V&V: Model-based testing

Designing Component-Based Architectures with Rational Rose RealTime

Avancier Methods (AM) Software Architecture Diagrams

Representing System Architecture

How to Harvest Reusable Components in Existing Software. Nikolai Mansurov Chief Scientist & Architect

Oliopäivät Modelling Now and in the Future, with Acronyms or without = RSA

UNIT I. 3. Write a short notes on process view of 4+1 architecture. 4. Why is object-oriented approach superior to procedural approach?

Orthographic Software Modeling A Practical Approach to View Based Development

Unified Modeling Language (UML)

Requirements and Design Overview

Topic : Object Oriented Design Principles

UP Requirements. Software Design - Dr Eitan Hadar (c) Activities of greater emphasis in this book. UP Workflows. Business Modeling.

Introduction to UML p. 1 Introduction to the Object-Oriented Paradigm p. 1 What Is Visual Modeling? p. 6 Systems of Graphical Notation p.

KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY. (An NBA Accredited Programme) ACADEMIC YEAR / EVEN SEMESTER

Lecture 17: (Architecture V)

SE310 Analysis and Design of Software Systems

Object-Oriented and Classical Software Engineering DESIGN 11/12/2017. CET/CSC490 Software Engineering Design CHAPTER 14. Stephen R. Schach.

Model-based Transition from Requirements to High-level Software Design

UML Fundamental. OutLine. NetFusion Tech. Co., Ltd. Jack Lee. Use-case diagram Class diagram Sequence diagram

Applying UML to System Engineering Some Lessons Learned Murray Cantor Principal Consultant

Module 1 : Fundamentals of Testing. Section 1: Manual Testing

Architectural Design

Test requirements in networked systems

S1 Informatic Engineering

Chapter 2, Modeling with UML: UML 2 Hightlights

What is Software Architecture

The ATCP Modeling Framework

the gamedesigninitiative at cornell university Lecture 13 Architecture Design

Architectural Blueprint The 4+1 View Model of Software Architecture. Philippe Kruchten

Ch 1: The Architecture Business Cycle

Software Design and Analysis CSCI 2040

Object-Oriented Design

IBM Rational Developer for System z v7.6. Download Full Version :

Use Case Model. Static Structure. Diagram. Collaboration. Collaboration. Diagram. Collaboration. Diagram. Diagram. Activity. Diagram.

Object-Oriented Design

Enterprise Architect Training Courses

Software Architecture

GSAW 2007 SW Architecture Workshop - Managing the Complexity of Your Large-Scale Software Architecture and Design. Richard Anthony

NIMSAD Evaluation of the Rational Unified Process

OBJECT ORIENTED DESIGN with the Unified Process. Use Case Realization

Automated Validation of T&E Instrumentation Systems

Object-Oriented Analysis and Design Using UML

Parallel Programming Patterns Overview and Concepts

SYLLABUS CHAPTER - 1 [SOFTWARE REUSE SUCCESS FACTORS] Reuse Driven Software Engineering is a Business

Analysis and Design with UML

A PROPOSAL FOR MODELING THE CONTROL SYSTEM FOR THE SPANISH LIGHT SOURCE IN UML

Today s Lecture. Types of Software Reuse. Software Reuse. Lecture 9: Software Re-Use

System and Software Architecture Description (SSAD)

Architectural Design

Introduction to Programming

CS 575: Software Design

Passport Automation System

Index. : (colon), 80 <<>> (guillemets), 34, 56

Creating a Lattix Dependency Model The Process

Outline of UML and Unified Process. Object Oriented Analysis/Design/Programming UML1.5. Koichiro Ochimizu, JAIST. UML&UP outline 1.

Ch 1: The Architecture Business Cycle

What s Next. INF 117 Project in Software Engineering. Lecture Notes -Spring Quarter, Michele Rousseau Set 6 System Architecture, UML

University of Calgary Department of Electrical and Computer Engineering. SENG : Object Oriented Analysis and Design Behrouz Homayoun Far

Java Software Solutions for AP Computer Science 3rd Edition, Lewis et al. 2011

Dog Houses to sky scrapers

Lecture 17 Engineering Design Resolution: Generating and Evaluating Architectures

Software Architecture

UNIT 5 - UML STATE DIAGRAMS AND MODELING

Master of Science Thesis. Modeling deployment and allocation in the Progress IDE

cameo Enterprise Architecture UPDM / DoDAF / MODAF / SysML / BPMN / SoaML USER GUIDE version 17.0

CHAPTER 5 ARCHITECTURAL DESIGN SE211 SOFTWARE DESIGN

Appendix A - Glossary(of OO software term s)

Architectures in Context

DITA PUBLISHING. The true costs of taking your DITA content online. A WebWorks.com White Paper.

Enterprise Architect. User Guide Series. Team Support. Author: Sparx Systems Date: 15/07/2016 Version: 1.0 CREATED WITH

Outline. COM overview. DCOM overview. Comparison DCOM and Corba

PASS4TEST. Prüfungshilfen für IT Zertifizierungen. Wir bieten Ihnen einen kostenlosen einjährigen Upgrade Service an

(Traditional) Software Development Activities

UNIT-I Introduction of Object Oriented Modeling

From Code To Architecture

Transcription:

Implementation Work Flow CSC 532: Advanced Software Engineer Louisiana Tech University

Topics to cover Introduction Artifacts Workers Activities

Introduction l Fundamental goal is to build a working version of system. l Craft out the Architecture l Implement the Design in terms of components. l Plan System Integrations l Implement Design classes and subsystems l Unit test components l Integrate Components.

Implementation Workflow Activities and Workers Architect! & Developers! Architectural! Implementation! System Integrator! Integrate! System! Component! Engineer! Implement! a Class! Implement a! Subsystem/component! Perform a Test!

Artifacts l Implementation Model - Component - Implementation subsystem - Interface l Architecture Description - View of Implementation Model l Integration Build Plan

Implementation Model l Describes how elements of design model are implemented in terms of components such as source code, executable, etc. l Describe how components are organized using the structuring and modularization mechanisms of the implementation environment and programming languages l Hierarchy of Implementation (sub) Systems containing Components and Interfaces

Component l Physical packaging of model elements l Standard stereotypes which the UML assigns Ø <<executable>> -- a program that may run on a node Ø <<library>> -- static or dynamic library Ø <<file>> -- static or dynamic library Ø <<table>> -- a database table Ø <<document>> -- a document Ø technology specific (<<ActiveX>>, <<Applet>>, <<DLL>>, <<CORBA Component>>, etc.)

Component Diagram <<Page>> Search.html <<Executable>> Search.exe <<page>> Front.html <<table>> Book.html <<table>> Author.

Implementation of subsystem l Organize implementation model artifacts into more manageable pieces l Manifested by a packaging mechanism in implementation environment Ø Component packages Ø Interfaces l Trace one-to-one with design subsystems Ø same dependencies to other subsystems, interfaces Ø provides same interfaces maps one-to-one with which components or other implementation subsystems within the subsystem provide the interfaces of the subsystem

Interface l As in design, interfaces define the operations implemented by components and implementation subsystems l A component that realizes (and thus provides) an interface must implement all the operations defined by the interface Accounting <<interface>> Post() Accounting

Component implementation with build tools l Build tools Ø Ø Ø Unix make Ant: XML based build tool Organize implementation into modules source Document Output (binary) package

Architectural Description l implementation model l Decomposition of implementation model into subsystems, their interfaces, and dependencies between them l Key components Ø trace to architecturally significant design classes Ø executable components Ø components that are general, central, or implement generic design mechanisms that many other components depend on

Integrate Build Plan l Describes the build that will occur with In a given iteration. l Build plan for each increment Ø list of functionality: use cases and/or scenarios Ø list of implementation subsystems and components l Test each build, including regression tests l Configuration management with the c build plan enit

WORKERS v v v ARCHITECT COMPONENT ENGINEER SYSTEM INTEGRATOR

ARCHITECT l Outlines the implementation model. l Ensure the completeness and correctness. l Mapping the executable components onto nodes within the deployment model. l Include the components from the implementation model and the updated contents of deployment model.

Component Engineer l Is responsible for the source code of the components and subsystems. l For coding the interfaces associated with components and subsystems. l Is responsible for unit testing of his or her components.

Unit Testing l Specification testing l Note that black box testing is not unit testing l Structural testing or white box testing control flow graph Method flow graph Class flow graph

System Integrator l Is responsible for designing integration build plan and performing incremental integration.

Implementation Workflow Activities and Workers Architect! Architectural! Implementation! System Integrator! Integrate! System! Component! Engineer! Implement a! Subsystem! Implement! a Class! Perform a Unit Test!

End chapter Questions/Review l What are main activities in this workflow? l Describe what are necessary tools or processes in this workflow and how they can help growing maturity of, improving quality of the SW product?