CS 410 Professional Workforce Development I Spring 2019

Slides:



Advertisements
Similar presentations
Prescriptive Process models
Advertisements

Intro slide « Your 1 or 2 liner statement / tag-line » (Website? Pictures, Video? Other links?)
I Speak 2010 © 2010 The McGraw-Hill Companies, Inc. All rights reserved. Appendix Working and Presenting as a Group.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
CS & ECE Senior Design Project Winter 2008 Karen Davis Chia Han Altan Ferendeci.
Project Title (as descriptive as possible) Group Members CPE Computer Engineering Design I Electrical and Computer Engineering.
Instructions & Notes This template was created to help you: – Show the team where you are going via slides representing each planned activity. – Keep your.
Best Practices In Design Outcomes Of A Survey P. H. King, PhD, PE Joan Walker, PhD Vanderbilt University.
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
1 The Initial Report Preparation Guidelines. 2 The Initial Report u Definition of project scope u Project aims and objectives u Initial project plan.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CS 3610: Software Engineering – Spring 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class.
<Idea Title> Students : XXX, YYY (University)
BIS3324 Group Assignment – Schedule, guideline & templates (2015-Jan Semester)
U.S. Department of Agriculture eGovernment Program Design Approach for usda.gov April 2003.
The Systems Development Life Cycle
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter Final Report – An Overview Week 4 Day 2.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Software Engineering Lecture 10: System Engineering.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Collaborative & Interpersonal Leadership
Technical Presentation or Poster
7 Training Employees What Do I Need to Know?
A Level Computer Science
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Project Management Information and Tracking Advanced Concepts
CS 389 – Software Engineering
Chapter 6 Initiating and Planning Systems Development Projects
Software Configuration Management
Architecture Concept Documents
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
Software Requirements analysis & specifications
Project Charter <Project Name>
Universal Design Lab 4.
MIT GSL 2018 week 3 | thursday Meteor and App Ideation.
Requirements Analysis
Systems analysis and design, 6th edition Dennis, wixom, and roth
Systems analysis and design, 6th edition Dennis, wixom, and roth
Project Management Process Groups
Analysis models and design models
Lecture 6 Initiating and Planning Systems Development Projects
CS 410 Professional Workforce Development I Spring 2019
CS 410 Professional Workforce Development I Spring 2019
CS 410 Professional Workforce Development I Spring 2019
CS 8532: Advanced Software Engineering
CS 410 Professional Workforce Development I
CMPE/SE 131 Software Engineering February 21 Class Meeting
Huddle Boards High-level Overview Let’s review a HUDDLE BOARD…
CS 410 Professional Workforce Development I Spring 2019
CS 410 Professional Workforce Development I Spring 2019
AICT5 – eProject Project Planning for ICT
Goal-Driven Software Measurement
CS 410 Professional Workforce Development I Spring 2019
Context By: Team Flirt.
Executive Project Kickoff
MEng projects 2012 week 10 update
X-Elevate.
Chapter 6 Initiating and Planning Systems Development Projects
Innovation Challenge Every business starts with an idea, but to be successful you need more than just a good idea. Starting from a common challenge question,
Chapter 8: Actor-System Interaction Modeling
Presentation transcript:

CS 410 Professional Workforce Development I Spring 2019 Module 3: Project Selection and Presentation Skills 02/09/2019 - 03/01/2019 Week 7 –26 February 2019 Instructor: Jim Brunelle (jabrunel@odu.edu) Office: E&CS 3111 (757-683-7722) Office Hours: Tuesday 1300-1400 or by Appt

Lecture Agenda 1030-1045: Welcome/Discussion 1045-1130: Website Review Website Contents Guidelines Feasibility Presentation Format Guidelines 1045-1130: Website Review Current State Process Flow Solution Statement/Characteristics Competition Matrix 1130-1145: Major Functional Component Diagram (MFCD) 1145-1155: Timeline to Formal Feasibility Presentation 1155-1200: Feasibility Presentation Grading 1200-1220: Group Planning Window CS 410 Spring 2019 Week 7: 26 February

“If you don’t know where you are going, you’ll end up someplace else.” “If you come to a fork in the road, take it.” “We’re lost, but we’re making good time.” -Yogi Berra CS 410 Spring 2019 Week 7: 26 February

Website Contents Guidelines Homepage Team color identified Think about a project name – try one out Something about your project (picture etc.) – ex: Quick Eats - Fall 2018 Maybe include Problem Description Links to other pages: Team, Problem, Solution, Presentations, Deliverables, References Team Biography Page (Done) Picture of each team member and mentor Bio for each team member and mentor Problem Page Identification of the generic societal problem (problem statement) Characteristics of the problem listed Current state flow diagram (indicate problem areas) CS 410 Spring 2019 Week 7: 26 February

Website Contents Guidelines Continued Solution Page Problem Solution Statement Problem Characteristics Solution Flow Diagram What the solution Will and Will Not do Presentations Page Original Idea Presentation Feasibility Presentation Deliverbles Page Process Flow Diagrams (Current/Solution) Competition Matrix Other working Material posted for review Reference Page Link to all reference information for research performed CS 410 Spring 2019 Week 7: 26 February

Feasibility Presentation Guidelines ~20-25 slides Title Page (Picture, Tag Line, CS410 xxx Team, Spring 2019...) (1 slide) Tale of Contents (What we will tell the audience) (1 slide) The Team (Who’s Who - Picture, Role...) (1 slide) Background (Leads into the problem statement – may include data or other pertinent information/illustrations etc) (~1-3 slides) The Problem (~3-6 slides) Problem Statement What/Who is Affected Problem Characteristics Current Process Flow Solution (~5-7 slides) Solution Statement or Objective Solution Characteristics Solution Process Flow MFCD (Hardware and Software) Market Assessment (~2 Slides) Competition Matrix Benefits to Customer Base Conclusion(s) (~1-2 slides) Key Points Summary Who Benefits/Why Important/Why Feasible... References (1 slide) CS 410 Spring 2019 Week 7: 26 February

Feasibility Presentation Examples Research Link Spring 2016 RepairLink Presentations SCIDS Sping 2014 ODU Tennis - Fall 2018 Powerplay Fall 2016 CS 410 Spring 2019 Week 7: 26 February

Problem=>Solution Example Problem Characteristics: Survival in the water column is contingent on the ability to see objects in low light conditions. Rapid acceleration is essential. Acceleration is accompanied by in increase in demand for oxygen. Packaging must be resilient and flexible. Solution Characteristics: Vision is achieved using forward-looking, high resolution optics that perform extraordinarily in well in low-light conditions. Acceleration is achieved by implementation of a turbo-thruster mechanism. A demand-driven oxygen portal responds in real time. Interlocking armor provides protection without sacrificing motion flexibility. CS 410 Spring 2019 Week 7: 26 February

Team Website Walk-through Problem Statement Problem Characteristics Current State Process Flow Solution Statement/Characteristics Competition Matrix CS410 – Gold - TutorU CS410 - Silver - Detecting and Tracking Seizures CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams What/Why Objective: “Create a Major Functional Component Diagram (MFCD). Build a Figure to include: Hardware needed Software needed Legacy systems with which it must interface User roles and where they interact with the solution” CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams What/Why What s it? The MFCD is a system architecture diagram (or diagrams) used to show the relationship between different components. Usually they are created for systems which include hardware and software and these are represented in the MFCD(s) to show the interaction between them.  CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams What/Why The MFCD(s) present a clear and comprehensive perspective of the key hardware and/or software constructs that represent the overall architecture of a system such that it can be understood by different stakeholders. The diagrams must self descriptive, consistent, and sufficiently complete to convey the overall architecture from a hardware and from a software perspective. The interdependencies between hardware components, software components and major interfaces should be evident. CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples - System CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples - Software CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples - Software CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples- Android APP CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples – Android APP CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Examples - Software CS 410 Spring 2019 Week 7: 26 February

Major Functional Component Diagrams Light reading – A Very Good Presentation on the Subject A Software Experts Veiw on Diagramming CS 410 Spring 2019 Week 7: 26 February

Current Process=>Solution Process =>MFCD Example CS 410 Spring 2019 Week 7: 26 February

Current Process=>Solution Process =>MFCD Example CS 410 Spring 2019 Week 7: 26 February

Current Process=>Solution Process =>MFCD Example CS 410 Spring 2019 Week 7: 26 February

Formal Feasibility Presentation: Tuesday, March 19 CS 410 Spring 2019 Week 7: 26 February

What’s Left to Meet 19 March deadline Build Feasibility Presentation Template Refine Problem Statement/Characteristics (if needed) Build/Deliver Solution Process Flow Build/Deliver MFCD Populate presentation template with latest “deliverable” versions Fill in Background, Customer/User info, Market analysis slide (if needed) Build Conclusions slide Establish “presenter” roles (~3-4 presenters/group): Intro Problem Solution Market Conclusion CS 410 Spring 2019 Week 7: 26 February

Feasibility Presentation Grading Ruberic CS 410 Spring 2019 Week 7: 26 February