CMPE/SE 131 Software Engineering February 21 Class Meeting

Slides:



Advertisements
Similar presentations
SOFTWARE PRESENTATION ODMS (OPEN SOURCE DOCUMENT MANAGEMENT SYSTEM)
Advertisements

CS 160: Software Engineering September 8 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Team READ THIS SLIDE CAREFULLY Beta Demonstrations will be given by each team at our all-hands meeting on the dates listed at All-Hands Meeting Agendas.All-Hands.
CS 235: User Interface Design August 27 Class Meeting Department of Computer Science San Jose State University Spring 2015 Instructor: Ron Mak
CS 235: User Interface Design August 27 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Term 2, 2011 Week 3. CONTENTS The physical design of a network Network diagrams People who develop and support networks Developing a network Supporting.
CS 160: Software Engineering October 8 Class Meeting
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Problem Statement: Users can get too busy at work or at home to check the current weather condition for sever weather. Many of the free weather software.
1 Introduction to Software Engineering Lecture 1.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
CS 151: Object-Oriented Design August 29 Class Meeting Department of Computer Science San Jose State University Spring 2012 Instructor: Ron Mak
Unit #7 Charts Questions? Comments?. MS PPT 2007: Presentations Made Easy; Planning and Preparing PowerPoint allows you to create a professional presentation.
DSD Course – Project Status Presentation 2 School of Innovation, Design and Engineering Malardalen University Dec 18 th,
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
CS 160 and CMPE/SE 131 Software Engineering February 18 Class Meeting Department of Computer Science Department of Computer Engineering San José State.
CS 160 and CMPE/SE 131 Software Engineering February 23 Class Meeting Department of Computer Science Department of Computer Engineering San José State.
CS 160 and CMPE/SE 131 Software Engineering February 11 Class Meeting Department of Computer Science Department of Computer Engineering San José State.
CMPE 226 Database Systems April 19 Class Meeting Department of Computer Engineering San Jose State University Spring 2016 Instructor: Ron Mak
CS 160 and CMPE/SE 131 Software Engineering March 22 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
CS 160 and CMPE/SE 131 Software Engineering March 24 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
Advanced Higher Computing Science
Information System Applications
Innola Solutions, Inc., USA March 24, 2017
Pepper modifying Sommerville's Book slides
CMPE 135: Object-Oriented Analysis and Design August 31 Class Meeting
Microsoft Office Live Meeting 2007
Working in the Forms Developer Environment
CMPE 280 Web UI Design and Development August 29 Class Meeting
Systems Engineering Tool for Intelligent Transportation
CSCI Research Project and Seminar Team #1 11/13/2007
Section 17.1 Section 17.2 Add an audio file using HTML
Software Documentation
Adding a File to a Course
Section 15.1 Section 15.2 Identify Webmastering tasks
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Chapter 3: The Project Management Process Groups: A Case Study
Design, prototyping and construction
CS 174: Server-Side Web Programming February 12 Class Meeting
Introduction to CS Senior Design Project I / II
CSE 403 Project SDS Presentation
Data Collection in MTM Choosing the right method for survey data collection.
Requirements – Scenarios and Use Cases
Increased Efficiency and Effectiveness
Read Me (Delete this slide.) [1 of 2]
Forging the Innovation Generation
Read Me (Delete this slide.) [1 of 2]
Systems Analysis and Design in a Changing World, 6th Edition
Analysis models and design models
Software Design Lecture : 15.
OOA&D II Bo Wang, Kan Qi Adapted from Alexey Tregubov’s Slides.
Workshop.
Read Me (Delete this slide.) (1 of 2)
Bulloch Information Session
Systems Analysis and Design I
CIS 4328 – Senior Project 2 And CEN Engineering of Software 2
CMPE/SE 131 Software Engineering March 23 Class Meeting
State of New Jersey Department of Health Patient Safety Reporting System Module 3 – Root Cause Analysis.
CMPE/SE 131 Software Engineering February 16 Class Meeting
Kapi’olani Community College
Chapter 3: The Project Management Process Groups: A Case Study
M. Kezunovic (P.I.) S. S. Luo D. Ristanovic Texas A&M University
Team [Team Name] Beta Presentation
CMPE/SE 131 Software Engineering March 7 Class Meeting
Design, prototyping and construction
Read Me (Delete this slide.) (1 of 2)
Chapter 8: Actor-System Interaction Modeling
CSE4939W/4940 CS & E Design Lab I/II
Presentation transcript:

CMPE/SE 131 Software Engineering February 21 Class Meeting Department of Computer Engineering San José State University Spring 2017 Instructor: Ron Mak www.cs.sjsu.edu/~mak

Conceptual Design

Conceptual Design, cont’d A high-level description of your application design. A written report and an oral presentation. A “product pitch”. Add to the Functional Specification. Conceptual design  formal design document Created by the software developers. Understandable by the product’s users, clients, and stakeholders.

Conceptual Design Contents Problem statement and objectives. Copy from the Functional Specification for now. Remove later when adding the Conceptual Design to the Functional Specification. Overview of your solution A list of major features. A description of your application’s major modules and how they will interact with each other. High-level diagrams. No implementation details.

Conceptual Design Contents, cont’d Prototype of a key use case A sequence of screen shots. Or a live demo with mocked-up web pages (can be static pages). Or Rails-generated web pages.

Example Conceptual Design Presentation Real-time Fault Analysis for Crewed Space Vehicle Systems (Based on a real NASA application and an actual presentation.)

Problem Statement During emergency situations, a real-time fault analysis system must rapidly suggest correct remedies for the onboard astronauts to implement. Space vehicle fault analysis is a daunting task, especially in extremely remote environments.

Project Objectives Design and develop a real-time fault analysis system for crewed space vehicles that overcomes the following challenges: Diverse and disparate data sources Incomplete or imprecise vehicle sensor data Insufficient working knowledge of the vehicle system Real time diagnosis and rapid response Limited system resources Loss of communication with ground control

Product Features A web application that stores and remembers past faults and their remedies in a repository. Each fault is defined by a snapshot of sensor readings. Collect and integrate data from various sources. Sensor readings Parts lists Maintenance manuals

Product Features, cont’d When a fault occurs, search for it in the repository. If there is a fault match, display its remedy. If there are no exact matches, then display the remedies of the closest matches. Compute and display the confidence level of each displayed remedy based on the closeness of match. Enter the latest fault and its solution into the repository. The repository “gains experience” and becomes more useful.

Major Modules A high-level diagram Data sources Server system Web Databases Sensors Files A high-level diagram Server system Web server Application objects Data integration server Virtual data views Users Faults archive server Faults matching engine Faults database Matching rules base

Fault Analysis Use Case Name: Fix Coolant Leak Goal: Provide remedies to a coolant leak. Summary: An astronaut must be provided remedies to a detected coolant leak in the space vehicle. Actors: The astronaut and the system sensors

Fault Analysis Use Case, cont’d Preconditions The astronaut is in the space vehicle. The space vehicle is in space. The system sensors are actively monitoring the vehicle. Primary trigger The vehicle sensors detect a drop in the warp engine coolant level.

Fault Analysis Use Case, cont’d Primary sequence The astronaut sees warnings of a coolant leak on the sensor monitor display. The astronaut sees possible diagnoses generated by real-time fault analysis. See use case “Match fault” See use case “Compute confidence level” The astronaut clicks on each diagnosis to display the associated remedy.

Fault Analysis Use Case, cont’d Primary postconditions The astronaut chooses the most likely diagnosis. The astronaut implements the corresponding remedy. Alternate sequences etc. Nonfunctional requirements The system sensors are constantly active. The system displays alerts in real time. Glossary astronaut = a person flying in the space vehicle. space vehicle = etc.

Use Case Demo http://www.cs.sjsu.edu/~mak/CMPE131/lectures/prototype/

Actual Screen Shot NASA lingo ISS International Space Station PUI Program Unique Identifier (i.e., part number) PRACA Problem Report and Corrective Action

Assignment #4: Conceptual Design Oral presentations next week. 5 - 6 teams Tuesday 5 - 6 teams Thursday We will draw lots at the start of class, so each team must be prepared to present. Do a product pitch for your web application. Each project team has up to 12 minutes. Grab the audience’s attention in the first minute. PowerPoint slides plus a live web demo. Demo the prototype of a key use case. Rails application (preferred) or PowerPoint slides. 16 teams in Section 3

Assignment #4: Conceptual Design, cont’d The rest of the class will represent potential future customers of your product. Allow a few minutes for Q&A and suggestions. The rest of the class will fill out survey forms to rate your presentation.

Assignment #4: Conceptual Design, cont’d Create a 1- or 2-page marketing brochure: The name of your product (the web application) Problem statement and objectives What is the purpose of this application? What will it do? A list of major features Submit your brochure (as a PDF, JPEG, or GIF) to at least one day before your presentation. Canvas: Assignment #4. Brochure I will post it on the class website.

Assignment #4: Conceptual Design, cont’d Written Conceptual Design At the conclusion of your project, you will add this to your Functional Specification. An overview of your solution A list of major features. A description of your application’s major modules and how they will interact with each other. High-level architecture diagrams. No implementation details.

Assignment #4: Conceptual Design, cont’d Screen shots of mocked-up web pages. Illustrate the sequence of web pages for a key use case. Taken from your live presentation. Due Friday, March 3. Submit to Canvas: Assignment #4. Conceptual Design

Design Meeting Video A video of a typical design meeting between software product developers and their clients. https://www.youtube.com/watch?v=BKorP55Aqvg