This assignment is done by Esha Ramtahal (0700148) and Seetiah L.d (0700184)
System Architecture of On-line Knowledge-based Anatomy Information System
Introduction
Anatomical information is fundamental for biomedicine, not only because there is a large amount of it, but also because anatomy serves as a framework for organizing other kinds of data.
Increased multimedia capabilities, together with new data sources such as the Visible Human, have led to many CD-ROM based anatomy atlases and tutorials. The World Wide Web provides the potential for these and other anatomical resources to be delivered over the Internet. However, most Web-accessible resources have to-date been little more than advertisements for CD-ROM products. The availability of the Web, together with the new anatomical information resources, present opportunities and challenges, both technical and economic, for delivering on-demand anatomical information that is customized to a wide variety of users.
The atlases consist of annotated images through various body regions, as well as stored animations of 3-D graphics reconstructions. Given an annotated image, a user is able to click on regions to see structures, to take an online quiz, to retrieve an associated animation, or to generate a "pin diagram" showing the names of all the structures in the image.
The atlases are widely used throughout the world, receiving over 7000 hits per day. However, on-line surveys and student feedback show a need for additional features. These features include 1) content from more parts of the body, 2) links to additional symbolic information besides just the name, 3) more control over the navigation, 4) varying levels of detail depending on the user, and 5) direct manipulation of 3-D models.
Functional Requirements
Users include K-12 students, undergraduates, professional students such as medical students, postdoctoral fellows and residents, professionals such as cardiac surgeons, and the lay public.
The spatial information resources include 2-D annotated images, 3-D labeled image volumes, 3-D models, and stored animations.
The symbolic information resources include the knowledge base, which implements the foundational model of anatomy. The symbolic resources also include metadata, which will be used to locate, track and identify the spatial information, since spatial information comes in many forms and may be located in different locations on the Internet.
The authoring programs shown in the upper left are used to create these resources, and include a Knowledge Builder for creating the foundational model, a Model Builder for creating the 3-D models from 3-D image volumes, and an Annotator, for associating names from the knowledge base with regions on the images.
The Structural Information Servers provide network access to these resources. The Annotated Image Server delivers interactive images that respond to mouse clicks, as in our current Web atlas programs. The Knowledge Server provides access to the foundational model, and provides answers to queries such as "Find all the synonyms of aorta", or "List the branches of the aorta".
The Data Server consults the metadata to provide the filenames of spatial objects that are associated with a set of anatomical concepts indexed by terms in the knowledge base, and the Graphics Server combines these spatial objects into scenes that are delivered to the client. These scenes can take the form of dynamically generated annotated images, animations, or VRML descriptions.
The Digital Anatomist module is an intelligent agent that acts as an intermediary between the user and the set of resources. Eventually the Digital Anatomist should act like a real anatomist in presenting anatomical information to the end user.
End User Interfaces
Although the information should be organized around the foundational model, the end-user will not necessarily see this model unless he or she requests it. Instead the information should be presented in different ways depending on the type of user, the manner of use, and the category of information. The type of user determines the level of detail that is appropriate to present. The manner of use includes reference, tutorial and consultant modes. The category of information is spatial or symbolic.
Non Functional Requirements
Non-Functional Requirements (NFRs) presents a systematic and pragmatic approach to `building quality into' software systems. Systems must exhibit software quality attributes, such as accuracy, performance, security and modifiability. However, such non-functional requirements (NFRs) are difficult to address in many projects, even though there are many techniques to meet functional requirements in order to provide desired functionality. This is particularly true since the NFRs for each system typically interact with each other, have a broad impact on the system and may be subjective.
Emergent Properties
The correctness of the system – Extent to which the system satisfies and fullfils the user’s specification
The overall weight – This is known only after all the modules are put together
The reliability – Extent to which the system can be expected to perform its intended function with required precision when subjected to the environment in which it was intended to use
The usability – Effort required learning, operating and interpreting the output of the system
Efficiency – The amount of computing resources and code required by the system to perform a function
Integrity (Robustness/Security) – Extent to which access to software or data by unauthorized person can be controlled
Maintainability – Effort required locating and fixing error in the operational product
Testability – Effort required testing the product to ensure it performs the intended functions
Flexibility – Effort required modifying the operational program
Portability – Effort required transferring the product from one hardware configuration and/or software system environment to another
Reusability – Extent to which the system or part of it can be used in other applications
Interoperability – Effort required coupling the system with another
Performance – The number of processes the system can handle in unit time
The correctness of the system – Extent to which the system satisfies and fullfils the user’s specification
The overall weight – This is known only after all the modules are put together
The reliability – Extent to which the system can be expected to perform its intended function with required precision when subjected to the environment in which it was intended to use
The usability – Effort required learning, operating and interpreting the output of the system
Efficiency – The amount of computing resources and code required by the system to perform a function
Integrity (Robustness/Security) – Extent to which access to software or data by unauthorized person can be controlled
Maintainability – Effort required locating and fixing error in the operational product
Testability – Effort required testing the product to ensure it performs the intended functions
Flexibility – Effort required modifying the operational program
Portability – Effort required transferring the product from one hardware configuration and/or software system environment to another
Reusability – Extent to which the system or part of it can be used in other applications
Interoperability – Effort required coupling the system with another
Performance – The number of processes the system can handle in unit time
