November 3, 2015  Embry Riddle Prescott Team #TBD Member1, Member2, Member3, Member4 [Alphabetical] Real-Time Systems Software Proof-of- Concept [12+

Slides:



Advertisements
Similar presentations
Lab Course / Praktikum: Winter Semester 2011/2012 Project Management and Software Development for Medical Applications Computer Aided Medical Procedures.
Advertisements

The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
03/12/2001 © Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Software Testing and Reliability Testing Real-Time Systems Aditya P. Mathur Purdue University May 19-23, Corporation Minneapolis/St Paul,
PERTEMUAN 7 Copyright © 2002 Pearson Education, Inc.
Connecting with Computer Science, 2e
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
David Harrison Senior Consultant, Popkin Software 22 April 2004
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
IS 460 Notes IS Strategic Planning By Thomas Hilton.
These slides are designed to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright.
Best Practices By Gabriel Rodriguez
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Chapter 13 Architectural Design
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
10/24/2015  Embry Riddle Prescott Team #TBD Member1, Member2, Member3, Member4 [Alphabetical] Level 3 – Internal Design Inspection Scrum Sprint Leader.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
Software Engineering. Software Engineering is… Design Coding Testing Debugging Documentation Maintenance …of new software.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
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.
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.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
ECE398: The Design Review Fall What the Design Review is  Board meeting with engineers- (faculty, TA, classmates)  Structured discussion of your.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Lab Course / Praktikum: S ummer Semester 2012 Project Management and Software Development for Medical Applications Computer Aided Medical Procedures (CAMP),
RBSP Radiation Belt Storm Probes RBSP Radiation Belt Storm Probes 12/25/20151 Flight Software Template for Instrument Critical Design Review Gary M. Heiligman.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
© Bennett, McRobb and Farmer 2005
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.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Software Systems Division (TEC-SW) ASSERT process & toolchain Maxime Perrotin, ESA.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
EE400D DOCUMENTATION INSTRUCTIONAL SERIES CRITICAL DESIGN REVIEW.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 6/6/2016 1/25 IT076IU Software Engineering Project Review 2.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
1 The Software Engineering Education at CSULA Jiang Guo Jose M. Macias June 4, 2010.
November 3, 2015  Embry Riddle Prescott Team #TBD Member1, Member2, Member3, Member4 [Alphabetical] Real-Time Systems Software Proof-of- Concept [12+
Introduction to Software Engineering Course Outline
CS616 Software Engineering I BoNY
Lecture 0 Software Engineering Course Introduction
Object-Oriented Analysis & Design
CMPE 412 Software Engineering
Chapter 13 Architectural Design
Chapter 18 MobileApp Design
Overview of System Engineering
BSA 376 Competitive Success/snaptutorial.com
BSA 376 AID Lessons in Excellence-- bsa376aid.com.
BSA 376 Education for Service/snaptutorial.com
BSA 376 Teaching Effectively-- snaptutorial.com
Team #TBD Member1, Member2, Member3, Member4 [Alphabetical]
Team #TBD Member1, Member2, Member3, Member4 [Alphabetical]
Chapter 13 Architectural Design
CS 8532: Advanced Software Engineering
Decision Time – Who will do what?
Team #TBD Member1, Member2, Member3, Member4 [Alphabetical]
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
System architecture, Def.
Team #TBD Member1, Member2, Member3, Member4 [Alphabetical]
Team #TBD Member1, Member2, Member3, Member4 [Alphabetical]
Presentation transcript:

November 3, 2015  Embry Riddle Prescott Team #TBD Member1, Member2, Member3, Member4 [Alphabetical] Real-Time Systems Software Proof-of- Concept [12+ Diagram Content Slides, Intro, Roadmap, Summary – Move Irrelevant Slides to Backup Section]

Presentation Roadmap Capability Requirements Functional Design (Modelio, Visio Stencils, UML Stencils, MS Software Design Stencils, or Basic Drawing Tools in PowerPoint) ModelioVisio StencilsUML StencilsMS Software Design StencilsModelioVisio StencilsUML StencilsMS Software Design Stencils Real-Time Requirements: Service Rates (T i ), Computational Load (C i ), and Deadlines (D i ) for 2 or More Services S i –Cheddare Worst-Case Analysis –Scheduling Point / Completion Point Tests –Feasibility and Safety Overall Real-Time Analysis & Design –Cyclic Executive –RTOS –Linux POSIX Real-Time Proof-of-Concept and Time-stamp Trace  Embry Riddle Prescott2 Real-Time Analysis Timing Diagrams (Worst-Case Analysis) Cheddar Analysis Scheduling Point or Completion Test System Models Block Diagram Software Functional Models CFD/DFDCFDDFD Entity Relationship Diagram (ERD)Entity Relationship Diagram Mealy/Moore State MachineMealyMoore Flowchart CASE TOOLS USED: Modelio, Cheddar, Other?

Key Functional SA/SD Models – Content #1 CFD/DFD - Transformation/Ev en-Driven ER/EER - Information Model State Machine – Behavioral Flow-Charts – Detailed Procedural  Sam Siewert CFD/DFD ER/EER SM/EFSM Flowchart

System Block Diagram – Content #2 Any Useful Information about System Keep it Simple – One Page View of Everything Users, IT, Software, External Systems and Hardware  Embry Riddle Prescott4 Software System Service, Task, Process, etc. Hardware or Other System External Entity I/O label End Users System Administration Cloud Service I/O label

Capability Requirements 1. Capability #1 2. Capability #2 3. Capability #3 4. Capability #4  Embry Riddle Prescott5

Real-Time Requirements 1. RT Requirement #1 2. RT Requirement #2  Embry Riddle Prescott6

Performance Requirements 1. WCET Requirement #1 2. WCET Requirement #2  Embry Riddle Prescott7

Service Set Feasibility and Safety ANALYSIS WCET Expected Ci RM LUB Test Cheddar Analysis for Worst-Case and Simulation Scheduling Point, Completion Test FeasibilityMarginSafety  Embry Riddle Prescott8

SA/SD CFD/DFD DESIGN  Embry Riddle Prescott9

ER/EER DESIGN  Embry Riddle Prescott10

SA/SD State Machine DESIGN  Embry Riddle Prescott11

SA/SD Flowchart DESIGN  Embry Riddle Prescott12

Proof-of-Concept ANALYSIS Detailed Description of Platform Resources (Jetson TK1 or Texas Instruments Tiva TM4C Dev Board) Prototype Implementation of Key Services (2+) Time-stamp Tracing of Key Services [Profiling of Key Services - Optional] Purpose –Addresses High Risk Design/Implementation –Real-Time Risks (Deadline, Deadlock, Inversion) –Resource Use Analysis –Resource Margin for Safety  Embry Riddle Prescott13

Highlight Concurrent Verification & Validation Plans  Sam Siewert14 Software Engineering: A Practitioner’s Approach, 8/e (McGraw- Hill, 2014) copyright 2014 by Roger Pressman Backlog –Requirements, Design Validation, Requirements (RT and Funcional), Design Verification Plans –Acceptance Test Plans –System Testing –Integration Testing –Unit Testing –Component Design –Code Generation

Summary Thank Audience Encourage Submission of Deficiency Sheets Open to Q&A for 10 Minutes  Sam Siewert15

Backup Slides Move Slides Not Making MUST PRESENT Status to HERE for Q&A  Embry Riddle Prescott 16