Time Domain Analysis Tool Semester Project Presentation Ehsan Ghaneie Ken Waller EEL 6883 – Software Engineering II Spring 2007.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
1 Prescriptive Process Models. 2 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive process.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Chapter 22 Product Line Engineering Week 1 CIS 673.
Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
Documenting a Software Architecture By Eng. Mohanned M. Dawoud.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Unified Modeling Language
The Rhapsody in C++ Tool Training "Essential" © I-Logix v2.3 25/9/2000 EI-1 “Essential” Rhapsody in C++ Introduction.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Software engineering for real-time systems
SE 470 Software Development Processes James Nowotarski 21 April 2003.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
© Copyright Eliyahu Brutman Programming Techniques Course.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Object Oriented Analysis and Design Using the UML
BRUE Behavioral Reverse Engineering in UML as Eclipse Plugin MSE Presentation 1 Sri Raguraman.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
Using UML to report results of project management for information systems projects Donna M. Gavin MMIS 621 Information Systems Project Management Assignment.
Slide 12.1 © The McGraw-Hill Companies, CS 4310: Software Engineering Lecture 7 Systems Analysis Object-Oriented Design.
Lesson 7 Guide for Software Design Description (SDD)
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
Software Engineering CS B Prof. George Heineman.
AgentTool (III) Dynamic MSE Presentation 1 Binti Sepaha.
Rational Unified Process Fundamentals Module 4: Disciplines II.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
Multi-agent Research Tool (MART) A proposal for MSE project Madhukar Kumar.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
Instructor: Peter Clarke
ACS 560 – SOFTWARE ENGINEERING Course Accomplishment Summary Shilpashree K.S Fall 2010 Purdue University – Fort Wayne Instructor – Dr. John Tanik.
11 Partnership for Performance How to hear this lecture Click on the icon: to hear the narration for each slide.
SWEN 5130 REQUIREMENTS ENGINEERING Unified Modeling Language Short Tutorial By Yuvaraj Mani Teaching Assistant SWEN 5130 Spring semester 2006.
IBM Software Group ® Overview of SA and RSA Integration John Jessup June 1, 2012 Slides from Kevin Cornell December 2008 Have been reused in this presentation.
Systems Analysis and Design in a Changing World, 3rd Edition
DEV337 Modeling Distributed Enterprise Applications Using UML in Visual Studio.NET David Keogh Program Manager Visual Studio Enterprise Tools.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
Request for Proposal (RFP)
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
PRJ566 Project Planning & Management Software Architecture.
Midterm Study Guide COP 4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of EE and Computer Science University of Central.
Lab 5 CPIT 250 System Analysis and Design.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
1 5/18/2007ã 2007, Spencer Rugaber Architectural Documentation Graphical (views) and textual Kruchten's 4+1 Views –Philippe B. Kruchten. "The 4+1 View.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
UML AN OVERVIEW. Topics covered in this Session 1. Introducing UML. 2. What constitutes the UML. 3. Concepts of UML.
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.
Building Enterprise Applications Using Visual Studio®
Systems Engineering Tool for Intelligent Transportation
Software Development, Quality and Documentation Tool
Unified Modeling Language
Object-Oriented Design
Software Development, Quality and Documentation Tool
Analysis models and design models
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
CS 8532: Advanced Software Engineering
Presentation transcript:

Time Domain Analysis Tool Semester Project Presentation Ehsan Ghaneie Ken Waller EEL 6883 – Software Engineering II Spring 2007

Presentation Agenda Project Overview/Purpose Project Metrics Project Deliverables Description of 3 rd Party Software Packages used Software Development Model System Design (Architectural and Detailed) Difficulties Encountered and Lessons Learned System Demonstration Questions and Answers

Project Overview and Purpose Generate Time-Domain plots Circuit Data File Dynamically “Tune” the circuit parameters and observe the result in both domains in a real-time manner Other features…

Project Metrics - Documentation Only Highlights shown in this Presentation Document NameNumber of PagesNumber of Diagrams Project Proposal/Description20 Concept of Operations (CONOPS)1410 (1 Sequence) Software Requirements60 Project Management Plan63 Architectural Design1213 (3 Package, 7 Use Case, 1 Sequence) Detailed Design1819 (11 Class, 8 Sequence) Test Plan1318 User's Manual57 System Installation10 System Requirements10 Totals78 70 (31 UML: 3 Package, 7 Use Case, 10 Sequence, 11 Class)

Project Metrics – Source Code Some additional metrics Number of OO-classes: 19 Number of Requirements: 22 Number of printed pages of source code (*.cpp/*.h): 63

Project Deliverables Documentation Project Proposal/Description Document Concept of Operations (CONOPS) Document Software Requirements Document Project Management Plan Document Architectural (High-Level) Design Document Detailed Design Document Test Plan Document User’s Manual Document System Installation Document System Requirements Document Project Presentation Slides Microsoft Visio Drawings and UML Model Software C++ Source Code (*.cpp/*.h files) All Visual Studio Project Related Files Executable Program File and any Additional Dynamic Link Libraries (DLL)

3 rd Party Software Packages Qt From TrollTech Object-Oriented C++ package for GUI development Open Source, freely available V used Qwt Available from SourceForge Extension of Qt that added ability to plot graphs Open Source, freely available V used FFTW (Fast Fourier Transform of the West) Available from MIT C-based library that assists with FFT computations/algorithms Helped reduce Development risks, but introduced learning curve risk

Software Development Model Modified Waterfall (Hybrid) Would have used Spiral, but time constraints prevented its use Integrates some aspects of Spiral Notes: CONOPS developed to help ID requirements (pen and paper, then formal capture) Design split into two phases: architectural and detailed

System Architecture Design – Package Diagram

System Architecture Design – Use Case Model

System Architecture Design – Subsystem Breakdown

System Detailed Design - Strategy Define the Static Model Use UML Class Diagrams Assign each class to a subsystem Define inheritance, associative, and compositional relationships Define methods Define Dynamic Model Use UML Sequence Diagrams Create a Sequence Diagram for each Use Case See Word document for a quick review

Difficulties and Lessons Learned Identifying, installing and configuring 3 rd Party Software Appropriate versions and licenses had to be considered Learning how to use 3 rd Party Software Hundreds of OO classes provided Documentation and examples were a huge help Lesson Learned: Tradeoffs! Reduced Development Risks, but increased Personnel/Training risks “No free lunch!”

Demonstration Time! Live execution of the resulting software application now demonstrated…

Questions/Comments? Thank you!