Presented by: Francis Ani & J.R. Armstrong

Slides:



Advertisements
Similar presentations
S Y S T E M S E N G I N E E R I N G.
Advertisements

Ch 3 System Development Environment
Write Your Project Title Here VU Logo Here Group Members Introduction Write your group members introduction here with names and VU Id.
CSCI2407 Software Systems Development Eric Tatham GH6.72
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
OO Process Steps  Define requirements Allocate and Derive requirements Map requirements to use cases Map requirements to classes  Define use cases Draw.
Conner Hansen Alex Summer Andreas Floeck Safe Message System.
Mr. Coffee Garage Door Opening System Jim Gregoire, Alex Johnson, Michael Miller, Will Shiver.
Introductions Michelle Johnson: CEO Myles Walsh: CFO James Goodrich: COO Ashley Kirby: CTO.
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Agricultural Silo Selection and Elevator System Kurt Goldstein Kayann Januchowski Keith Dugas Bill Epperson.
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
Team 4 Hau Chan Kit Cheng Nick Pearson
Term Project User Interface Specifications in a Usability Engineering Course: Challenges and Suggestions Laura Leventhal Julie Barnes Joe Chao Bowling.
Starting a project 1 Starting a Project Where do we now start? Where are we going? Will we know when we arrive?
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
HACS HOME IN YOUR POCKET. Today’s Topic User Interaction User Interaction User Authentication User Authentication Database Database Design of Devices.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 1.1.
RUP Requirements RUP Artifacts and Deliverables
Lesson 7 Guide for Software Design Description (SDD)
CPSC 871 John D. McGregor Module 4 Session 3 Architecture Evaluation.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Relating Testing to Quality –Timeliness of Testing –Quality Attributes Gauge by Testing –Roles Defining Test Discipline Activities Elaborating the Test.
Requirements Engineering ments_analysis.
Architectural Design Resolution Analyzed SRS Architectural Design Process Develop Architectural Design Alternatives Evaluate Architectural Alternatives.
SOFTWARE ARCHITECT – DESIGN.  Introduction  Architecture Drivers  POS System Architecture  Mapping Between Perspective  Evaluate Architecture  Project.
CSC 480 Software Engineering OOAD Process. Topics Overview: OOAD Process The object model Identifying classes Responsibilities and collaborations Hierarchy:
1 Final Status Report Sonali PagadeNibha Dhagat David Ziman Reginald Bradshaw II Sebastian Schagerer Janet Xu Phan Marvel Electronics & Home Entertainment.
© 2005 Prentice Hall10-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
User interface design and human computer interaction Xiangming Mu.
Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA.
CPSC 871 John D. McGregor Module 3 Session 1 Architecture.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
De la Rosa-Pohl ECE 1100 Introduction to Engineering Project 3: Symon! University of Houston Len Trombetta.
Human Computer Interaction
How I spend my money Software architecture course Mohan, Maxim.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Packets.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Information Systems Architecture (ISA) Conceptual blueprint for organization’s desired information systems structure Consists of:  Data (e.g. Enterprise.
Information Systems Architecture (ISA)
1 Introduction to Design. 2 Outline Basics of design Design approaches.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 14.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Requirements Engineering ments_analysis.
Lecture 1: Introduction – Graduation Projects Topics to Discuss in Lectures 1. Project Deliverables 2. Course grading 3. Project Concept Writing.
Object Oriented Analysis and Design Introduction to Rational Rose.
Different views of information system (IS) structural view (data, hardware, software/application, procedures) Object view Services view (user interface,
Monica Gloudemans Ekaterina Schwartz Gloudemans/Schwartz ACS 560 CMAP.
Product Design and Development Chapter 3
MIS Systems Analysis & Design Summary Updated 2013.
1 slc5 TTYP – C++ revisited 1 Which of the following statements are reasonable after the following statement: char* fred = new char[5]; a. fred = bill;
C_ITIP211 LECTURER: E.DONDO. Unit 1 : The Systems Development Environment.
Elaboration popo.
Lecture 9z Case Study ADD: Garage Door
Review for Final, Fall 2010 Close book, Close notes
Group Y Presenters: (indicate roles)
CGS 2545: Database Concepts Fall 2010
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Informatics 121 Software Design I
Chapter 9 Designing Databases
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Informatics 121 Software Design I
واسط كاربري هوشمند Intelligent User Interface
4+1 View Model of Software Architecture
Informatics 121 Software Design I
PPT and video are due no later than February 15, 2019
4+1 View Model of Software Architecture
Problem Statement. : Team Name. :. Team Leader Name. :
Informatics 121 Software Design I
Presentation transcript:

Presented by: Francis Ani & J.R. Armstrong Acme Garage Door Company’s Simulated Garage Door Opener System (SiGDOS) Presented by: Francis Ani & J.R. Armstrong

Background Acme Garage Door Company Founded in 2009 Evaluation before production of first product Two person software development team Francis Ani J.R. Armstrong Primary constraints Four week development timeframe Design must be highly modifiable

Product Design Project Mission Statement Use Case Diagram Use Case Descriptions User-Level Requirements Prototype

Use Case Diagram

Architectural Design Development Conceptual Model Functional Decomposition Modular Decomposition Combined Decomposition Class Diagram Utility Tree Profiles and Scenarios Architectural Scoring Matrix Architectural Design Rational

Combined Decomposition

Utility Tree

Architectural Design Rationale Layered approach Control devices placed in user interface layer System logic placed in simulation layer Data store layer maintains state between sessions Emphasis on modifiability Work light even/odd count scheme abandoned in favor of a conceptually simpler toggle

Detailed Design Development Class Diagrams Operation Specification Sequence Diagrams State Chart Mapping Between Models Detailed Design Rationale

User Interface Layer

Simulation Layer

Sequence Diagram for State Changes within the Simulation Layer

State Chart

Detailed Design Rationale Detailed design provided confirmation of architecture design Two priorities emphasized Core functionality Modifiability Detailed design fulfills the requirements set forth in the SRS