CS 545 Software Systems Design Project Presentation Format Lecture Created by Dan Benson Computer Science Lectures © D. Benson, 2002.

Slides:



Advertisements
Similar presentations
10 Golden Questions for Concept Exploration & Development Dr. Dan C. Surber (317)
Advertisements

1 9 Moving to Design Lecture Analysis Objectives to Design Objectives Figure 9-2.
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
Univ. of XXXXXXXXX 1 Things To Include: Team Photo Team Logo/Name.
TSS Architecture Definition Context. TSS Scoping Study Context Detailed Requirements Specification (products, functionality) High Level Architecture Description.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
[BA3750 PRODUCT or SERVICE] Your Logo Here Insert Product Photograph Here.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
Payload Subsystem Integration and Testing Report Team Name 1 Team Name 2 Team Name N Universities/Institutions Team Members Date.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
Object-Oriented Analysis and Design
LECTURE 5 SEQUENCE DIAGRAM 1. INTRODUCTION – SYSTEM SEQUENCE DIAGRAM A system sequence diagram is a fast and easily created artifact that illustrates.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Chapter 7: The Object-Oriented Approach to Requirements
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
Homework Assignment 3 Due date: Tuesday, Wednesday, or Thursday, October 4-6, 2005 input: push-button switch output: seven-segment LED 7 points Menu System.
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
UML Diagrams: Class Diagrams The Static Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Requirements Documentation CSCI 5801: Software Engineering.
SimArch: Work in Progress Multimedia Teaching Tool Faculty of Electronic Engineering University of Nis Serbia.
Lecture 7: Requirements Engineering
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Database Management System Prepared by Dr. Ahmed El-Ragal Reviewed & Presented By Mr. Mahmoud Rafeek Alfarra College Of Science & Technology- Khan younis.
The Static Analysis Model Class Diagrams Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty of Computers and Information, Cairo University.
Data flow & information requirements.  Establishing IPSO  Recording information about the existing system  Identifying the problems with the system.
CS251 – Software Engineering Lecture 9: Software Design Slides by Mohammad El-Ramly, PhD
44095: IT for Management Systems Concepts 2 By:Ian Perry Room: C48 Tel:
ECE477 Midterm Design Review: Team #
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Solar Probe Plus A NASA Mission to Touch the Sun March 2015 Instrument Suite Name Presenter's Name.
Computer Science 340 Software Design & Testing Software Architecture.
Architectural Design Introduction Design has been described as a multistep process in which representations of data and program structure,
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Chapter 6: System Models Omar Meqdadi SE 273 Lecture 6 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Status Update Instructions (Required by NASA/Wallops) These completed slides are due to no later than Wednesday, March 6 th, 2013,
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Software Engineering Lecture 10: System Engineering.
Describing MCM Mission Package Software Interoperability with Architectural Descriptions.
Midterm/Final Presentation Project Name Students: [Name1], [Name2] Supervisor: [SV Name] Context: Project [A/B/Special] Semester: Winter/Spring, Year Date:
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Architectural Complexity  A useful technique for assessing the overall complexity of a proposed architecture is to consider dependencies between components.
Accounting systems design & evaluation 9434SB 18 March 2002.
Guidelines for a Technical Presentation or Poster by Dr. Robert A. Pilgrim Class ID Date Title Author(S) Event/Venue Date.
Technical Presentation or Poster
Systems Analysis and Design in a Changing World, Fourth Edition
UML Diagrams: Class Diagrams The Static Analysis Model
Instructor: Dr. Hany H. Ammar
Business System Development
Object Oriented Approach
IT 440: SYSTEM INTEGRATION
Insert Product Photograph Here
CH#3 Software Designing (Object Oriented Design)
Product Name.
Sequence Diagrams Lecture 6.
Component-Level Design
Computer Architecture and Assembly Language CS 233 Lecture 1
SWEN 5230 Your Project Title
Technical Communication Skills Practicum Software Design Narrative
CS 8532: Advanced Software Engineering
CSE 498, Collaborative Design
Product Name.
Product Name.
Computer Architecture and Assembly Language CS 233 Lecture 1
FED ...cont. Your Logo Here Mr. Eastwood PHS.
Requirements “Content Guide”
Presentation transcript:

CS 545 Software Systems Design Project Presentation Format Lecture Created by Dan Benson Computer Science Lectures © D. Benson, 2002

{date of presentation} {system or program name} Architecture Review {Name} Optional: Developer picture or logo

CS 545 Semester Project 3 {system} Mission Customer Mission/purpose Functional overview LUNAS-EZ Subsystem OCS CSCI Overview 2 March 2000

CS 545 Semester Project 4 Major Technical and Performance Requirements List Major Technical Requirements List Major Performance Requirements List System Constraints

CS 545 Semester Project 5 External Interface [or Context Diagram] {component} {name} System {name} {Data} LUNAS-EZ Subsystem OCS CSCI Overview 2 March 2000 {Data} {name} (Notational Example) Internal Components {Data}

CS 545 Semester Project 6 {system name} System Diagram LUNAS-EZ Subsystem REC 2 March 2000 Block diagram of the entire system. This is an overview chart showing major processing functions with appropriate entry points for external interfaces. Do not have to repeat the detailed input information of the external input/output chart when showing interfaces.

CS 545 Semester Project 7 [name] System Architecture Processing –Describe the processing with the use of word charts and architecture diagrams for each functional component or object in the system diagram –Additional charts may be used if necessary LUNAS-EZ Subsystem REC 2 March 2000

CS 545 Semester Project 8 Quality Scenarios List the quality scenarios you have included in your system design Describe how your design meets the quality requirements you have identified