Print Email Download Reference This Send to Kindle Reddit This
submit to reddit

Most Intelligent Animal Created By God Information Technology Essay

Man is the most intelligent animal created by god on earth. Human brain has capability to turn most of the impossible things into possible. This includes flying in the sky (airplane), walking on moon, breathing under water and many more. There is one thing in the list of impossible things for which man is still working out which is “RISK” because most probably it depends upon luck. The risk cannot be diminished completely but can be reduced to some extent.

The proposed tool will help hospitals to provide quality service to cope up with other hospitals in this competitive world. The risk evaluator will help doctor to take suitable decisions at proper time. The features like Review, Escalate and Move Overide help website to work efficiently and give effective results. This will automatically help hospital to gain goodwill in the society and increase its turnover.

Introduction

The tool provides will estimation of risk for the doctors which would help to touch cases that are allotted to them at right time in order to prevent further consequences of delaying the case of patient which may even result to patient’s death.

The tool will consist of four colors i.e. Green, Yellow, Orange and Red which would signify the risk level of case. It will consist of scorecard for every user which is doctor. Rules Studio which would act as a control panel for the tool. It would consist of certain set of rules or the parameters which would decide the risk level of the case. Case Query which would have doctor and patient id numbers, date of the opening and closing of case. It would also consist of case details and problem discussion forum for doctors.

It would be a web-based system so it would be controlled by a technical administrator which would be an IT person. So id and password would be provided to every doctor. The purpose of making this tool web-based is that all the doctors can access the tool from anywhere and do discussion on case apart from their workplace. The scoreboard color would be changing according to parameters specified in Rule Studio.

Target Reader

Documentation is done in order to explain that what the proposed project or tool is all about. The documentation is like a stick without which any software is worthless to use whether it is from a user or developer side. So the documentation part is necessary for both user and developer for user it will documentation acts as user manual while for developer side it acts as steps on which other programmer can work by reading the document. The tool that I have developing is of medical domain therefore the users which would be dealing with the tool would be the doctors and the hospitals. The tool will certainly help hospitals to cope up with the competition world and increase its profit. As this tool is also a part of academics so the targeted users will be the students or juniors who will refer the documentation and even some of the faculty members including Mr. Ravi Sachdeva( Project Manager), M.s Asma Tuteja (Supervisor) and Mr. Arun Choudhary (Advisor).

Problem Background

Each and everything in this world exists with a possibility of success as well as failure. We can define risk as an edge between success and failure. In today’s era of fast lifestyle people don’t like the services which are provided in quality manner. This is because they can get quality service from anywhere but assurance of getting it in timely manner is real challenge. There is not a single domain in which risk is not involved. Some of the major domains in which little difference in risk may turn into major catastrophe are Law, Engineering, Architecture, share marketing etc. I have selected medical domain for the evaluation of risk as a final year project. This is because in medical domain risk is equal to the life of a person. Even in today’s life most of the doctors are working in multiple places. While working on other places they sometimes get confused due to strain of work. This may lead to negligence towards patient in case if the patient’s case is not touched at proper time. This negligence sometimes further leads to loss of life of an innocent. Sometimes problem may occur due to the chaos or confusion created by the high level management while assigning the patient to the related doctors.

Tangible Benefits:-

The cost in helping the patient in avoiding the risk.

To help doctor to continuously monitor the risk of case handed over to them.

Mail and SMS service keep on alerting doctor about the risk of case.

Algorithm will be used to reduce the complexity of the system.

Web security enables it to have Privacy in information.

Intangible Benefits:-

It will reduce the efforts of the doctors and the patients.

It will help in stress management

Cost saved can be used to upgrade their status in society.

Project Goals

While developing this tool following will be the main goal: -

The proposed tool should be developed on time.

As the project is related to the risk so it will be my prior goal to know what a risk actually means and how it can be handled.

The tool should evaluate risk properly so that the doctors could take proper decisions at appropriate time.

It should sent notifications at proper interval of time.

The risk level should increase automatically when severity level increased.

The escalation process should work effectively i.e. the case should be automatically transferred to the associated senior doctor.

Last but not the least efforts will be made to make the tool user friendly as much as possible.

Project Objectives

Objectives of the proposed tool are as follows: -

To minimize the risk factor in the cases which would be handed over to doctor.

To provide quality service for patient satisfaction and to enhance reputation of hospital.

To track the progress of doctor his professional carrier that how many backlogs (cases) he have or how many days on an average do a doctor need to close the case that he is associated with. This will automatically help an organization to enhance its reputation and good will of the hospital.

To fulfill the requirements of a final year project set by Staffordshire University, UK. Which are required for the Degree of Bachelors in Engineering in Software.

To gain proper knowledge regarding planning of the project so that the developer would work effectively in corporate field.

Review of Modules

Modules are the different parts in which the system is divided. The modules that I would be using for making my tool are as follows:-

Risk Evaluator: - This module is responsible for the evaluation of the risk which is the core part of the module.

Rules Studio: - This module will act as a control panel as all the rules and parameters will be defined which are necessary for the evaluation of risk.

Case Management: - This module will look after all the cases that will come to the hospital.

Review of functionality

One of the factors which is responsible for the success or failure of the project is the functionality of the project. The more the features the better is your project but it doesn’t mean that the system should have irrelevant functionalities that create confusion in users. The tool comprises of following functionalities: -

Accept Ownership: - When cases will be assigned to the doctors then this functionality will enable them to accept an ownership of the case which will ensure that the doctor who is assigned to case is thoroughly responsible for the treatment of the patient of corresponding case.

Case Query: - This functionality will act as notes regarding the existing case so that doctors will be able to refer to those notes and work on the cases which are similar to those.

Escalate and override: - This functionality will help doctor to escalate or forward the case to the immediate senior if he is unable to handle or find it difficult to work on case. Override functionality is the functionality in which doctor sends request to his senior doctor to work on the particular case. When senior doctor login in tool that time he see a request send to him by his junior doctor to work on that case with reason that why he want to work on that case and if he’s working then what are the measures which he has taken to work on that case. If a certain case is not handled properly or the progress of case is not up to the mark then doctor who is working on that case can escalate the case to the senior.

Risk levels: - This functionality will show the status of the risk. It will include green, yellow, orange and red color according to the ascending order of case registry or touch.

Update Case: - It will update the data regarding the case.

Workbench: - This functionality will help user to add note regarding the cases that will come to hospital. It will also give information regarding the severity of the case which would be set from 1 to 3 in which 3 will be the most critical status of patient.

SMS Facility: - This facility will continuously send alert to the doctor via SMS regarding the increasing risk status of patient.

Mail Facility: - This facility will send alerts to the doctor via e-mail regarding the increasing risk status of patient so that he could work or take action on the particular case.

Use of algorithm: - For effective working of the tool I am using certain algorithms.

Web Security: - As the tool is online so in order to prevent it from the hackers I would be providing certain security measures.

Project feasibility study

Feasibility study helps us to know whether the practical implementation of the project is possible or not. It is divided in to three parts:-

Technical Feasibility: - Technical feasibility is the most important feasibility regarding this tool. It will ensure that whether the hardware and software resources that my system need are feasible or not. As my tool is compatible with windows XP and most of the people are using same operating system or other windows application so developer can say that the proposed tool is technically feasible.

Operational Feasibility: - Operational feasibility is regarding whether the tool which developer is developing will operate properly or not. Developer need to purchase a space on web as my tool is online. The tool requires hardware as a server which will serve the clients in which ASP.NET should be installed. On the client side client should have a system which should be connected to the internet with a web browser in order to run the tool.

Schedule Feasibility: - Schedule feasibility is related to the time taken by the project to complete. It will tell me whether developer will deliver the system on time or not. For this purpose developer has prepared a Development phase and other scheduling tool in order to track whether developer is working according to schedule. Developer is using scheduling tools like Gantt Chart, Work Breakdown Structure and Development plan which will take care that project is working according to time.

Target users

The proposed tool belongs to the medical domain. It is specially designed for the doctors and hospitals. It would be best suited for medical colleges as the students would be able to learn effectively how and when to handle the cases at critical times.

The software would aide doctors and hospital to serve their patient in quality manner that too effectively at appropriate time. It would automatically increase the reputation of college or hospital. The discussion forum will help doctors to share their knowledge and experience. There would be very less probability of embezzlement regarding the cases further leading in an increase in profits of hospital.

Challenges involved in the project

The challenges that are involved in developing the tool are as follows: -

to make this tool intelligent enough to evaluate proper risk at proper time.

As it would be a web-based system so it would be challenging to give a proper security for the system. So that, no person other than organization would try to fetch data or commit any kind of cyber crime.

In escalation module, escalating the case to immediate senior automatically is again a part of challenge task.

Effective usage of algorithm is also of the major challenge in the project.

Making system intelligent with effective evaluation of the risk adds more challenge in the project. Sending alerts by email and SMS to the doctors at proper interval of time when the level of risk level will increase is also one of the major challenges in project.

Making tool user friendly will be the most challenging part of the project. As, ultimately it will be the doctors who are main users of tool and have less technical information regarding IT field.

Getting the concepts of ASP.NET and SQL 2000 to work to make tool successful.

Project Scope

Project scope is related to the limitations of the project. It tells us the boundary of the project. The limitation of my project is that as it is an online tool so some time it may take time to load data. My tool needs a proper entry of data for correct evaluation of the risk. The features that I have used as core functionality are Accept Ownership, Case Query, Escalate and override, Risk levels, Update Case, Workbench. Other than this the other features like sending alerts to doctor by E-mail and SMS. Use of the algorithms and web security all these are the scope of my project that is I have made a boundary for my project.

Literature review

The preliminary research done by the developer helped developer to know what are the requirements of the proposed tool. Developer found it important to conduct domain and technical research before conducting research on design of the system.

Secondary Research

After doing primary research developer is on stage where he can judge that what is required from the tool or its expectations. The details which he has gained from research have made a structure of functionalities that should be there in the proposed tool. What developer should do next is to analyze the technologies that he should use to develop the proposed tool successful according to the requirements of the user. Regarding this, a rigorous research is to be conducted such as technical research, research on design patterns, various programming platforms etc. In order to make strong basic structure of the tool and proper development of the tool it is necessary to finalize a software development methodology.

Methodology selection research

Methodology is the key for the accomplishment of the project because it is the way through which a project is carried out. Selection of wrong methodology may lead developer towards failure of project. The main aim of the methodology in this project is to develop tool that meet various aspects such as specific scope, time, resources, goals, quality and the needs and expectations of the target users.

According to the research conducted by the developer regarding the use of methodology he came across to fact that some methodologies have both good as well as bad aspects. In order to confirm which software development methodology to be used developer did some comparison and evaluation of some methodologies. These methodologies were Waterfall, Spiral and Rational Unified Process (RUP). When developer conducted further research on waterfall model he found that it lacks iteration property in which a developer can roll back can make changes if needed. Due, to this developer stopped further research on waterfall model as it was vain full.

(Chatterjee, S., 2003)

Then developer conducted research on two system development methodologies which are

Spiral Model

Rational Unified Process(RUP)

Spiral Model

Some of the properties of spiral model are as follows:-

It breaks system into different functionality stages with various kinds of risks.

It has many similarities in development phase with waterfall model; the order of execution makes a difference.

It emphases on evolutionary process which is based upon risk assessment of each element.

It helps to handle high risk elements at early stages of project so that all major risks are identified as well as solved instantaneously. “Each cycle involves a progression through the same sequence of steps, for each portion of the product and for each of its levels of elaboration, from an overall concept-of operation document down to the coding of each individual program.” (Boehm, 1986)

Image20

(Source: http://home.austin.rr.com/wshort/cs370/semester_project.htm)

Need of Spiral Model: -

It provides systematic method in development of software product.

It offers balanced mixture of existing approaches to a problem, including prototyping, specifying and development even at stages of evolvement which is revolutionary.

As important issues are identified at early stages of the model so, estimations like scheduling and budget get more practical as project flows ahead.

If a developer can start working on project directly if he gets frustrated from a prolonged design process which can encourage him further towards success of a project due to his excitement.

In this model main emphasis is given on the risk that would be faced during development of the project.

Problems in implementing Spiral Model: -

The project developed by developer is not that high skilled whereas to use this model a highly skilled and quiet experienced person is needed in order to do proper risk analysis, planning, scheduling etc.

Due to various stages of evolvement, process needs to be iterated more than one time so, it is quiet expensive in terms of time.

As model supports increment, so features of product cannot be developed all together. This makes it difficult for the developers to make final documentation as he has to change it again and again due to incremental.

Rational Unified Process (RUP)

Some of the features of RUP model are as follows: -

It offers well disciplined mechanism towards managing and assigning tasks and responsibilities in organization.

It consists of business modeling and deployment with an appropriate project skeleton that illustrates processes that are incremental and iterative.

It ensures that a high quality software product is developed which meets requirements of the user that too on time and relevant budget.

It is a flexible type of model which can be implemented on various types of projects with reference to size, complexity and duration.

It helps to motivate developer by showing some outputs at early stages of project.

As RUP encourages iterative approach so it helps to reduce the risk of poor quality of project at early stages of development of the project.

This model gives an approach that clears an idea to targeted organization that what they will get after applying developing efforts.

RUP has better ability to apply changes and also help to track changes that are required on an environment as compared to other methodologies.

RUP also eradicate risk in early stages of development making it a successful project that meets all requirements and needs of client.

Structural representation of RUP Model

The figure drawn below shows how RUP model works: -

4763_fig2

Source:http://www.128.ibm.com/developerworks/rational/library/content/RationalEdge/may04/4763_fig2.jpg

In above figure vertical axis represents logically grouped disciplines, presenting static aspects of process whereas horizontal axis represents time, showing lifecycle aspects of the process.

Phases of RUP Model

RUP comprises of four phases which are Inception phase, Elaboration phase, Construction Phase and Transition Phase.

Inception Phase: -

Research Methods

Research is of the major factor which is responsible for the success. Research can be conducted through various ways from which the data gathering technique is most popular for effective user interaction projects. It gives us an idea which things we need to add to our system to make it better from the existing system. The research phase of this module consists of two phase’s primary and secondary research. For the primary research purpose the data gathering technique that I have selected are Interview, questionnaires and Naturalistic Observation.

Here are the series of interview questions that I have used for research purpose

If not which factor do you think is creating a hindrance in it?

………………………………………………………………………………………………………………………………………………………………………………………………………………

What problems are you facing while managing your hospital?

………………………………………………………………………………………………………………………………………………………………………………………………

How you track the performance of the doctors in hospital?

………………………………………………………………………………………………………………………………………………………………………………………………

Which are the other Features according to you must be added to this project?

………………………………………………………………………………………………………………………………………………………………………………………………………………

Which are the major risk factors according to you are need to be taken care of in your profession?

………………………………………………………………………………………………………………………………………………………………………………………………………………

………………………………………………………………………………………………………………………………………………………………………………………………………………

What are the problems you are facing on those factors?

………………………………………………………………………………………………………………………………………………………………………………………………………………

What are the measures you used to take in order to solve those factors?

………………………………………………………………………………………………………………………………………………………………………………………………………

According to you how much should be the cost of Risk Assessment Tool?

………………………………………………………………………………………………………

Conclusion and Analysis

The series of questionnaires that I have used are as follows:-

Do you think that the work flow of your hospital is carrying on in systematic way?

 Yes  No  Can’t say

(This question will ensure me whether the work flow of hospital is carried on efficiently or not)

Do you think that all the patients in your hospitals are taken care in or served in an effective manner?

 Yes  No  Can’t say

(This will ensure whether the patients are properly handled in hospital)

Do you think that each case in your hospital is attended at appropriate time?

 Yes  No  Can’t say

(This question will ensure whether all the patients are enrolled properly by hospital or not)

Do you think that you can manage all the records of your hospital efficiently manually?

 Yes  No  Can’t say

(This question will ensure that how many doctors need computerization for their work)

Do you have multiple branches of your hospital?

 Yes  No  Can’t say

(If yes) are you able to manage your branches in an efficient manner?

 Yes  No  Can’t say

(This will make sure that whether the doctors are able to handle or communicate distant cases properly while working in other branches or hospitals)

Do you think that your doctors are efficient enough to make proper decisions at critical situations?

 Yes  No  Can’t say

(This question will ensure whether the doctors are aware of risk factor regarding patients)

Do you think that your patients are satisfied with your service?

 Yes  No  Can’t say

(This will ensure whether they need a progress in management which my tool can ensure)

Are you satisfied with the reputation of your hospital?

 Yes  No  Can’t say

(To check the feasibility of project)

If not which factor do you think is creating a hindrance in it?

Time factor ……………………………………………………………………………………………………

(It will give me an idea of the factors which doctors are cautious about in their professional carrier)

Which are the other Features according to you must be added to this project?

………………………………………………………………………………………………………………………………………………………………………………………………………………

(This will give me an idea which feature should I add to the next version or same version of the project)

Which are the major risk factors according to you are need to be taken care of in your profession?

………………………………………………………………………………………………………………………………………………………………………………………………………………

………………………………………………………………………………………………………………………………………………………………………………………………………………

(This question will make me aware of the risk factors of medical field)

What are the problems you are facing on those factors?

………………………………………………………………………………………………………………………………………………………………………………………………………………

(This question will make me aware of what problems they are facing due to their risk factors)

What are the measures you used to take in order to solve those factors?

………………………………………………………………………………………………………………………………………………………………………………………………………………

(This will make me aware of what measures the doctors are taking in order to overtake the these factors)

Are you facing problem sometimes regarding management of the patients?

 Yes  No  Can’t say

Are you aware of any of the risk assessment tool?

 Yes  No  Can’t say

(It will give me an idea about the existing risk management tools in market)

How much importance do you give to risk in your profession?

 Very Much  Quite a bit  Very less

(This will give me an idea about how much serious doctors are concerned about the risk factor)

Do you think that your hospital is good enough in terms of risk management? (If not)

 Yes  No  Can’t say

(This will give me a rate that how hospitals are efficient to handle the risk that they face in their professional carrier for better reputation of hospital)

Do you agree that your hospital needs a risk assessment tool for better risk analysis?

 Yes  No  Can’t say

(It will give me an idea about the requirement of my tool)

According to you how much should be the cost of Risk Assessment Tool?

………………………………………………………………………………………………………

(This will give me an idea about the price of my tool)

Conclusion and Analysis of questionnaires

Thus, from the above survey of the questionnaires it can be concluded that the tool which I am developing as my Final Year Project for the medical purpose of the doctor it is worth and fruitful. It will both socially and as well as economically enhance the goodwill of an organization. After doing this questionnaire survey I am pretty sure and confident that the features that I am including in my tool will definitely help doctors to evaluate risk in their profession.

Naturalistic Observation

Naturalistic observation is a kind of data gathering technique in which a person or user directly goes to the field or place of the related domain of which he has to gather data where he notes and watch how the people are working practically in their offices. Likewise I visited some hospitals and after visiting various hospitals it was concluded that the time taken by them to complete the case of one patient is more. Even although the doctors are socially concerned about the patient but still the high level management is more concerned with the money and the time. The study has also proved that the hospital is not able to manage an individual backlog or performance of the doctors that are working in the hospital. The doctors are sometimes unable to manage the patients that are on high priority which are VIP patients. Even in some of the cases it is observed that the doctors are not aware of risk factors.

Analysis of Research

After going through a complete research it can be analyzed that the time I have utilized for making a risk assessment tool will be of great use. I realized the need of my tool after conducting data gathering technique. It can be verified by having a look on the graphs that i have given in questionnaire analysis.

Hardware and Software Requirement

Hardware and Software requirement for developing a system:-

Operating System : - Windows 98 and above editions

Random Access Memory (RAM):- 512 MB and above

Processor :- Pentium3 and above

Hard Disk :- 6GB

Desktop Monitor :- Any desktop monitor(Color or Black and White)

Network Interface Card(NIC) :- 10mbps- 100mbps for internet connectivity

Hardware and Software requirements for Running the project:-

Operating System :- Windows 98 and above editions

Web Browser : - Any web browser for surfing

Web Server : - Internet Information Services (IIS) with .NET Framework installed.

Software Development Tools : - Microsoft Visual Studio .NET 2003 or Microsoft Visual Studio .NET 2005

Database Management System : - Microsoft SQL Server 2000

Software Modeling Tools : -Visual Paradigm and Microsoft Visio.

Project Management Tools : - Microsoft Project

System Documentation and Presentation Tools: - Microsoft Office XP

Risk Identification

The project plan and the project scope statement are evaluated to identify the project risks with the help of risk item check list. The possible potential threats to our project are stated below:

Natural Threats: All the enlisted threats will cause loss in terms of resource and finance that will eventually lead to project failure

Internal fire: Fire can cause destructions to irreparable limits that will have the same impact.

Technical Threats

Power failure/fluctuation: I am developing this project in Panipat where there is a big problem of electricity. No power will lead to delay in work. Fluctuations might cause system damage that will lead to data loss and an abrupt project delay or even a failure.

Communications failure: If the message is not passed on correctly between the supervisor and supervisee then there might be a serious problem. I might have a misconception about a particular matter and finally what I will work would be wrong.

Loss of data storage device: It might be possible that the data stored might get lost due to theft/damage of computers or any other data storage device like CD-ROMS, USB Drives, Floppy diskettes etc. This might cause incorrigible damage in terms of important data being lost which in turn will lead to project delay or failure.

Human Threats:

Personnel Shortfalls: it may be possible that I will fall ill during the project duration. So, this may cause in project delay or if the resources will be overloaded than it might be possible that quality product will not be produced.

Unrealistic Schedules and Budgets: The FYP runs in parallel with the other academic works so we have to plan and allocate enough time to the FYP. It might be possible that due to some unforeseen reasons, we become overburdened at the peak time (placements works etc) and might not do justice to the project. The time line estimating that I will do is based on heuristics and might lack professionalism. This again will lead to project delays.

Testing

After dedicating efforts towards a system the developer has successfully completed an implementation part of the Risk Assessment Tool. The only way to ensure the quality of system is to do effective testing. Testing is the most important part of the project because it gives you the result of project for which you have been working hard and dedicates all your efforts. This phase of the project gives the second for the developers to debug the error and make it more enhanced if required.

In order to accomplish this, tests are performed on every module for supporting system development by the developer. It gives a confirmation whether an implemented system meets an expectation and the required results are achieved. It helps a developer to debug errors if any. It also assists developer to assure whether system meets user requirement. The most important thing in testing is to include user while testing it assures usability and user acceptance towards system.

The developer has used various types of testing which are as follows:-

Unit testing: - The main purpose of unit testing is to check whether the source code of a particular module is working efficiently and effectively or not. As the modules are big it makes a bit tedious job to conduct unit testing. According to the stage of testing diagram, unit testing is conducted at developing period.

Integration testing: - The main purpose of integration testing is to verify whether two or more modules interact properly to each other and produce proper results. This type of testing, test cases is developed by the tester in order to exercise an interface among the modules. Integration testing is nothing but an assumptions made by the developer regarding system.

(Jalote, 2005, p 506)

Unit testing: - Unit testing refers to the testing of a system as a whole. It means that all the modules and applications of the system are integrated and then testing is performed on it. It ensures that the system which you have made for the user is ready to use effectively and efficiently. In this testing the results of the analysis phase are confirmed. It gives an information regarding flaws that occur when whole system is assembled. Developer derived test cases for System testing from the architecture/design of the system, from input of the end user and by user stories. (Jalote, 2005, p 19-21)

White Box testing: - White box testing cannot be considered as testing, it’s a strategy which is used for testing. White box testing permits user to communicate with the system and access the testing results. This strategy gives an idea to the user that what system is going to do. But, not able to judge how system perform tasks.

Designing

Designing is the phase in which a user makes user who are its users and the how it can be used. In this phase diagrams are drawn which are signifying the system. The main objective of design is to create effective designs.

Use Case Diagram

High Level Diagram

Create Case

Manage Case

Manage Rules Studio

Note Entry

Search Case

Work Break down Structure

Project Initiation Date

27th July 2009

Project Duration

33 weeks

Project Completion Date

18th March 2010

Phase-I

Project Definition(Duration: around 1 week)

Idea Generation

Project Title Selection

Abstract Draft Project Proposal

Project Planning(Duration: around 2 weeks)

Work Breakdown Structure

Schedule and Time Estimation

Gantt Chart

Project Proposal Form

Phase-II

Requirement Analysis(Duration: around 12 weeks)

Identify project specifications

Project Background

Resources required

Techniques to be learnt

Goals and Objectives

Determine System Functionalities

Identify scope of research

Project Specification Form

Investigation and Research

3D software

Action Scripting

Human Computer Interaction

Multimedia Design Principles

Current multimedia applications

User requirements

Analysis

User Modeling and Profiling

Domain analysis

System analysis

Risk analysis

System Design(Duration: around 3 weeks)

Navigational Design

Story Boarding

Data flow Diagram

Abstract Interface Design

Screen layout

Content Design

Interactivity Design

Functionality Design

Development(Duration: around 8 weeks)

Code generation

Midpoint Interview

Media processing

3D Character Modeling

Module Integration

Implementation(Duration: around 1 weeks)

3D Character Implementation

Installation of system

Observation

Testing and Evaluation(Duration: around 4weeks)

Test Plans

Black box testing

Integration Testing

System Testing

Critical Evaluation

Phase III

Project Ending(Duration: around 2 weeks)

Finalizing final documentation

Submission of the finished product

Presentation

Development Plan

Task

Duration

Start Date

End Date

Project Definition

5 days

Mon 8/11/09

Fri 8/15/09

Project Planning

9 days

Mon 8/18/09

Thu 8/28/09

Requirement Analysis

23 days

Mon 9/1/09

Fri 10/17/09

System Design

20 days

Mon 10/20/09

Fri 11/14/09

Development

31 days

Mon 11/17/09

Mon 12/29/09

Implementation

41 days

Fri 1/2/10

Fri 2/27/10

Testing and Evaluation

23 days

Mon 2/2/10

Fri 3/25/10

Project Ending

16 days

Wed 3/10/10

Tue 3/18/10

Degree of Success

According to the developer this part is the most important part of the project as it evaluates how Risk Assessment Tool (RAT) is different from other projects.

Every developer should accept the fact that none of the system is flawless or unique and every system has degree of enhancement in order to make different version. As Risk Assessment Tool (RAT) is an individual academic project, there are numerous ways to make tool better. Developer should focus on fact that how much successful he has been in developing project and whether it meets all the requirements of the user.

In order to evaluate the success of the tool, developer has chosen the following criteria regarding evaluation: -

Achieving user requirements and Objectives of Tool: - A tool is successful when it meets user requirements and achieves objectives of both client as well as user.

Easy to use: - Elements like presentation, user acceptance, recoverability and recoverability will be evaluated in this criterion.

Efficient Project Management: - Capability to manage tool in efficient manner and professional way.

Working of Functionalities: - All the functionalities i.e. core enhanced and special will be evaluated.

Analysis and Research: - It is important to carry out research of the project in proper direction and also do appropriate analysis work to make your tool successful.

Documentation: - Documentation should be done effectively. Documentation should be done in such a way that it should speak your system. As ultimately every user is going to read documentation before using tool.

3-8.1.1 Achieving user requirements and Objectives of Tool

Sr. No.

Criteria of Evaluation

Accomplished

1.

Learning and application of several practices and principles of Software engineering while developing tool.

2.

Gaining knowledge of advance features of Visual Studio 2005 and .NET for completing tool.

3.

Implementing three tier architecture and suitable design pattern.

4.

Complete Allocation of tools and requirements to meet user/client requirements.

5.

Introducing a perfect risk assessment tool which helps to minimize risk of patients.

6.

Developing tool which utilizes memory efficiently

7.

Proper escalations at appropriate time.

3-8.1.2 Easy to use

Sr. No.

Criteria of Evaluation

Accomplished

1.

Admin can add user and allow user to login.

2.

User can modify /update password

3.

Doctor can escalate case

4.

Patient can view case

5.

Update severity of case

6.

Doctor Move Overide

7.

Proper escalations at appropriate time.

8.

User can perform multiple tasks at one page.

9.

Doctor gets notification through SMS / E-mail

3-8.1.3 Efficient Project Management

PMBOK methodology was used by the developer to plan this tool. At the commencing of tool the resources as well as time both were equally balanced properly. Therefore, project was on track when it reached mid-point where analysis of tool begins.

Time taken in understanding the process of move override and auto escalation is one of the main drawback. It took many days in trying to understand these feature this automatically delayed other tasks regarding time.

Later in stage of integration testing, many problems were encountered and it took a quiet long time to resolve the problems. Therefore, in order to cope up with schedule developer completed many tasks in hurry. Despite making project in hurry desired output of tool was not affected and implementation chapter was completed flawless.

Time management was the part which could have been done in proper way. As the domain in which developer was working was new to him and was quiet inexperienced in project added delay problems in project. Except these problems whole project was carried out according to Gantt chart.

3-8.1.4 Working of Functionalities

Sr. No.

Functionality

Accomplished

1.

Accept Ownership (core)

2.

Case Query (Core)

3.

Escalate and override (Core)

4.

Risk levels (Core)

5.

Update Case (Core)

6.

Workbench (Core)

7.

SMS Facility (Special)

8.

E-mail Facility (Special)

9.

Web Security (Enhanced)

10.

Use of algorithm (Enhaced)

3- 8.1.5 Analysis and Research

Sr. No.

Criteria

Accomplished

1.

Questionnaires

2.

Questionnaires analysis

3.

Naturalistic observation

4.

Research on development tools

5.

Research on methodology

6.

Research on Programming Language

7.

Risk analysis

3- 8.1.6 Documentation

For better and easy reading bullets format is introduced and important data is shown in tables.

Spell check is done to correct grammar and spelling mistakes.

Staffordshire University format is used to document the documentation.

The documentation is done chapter wise to help reader to understand easily. Harvard referencing is used for referencing.

3- 8.1.7 Critical Evaluation

Overall all the major objectives have been fulfilled; all the modules and features are working properly with few bugs left to be rectified. As a whole, the system can be deployed onto the client’s machine. The following graph shows the heuristic evaluation (evaluation done by the developers themselves) for this project. It is a measure of work expected (PSF) against work completed.

Print Email Download Reference This Send to Kindle Reddit This

Share This Essay

To share this essay on Reddit, Facebook, Twitter, or Google+ just click on the buttons below:

Request Removal

If you are the original writer of this essay and no longer wish to have the essay published on the UK Essays website then please click on the link below to request removal:

Request the removal of this essay.


More from UK Essays