1 An Approach for Repeatable Sensor Web Construction WGISS – 25 Sanya, Hainan Island, China February 25, 2008.

Slides:



Advertisements
Similar presentations
Week 2 The Object-Oriented Approach to Requirements
Advertisements

The HR Paradigm Shift Discover Stakeholder Value for the Human Resources Function.
Deliverable #8: Detailed Design - Overview due: Wednesday, 7 March All Deliverable materials are to be posted into Team Concert. Your to.
Chapter 16: Analysis and Design (a short introduction) ● As engineers in other desciplines do, it necessary for real projects to “analyse” and “design”
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Rational Rose 2000 Interaction Diagrams.
18-1 Verifying Object Behavior and Collaboration Role playing – the act of simulating object behavior and collaboration by acting out an object’s behaviors.
Software Testing and Quality Assurance
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
Objectives Explain the purpose and objectives of object- oriented design Develop design class diagrams Develop interaction diagrams based on the principles.
Session 8. GEOSS requirements, functions, architecture Session Feedback Presenter: Max Craglia.
Object Oriented Analysis and Design Using the UML
Enterprise Architecture
Object-Oriented Analysis and Design
Chapter 3 Object-Oriented Analysis of Library Management System(LMS)
Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative Development Part III Elaboration Iteration I – Basic1.
Getting Smarter with Information An Information Agenda Approach
Developing Enterprise Architecture
The Design Discipline.
Systems Analysis and Design in a Changing World, Fifth Edition
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
UML - Development Process 1 Software Development Process Using UML (2)
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
12 Systems Analysis and Design in a Changing World, Fifth Edition.
Unified Modeling Language, Version 2.0
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Chapter 7 Applying UML and Patterns Craig Larman
Lecture 3 Uses Cases Topics UML Use Cases pop quiz Readings: Chapter 3 January 24, 2008 CSCE 492 Software Engineering.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
Software Engineering COSC 4460 Class 4 Cherry Owen.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Introducing Project Management Update December 2011.
Use Case Model Use case diagram. Relevant Requirements Artifacts Use-Case Model Supplementary Specification Use-Case Specifications... Glossary Actors.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
The principles of an object oriented software development process Week 04 1.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
Exam 2 Review Software Engineering CS 561. Outline Requirements Development UML Class Diagrams Design Patterns Users, Usability, and User Interfaces Software.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Refining the Use Cases 1. How Use Cases Evolve  Early efforts typically define most of the major use cases.  The refining stages complete the process.
Project Deliverables CIS 4328 – Senior Project 2 And CEN Engineering of Software 2.
Enterprise Architecture Reference Framework Generalities
Lecture 5 Introduction to Use Case Analysis and the Analysis Model Introduction to the UML.
July 2003 At A Glance The GMSEC provides efficient and enabling GSFC mission services and products for the next decade. Benefits Establishes a Single Strategic.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
Models of the OASIS SOA Reference Architecture Foundation Ken Laskey Chair, SOA Reference Model Technical Committee 20 March 2013.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Process 4 Hours.
UML: Unified modeling language
Object-Oriented Design
DESIGNING YOUR SYSTEM.
Software Design Lecture : 15.
Systems Engineering for Mission-Driven Modeling
Presentation transcript:

1 An Approach for Repeatable Sensor Web Construction WGISS – 25 Sanya, Hainan Island, China February 25, 2008

2 Drivers for Repeatable Construction Environment –Highly Collaborative –Multiple Projects and Nations –Varying Technologies Innovation –We are learning –Approaches are still developing –Developing Experience base for Best Practices Identify the Principles, Spread the knowledge –Others can see what worked – and what didnt –Increased efficiency in future efforts –Communicate to Executive Stakeholders Avoid Re-inventing the wheel –Increased efficiency –Identify composite services (and interfaces)

3 Approach Leverage Best Practices –Establish a Plan –Elaborate the Solution –Model the Solution –Produce Iteratively –Recognizing Patterns Communicate Openly –Artifacts are living and available –Regular Telecons Currently Leveraging this Approach –Flood Sensor Web –Wildfire Web

4 1) Establish a Plan Capture the Big Picture –Introduce the Project –Establish a Vision Statement Why do this project? Key Stakeholders Key Benefit Areas –Establish Framework of the Plan Anticipated Duration Key Phases –What capabilities will be present in each phase

5 2) Elaborate the Solution Sensor Application Case –Based on Use Case Modeling –Ensure that all parties agree on what is to be done –Using the language of the domain Includes –Summary –Actors –Preconditions –Resources Contributed –Triggers –Basic Flow –Alternate Flows –Post Conditions

6 Resources Contributed Data Modeling Services

7 Resources Contributed (Cond) Event Services Application/DSS Resources

8 Sensor Web Flow Describing Relationships –Applied GEOSS Architecture Components Observations, Information, Models, Forecasts, etc. Example

9 3) Model the solution Use Interaction Diagrams Shows how the pieces will work together Example Identify Components Identify Services Identify Standards Identify Patterns Identify Composite Services

10 Questions?