1. 1 ECCF Training 2.0 Guidance for the Logical Perspective Specification ECCF Training Working Group January 2011

2. 2 Outline Introduction What is the Logical Perspective Specification (LPS) ? Fundamental Artifacts These are basic artifacts that are required at each specification level Examine each specification artifact by RM-ODP (Reference Model of Open Distributed Processing) viewpoint Define the artifacts Link them to the template Provide examples Engage in constructive exercises

3. What is the Logical Perspective Specification? Platform Independent Addresses the business functionality and behavior of a service, independent of the technology that implements it. Moves from the analysis model in the CPS (Conceptual Perspective Specification) to a logical model in the LPS Refines and constrains the functional and behavioral information presented in the CPS Defines in a more structured way the inputs, outputs, pre-conditions, post- conditions, and error messages for each operation Contains a technology-independent specification of the service contract Typically one LPS for one CPS 3

4. Fundamental Artifacts Business service name Service description and purpose Describe the service in general terms and discuss its intended use. Scope Describe the overall scope of the service. Define all functionality that this particular service provides. Referenced standards Provide details and references to the standards that are used in this service. An example would be a service where the domain model is derived from the BRIDG (Bioinformatics Research Integrated Domain Group) model. 4

5. Enterprise Viewpoint Artifacts The primary artifacts generated from the Enterprise Viewpoint in the Logical Perspective Specification include: Refined CPS Enterprise Viewpoint Artifacts: There may or may not be refinements that are made from the CPS to the LPS level. Refined Conformance Statements: Includes a list of all the Conformance profiles from the CPS that this LPS is conformant to. Includes the specific version of the CPS used. Note: Refinements are used to clarify or correct artifacts and conformance statements from the CPS for use in the LPS. An Image showing a slice of the ECCF organizational matrix Along the left from top to bottom are the specifications Conceptual, Logical, and Physical There is only one column with the heading “Enterprise Viewpoint” In the boxes are summaries of the artifacts for each specification at the Enterprise viewpoint level. The Logical specification row is highlighted by a red box around it, and it contains the following list: Use case specification Wireframes Business rules Industry technology-neutral standards 5

6. Enterprise Viewpoint Artifacts: Relationship to the CPS Provides details on how this specification relates to the Conceptual Perspective Specification Includes the version number and a link to the CPS Example from Molecular Annotation Service: Conceptual Functional Service Specification Name: Molecular annotation Conceptual Functional Service Specification Version: 0.1.1 Link: http://ncisvn.nci.nih.gov/svn/cabiodb/ECCF/artifacts/conceptual/CIMSS_Molecula r_Annotation_Service.doc 6 Conceptual Functional Service Specification Name Conceptual Functional Service Specification Version Description & Link to the Conceptual Functional Service Specification Molecular Annotation Conceptual Functional Service Specification 0.1.1http://ncisvn.nci.nih.gov/svn/cabiodb/ECCF/artifacts/con ceptual/CIMSS_Molecular_Annotation_Service.doc

7. Enterprise Viewpoint Artifacts: Conformance Profile Statements which group functional and semantic profiles around a usage context. One or more Functional Profiles – Collection of functionality which this compliance profile will exhibit Exactly one Semantic Profile – The semantics of the input and output parameters which should be used for the functionality mentioned above. The LPS lists all of the Conformance Profiles from the CPS that it is conformant to. The LPS must be conformant to all of the mandatory conformance profiles from the CPS The LPS can add onto the functionality, but cannot remove or modify any functionality from the CPS conformance profile. 7

8. Molecular Annotation Service: Conformance Profile Name LSDAM-based Gene Annotation Conformance Profile Description Defines the functionality for the Gene Annotation Service using LSDAM semantics Usage This profile would be used by a researcher wishing to access gene annotations 8

9. Molecular Annotation Service: Conformance Profile Profile Number – MA-CP1 Conformance Profile Name: LSDAM-based Gene Annotation Conformance Profile Functional Profiles: Number – MA-FP1 Name – Gene Annotation Query Profile Number – MA-FP2 Name – Freestyle Search Profile Semantic Profiles: Number – MA-SP1 Name – LSDAM v1.1 9

10. Information Viewpoint Artifacts The primary artifacts generated from the Information Viewpoint in the LPS include: Serializable Information Model: Add constraints and localizations to domain analysis work begun in the CPS Primary Information Objects Control Data Types Value Set Definitions An Image showing a slice of the ECCF organizational matrix Along the left from top to bottom are the specifications Conceptual, Logical, and Physical There is only one column with the heading “Information Viewpoint” In the boxes are summaries of the artifacts for each specification at the Information viewpoint level. The Logical specification row is highlighted by a red box around it, and it contains the following text: Domain Information model Constrained Information model Locallized Information model 10

11. Information Viewpoint Artifacts: Primary Information Object Types Criteria: Primary objects represent the main functionality of the service Primary objects are the central objects in the information model to which all other objects are associated. Primary objects generally form the input and output objects for the majority of the service functionality Primary objects generally experience state changes as service functionality is executed. There can be one or several Primary Information Objects for a service Specification: Object Model (UML, RMIM) Relationship to referenced models 11

12. Molecular Annotation Service: Primary Information Object The Gene class meets the criteria outlined: The service is designed to allow retrieval Genes and various annotations related to a Gene. The Gene object is the central object. It has associations such as MolecularFunction, CellularComponent, BiologicalProcess, and GeneSearchCriteria Genes (or Gene Identifiers) serve as either the input or the output of nearly every service operation. 12

13. Molecular Annotation Service: Gene Model This is a UML model from the Molecular Annotation Service Logical Perspective Specification. It shows the Gene class, its closest associations and their attributes. 13

14. Molecular Annotation Service: Gene Model Relationship to LSDAM The Molecular Annotation Service LPS includes a diagram and a table relating the Gene model back to classes in the LSDAM Mapping is one-to-one except for additional attributes on Gene and NucleicAcidSequenceFeature 14

15. Molecular Annotation Service: Gene Model Relationship to LSDAM UML diagram relating the Molecular Annotation classes to the LSDAM It is essentially a one-to-one mapping 15

16. Molecular Annotation Service: Gene Model Relationship to LSDAM TraceAttribute NameTypeDescription LSDAMSymbolSTThe 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. Gene Class Attribute Name – Symbol Trace – LSDAM Description – The official symbol for the gene based on an organism-specific database of gene symbols, such as HUGO, MGI or RGD Attribute Name – fullName Trace – New Description – The title of the gene. 16 Gene

17. Information Viewpoint Artifacts: Control Data Type Definitions Control data types are classes used by the service for input and output that are created specifically to perform certain service actions. Examples of common control data types: Exception Types Search Criteria Input Criteria Result Sets Specification of control data types should include: UML diagrams of the types and hierarchies Data type descriptions 17

18. Molecular Annotation Service: MAException UML diagram: Class – MAException Attributes: code: ST message: ST severity: ST type: ST 18

19. Molecular Annotation Service: MAException Data TypeStatus / Return Value / Exception Data Type Description MAExceptionExceptionException thrown when there is an error in the operation of MA Service methods. Date type description: MAException Control Data type – Exception Description - Exception thrown when there is an error in the operation of MA Service methods. 19

20. Molecular Annotation Service: Search Criteria UML Diagram: This diagram represents a hierarchy of the following classes: SearchCriteria Sub-Class: GeneListSearchCriteria Association: Organism Sub-Class: GeneSearchCriteria Association: Organism ReporterSearchCriteria Association: Microarray 20

21. Molecular Annotation Service: Search Criteria Data Type Descriptions: GeneSearchCriteria Control Data Type - Query Search Criteria Description - Search criteria object for finding genes of interest given a single symbol or alias. GeneListSearchCriteria Control Data Type - Query Search Criteria Description - Search criteria object for finding genes of interest given a list of symbols or aliases. ReporterSearchCriteria Control Data Type - Query Search Criteria Description - Search criteria object for finding genes of interest given a reporter name. 21 Data TypeQuery Search Criteria / Search Result Limiter / Result Set Data Type Description GeneSearchCriteriaQuery Search CriteriaSearch criteria object for finding genes of interest given a single symbol or alias. GeneListSearchCriteriaQuery Search CriteriaSearch criteria object for finding genes of interest given a list of symbols or aliases. ReporterSearchCriteriaQuery Search CriteriaSearch criteria object for finding genes of interest given a reporter name.

22. Information Viewpoint Artifacts: Value Set Definitions Attributes whose values are controlled by a list of valid values Error Codes Status Codes These can be values for attributes on project specific data types, or additional constraints placed on referenced data types. 22

23. Molecular Annotation Service: Error Codes Error CodeError ConditionDescription MAE00000FatalRemote system error MAE10001ErrorGene does not exist MAE10002ErrorSpecified microarray is not supported MAE10003ErrorReporter not found MAE00000 Condition - Fatal Description - Remote system error MAE10001 Condition - Error Description - Gene does not exist MAE10002 Condition - Error Description - Specified microarray is not supported MAE10003 Condition - Error Description - Reporter not found 23

24. Information Viewpoint Exercise: Primary Information Objects Given the following capabilities from the Subject Registration service, identify at least one primary information object. Capability - Initiate Subject Enrollment Description - This capability is used to initiate subject registration on a study. Capability - Reserve Slot Description - This capability is used to reserve a slot for the subject on a trial. Capability - Pre-Register Subject Description - This capability is used to pre-register subject on a trial. Some trials mandate a screening of a subject before they can be accrued to the study. Capability - Enroll Subject Description - This capability is used to enroll subject on trial. At this point the subject can be deemed enrolled on the trial and they would be counted towards the accrual. 24 CapabilityDescription Initiate Subject Enrollment This capability is used to initiate subject registration on a study. Reserve Slot This capability is used to reserve a slot for the subject on a trial. Pre-Register Subject This capability is used to pre-register subject on a trial. Some trials mandate a screening of a subject before they can be accrued to the study. Enroll Subject This capability is used to enroll subject on trial. At this point the subject can be deemed enrolled on the trial and they would be counted towards the accrual.

25. Information Viewpoint Exercise: Model Constraints Scenario: As an architect of the Service Registration service you are designing the serializable information model. The following information needs to be captured for subjects of a study: Biographical information: name, date of birth, gender, primary race, primary ethnicity, telephone number, and address Study Registration information: subject status and status change date & time Your Conceptual Perspective Specification used the following StudySubject object from the BRIDG domain analysis model. Constrain the object to meet the requirements outlined above. 25

26. Information Viewpoint Exercise: Model Constraints (cont.) StudySubject ConfidentialityIndicator: BL paymentMethodCode: CD statusCode: CD statusDate: TS.DATETIME ::Person deathIndicator: BL educationLevelCode: CD ethnicGroupCode: DSET initials: ST maritalStatusCode: CD name: DSET occupationDateRange: IVL postalAddress: AD primaryOccupationCode: CD raceCode: DSET telecomAddress: BAG ::BiologicalEntity actualIndicator: BL administrativeGenderCode: CD birthCountryCode: CD birthDate: TS.DATETIME birthOrder: INT.POS deathDate: TS.DATETIME 26

27. Information Viewpoint Exercise: Model Constraints (cont.) StudySubject statusCode: CD statusDate: TS.DATETIME ::Person ethnicGroupCode: DSET (constrained to exactly one element in the set) name: DSET postalAddress: AD raceCode: DSET (constrained to exactly one element in the set) telecomAddress: BAG ::BiologicalEntity administrativeGenderCode: CD birthDate: TS.DATE 27 CD TS.DATE

28. Information Viewpoint Exercise: Control Data Types Given the following capabilities from the Subject Registration service, identify any control data types that may be necessary: Capability - Query Subject Registration Description - This capability is used to query and retrieve subject registration data including demography data. This also provides the capability to query epoch specific data, for e.g. it can be used to provide data on how many people were screened and how many failed screening for each possible reason. Capability - Import Registrations Description - This capability is used to import legacy registrations. Capability - Generate Summary3 Report Description - This capability is used to generate Summary 3 report. 28 CapabilityDescription Query Subject Registration This capability is used to query and retrieve subject registration data including demography data. This also provides the capability to query epoch specific data, for e.g. it can be used to provide data on how many people were screened and how many failed screening for each possible reason. Import RegistrationsThis capability is used to import legacy registrations. Generate Summary3 Report This capability is used to generate Summary 3 report.

29. Information Viewpoint Exercise: Control Data Types (cont.) Capability - Query Subject Registration Possible Control Data Types: Input - Search criteria type Output - Exception type Output -Result set type Capability - Import Registrations Possible Control Data Types: Input - Specific import format type Output – Exception type Capability - Generate Summary3 Report Possible Control Data Types: Input – Report parameter type Output – Report format type Output – Exception type 29 CapabilityPossible Control Data Types Query Subject Registration Input - Search criteria type Output - Exception type Output -Result set type Import Registrations Input - Specific import format type Output – Exception type Generate Summary3 Report Input – Report parameter type Output – Report format type Output – Exception type

30. Behavioral Viewpoint PIM Artifacts The primary artifacts generated from the Behavioral Viewpoint at the PIM specification include: State Model: State should be expressed for important objects relevant to the service specification. Service Contract: Platform Independent service interfaces. Provides a logical grouping of service capabilities. Interface model List of operations for each interface Detailed operation behavior descriptions Dynamic Model: Model of complex internal and external relationships and interactions. An Image showing a slice of the ECCF organizational matrix Along the left from top to bottom are the specifications Conceptual, Logical, and Physical There is only one column with the heading “Behavioral Viewpoint” In the boxes are summaries of the artifacts for each specification at the Behavioral viewpoint level. The Logical specification row is highlighted by a red box around it, and it contains the following text: Service Interface PIM Collaboration Specification 30

31. Behavioral Viewpoint Artifacts: State Model Include the UML model describing the state transitions of the primary information object(s) of the service. Provide details on the state transitions and discuss any significant implementation considerations based on entity states. Molecular Annotation Service Example: Current service is essentially an open, read-only service. Queries are executed against the service to retrieve results. As such, the only state that a Gene can be in is “Active”. 31

32. Behavioral Viewpoint Artifacts: Interface Model Related service operations may be grouped into interfaces to a provide a logical grouping for service implementers. This grouping may be different than the functional profiles. Specification: Interface Model UML Interface description table Molecular Annotation Service: Interface Description Table Interface Number - MA-INF1 Interface Name - MAGeneAnnotationQuery Interface Description - Includes all of the operations for retrieving gene annotations Interface Number - MA-INF2 Interface Name - MAFreestyleSearch Interface Description - Includes all of the operations for Freestyle Search 32 Interface NoInterface NameInterface Description MA-INF1MAGeneAnnotationQueryIncludes all of the operations for retrieving gene annotations MA-INF2MAFreestyleSearchIncludes all of the operations for Freestyle Search

33. Molecular Annotation Service: Interface Model UML UML image if interfaces in a hierarchical fashion Super-Interface: MAService Sub-Interface: MAGeneAnnotationQuery Sub-Interface: MAFreestyleSearch MAGeneAnnotationQuery Operations getAgentAssociations getBiologicalProcesses getCellularLocations getDiseaseAssociations getFunctionalAssociations getGenesByMicroarrayReporter getGenesBySymbol getHomologousGene getStructualVariations MAFreestyleSearch Operations: freestyleSummarySearch freestyleSearch 33

34. Behavioral Viewpoint Artifacts: List of Operations List the operations for each interface Molecular Annotation Service: List of Operations (Truncated) Operation Number - MA-INF1-OP1 Operation Name - getGenesBySymbol Interface Name - MAGeneAnnotationQuery Operation Description - Returns the genes named by the specified gene symbols and/or gene aliases Operation Number - MA-INF1-OP2 Operation Name - getCellularLocations Interface Name - MAGeneAnnotationQuery Operation Description - Returns annotations describing a gene’s location within a cell Operation Number - MA-INF2-OP1 Operation Name - freestyleSummarySearch Interface Name - MAFreestyleSearchProfile Operation Description - Returns a summary result for a given keyword or keywords Operation Number - MA-INF2-OP2 Operation Name - freestyleSearch Interface Name - MAFreestyleSearchProfile Operation Description - Returns a list of results matching the given keyword or keywords 34 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

35. Behavioral Viewpoint Artifacts: Operation Behavior Descriptions Detailed description of the behavior of each interface operation Includes the following information: Behavior Description Textual description of the operation behavior and business logic Pre-Conditions Any pre-conditions necessary for invoking this operation Security Conditions Describe in detail the security constraints which the user needs to fulfill in order to execute this operation Inputs Provide details of the inputs required to invoke this operation. Indicate if the input is mandatory or optional. Outputs Details of the operation outputs. 35

36. Behavioral Viewpoint Artifacts: Operation Behavior Descriptions Included information (cont.): Post-Conditions Describe the details of the system state after the operation has been successfully executed. Exception Conditions List and describe any exception conditions for this operation with common error codes where applicable. Additional Implementation Details Notes Any additional notes dealing restrictions to the operation and its relation to other operations in the service. 36

37. Molecular Annotation Service: Operation Behavior Description Behavior DescriptionClient supplies a ReporterSearchCriteria instance with a reporter name and a microarray design as search criteria 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 getGenesByMicroArrayReporter Behavior Description Client supplies a ReporterSearchCriteria instance with a reporter name and a microarray design as search criteria 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-conditions None Security Conditions None Inputs ReporterSearchCriteria Outputs Fully-populated instance(s) of Gene 37

38. Molecular Annotation Service: Operation Behavior Description Post-ConditionsNone Alternate ConditionsNo matching genes found Exception ConditionsSpecified microarray is not supported Reporter not found Additional DetailsNone NotesNone getGenesByMicroArrayReporter (cont.): Post-Conditions None Alternate Conditions No matching genes found Exception Conditions Specified microarray is not supported Reporter not found Additional Details None Notes None 38

39. Behavioral Viewpoint Artifacts: Dynamic Model Includes the descriptions of the interactions of the service. Sequence diagrams describing significant interactions with the service. Relationships to external services. Molecular Annotation Service: External Service Relationships Service - Integrative Translational Research System Relationship - Depends Data - Molecular Annotations Description - Integrative Translational Research Systems such as caIntegrator depend on Molecular Annotations for looking up annotations for microarray reporters used in experiments being analyzed. Service - Gene Expression Analysis Tool Relationship - Depends Data - Molecular Annotations Description - Gene Expression Analysis Tools such as GEWorkbench depend on a Molecular Annotations for putting expression data in context of a genome. 39 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.

40. Behavioral Viewpoint Exercise: Interface Model Given the following Service Registration Interfaces, match the operations with the most appropriate interface. Interfaces: SRManagementBase - Provides the functionality common to both the registering site as well as coordinating center. SRQuery - Provides the functionality to query subject registration SRManagementSite - Provides the functionality available to the Site Registrar at the registering site SRReporting - Provides the functionality available to the Study Registrar (as well as other approved personnel) at the Study Coordinating center. Operations: querySubjectRegistration retrieveAccrualData initiateSubjectRegistration updateSubjectRegistration 40

41. Behavioral Viewpoint Exercise: Operation Behavior Description For the following Subject Registration Service Operation, detail possible pre-conditions, security conditions, post-conditions, and exception conditions initiateSubjectEnrollment Description: This functionality is invoked by the client to initiate subject enrollment. Clients can provide consent correspondence data like consent delivery, consent presenter etc to begin the enrollment process. Inputs: BiologicEntityIdentifier [M] DocumentIdentifier (study identifier) [M] OrganizationIdentifier (registering site identifier) [M] StudySubject including the following: DSET [M] ScheduledEpoch [O] Outputs: StudySubject 41

42. Behavioral Viewpoint Exercise: Operation Behavior Description Behavior Description This functionality is invoked by the client to initiate subject enrollment. Clients can provide consent correspondence data like consent delivery, consent presenter etc. to begin the enrollment process Pre-Conditions Study must exist and is in the “OPEN” state StudySite must exist and is in “ACTIVE” state Security Conditions The requestors: Must be a member of the Site Registrar group at the given site Must be a member of the Site Registrar group for the given study Inputs BRIDG: BiologicEntityIdentifier [M] DocumentIdentifier (study identifier) [M] OrganizationIdentifier (registering site identifier) [M] StudySubject including the following: DSET [M] ScheduledEpoch [O] Outputs BRIDG: StudySubject (Containing a temporary identifier in field identifier of II) 42

43. Behavioral Viewpoint Exercise: Operation Behavior Description Post-Conditions Subject is Pending On-Study Exception Conditions Invalid StudySubject class representation Subject already registered to the study Invalid StudyProtocol identifier Study site is not active Study Protocol is not open for enrollment Invalid data type or code value for an attribute Additional Implementation Details The operation will refer to the subject management service to pull the subject. Take a snapshot of the subject and freeze it against the registration. Discard subject demography details from the input of the operation. Use the demography data fetched from the subject management. Notes None 43

44. Deployment Viewpoint Artifacts The primary artifacts generated from the Deployment Viewpoint at the LPS include: Deployment Model: Platform Independent deployment consideration and plans List deployment scenarios for this service. Provide deployment guidelines for the service implementers. An Image showing a slice of the ECCF organizational matrix Along the left from top to bottom are the specifications Conceptual, Logical, and Physical There is only one column with the heading “Deployment Viewpoint” In the boxes are summaries of the artifacts for each specification at the Deployment viewpoint level. The Logical specification row is highlighted by a red box around it, and it contains the following text: Deployment considerations 44

45. Other Mandatory Artifacts Conformance Statements Testable and verifiable statements made in the context of a single viewpoint. References Table identifying the sources used to create the specification Glossary Citation of terms specific to this specification and not included in the overall CBIIT Glossary Interface to profile mapping The mapping of the Interfaces from the LPS to the corresponding profiles in the CPS. Interface operations to profile capabilities The mapping of the operations of the interfaces to the corresponding profile capabilities from the CPS. 45

46. Molecular Annotation Service: Conformance Statements (subset) #NameTypeViewpointDescriptionTest Method 1Query Performance ObligationEng.The MA service should provide a response within 0.5 seconds to support a synchronous UI based client Test cases to include performance testing 2Semantic Model ObligationInf.The MA service must provide traceability to classes in the LS PIM as identified in section 2.3 Design review 3Data TypesObligationInf.The MA service must conform to NCI’s constrained list of ISO 21090 data types. Design review 4Functional Profiles ObligationComp.Functional Profiles shall be deployed as functional wholes. Ignoring or omitting functional behavior defined within a functional profile is not permitted, nor is diverging from the detailed functional specifications provided in Section 5. Design review & test cases Conformance Statement 1 Name - Query Performance Type - Obligation Viewpoint - Eng. Description - The MA service should provide a response within 0.5 seconds to support a synchronous UI based client Test Method - Test cases to include performance testing Conformance Statement 2 Name - Semantic Model Type – Obligation Viewpoint Inf. Description - The MA service must provide traceability to classes in the LS PIM as identified in section 2.3 Test Method - Design review Conformance Statement 3 Name - Data Types Type - Obligation Viewpoint - Inf. Description - The MA service must conform to NCI’s constrained list of ISO 21090 data types. Test Method - Design review Conformance Statement 4 Name - Functional Profiles Type - Obligation Viewpoint - Comp. Description - Functional Profiles shall be deployed as functional wholes. Ignoring or omitting functional behavior defined within a functional profile is not permitted, nor is diverging from the detailed functional specifications provided in Section 5. Test Method - Design review & test cases 46

47. Molecular Annotation Service: Interface to Profile Mapping Interface No.InterfaceProfile No.Profile MA-INF1MAGeneAnnotationQueryMA-FP1Gene Annotation Query Profile MA-INF2MAFreestyleSearchMA-FP2Freestyle Search Profile Interface Number - MA-INF1 Interface Name - MAGeneAnnotationQuery Functional Profile Number - MA-FP1 Functional Profile Name - Gene Annotation Query Profile Interface Number - MA-INF2 Interface Name - MAFreestyleSearch Functional Profile Number - MA-FP2 Functional Profile Name - Freestyle Search Profile 47

48. Molecular Annotation Service: Operation to Capability Mapping Operation No. Operation NameCapability No. Profile Capability MA-INF1-OP1getGenesBySymbolMA-CPB1Get Genes By Symbol or Alias MA-INF1-OP2getGenesByMicroarrayReporterMA-CPB2Get Genes By Microarray Reporter MA-INF2-OP1freestyleSummarySearchMA-CPB10Freestyle Summary Search MA-INF2-OP1freestyleSearchMA-CPB11Freestyle Search Operation Number – MA-INF1-OP1 Operation Name – getGenesBySymbol Capability Number – MA-CPB1 Profile Capability – Get Genes By Symbol or Alias Operation Number – MA-INF1-OP2 Operation Name – getGenesByMicroarrayReporter Capability Number – MA-CPB2 Profile Capability – Get Genese By Microarray Reporter Operation Number – MA-INF2-OP1 Operation Name – freestyleSummarySearch Capability Number – MA-CPB10 Profile Capability – Freestyle Summary Search Operation Number – MA-INF2-OP2 Operation Name – freestyleSearch Capability Number – MA-CPB11 Profile Capability – Freestyle Search 48

49. Logical Perspective Specification Summary Enterprise Viewpoint Relationship to CPS Refine conformance statements from CPS Information Viewpoint Further constrains and localizes the CPS information model to meet the needs of the current project. Details primary objects as well as control data types Behavioral Viewpoint Formalized Service Contract Logically group operations into interfaces Detailed descriptions of service operations Deployment Viewpoint Deployment Considerations 49

50. References Molecular Annotation Service PIM: https://ncisvn.nci.nih.gov/svn/cabiodb/ECCF/artifacts/logical/PIMSS_Molecular_Ann otation_Service.dochttps://ncisvn.nci.nih.gov/svn/cabiodb/ECCF/artifacts/logical/PIMSS_Molecular_Ann otation_Service.doc Service Registration Service PIM: https://ncisvn.nci.nih.gov/svn/c3pr/trunk/c3prv2/documentation/design/essn/Subject Registration/PIMSS_Subject_Registration_Service.dochttps://ncisvn.nci.nih.gov/svn/c3pr/trunk/c3prv2/documentation/design/essn/Subject Registration/PIMSS_Subject_Registration_Service.doc caBIG PIM Service Specification Template: http://gforge.nci.nih.gov/svnroot/candc/trunk/documents/artifact_templates/logical/c aBIG_Platform_Independent_Model_Template.dochttp://gforge.nci.nih.gov/svnroot/candc/trunk/documents/artifact_templates/logical/c aBIG_Platform_Independent_Model_Template.doc CBIIT SAIF Implentation Guide (16-Dec-2010 version): https://wiki.nci.nih.gov/download/attachments/33401213/16Dec2010SAIFIG.pdf?ver sion=1&modificationDate=1292539920000https://wiki.nci.nih.gov/download/attachments/33401213/16Dec2010SAIFIG.pdf?ver sion=1&modificationDate=1292539920000 50