The general structure of a writing piece
- Introduction
- what are you taling of ?
- What are you taiking about it?
- Why now?
- so what?
- conclusion
Monday, 28 April 2008
Wednesday, 16 April 2008
Lessons from Steve Jobs
“The only way to do great work is to love what you do. If you haven’t found it yet, keep looking. Don’t settle. As with all matters of the heart, you’ll know when you find it.”
“Your time is limited, so don’t waste it living someone else’s life. Don’t be trapped by dogma - which is living with the results of other people’s thinking. Don’t let the noise of other’s opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary.”
“You know, we don’t grow most of the food we eat. We wear clothes other people make. We speak a language that other people developed. We use a mathematics that other people evolved… I mean, we’re constantly taking things. It’s a wonderful, ecstatic feeling to create something that puts it back in the pool of human experience and knowledge.”
“We’re here to put a dent in the universe. Otherwise why else even be here?”
“I’m the only person I know that’s lost a quarter of a billion dollars in one year…. It’s very character-building.”
“I would trade all of my technology for an afternoon with Socrates.”
“There’s a phrase in Buddhism, ‘Beginner’s mind.’ It’s wonderful to have a beginner’s mind.”
“Innovation distinguishes between a leader and a follower.”
“We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on.”
“Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.”
“Your time is limited, so don’t waste it living someone else’s life. Don’t be trapped by dogma - which is living with the results of other people’s thinking. Don’t let the noise of other’s opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary.”
“You know, we don’t grow most of the food we eat. We wear clothes other people make. We speak a language that other people developed. We use a mathematics that other people evolved… I mean, we’re constantly taking things. It’s a wonderful, ecstatic feeling to create something that puts it back in the pool of human experience and knowledge.”
“We’re here to put a dent in the universe. Otherwise why else even be here?”
“I’m the only person I know that’s lost a quarter of a billion dollars in one year…. It’s very character-building.”
“I would trade all of my technology for an afternoon with Socrates.”
“There’s a phrase in Buddhism, ‘Beginner’s mind.’ It’s wonderful to have a beginner’s mind.”
“Innovation distinguishes between a leader and a follower.”
“We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on.”
“Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.”
Thursday, 10 April 2008
China or India
Where do we have to invest, China or India? There are three reasons to invest in China rather than India.
First, China leads India in terms of economy growth rate; therefore, we can expect much more return on investments than India. China's GDP totaled 3,100 billion U.S. dollars in the year of 2007, up to 11 percent over the same period last year, according to the China National Bank. However, India raised GDP growth of 8.7 percent, up to 928billion dollars in total GDP according to the Reserve Bank of India. This economic data appears to be sustainable until two or three years after, as we have seen so far.
Second, China leads India in terms of market size; therefore, we can expect much more opportunities than India. China’s GDP per person was 2,280 dollars in the year of 2007; on the other hand, India’s GDP per person was 830 dollars in the same year according to National Bank. As the China’s economy grows, the brand market will grows as well. This means that international brand market will grows much more rapidly in China than in India. In addition, because China is the site for the next Olympic Games, all the global companies will invest or try to enter this attractive market by the year of 2010.
Third, China’s dominant industry is manufacturing; however, India is strong in technology and IT services high value industry, but is obviously not a high volume industry. Typically, service industry does not rely on high, intensive capital, on which China’s manufacturing industry has relied to a great extent. By this reason, a large number of foreign investments are turning toward China, and we need to move forward with the same reason.
In conclusion, in terms of growth rate, market size, and the event of Beijing Olympic, to invest China is the best choice. The decision of China investment is most critical to the growth of our company and the right decision will lead us to be a global leader.
First, China leads India in terms of economy growth rate; therefore, we can expect much more return on investments than India. China's GDP totaled 3,100 billion U.S. dollars in the year of 2007, up to 11 percent over the same period last year, according to the China National Bank. However, India raised GDP growth of 8.7 percent, up to 928billion dollars in total GDP according to the Reserve Bank of India. This economic data appears to be sustainable until two or three years after, as we have seen so far.
Second, China leads India in terms of market size; therefore, we can expect much more opportunities than India. China’s GDP per person was 2,280 dollars in the year of 2007; on the other hand, India’s GDP per person was 830 dollars in the same year according to National Bank. As the China’s economy grows, the brand market will grows as well. This means that international brand market will grows much more rapidly in China than in India. In addition, because China is the site for the next Olympic Games, all the global companies will invest or try to enter this attractive market by the year of 2010.
Third, China’s dominant industry is manufacturing; however, India is strong in technology and IT services high value industry, but is obviously not a high volume industry. Typically, service industry does not rely on high, intensive capital, on which China’s manufacturing industry has relied to a great extent. By this reason, a large number of foreign investments are turning toward China, and we need to move forward with the same reason.
In conclusion, in terms of growth rate, market size, and the event of Beijing Olympic, to invest China is the best choice. The decision of China investment is most critical to the growth of our company and the right decision will lead us to be a global leader.
Tuesday, 8 April 2008
How to prepare Good meeting
0. Do we really need a meeting?
1. Purpose
- critical issues
2. Agenda
- 1page
- grouping topics
- prioritize topics
- Keep track on time (time keeper) + notes (Note taker)
- Responsibilities
3. People
- pick right participants
4. Place + Time
- Bad Time: lunch, at 5:00PM, Friday afternoon, Monday early morning
- Best Time: Tuesday/Wednesday/Thursday morning
- don't bring high sugar stuff, pasta, pizza
- Place: adequate size, depends on group size, visual aids
- Time: don't over 2 hours
5. Invite /DRAFT Agenda
- please review, comment about attached draft agenda
6. Resend with changes/ P
- based on all sets, well-prepared to the meeting
7. Arrive Early
- host should arrive early.
8. Start on Time
9. Set the Tone
10. Run the meeting
11. Meeting Minustes/Meeting Summary
12. Actions
1. Purpose
- critical issues
2. Agenda
- 1page
- grouping topics
- prioritize topics
- Keep track on time (time keeper) + notes (Note taker)
- Responsibilities
3. People
- pick right participants
4. Place + Time
- Bad Time: lunch, at 5:00PM, Friday afternoon, Monday early morning
- Best Time: Tuesday/Wednesday/Thursday morning
- don't bring high sugar stuff, pasta, pizza
- Place: adequate size, depends on group size, visual aids
- Time: don't over 2 hours
5. Invite /DRAFT Agenda
- please review, comment about attached draft agenda
6. Resend with changes/ P
- based on all sets, well-prepared to the meeting
7. Arrive Early
- host should arrive early.
8. Start on Time
9. Set the Tone
10. Run the meeting
11. Meeting Minustes/Meeting Summary
12. Actions
Monday, 7 April 2008
7 things employee want most to be happy at work
Ask bosses what makes employee happy at work, and many are likely to think in terms of tangible rewards: a good salary, a pleasant office, generous benefits.
1. Appreciation
2. Respect
3. Trust
4. Individual growth
5. A good boss
6. Compatible co-workers
7. A sense of purpose
By Marlilyn Gardner
1. Appreciation
2. Respect
3. Trust
4. Individual growth
5. A good boss
6. Compatible co-workers
7. A sense of purpose
By Marlilyn Gardner
Thursday, 3 April 2008
Interview Tip
1) Dress Attire / Hair / Good Appearance/ Posture/ Charm / Pleasant
2) Resume : Right Upfront by two hands
3) Interrupted behavior/ Eye Contact
4) Asset Points (Weaving asset points)
5) Memorable Story/ Differentiation
6) Company Knowledge
7) Enthusiasm/ Potential / Simple/ Engage / Enjoy
8) Action Statement - I created/developed/improved ....
9) Result Oriented/ Add Quatative number
10) How handle difficult question/situation
11) Ask Good Question ; Poze/ Scilence/ At the end
12) Specific Story about team skill (worst team experience )
13) Hardworking
14) Handle salary question, elogance
15) Ask Next step; Ask email address
16) Last chabge; Ending(Handshake), Ask Next Step
2) Resume : Right Upfront by two hands
3) Interrupted behavior/ Eye Contact
4) Asset Points (Weaving asset points)
5) Memorable Story/ Differentiation
6) Company Knowledge
7) Enthusiasm/ Potential / Simple/ Engage / Enjoy
8) Action Statement - I created/developed/improved ....
9) Result Oriented/ Add Quatative number
10) How handle difficult question/situation
11) Ask Good Question ; Poze/ Scilence/ At the end
12) Specific Story about team skill (worst team experience )
13) Hardworking
14) Handle salary question, elogance
15) Ask Next step; Ask email address
16) Last chabge; Ending(Handshake), Ask Next Step
Monday, 28 January 2008
Steve Job's Presentation Tip
1. Set the theme.
2. Demonstrate enthusiasm.
3. Provide an outline.
4. Make numbers meaningful.
5. Try for an unforgettable moment.
6. Create visual slides.
7. Give 'em a show.
8. Don't sweat the small stuff.
9. Sell the benefit.
10. Rehearse, rehearse, rehearse.
2. Demonstrate enthusiasm.
3. Provide an outline.
4. Make numbers meaningful.
5. Try for an unforgettable moment.
6. Create visual slides.
7. Give 'em a show.
8. Don't sweat the small stuff.
9. Sell the benefit.
10. Rehearse, rehearse, rehearse.
Wednesday, 23 January 2008
When to use Passive
1) When you don't know who did the action
2) when your readers don't care who did the action
3) when you don't want the readers to know who did the action
4) when the receiver of action is more important than the doer of the action
5) when you wish to be less confrontational
2) when your readers don't care who did the action
3) when you don't want the readers to know who did the action
4) when the receiver of action is more important than the doer of the action
5) when you wish to be less confrontational
Goal with SMART
To make good plan, one should make good goal.
There are famous tool to make good goal.
SMART
Specific, Measurable, Attainable, Relevant, Time-Bound
There are famous tool to make good goal.
SMART
Specific, Measurable, Attainable, Relevant, Time-Bound
Monday, 21 January 2008
SOA
Biz View: a set of services that a business wants to expose to their customers and partners, or other portions of the organization
Architecture view: a set of architectural principles, patterns and criteria which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composability and single implementation
Implementation View: a programming model complete with standards, tools and technologies such as Web Services
An SOA is composed of multiple layers. At the heart of the SOA is the Service Model that defines Services and Components that realize them
Service modeling – what we model
Layer 1 which is the bottom layer describes operational systems. This layer contains existing systems or applications including existing CRM and ERP packaged applications, legacy applications and “older” object-oriented system implementations as well as business intelligence applications. The composite layered architecture of an SOA can leverage existing systems, integrate them using service-oriented integration.
Layer 2 is the component layer which used container–based technologies and designs used in typical component-based development.
Layer 3 provides for the mechanism to take enterprise scale components, business unit specific components and in some cases project specific components and provides services through their interfaces. The interfaces get exported out as service descriptions in this layer, where services exist in isolation or as composite services.
Level 4 is an evolution of service composition into flows or choreographies of services bundled into a flow to act as an application. These applications support specific use-cases and business processes. Here, visual flow composition tools such as WebSphere WBI-Modeler can be used for design of application flow.
Layer 5, the presentation layer is usually out of scope for an SOA. However, it is depicted because some recent standards such as Web Services for remote Portlets version 2.0 may indeed leverage Web Services at the application interface or presentation level. It is also important to note that SOA decouples the user interface from the components.
Layer 6 enables the integration of services through the introduction of a reliable and intelligent routing, protocol mediation, and other transformation mechanisms often described as the Enterprise Service Bus .
Layer7 ensures quality of service through sense-and–respond mechanisms and tools that monitor the health of SOA applications, including the all important standards implementations of WS-Management.
Architecture view: a set of architectural principles, patterns and criteria which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composability and single implementation
Implementation View: a programming model complete with standards, tools and technologies such as Web Services
An SOA is composed of multiple layers. At the heart of the SOA is the Service Model that defines Services and Components that realize them
Service modeling – what we model
Layer 1 which is the bottom layer describes operational systems. This layer contains existing systems or applications including existing CRM and ERP packaged applications, legacy applications and “older” object-oriented system implementations as well as business intelligence applications. The composite layered architecture of an SOA can leverage existing systems, integrate them using service-oriented integration.
Layer 2 is the component layer which used container–based technologies and designs used in typical component-based development.
Layer 3 provides for the mechanism to take enterprise scale components, business unit specific components and in some cases project specific components and provides services through their interfaces. The interfaces get exported out as service descriptions in this layer, where services exist in isolation or as composite services.
Level 4 is an evolution of service composition into flows or choreographies of services bundled into a flow to act as an application. These applications support specific use-cases and business processes. Here, visual flow composition tools such as WebSphere WBI-Modeler can be used for design of application flow.
Layer 5, the presentation layer is usually out of scope for an SOA. However, it is depicted because some recent standards such as Web Services for remote Portlets version 2.0 may indeed leverage Web Services at the application interface or presentation level. It is also important to note that SOA decouples the user interface from the components.
Layer 6 enables the integration of services through the introduction of a reliable and intelligent routing, protocol mediation, and other transformation mechanisms often described as the Enterprise Service Bus .
Layer7 ensures quality of service through sense-and–respond mechanisms and tools that monitor the health of SOA applications, including the all important standards implementations of WS-Management.
Wednesday, 16 January 2008
Human Computation and Louis von Ahn
http://video.google.com/videoplay?docid=-8246463980976635143&q=luis+von+ahn&pr=goog-sl
Luis von Ahn, he is a really, really, really genius!!!
I studied MPEG1,2 4 and MPEG7 10 years ago.
But still how to abstract specific objects from image and how to describe the relevant objects are open problem in image processing area.
But he solved this by "human computation" concept.
His main idea is like this;
let people compute for opem problem which computer cannot solved yet.
But use the people with fun and for free!
He is one of the Cooooooolest guy , a professor of CMU , as I ever met.....
(I'm going to have his class in this semester!!!!)
His PhD thesis was CAPTCHA (A program that can tell whether it suers is a human or a computer) in 2005.
a program that can generate and grade test that:
A.most humans can pass
B.current computer programs cannot pass
The official CAPTCHA site : http://www.captcha.net/
http://recaptcha.net/
Human Computation : http://www.cs.cmu.edu/~biglou/research.html
Luis von Ahn:http://www.cs.cmu.edu/~biglou/
Luis von Ahn, he is a really, really, really genius!!!
I studied MPEG1,2 4 and MPEG7 10 years ago.
But still how to abstract specific objects from image and how to describe the relevant objects are open problem in image processing area.
But he solved this by "human computation" concept.
His main idea is like this;
let people compute for opem problem which computer cannot solved yet.
But use the people with fun and for free!
He is one of the Cooooooolest guy , a professor of CMU , as I ever met.....
(I'm going to have his class in this semester!!!!)
His PhD thesis was CAPTCHA (A program that can tell whether it suers is a human or a computer) in 2005.
a program that can generate and grade test that:
A.most humans can pass
B.current computer programs cannot pass
The official CAPTCHA site : http://www.captcha.net/
http://recaptcha.net/
Human Computation : http://www.cs.cmu.edu/~biglou/research.html
Luis von Ahn:http://www.cs.cmu.edu/~biglou/
Tuesday, 15 January 2008
Simplicity and Separation of Concern
"One of the most degenerative tendencies of the last forty years is the belief that if you are understandable, you are vulgar." by Peter Drucker
"Insecure managers create complexity. Frightened, nervous managers use think, convoluted planning books and busy slides filled with everything they've known since childhood. Real leaders don't need clutter. People mush have the self-confidence to be clear, precise, to be sure that every person in their organization - highest to lowest - understands what the business is trying to achieve. But it is not easy.You cannot believe how hard it is for people to be simple, how much they fear being simple. They worry that if they are simple, people will think they are simple minded. In reality, of course, it is just the reverse. Clear, tough-minded people are the most simple." by Jack Welch.
I 100% agreed about Jack Welch's last expression; "Clear minded people are the most simple".
Software architect is one of very hard occupation in the world, I think.
There are too many constraints in the company and technology and too many uncertainties in the business policy. However, software architect should make architectural decision and meet many different business objectives. And architectural decision should be reasonable, objective, and meet stake holder's totally different views; CEO wants numbers, CTO wants reliability, developers want codes, designers want lots of diagrams.....Although this complex and different perspectives, software architect make "simple" architectural decision. Simple architecture is the key for architectural decision. I paraded Yoda's saying in the movie "Star Wars", "May the force be with you."; My favorites :-) !!!
"Insecure managers create complexity. Frightened, nervous managers use think, convoluted planning books and busy slides filled with everything they've known since childhood. Real leaders don't need clutter. People mush have the self-confidence to be clear, precise, to be sure that every person in their organization - highest to lowest - understands what the business is trying to achieve. But it is not easy.You cannot believe how hard it is for people to be simple, how much they fear being simple. They worry that if they are simple, people will think they are simple minded. In reality, of course, it is just the reverse. Clear, tough-minded people are the most simple." by Jack Welch.
I 100% agreed about Jack Welch's last expression; "Clear minded people are the most simple".
Software architect is one of very hard occupation in the world, I think.
There are too many constraints in the company and technology and too many uncertainties in the business policy. However, software architect should make architectural decision and meet many different business objectives. And architectural decision should be reasonable, objective, and meet stake holder's totally different views; CEO wants numbers, CTO wants reliability, developers want codes, designers want lots of diagrams.....Although this complex and different perspectives, software architect make "simple" architectural decision. Simple architecture is the key for architectural decision. I paraded Yoda's saying in the movie "Star Wars", "May the force be with you."; My favorites :-) !!!
Monday, 14 January 2008
Foundation Facility
JMS
Java Messaging service offers a unified wrapper over queuing mechanisms. The framework wraps the JMS implementation and provides methods for applications to use this service without knowledge of the underlying queuing mechanism or the JMS API. The JMS API offers a asynchronous send and receive mechanisms and also a synchronous send and receive mechanism for application clients. The synchronous implementation is a convenience implementation which calls the send and then the receive methods with an appropriate timeout. The mechanism uses the JMS correlation id to associate the request and the response. The framework also implements a wrapper over a JMS Topic thereby allowing an application to work in a publish subscribe mode.
Logging
This supports for reporting application events into persistent storage areas. Logging provides precise context about a run of the application. Once inserted into the code, the generation of logging output requires no human intervention. Second, log output can be saved in a persistent medium to be studied at a later time.
Rules
It provide flexibility to application design and development by externalizing dynamic business logic. As some areas of the business are more susceptible to change than others. It is important to therefore have a mechanism that allows an application to identify areas that are likely to change and externalize the logic contained within them. This changes should be managed is a such a manner that there is no to less development effort required. It uses code generator to generate rule classes. Rule classes run in the same address space as the application program. This enhances performance as rule classes run in the same address space and use the same thread of execution, they share the transaction database session context for data. This avoids reads from database for data that is already loaded. Rules can also be dynamically changed by integrating with dynamic class loader.
Dynamic class loading:
This facilitates deployment of business rules dynamically without stopping the application server. Rules as mentioned above are business logic that changes frequently and needs to be deployed on the application server without restarting the application server. Rules are deployed as jar files in the application server, any changes to the rules would negotiate a re-deployment of the jar files. Currently it is not recommended that the hot deployment option of the application server be used. This is because the application server vendors claim that it might cause potential synchronization problems with the deployed application and might cause deployed applications to be deleted or modified incorrectly.Custom class loader load classes directly from the disk. It scans a pre-defined area on the file system for changed files based on time stamp. Clients already in middle of a method call will continue to use the old class, while new clients will receive an object from the changed class. It checks for modified classes on configurable time based interval.
Configuration:
It supports for retrieving of application parameters defined in properties file. It synchronizes with the changes made to the application parameters while the application is running. This component uses caching and logging architectural mechanisms. Configuration allows for providing set of properties in a different properties file to
Helpers
The Framework offers various helper functions to facilitate the building of framework components. These components are expected to be re-used across various other sophisticated framework facilities or components.The following helpers are available as part of the framework. These facilities are implemented as helpers as any improvements to these facilities can be done in a central place benefiting all framework components that use them. For example, if there are changes to reflection helper to leverage performance enhancements to the next version of J2SE, then all components will benefit from the same. Similarly the XML Helper wraps the DOM implementation of Xerxes and provides an easy to use interface. The XML Helper includes some significant performance enhancements in the way commonly used XPath (/Customer/Name/) expressions are evaluated. It uses a custom mechanism for these kind of expressions instead of the much slower XPath API. XPath API is still supported for the complete XPath specification.
Error and Exception Mechanism:
This architectural mechanism handles application errors and loggs them as per standard strategy. Error handling supports for multi-lingual error messages for the same error codes. Two named exceptions viz FrameworkException and BusinessException are provided to be used to denote any application errors. Unique error code is assigned with each exception to identify the error.
Service locator
This is a deviation of the standard service locator pattern. It provides transparent object access to applications or other framework components. The service locator abstracts the service discovery process. This discovers a service based on a set of configuration parameters provided. This will then return an object of the service based on the parameter defined. The service locator handles the discovery of JNDI services apart from specific services like EJBs, JMS handles and POJOs. It caches JNDI resources to avoid lookups for each invocation.
Alert
This architectural service provides mechanism for sending alerts for an event. Events needs to be registered with alert service. Event handlers are implemented that handles the event. Support for alerting by SMS and Email is provided using SMS and Mail helper architectural components. Events have information as required by it’s event handler. Client provides those information in the Event and does not need to know about the recipients and mode of alerts. Event handler identifies the list of recipients and modes of sending alert. Alerts are sent asynchronously where client does not wait until alert is sent.
Reporting for batches
This architectural service is a wrapper over third party, OZ reporting, tool and provides option to plug-in another reporting tool in future without change in the client code. OLTP reports will continue in the same style as the existing KB system. Mainly this service is used by batch. Report service supports two modes of execution, synchronous and asynchronous. In asynchronous execution mode, the client request a report and then poll for the status based on the report task ID that was provided when requesting a report. In synchronous execution mode, the client waits for the completion of the report.
Mail
Mail component provides facility to send an email. Mail shields client from internals of sending email. Client is not required to know about the details on how to send mails. Mail component currently is used by Alert. Mail component currently inserts a record in a table owned by e-business team. E-business team finally reads records from the table and sends mail using their existing mail gateway.
SMS
SMS component provides facility to send a SMS. SMS shields client from internals of sending SMS. Client is not required to know about the details on how to send SMS. SMS component currently is used by Alert. SMS component currently inserts a record in a table owned by e-business team. E-business team finally reads records from the table and sends SMS using their existing SMS gateway.
Data Compression
Data compression implements a simplified API over the GZIP implementation. This mechanism can be used to compress data being transferred from the channel tier to the application tier or from the client to the channel tier. This mechanism can be used where-in the available bandwidth mandates a data compression mechanism. By implementing a standard compression algorithm, the data compression mechanism allows even third-party applications to compress data.
Charset Conversion
This supports for conversion from EBCDIC character set to ASCII character set and vice versa. Client code need not code for character conversion every time instead they can use this component.
FTP helper
FTP helper assists in listing and exchanging files between two servers. This uses the Apache commons FTP library, but makes modifications to the open-source library by providing support for the IBM mainframe file system. Files are exchanged using FTP protocol where host runs FTP service. This component consists of a convenience GUI which shows the progress of the files downloaded or uploaded. Client can get the listing of files on host system using this component. This component supports DBCS.
File Parser
This architectural mechanism provides a uniform approach for parsing of ASCII flat files. It supports position based and delimiter based file parsing. It returns the parsed file as a domain object thus freeing developer from file IO operations. Provision for returning domain objects after each record is parsed or in batch of records is provided so as to maximize memory utilisation as per the application need. It supports two models for parsing viz push and pull. Push model parse pre-configured number of records and send to the client as domain object. Pull model waits for client to request to parse the file sequentially in batches. Client receives an handle to lazy fetch which can be iterated through to generate next batch of records.
Bootstrap
This architectural component assist in initializing required services or components in application server before any client request can be serviced. It also helps in improving performance by ensuring globally required services are initialized and available when required rather than loading them at the time of request. In the channel tier, where there is a web container, a bootstrap Servlet is used. In the application server, which is not expected to host a web-container, this component uses the custom API provided by application server. Hence this component is coupled with application server and is currently available for use in IBM Websphere application server for the application tier.
Data Access Service
This architectural mechanism allows access to the persistent store. It is wrapper on Hibernate ORM that provides XML based mapping of objects to relational mapping. It uses IOC (inversion of control) to keep the connection handles encapsulated from a developer and internally uses a reference counting mechanism to finally close database connection. It throws named exceptions to flag application developers of exceptions that can be handled like no data found.
Batch-Shared OLTP
The framework includes a high performing batch framework. The batch framework will provide application developers a platform to assemble business components to be used in a batch mode. The batch framework provides abstract classes for batch application development. The batch framework uses JMS to stream batch jobs. The batch framework does not use custom threads, but rather uses JMS as the threading mechanism to achieve parallelism in a batch job. A batch job can be distributed across not just processes (JVMs) but across servers (or machines). This provides a lot of flexibility in distributing a job. A batch job can therefore be run on the same server as the OLTP or can be run on a different server. It is also possible to introduce new servers for just batch processing, thereby improving the scalability of the batch framework.
The framework provides an abstract batch data class, which can be extended to set the data for the batch process. The developer therefore needs to extend the class for the batch data. Once the data set has been coded for a particular batch process, then the application developer will need to map the batch data set with the input for the process component that needs to be used for the batch process. To actually execute the batch process, the application developer will need to register the batch process using the batch processing administration GUI provided.
PL/SQL Batch Process
The batch framework also provides a PL/SQL version of the batch framework. The PL/SQL version does not share the OLTP process components or the business common services, but provides a simple high performing batch framework in PL/SQL. PL/SQL offers a “near data processing” batch framework. This framework will provide a high batch throughput on a lower system configuration due to the inherent benefits of processing near the data. This framework will need source code duplication and will increase the maintenance effort of the application. Though this will increase the maintenance effort, this framework cannot be written off as it provides a very high batch throughput. For extremely time critical batch processing, this framework may need to be used. The actual usage of the same will depend on the specific requirements for the application.
Java Messaging service offers a unified wrapper over queuing mechanisms. The framework wraps the JMS implementation and provides methods for applications to use this service without knowledge of the underlying queuing mechanism or the JMS API. The JMS API offers a asynchronous send and receive mechanisms and also a synchronous send and receive mechanism for application clients. The synchronous implementation is a convenience implementation which calls the send and then the receive methods with an appropriate timeout. The mechanism uses the JMS correlation id to associate the request and the response. The framework also implements a wrapper over a JMS Topic thereby allowing an application to work in a publish subscribe mode.
Logging
This supports for reporting application events into persistent storage areas. Logging provides precise context about a run of the application. Once inserted into the code, the generation of logging output requires no human intervention. Second, log output can be saved in a persistent medium to be studied at a later time.
Rules
It provide flexibility to application design and development by externalizing dynamic business logic. As some areas of the business are more susceptible to change than others. It is important to therefore have a mechanism that allows an application to identify areas that are likely to change and externalize the logic contained within them. This changes should be managed is a such a manner that there is no to less development effort required. It uses code generator to generate rule classes. Rule classes run in the same address space as the application program. This enhances performance as rule classes run in the same address space and use the same thread of execution, they share the transaction database session context for data. This avoids reads from database for data that is already loaded. Rules can also be dynamically changed by integrating with dynamic class loader.
Dynamic class loading:
This facilitates deployment of business rules dynamically without stopping the application server. Rules as mentioned above are business logic that changes frequently and needs to be deployed on the application server without restarting the application server. Rules are deployed as jar files in the application server, any changes to the rules would negotiate a re-deployment of the jar files. Currently it is not recommended that the hot deployment option of the application server be used. This is because the application server vendors claim that it might cause potential synchronization problems with the deployed application and might cause deployed applications to be deleted or modified incorrectly.Custom class loader load classes directly from the disk. It scans a pre-defined area on the file system for changed files based on time stamp. Clients already in middle of a method call will continue to use the old class, while new clients will receive an object from the changed class. It checks for modified classes on configurable time based interval.
Configuration:
It supports for retrieving of application parameters defined in properties file. It synchronizes with the changes made to the application parameters while the application is running. This component uses caching and logging architectural mechanisms. Configuration allows for providing set of properties in a different properties file to
Helpers
The Framework offers various helper functions to facilitate the building of framework components. These components are expected to be re-used across various other sophisticated framework facilities or components.The following helpers are available as part of the framework. These facilities are implemented as helpers as any improvements to these facilities can be done in a central place benefiting all framework components that use them. For example, if there are changes to reflection helper to leverage performance enhancements to the next version of J2SE, then all components will benefit from the same. Similarly the XML Helper wraps the DOM implementation of Xerxes and provides an easy to use interface. The XML Helper includes some significant performance enhancements in the way commonly used XPath (/Customer/Name/) expressions are evaluated. It uses a custom mechanism for these kind of expressions instead of the much slower XPath API. XPath API is still supported for the complete XPath specification.
Error and Exception Mechanism:
This architectural mechanism handles application errors and loggs them as per standard strategy. Error handling supports for multi-lingual error messages for the same error codes. Two named exceptions viz FrameworkException and BusinessException are provided to be used to denote any application errors. Unique error code is assigned with each exception to identify the error.
Service locator
This is a deviation of the standard service locator pattern. It provides transparent object access to applications or other framework components. The service locator abstracts the service discovery process. This discovers a service based on a set of configuration parameters provided. This will then return an object of the service based on the parameter defined. The service locator handles the discovery of JNDI services apart from specific services like EJBs, JMS handles and POJOs. It caches JNDI resources to avoid lookups for each invocation.
Alert
This architectural service provides mechanism for sending alerts for an event. Events needs to be registered with alert service. Event handlers are implemented that handles the event. Support for alerting by SMS and Email is provided using SMS and Mail helper architectural components. Events have information as required by it’s event handler. Client provides those information in the Event and does not need to know about the recipients and mode of alerts. Event handler identifies the list of recipients and modes of sending alert. Alerts are sent asynchronously where client does not wait until alert is sent.
Reporting for batches
This architectural service is a wrapper over third party, OZ reporting, tool and provides option to plug-in another reporting tool in future without change in the client code. OLTP reports will continue in the same style as the existing KB system. Mainly this service is used by batch. Report service supports two modes of execution, synchronous and asynchronous. In asynchronous execution mode, the client request a report and then poll for the status based on the report task ID that was provided when requesting a report. In synchronous execution mode, the client waits for the completion of the report.
Mail component provides facility to send an email. Mail shields client from internals of sending email. Client is not required to know about the details on how to send mails. Mail component currently is used by Alert. Mail component currently inserts a record in a table owned by e-business team. E-business team finally reads records from the table and sends mail using their existing mail gateway.
SMS
SMS component provides facility to send a SMS. SMS shields client from internals of sending SMS. Client is not required to know about the details on how to send SMS. SMS component currently is used by Alert. SMS component currently inserts a record in a table owned by e-business team. E-business team finally reads records from the table and sends SMS using their existing SMS gateway.
Data Compression
Data compression implements a simplified API over the GZIP implementation. This mechanism can be used to compress data being transferred from the channel tier to the application tier or from the client to the channel tier. This mechanism can be used where-in the available bandwidth mandates a data compression mechanism. By implementing a standard compression algorithm, the data compression mechanism allows even third-party applications to compress data.
Charset Conversion
This supports for conversion from EBCDIC character set to ASCII character set and vice versa. Client code need not code for character conversion every time instead they can use this component.
FTP helper
FTP helper assists in listing and exchanging files between two servers. This uses the Apache commons FTP library, but makes modifications to the open-source library by providing support for the IBM mainframe file system. Files are exchanged using FTP protocol where host runs FTP service. This component consists of a convenience GUI which shows the progress of the files downloaded or uploaded. Client can get the listing of files on host system using this component. This component supports DBCS.
File Parser
This architectural mechanism provides a uniform approach for parsing of ASCII flat files. It supports position based and delimiter based file parsing. It returns the parsed file as a domain object thus freeing developer from file IO operations. Provision for returning domain objects after each record is parsed or in batch of records is provided so as to maximize memory utilisation as per the application need. It supports two models for parsing viz push and pull. Push model parse pre-configured number of records and send to the client as domain object. Pull model waits for client to request to parse the file sequentially in batches. Client receives an handle to lazy fetch which can be iterated through to generate next batch of records.
Bootstrap
This architectural component assist in initializing required services or components in application server before any client request can be serviced. It also helps in improving performance by ensuring globally required services are initialized and available when required rather than loading them at the time of request. In the channel tier, where there is a web container, a bootstrap Servlet is used. In the application server, which is not expected to host a web-container, this component uses the custom API provided by application server. Hence this component is coupled with application server and is currently available for use in IBM Websphere application server for the application tier.
Data Access Service
This architectural mechanism allows access to the persistent store. It is wrapper on Hibernate ORM that provides XML based mapping of objects to relational mapping. It uses IOC (inversion of control) to keep the connection handles encapsulated from a developer and internally uses a reference counting mechanism to finally close database connection. It throws named exceptions to flag application developers of exceptions that can be handled like no data found.
Batch-Shared OLTP
The framework includes a high performing batch framework. The batch framework will provide application developers a platform to assemble business components to be used in a batch mode. The batch framework provides abstract classes for batch application development. The batch framework uses JMS to stream batch jobs. The batch framework does not use custom threads, but rather uses JMS as the threading mechanism to achieve parallelism in a batch job. A batch job can be distributed across not just processes (JVMs) but across servers (or machines). This provides a lot of flexibility in distributing a job. A batch job can therefore be run on the same server as the OLTP or can be run on a different server. It is also possible to introduce new servers for just batch processing, thereby improving the scalability of the batch framework.
The framework provides an abstract batch data class, which can be extended to set the data for the batch process. The developer therefore needs to extend the class for the batch data. Once the data set has been coded for a particular batch process, then the application developer will need to map the batch data set with the input for the process component that needs to be used for the batch process. To actually execute the batch process, the application developer will need to register the batch process using the batch processing administration GUI provided.
PL/SQL Batch Process
The batch framework also provides a PL/SQL version of the batch framework. The PL/SQL version does not share the OLTP process components or the business common services, but provides a simple high performing batch framework in PL/SQL. PL/SQL offers a “near data processing” batch framework. This framework will provide a high batch throughput on a lower system configuration due to the inherent benefits of processing near the data. This framework will need source code duplication and will increase the maintenance effort of the application. Though this will increase the maintenance effort, this framework cannot be written off as it provides a very high batch throughput. For extremely time critical batch processing, this framework may need to be used. The actual usage of the same will depend on the specific requirements for the application.
Framework
Framework implements J2EE-based OLTP, batch, and foundation architecture as technical environment of J2EE development. it provides a development environment where application developers focus on the business process development.The framework components are split into 2 sections, the architectural mechanisms and the integration mechanisms. Architectural Mechanisms are framework infrastructure components. Integration mechanism are components which can be used for integrating systems
1) Channel Tier
1) Channel Tier
This tier provides various protocol services for communication with Presentation. Converts different message formats to internal standard formats, check validity, and supports posting to hosts that provides actual business services. Features of the channel tier are as below:• Handles multiple request protocols • Comprehensive connectivity to a large variety of systems• Uses Asynchronous IO for TCP/IP • Configurable audit logging with pre and post formatted inputs and outputs• Plug-in support for validations• Re-use validations across transactions• Push data to a client via TCP/IP for long running transactions.
2) Biz Tier
Biz tier comprises of Service Orchestrator, Service Provider and Data abstraction components. Message router in channel tier forward the message to Service orchestrator.
a. Service Orchestrator
This sub component deals with invocation of appropriate service provider for the transaction being sent by message router. It comprises of message listener, transaction coordinator, service command, and process orchestrator.Message Listener is implemented as a message driven bean and provides mechanism for receiving transaction from message router in channel tier. Process orchestrator manages the invocation of one or more than one service commands to execute transaction. Services are invoked synchronously. Process orchestrator caches the work flow information from the repository.Service command converts XML message to the DTO java object as required by service provider which executes the transaction. Service command then invokes service provider using the DTO java object. Following figure shows the flow of transaction within Service orchestrator.
b. Service Provider
This component comprises of process component, EIS wrapper, referential component or domain component. Service provider manages the business processes for the transaction. Service provider communicates with the back end systems that provides the business functionality. Data required by host system is provided by service provider by formatting or generating data from the available data with transaction. Data is retrieved from database using referential component. EIS wrapper acts as a proxy for allowing back end services to be invoked by service provider.
c. System Integration Mechanisms
Component in the service provider communicate with multiple host system via system interface. System interface allows for a standard mechanism for clients to connect to host systems. The system interface consists of a basic interface which is used by clients to communicate with different back-end systems. An interface to a specific back-end system can be obtained via a System interface factory. The system interface factory will create an instance of the appropriate back-end system connector and return the interface for the same. The system interface handles this posting of the reversal, which is completely independent of any application developer intervention. In case the reversal transaction so posted fails, then the transaction is marked as pending reversal in a local log. The log is a database table. When a user initiates another transaction, the reversal transaction is attempted again. This auto reversal function assumes that the host system will return a success for a reversal transaction for which the original transaction does not exist. The auto reversal function will not handle any failures for the reversals sent.
3) J2EE Fundamental Facility
Fundamental facility provides sets of architectural services and architectural classes that can be used for building an application or framework.
Friday, 11 January 2008
What level of education is required to understand my blog?
How do they evaluate my blog?I tried to my other blog (written in Korean, but most of contents are open source framework including "Hibernate", "Spring" and other UML and Software architecture artifact) but they evaluate as "high school" (http://blog.naver.com/tooth2)I cannot understand what their criteria is...is it English only?
Thursday, 10 January 2008
PAN technology overview
Sensors can be combined with WPAN(wireless personal area network) technology to access or communicate with Distributed Environment.There are several WPAN technologies available; Bluetooth, UWB(Ultra-wide band), and Zigbee.
Bluetooth is nowadays well-known technology.
UWB technology is one of the wireless transmission technology, it can deliver digital data with lower power, more data using wide-spread spectrum in short range. Zigbee is also alternative , it has low complexity for design, low cost, the price is rather cheaper than Bluetooth low power consumption. However its data rate is low , maximum 250kbps,
RFID + WSN Application
What would be the future application for RFID and wireless sensor network technology?
Since the US government invested 19$ budget in 2004, several projects have been researched by military service and research institute.
WSN will be used in DoD, health Care, transportation, Industrial Automation, Retail Industry, manufacturing, retail/supply chain, environment , disaster prevention and home network as well.
DoD
If mote can be spread out in enemy's area using remote-controlled spy plane, the mote can make communication network and activate the sensors then it can detect vehicle and its route. There are many research project which are sponsored by military, Vanderbuilt college has researched about ‘Shooter Localization’ project for military purpose and Ohio Sate university has researched about ‘Line in the Sand’ project to figure out enemy’s movement based on vibration sensors and UCLA has developed ‘Power Aware Distributed Systems’ based on vibration and actuator sensors in enemy’s area.
Environment
- Using temperature, humidity, heat, location, vibration sensors, application can detect and control environment in real time and prevent and efficient response when the fire or collapse is occurred.
Disaster Prevention
- Application can decide and notify disaster based on sensing data analysis
Health care
- Application can detect and analyze patients health from bio sensors which can collect pulse, temperature and blood pressure of patient. Through this application, doctors can monitor, diagnose and prescribe the patient in distant when emergency occurs.
If temperature sensor and humidity sensors are attached to blood or anti-cancer medicines, this application can provide right temperature and humidity and raise down blood disposal ratio.
Transportation
- Using vibration, actuator, application can detect crash or traffic and control traffic congestion efficiently in real time.
Retail/Supply Chain
If WSN technology is combined with RFID, then RFID/WSN can be applied retail/supply chain management area very efficiently. RFID will be used in Identification/Access &Tracking, . sensor network can collect, analyze, transmit to monitor & control.
These applications will be commercialized soon according to sensor node manufacturing company such as SAIC (Science Application International Co.) , Dust Networks , Sensicast System
Since the US government invested 19$ budget in 2004, several projects have been researched by military service and research institute.
WSN will be used in DoD, health Care, transportation, Industrial Automation, Retail Industry, manufacturing, retail/supply chain, environment , disaster prevention and home network as well.
DoD
If mote can be spread out in enemy's area using remote-controlled spy plane, the mote can make communication network and activate the sensors then it can detect vehicle and its route. There are many research project which are sponsored by military, Vanderbuilt college has researched about ‘Shooter Localization’ project for military purpose and Ohio Sate university has researched about ‘Line in the Sand’ project to figure out enemy’s movement based on vibration sensors and UCLA has developed ‘Power Aware Distributed Systems’ based on vibration and actuator sensors in enemy’s area.
Environment
- Using temperature, humidity, heat, location, vibration sensors, application can detect and control environment in real time and prevent and efficient response when the fire or collapse is occurred.
Disaster Prevention
- Application can decide and notify disaster based on sensing data analysis
Health care
- Application can detect and analyze patients health from bio sensors which can collect pulse, temperature and blood pressure of patient. Through this application, doctors can monitor, diagnose and prescribe the patient in distant when emergency occurs.
If temperature sensor and humidity sensors are attached to blood or anti-cancer medicines, this application can provide right temperature and humidity and raise down blood disposal ratio.
Transportation
- Using vibration, actuator, application can detect crash or traffic and control traffic congestion efficiently in real time.
Retail/Supply Chain
If WSN technology is combined with RFID, then RFID/WSN can be applied retail/supply chain management area very efficiently. RFID will be used in Identification/Access &Tracking, . sensor network can collect, analyze, transmit to monitor & control.
These applications will be commercialized soon according to sensor node manufacturing company such as SAIC (Science Application International Co.) , Dust Networks , Sensicast System
Smart Dust
One of the sensor node technology is Smart Dust, it can be utilized as tiny sensor node. Smart Dust technology was originally developed in the mid 1990’s at university research institutions, the University of California, Berkeley, for defense and intelligence applications. As the research world rallied around the concept of “Smart Dust” ,the first project was conducted by Kris Pister, a Professor at UC Berkeley and founder and CTO of Dust Networks, universities and research institutions worldwide started to take a closer look at the impact of ubiquitous sensing and control. Smart Dust (Silicon Mote) can collect , analyze data and transmit them to 30m range distance by wirelessSmartDust was designed in very small Silicon Mote and integrated with SoC and solar-cell technology in early days.
Intel Mote
One component of the sensor node is low-power CPU, this component has been developed by Intel, ARM, and Motorola. Intel developed motes which use micro processor based on ARM 32bit CPU , as following image shows Intel Mote . It has 64KB RAM, 512 KB memory and 12MHz CPU clock. RF Module is based on 2.4GHz Blue tooth which is developed by Zeevo, and its transmit ration is up to maximum 720kbps.
One component of the sensor node is low-power CPU, this component has been developed by Intel, ARM, and Motorola. Intel developed motes which use micro processor based on ARM 32bit CPU , as following image shows Intel Mote . It has 64KB RAM, 512 KB memory and 12MHz CPU clock. RF Module is based on 2.4GHz Blue tooth which is developed by Zeevo, and its transmit ration is up to maximum 720kbps.
Problems and other approach
However, the sensor node technology has still outstanding issues such as sensor size , battery life cycle, cost for installation and data accuracy. To solve these issues many research and development project is still going on. By the Dust technologies, current sensor mote size is as small as 1cent, however, it can be recognized by eye, so it can easily exposed to enemy or general human beings who may regard it as “dust” and throw it away.
Second, limitation of battery life cycle can be an obstacle for the deployment. To extend battery’s life cycle there are several approaches has been researched and developed. In initial stage, it is proposed instead of battery, that solar cell is used. However, solar cell cannot minimized mote size and not efficient in energy transformation. Since then, instead on solar cell, acoustic noise and kinetic energy by vibration between the motes are replaced.
l Solar cell
l Energy source from human body (Temperature)
l Source from building(heat)
l Kinetic Energy (by Vibration, by Motion
l Acoustic Noise
Nowadays, other approach for better life cycle is researched by communication engineering area, which is to optimize sensor network To minimize battery exchange cost, there are several efficient communication routing protocol is proposed for example, SMedia Access Control by prof. Wei Ye.
Third, sensor mote’s price is not cheap. Recently, MEMS technology has dramatically led to the development of ultra small in size, low-power, low-cost sensor devices. However, cost is shrink down from 50$/mote to 1$/mote. Still, it will cost huge amount of money to apply and create sensor network in real world.
However, the sensor node technology has still outstanding issues such as sensor size , battery life cycle, cost for installation and data accuracy. To solve these issues many research and development project is still going on. By the Dust technologies, current sensor mote size is as small as 1cent, however, it can be recognized by eye, so it can easily exposed to enemy or general human beings who may regard it as “dust” and throw it away.
Second, limitation of battery life cycle can be an obstacle for the deployment. To extend battery’s life cycle there are several approaches has been researched and developed. In initial stage, it is proposed instead of battery, that solar cell is used. However, solar cell cannot minimized mote size and not efficient in energy transformation. Since then, instead on solar cell, acoustic noise and kinetic energy by vibration between the motes are replaced.
l Solar cell
l Energy source from human body (Temperature)
l Source from building(heat)
l Kinetic Energy (by Vibration, by Motion
l Acoustic Noise
Nowadays, other approach for better life cycle is researched by communication engineering area, which is to optimize sensor network To minimize battery exchange cost, there are several efficient communication routing protocol is proposed for example, SMedia Access Control by prof. Wei Ye.
Third, sensor mote’s price is not cheap. Recently, MEMS technology has dramatically led to the development of ultra small in size, low-power, low-cost sensor devices. However, cost is shrink down from 50$/mote to 1$/mote. Still, it will cost huge amount of money to apply and create sensor network in real world.
RFID application use case model + domain model
Problem statement
Domain Model
In this problem context, key concerns are RFID tag , People Registration /Asset Registration and Location Event. The others are duplicated information from HR, e-Records and e-Logistics system which is originally managed patient’s medical information, employee’s detail information and asset’s information. By applying “separation of concerns” concept, key abstraction can shows this domain characteristics concisely, however, with other entity can describe well enough to understand this domain as well. Key abstraction (yellow) will be designed first in design stage and others will be designed later and be consistent with existing environment.
E-records is the master domain of patient’s medical information. HR is the master domain of employee’s information such as department, special occupation, and position. E-Logistics is the master domain of asset’s information such as asset category (disposable supplies, expensive equipment, etc) and earned date , earned price, and etc. These entity should be consistent with original master entity in HR, e-Records, and e-Logistics. To meet consistency, in design stage, these entities should be designed to meet their original domain’s design specification such as database schema, interface specification and etc.
The problem context of requirements analysis for an asset tracking system using RFID technology. The system will track important assets and entities in the hospital (pharmaceuticals, supplies, durable medical equipment, patients, doctors, nurses, etc.) and provide specific user interfaces that are tailored for particular kinds of asset tracking.
1) Supply Tracker (search inventory, display inventory, order supplies, update inventory) - primarily used by an individual playing the role of Purchaser
2) People Tracker (admit patient, register visitor, discharge patient, register staff, query person location, monitor visitors, monitor ward) - primarily used by Nurses, Administrative Staff and Security Personnel
Approach
Through this project approach can be summarized as following :
Through this project approach can be summarized as following :
1) Construct questionnaires for various stakeholders
2) Make a list of use cases (brief format) and initial prioritization
3) Develop fully-dressed use cases for high-priority use cases
4) Describe UML use case model for fully-dressed use cases
5) Describe UML system sequence diagram for each fully-dressed use case
6) Describe UML domain model
Use Case Model
1) Supply Tracker Application
1) Supply Tracker Application
2) People Tracker Application
The business value of the system is driven by several current issues which are of concern :
- Unauthorized visitor access (e.g. risk of drug theft or infant abduction)
- More effective inventory management
- More effective shared use of high-demand capital equipment (e.g. sonogram machines)
- Unauthorized visitor access (e.g. risk of drug theft or infant abduction)
- More effective inventory management
- More effective shared use of high-demand capital equipment (e.g. sonogram machines)
Domain Model
In this problem context, key concerns are RFID tag , People Registration /Asset Registration and Location Event. The others are duplicated information from HR, e-Records and e-Logistics system which is originally managed patient’s medical information, employee’s detail information and asset’s information. By applying “separation of concerns” concept, key abstraction can shows this domain characteristics concisely, however, with other entity can describe well enough to understand this domain as well. Key abstraction (yellow) will be designed first in design stage and others will be designed later and be consistent with existing environment.
E-records is the master domain of patient’s medical information. HR is the master domain of employee’s information such as department, special occupation, and position. E-Logistics is the master domain of asset’s information such as asset category (disposable supplies, expensive equipment, etc) and earned date , earned price, and etc. These entity should be consistent with original master entity in HR, e-Records, and e-Logistics. To meet consistency, in design stage, these entities should be designed to meet their original domain’s design specification such as database schema, interface specification and etc.
RFID application proposal for Hospital
Introduction
Specifically out of scope are systems and the networks architecture on which they run and the management of these systems and operation systems. However it is expected that the cost estimation of recommended solution will need assumption of generic architecture which can be applied to the implementation plan of these systems.
When the client wants to use RFID throughout the hospital for many different purposes, including patient identification, billing, surgical safety, personnel location and, of course, drug tracking. The client understands that it will be able to control some of the RFID systems, such as patient identification, but for others it must remain compatible with RFID tags coming from outside entities, such as drug companies. The client also sees RFID as the beginning of "ubiquitous computing" in the medical field.
The client understands ubiquitous computing to mean that in the future numerous computers and chips will be embedded in the walls of rooms, in surgical instruments, laboratory apparatus, patient blood sample containers, employees badges, patient wristbands - essentially all over the hospital. These devices can interconnect through wireless technology to form a vast network of computers and sensors that will allow automation of many functions now performed manually, such as capture of billing information. It expects that this technology will be able to improve the efficiency and safety of health care delivery.
The question that the client asked which set of technologies should be used, how can it be sure to be compatible with outside products having RFIDs, and what future applications can be developed to
Summary of Result
The purpose of this project is to propose the high level application recommendation for a hospital to be adopted as the RFID technology blueprint for the hospital, cost of recommended application and IT deployment strategy are also part of a sequence of deployment plan following 5-years time frame.
This proposal contains:
This proposal contains:
(1) Review of RFID technologies applicable to the health care industry, including an assessment of RFID devices, readers and support systems applicable to a hospital
(2) Recommendation of the ten best applications of RFID for a hospital using the four criteria
(3) Recommendation of the ten solution deployment strategy for the next five years
(4) Estimation of deployment costs for recommended solution including RFID devices and support systems.
(2) Recommendation of the ten best applications of RFID for a hospital using the four criteria
(3) Recommendation of the ten solution deployment strategy for the next five years
(4) Estimation of deployment costs for recommended solution including RFID devices and support systems.
Specifically out of scope are systems and the networks architecture on which they run and the management of these systems and operation systems. However it is expected that the cost estimation of recommended solution will need assumption of generic architecture which can be applied to the implementation plan of these systems.Problem Statement
The United States Food and Drug Administration (FDA) (http://www.fda.gov/) is requiring drug companies to enhance the safety and security of the U.S. drug supply by 2007 using radio-frequency identification (RFID). As described by the FDA, this is "a state-of-the-art technology that uses electronic tags on product packaging to allow manufacturers and distributors to more precisely keep track of drug products as they move through the supply chain." The client wants to be able to satisfy FDA requirements for drug tracking within its hospitals, which will require it to install RFID readers.
When the client wants to use RFID throughout the hospital for many different purposes, including patient identification, billing, surgical safety, personnel location and, of course, drug tracking. The client understands that it will be able to control some of the RFID systems, such as patient identification, but for others it must remain compatible with RFID tags coming from outside entities, such as drug companies. The client also sees RFID as the beginning of "ubiquitous computing" in the medical field.
The client understands ubiquitous computing to mean that in the future numerous computers and chips will be embedded in the walls of rooms, in surgical instruments, laboratory apparatus, patient blood sample containers, employees badges, patient wristbands - essentially all over the hospital. These devices can interconnect through wireless technology to form a vast network of computers and sensors that will allow automation of many functions now performed manually, such as capture of billing information. It expects that this technology will be able to improve the efficiency and safety of health care delivery.
The question that the client asked which set of technologies should be used, how can it be sure to be compatible with outside products having RFIDs, and what future applications can be developed to
(1) increase profit,
(2) promote safety,
(3) improve the speed and quality of health care delivery; and
(4) comply with FDA regulations regarding RFID in drug packaging.
The client is looking for a far-ranging, creative implementation of RFID-based ubiquitous computing in its hospitals. It will also need to understand the cost of various alternatives.
The client is looking for a far-ranging, creative implementation of RFID-based ubiquitous computing in its hospitals. It will also need to understand the cost of various alternatives.
Summary of Result
To drive Health-care transformation this project would focus on using new technologies and leveraging the electronic health record for more effective patient care, easier communication for hospital staff and better efficiency. Technologies to be employed will include: wireless handheld devices for connection to electronic health records; radio-frequency identification (RFID) tags for tracking personnel, equipment and patients; and monitoring devices in patient rooms to alert nurses of patient status.
The ten applications 
1. Ready to Go, will provide emergency check before ambulance leaving
2. Operation Monitoring will improve patient safety by check and monitoring before/while operation
3. Surgical Instrument/Equipment management system will provide the status of surgical instrument – for e.g. Sterilization/contamination/infection and etc.
4. Patient Tracking will provide patient we will look through in next slides and protect infant stolen by real-time notification as well.
1. Ready to Go, will provide emergency check before ambulance leaving
2. Operation Monitoring will improve patient safety by check and monitoring before/while operation
3. Surgical Instrument/Equipment management system will provide the status of surgical instrument – for e.g. Sterilization/contamination/infection and etc.
4. Patient Tracking will provide patient we will look through in next slides and protect infant stolen by real-time notification as well.
5. Employ Tracking will provide employer's location information and notification to doctors and nurses when they are called.
6. Drug Tracking is the FDA compliance Application and also provide drug inventory as well.
7. Sample/Organ Management will provide Identification and speed up test center’s billing process as well.
8. e-Patient Medical Record will provide right Medication and Speed up diagnosis process as well 9. Home Nursing System will provide 24hours home care service for special patient like diabetic patient etc.
10.Patient Guidance system will protect elderly or blind people getting lost in the hospital and provide navigation information by headset.
6. Drug Tracking is the FDA compliance Application and also provide drug inventory as well.
7. Sample/Organ Management will provide Identification and speed up test center’s billing process as well.
8. e-Patient Medical Record will provide right Medication and Speed up diagnosis process as well 9. Home Nursing System will provide 24hours home care service for special patient like diabetic patient etc.
10.Patient Guidance system will protect elderly or blind people getting lost in the hospital and provide navigation information by headset.
Subscribe to:
Posts (Atom)
Posts
