University of Southern California Center for Software Engineering CSE USC 477 Class Project – HazMat (Hazardous materials) Spring 2003 Feb. 4.

Slides:

Advertisements

Similar presentations

MBASE Integration Framework

Advertisements

1 Lecture #8 Purpose of SSRD Describe Capability Requirements: system subject matter measured by concrete means Describe Project, Level of Service, and.

MBASE Process: WinWin Spiral

University of Southern California Center for Software Engineering CSE USC 1 Digital Library Projects’ MBASE Experience Dan Port USC-CSE Annual Research.

Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.

Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz

Documenting a Software Architecture By Eng. Mohanned M. Dawoud.

Outline About author. The problem that discussed in the article.

University of Southern California Center for Systems and Software Engineering Design-Code Review Preparation Pongtip Aroonvatanaporn CSCI577b Spring 2012.

University of Southern California Center for Systems and Software Engineering Core Capability Drive-Through (CCD) Feedback Pongtip Aroonvatanaporn CSCI.

Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)

Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,

Mastering Object-Oriented Analysis and Design with UML Module 4: Analysis and Design Overview.

University of Southern California Center for Software Engineering CSE USC MBASE Essentials Planning and control Milestone content Process models Life cycle.

University of Southern California Center for Systems and Software Engineering USC CSSE Research Overview Barry Boehm Sue Koolmanojwong Jo Ann Lane Nupul.

University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.

University of Southern California Center for Software Engineering CSE USC ©USC-CSE 10/23/01 1 COSYSMO Portion The COCOMO II Suite of Software Cost Estimation.

USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Software Architecting On the Acquisition Side.

2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.

Systems Analysis and Design in a Changing World, Tuesday, Jan 30.

University of Southern California Center for Software Engineering CSE USC Distributed Assessment of Risk Tool DART Jesal Bhuta

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 1.

The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.

University of Southern California Center for Software Engineering C S E USC Agile and Plan-Driven Methods Barry Boehm, USC USC-CSE Affiliates’ Workshop.

Object Oriented Analysis and Design Using the UML

University of Southern California Center for Software Engineering CSE USC Sep. 24, 2009 v01 ©USC-CSE CS 577a Software Engineering I Peer Review.

Merlin ITEA Symposium Merlin Overview2 Problem domain Companies hardly develop embedded products completely on their own Embedded systems need.

University of Southern California Center for Software Engineering C S E USC August 2001©USC-CSE1 CeBASE Experience Base (eBASE) -Shared Vision Barry Boehm,

CC20O7N - Software Engineering 1 CC2007N Software Engineering 1 Requirements Engineering Practices with Techniques.

Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.

Requirements Analysis

Operational Concept Description

University of Southern California Center for Systems and Software Engineering 10/30/2009 © 2009 USC CSSE1 July 2008©USC-CSSE1 The Incremental Commitment.

University of Southern California Center for Systems and Software Engineering The Incremental Commitment Spiral Model Electronic Process Guide (EPG) and.

University of Southern California Center for Systems and Software Engineering Retrospective Analysis Supannika Koolmanojwong October 21,

University of Southern California Center for Systems and Software Engineering 1 CS577a Software Engineering I DCR ARB and Package Workshop Supannika Koolmanojwong.

University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE11 USC e-Services Software Engineering Projects.

University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.

Lecture 7: Requirements Engineering

University of Southern California Center for Systems and Software Engineering Introduction to: System and Software Construction, Transition and Support.

Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.

University of Southern California Center for Systems and Software Engineering 09/08/2010© USC-CSSE1 System and Software Requirements Definition.

Inception Chapter 4 Applying UML and Patterns -Craig Larman.

System Context and Domain Analysis Abbas Rasoolzadegan.

CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.

University of Southern California Center for Systems and Software Engineering 10/25/2010(C) USC CSSE1 CS 577a Overall FCR Feedback [Updated/More]

University of Southern California Center for Software Engineering CSE USC A Case for Anchor Point Milestones and Feasibility Rationales April 2005 Barry.

J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.

University of Southern California Center for Systems and Software Engineering 577 process CSCI 577a Software Engineering I Supannika Koolmanojwong Mobasser.

University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE CSCI577B 2010 Light Weight Sw Engg for Off-the-Books.

Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.

Pair Development Framework Monvorath (Molly) Phongpaibul.

Soft. Eng. I, Spring 2007Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 3 Title: The Feasibility study Mandatory reading: I. Sommerville, Section.

University of Southern California Center for Software Engineering CSE USC SCRover Increment 3 and JPL’s DDP Tool USC-CSE Annual Research Review March 16,

University of Southern California Center for Systems and Software Engineering Aug. 26, 2010 © USC-CSE Page 1 A Winsor Brown CS 577a Lecture Fall.

1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.

Rational Unified Process Fundamentals Module 5: Implementing Rational Unified Process Rational Unified Process Fundamentals Module 5: Implementing Rational.

AHS+Associates Principles of Architecture & Construction Grades: 9-12 Credit: 1 Elective Description: Provides an overview to the various fields of architecture,

University of Southern California Center for Systems and Software Engineering RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong.

University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Fall 2010 Software Planning Guidelines.

1 Essential Software Architecture Documenting a Software Architecture.

USC e-Services Software Engineering Projects

Client Introductions to CS577a

CS577a Software Engineering I DCR ARB and Package Workshop

ICM_Sw Essentials for CS510

ICM-Sw Essentials for 577 Process models Success models Product models

CS 577b Software Engineering II -- Introduction

CS577a Software Engineering ARB #2 Workshop

Incremental Commitment Model (ICM)* for Software

Overview of BSSE at Rose-Hulman Institute of Technology

Presentation transcript:

University of Southern California Center for Software Engineering CSE USC 477 Class Project – HazMat (Hazardous materials) Spring 2003 Feb. 4

University of Southern California Center for Software Engineering CSE USC Feb. 04/032 ©USC-CSE Topics MBASE model (help students understand the purpose of docs provided.) HazMat overview (introducing the project context) HazMat OCD HazMat SSRD Grading Criteria Questions

University of Southern California Center for Software Engineering CSE USC Feb. 04/033 ©USC-CSE Ingredients of a project project mgmt Product Const. Delivery & Maint. concept commitment schematic/blueprint plan project mgmt

University of Southern California Center for Software Engineering CSE USC Feb. 04/034 ©USC-CSE MBASE Artifacts OCD (Operational Concept Description) SSRD (System and Software Requirements Description) SSAD (System and Software Architecture Description) LCP (Life Cycle Plan) FRD (Feasibility Rational Description)

University of Southern California Center for Software Engineering CSE USC Feb. 04/035 ©USC-CSE Purpose of OCD Describe context of system. What do we have now? why build a new system? Describe stakeholders of the system: how the system will work when deployed. Describe evolution from current to new operational concept. Clarify the value of new system.

University of Southern California Center for Software Engineering CSE USC Feb. 04/036 ©USC-CSE Purpose of SSRD Describe Capability Requirements Describe Project, Level of Service, and Evolutionary (non-functional) Requirements: Describe Global Constraints Mandates (“must”, “shall”, “will”) / prioritizing.

University of Southern California Center for Software Engineering CSE USC Feb. 04/037 ©USC-CSE HazMat Project Objective –To explore a set of requirements, design, and code to the HDCP testbed by developing a scout (rover) prototype. –To gain tacit knowledge about the application of the MBASE guidelines to robotic development.

University of Southern California Center for Software Engineering CSE USC Feb. 04/038 ©USC-CSE The problem

University of Southern California Center for Software Engineering CSE USC Feb. 04/039 ©USC-CSE How about…

University of Southern California Center for Software Engineering CSE USC Feb. 04/0310 ©USC-CSE Key Stakeholders

University of Southern California Center for Software Engineering CSE USC Feb. 04/0311 ©USC-CSE Scout (Rover) Movement Go ahead Change moving direction Battery:78% Wireless:connected Behavior:follow path Messages:

University of Southern California Center for Software Engineering CSE USC Feb. 04/0312 ©USC-CSE Camera Control Document the interested objects. Capture

University of Southern California Center for Software Engineering CSE USC Feb. 04/0313 ©USC-CSE Environment Map Display

University of Southern California Center for Software Engineering CSE USC Feb. 04/0314 ©USC-CSE A more complex scenario

University of Southern California Center for Software Engineering CSE USC Feb. 04/0315 ©USC-CSE Project Requirement

University of Southern California Center for Software Engineering CSE USC Feb. 04/0316 ©USC-CSE Thank you!