1 ECCF Training 2.0 Guidance for the Platform Independent Model (PIM) ECCF Training Working Group January 2011.

Slides:



Advertisements
Similar presentations
1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
Advertisements

Requirements Elicitation and Use Case Diagrams
Chapters 7 & 9 System Scope
Use Case Model. C-S 5462 Use case model describes what the user expects the system to do –functional requirements may describe only the functionalities.
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Chapter 14 Requirements and Specifications. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Software Engineering The implementation.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
1 SWE Introduction to Software Engineering Lecture 15 – System Modeling Using UML.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
UML exam advice. Minimal, yet sufficient UML course 80% of modeling can be done with 20% of the UML. Which 20% was that again? We’re supposed to be “Use.
Roles and Responsibilities Jahangheer Shaik. Service Specification Specification requires development of three inter-related documents CIM, PIM and PSM.
The Software Development Life Cycle: An Overview
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
Project Analysis Course ( ) Week 2 Activities.
1 ECCF Training 2.0 Platform Specific Model (PSM) ECCF Training Working Group January 2011.
CMSC 345 Fall 2000 Unit Testing. The testing process.
1 Objectives  Describe design constraints.  Identify methods of specifying functional requirements.  Describe techniques for writing and structuring.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
UML Diagrams: Class Diagrams The Static Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Testing Workflow In the Unified Process and Agile/Scrum processes.
Dynamic Modeling Chapter 11 Part of Analysis Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
1 ECCF Training 2.0 Guidance for the Logical Perspective Specification ECCF Training Working Group January 2011.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Approaching a Problem Where do we start? How do we proceed?
1 caBIO ECCF Pilot Konrad Rokicki ICR Workspace Call July 28, 2010.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
1 Introduction to Software Engineering Lecture 1.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group March 2011.
The Static Analysis Model Class Diagrams Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty of Computers and Information, Cairo University.
Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
1 SAIF-Effects on Data Service Specifications Baris Suzek Georgetown University Architecture/VCDE Joint Face-to-Face June,3, 2010 St. Louis, Missouri.
Introduction To OOP 1.0 Fundamentals Of Java Programming Language 2.0 Exception Handling 3.0 Classes, Inheritance And Polymorphism © 2011 | PN AZRINA.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
1 ECCF Training 2.0 Implemental Perspective (IP) ECCF Training Working Group January 2011.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
System sequence diagrams
1 ECCF Training 2.0 Guidance for the Logical Perspective Specification ECCF Training Working Group January 2011.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Introduction to UML Todd Bacastow Rational Unified Process A process for the effective implementation of key “Best Practices” Control Changes Manage.
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group January 2011.
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group March 2011.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 17 Object-Oriented Design and Modeling Using the UML.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
CompSci 280 S Introduction to Software Development
An Overview of Requirements Engineering Tools and Methodologies*
UML Diagrams: Class Diagrams The Static Analysis Model
Recall The Team Skills Analyzing the Problem (with 5 steps)
System sequence diagrams
Use Case Model.
Unified Modeling Language
Introduction to Unified Modeling Language (UML)
Unified Modeling Language
Analysis models and design models
Software Design Lecture : 15.
Software Development Process Using UML Recap
UML Design for an Automated Registration System
Presentation transcript:

1 ECCF Training 2.0 Guidance for the Platform Independent Model (PIM) ECCF Training Working Group January 2011

2 Outline What is the PIM? Looking through the viewpoints Detailed look at artifacts by viewpoint Explanation Example Exercise Other Artifacts

What is the PIM? From analysis in CIM to logical model in PIM Independent of technology stack Typically one PIM for one CIM 3

Looking through the viewpoints Enterprise Viewpoint Minimal focus for the PIM (optional artifacts) Mostly traceability to CIM Information Viewpoint Constrained Local Information Model Computational / Behavioral Service Contract Engineering / Implementation Deployment Considerations 4

Artifacts by Viewpoint Information Viewpoint 5

Information Model Add constraints and localizations to information model work begun in the CIM Artifacts: Primary Information Object Types State Model Error Information Model Control Data Types Value Set Definitions 6

Primary Information Object Types What are the Primary Information Objects? Represent the main functionality Other objects are associated with primary objects Generally form the input and output State is controlled by functionality of the service There can be more than one primary object type How do we define them? Object Model State Transition Model Traceability to referenced models 7

MA Gene Object Model 8

MA Gene State Model 9

MA Gene Model Reference UML 10

MA Gene Model Traceability TraceAttribute NameTypeDescription LSPIMSymbolSTThe official symbol for the gene based on an organism-specific database of gene symbols, such as HUGO, MGI or RGD NewfullNameSTThe title of the gene. 11 Gene

Error Information Model Defines the types for all the errors that the service may throw 12

MA Exception Model 13

Control Data Type Definitions What are control data types? Search Criteria Exception Conditions Input Criteria Result Sets 14

MA – Search Criteria Types 15

Value Set Definitions Attributes whose values are controlled by a list of valid values Error Codes Status Codes 16

MA – Error Codes Error CodeError ConditionDescription MAE00000FatalRemote system error MAE10001ErrorGene does not exist MAE10002ErrorSpecified microarray is not supported MAE10003ErrorReporter not found 17

Artifacts by Viewpoint Computational / Behavioral Viewpoint 18

Interface Model Provides a logical grouping for service implementers Artifacts: UML model of interfaces List of operations Detailed operation behavior descriptions 19

MA – Interface Model Interface NoInterface NameInterface Description MA-INF1MAGeneAnnotationQueryIncludes all of the operations for retrieving gene annotations MA-INF2MAFreestyleSearchIncludes all of the operations for Freestyle Search 20

MA – Interface Model UML 21

MA – List of Operations (Truncated) Operation No. Operation NameInterface NameOperation Description MA-INF1-OP1getGenesBySymbolMAGeneAnnotationQueryReturns the genes named by the specified gene symbols and/or gene aliases MA-INF1-OP2getCellularLocationsMAGeneAnnotationQueryReturns annotations describing a gene’s location within a cell MA-INF2-OP1freestyleSummarySearchMAFreestyleSearchProfileReturns a summary result for a given keyword or keywords MA-INF2-OP2freestyleSearchMAFreestyleSearchProfileReturns a list of results matching the given keyword or keywords 22

Operation Behavior Description Detailed description of the behavior of each interface operation Grouped by interface Includes: Description Pre-Conditions Security Conditions Inputs Outputs Post-Conditions Exception Conditions Additional Implementation Details Notes 23

MA - getGenesByMicroArrayReporter Behavior DescriptionClient supplies a ReporterSearchCriteria instance with a reporter name and a microarray design to search within The case of the reporter name is ignored If the Microarray is null then all Microarrays are searched The system returns the matching Gene object(s), if any Pre-ConditionsNone Security Pre- Conditions None InputsReporterSearchCriteria OutputsFully-populated instance(s) of Gene 24

MA - getGenesByMicroArrayReporter (cont.) Post-ConditionsNone Alternate ConditionsNo matching genes found Exception ConditionsSpecified microarray is not supported Reporter not found Additional DetailsNone NotesNone 25

Dynamic Model Describe the interactions of the service with sequence diagrams or collaboration diagrams Includes relationships with other services 26

MA – External Service Relationships Service / System / Actor’s Name RelationshipDataDescription Integrative Translational Research System DependsMolecular Annotations Integrative Translational Research Systems such as caIntegrator depend on Molecular Annotations for looking up annotations for microarray reporters used in experiments being analyzed. Gene Expression Analysis Tool DependsMolecular Annotations Gene Expression Analysis Tools such as GEWorkbench depend on a Molecular Annotations for putting expression data in context of a genome. 27