Skip to main content

Common Problems Faced by Business Organization in implementing Internet Based Applications

Business organization which is always expecting and looking for gain profits in to. These organizations inspiring to implement internet based applications to improve their business. Mainly there are two reasons why is that. They are,

·         They can communicate all over the world.
·         No need to install at every client’s computer.

And there is new concept call cloud computing. But in this model also have many disadvantages (Not customizable, do not matching with the requirements, changing small thing also a big cost to the company…). Therefore business organizations like to develop their own systems in-house. Even though there are some common problems too.

·         Mainly cost is the most critical thing of implementing these applications. When you are turning to this point, first of all need to estimate budget. Regarding to that there can be several expenditures. 

o    E.g.:- salary, wages, electricity……..etc. (there can be many direct and indirect costs).
Also to this project you are allocating available and sacred company resources and buying or hiring some extra recourses (it can be human recourses or other) too.

o    Let’s go to the implementation process,

Ø  Implementation method
There are many methods (spiral, waterfall, object oriented…..etc), but adopt community or hybrid developing model typically more expensive as well as it gives many benefits. 

Ø  If you are implementing critical system just like internet payment system (e-banking), then you have to add more security features. It will provide additional expenditure to the budget.

Ø  Not only that to keep the data of customers, payments or any other then require to save somewhere that data. Thus necessary to use database management system. There are many free DBMS but according to the customer base (mostly) most companies purchase some better ones (oracle 10g, 11g). Then another cost to the project.

Ø  Also need to modify and update the backend with the application. It is cost too.

Ø  Testing also a cost. Because need to arrange test environment and testing team to the particular project.

Ø  Then the next step is deployment.
-To deploy the project need dedicated machines, servers, cables sometime space also.

-if you didn’t deploy accurately then there are many problems can appear.
Unfortunately most of the projects end up with many bugs due to many reasons.

·         Technical issues also reason for this purpose,
o    Software bugs.
o    No tech leads to guide.
o    Logical errors.

·         But most of problems are non –technical ,

o    Over budget of the project, then there are no any advantage to the company only wastage of money and recourses.

o    Over time
Some projects take twice as long to complete as planned. It is wastage and cost at every corner. And with the time value of the project also decrease.

o    Deliver less than half of the discussed functionality (this will cause to throw the project to garbage bin).

o    Organization polices,
Mostly for development require confidential information of company (financial details). So senior managers are don’t like to support and provide these information.

o    Developers are not capable to do that and no proper training for them.

o    Poorly selected data.
Week test data
E.g.:- -use correct inputs/data
          -data gather problems.

o    Badly organized data.

o    Incorrect data models.

o    Software has limited capability (using high capable software is a cost).

o    Project managers underestimate time requirements.

o    System can be underutilized.

o    Inexperienced project managers.

o    Incapable project managers.

o    No proper risk analysis,
When doing a project risk assessment and contiguous planning takes more time and money. But if you ignore that then most probably project can be a failure.

o    Personnel problems.
(Developers can get sick, leave the company and their personal matters also can affect)

However solving all technical and non-technical problems end up with the success. Then there are another three problems.

·         Performance
Sometimes project is a success one although the performance in not as expected. With this type of applications it is very difficult to deal and not user friendly (only complete the basic functions without thinking about the speed………..etc.).

·         Maintaining
To maintain the system need capable dedicated people. They should be ready to give support to for any problem by 24/7 basis. This also cost to the company. Therefore most of organizations neglect the system after two three years of deployment.

·         Hackers/crackers
That is big and uncontrollable problem.






Comments

Popular posts from this blog

Accessibility Testing

Accessibility Testing is a non-functional testing type. This means anyone can use a particular web application, mobile application, website, or any other software package. Any human means not only perfect men or women but also differently able people as well. Things can be used for testing, 

Differences between Severity ,Priority and Status

In market there are many bug tracking and project management tools available. These tools allow us to keep essential information of a bug or task. You will see there are three places have to fill when key in a task. Those three places are Status, Priority and Status of a bug/task. Let's see what those stand for.  Severity Priority Status Connotation Severity of a bug means how much it affecting to functionality of the software. Total damage it can do. Priority means how fast a bug or task should be resolve. Status means the current position of the bug/task. Types            Critical            Major            Moderate            Minor           Cosmetic           Low           Medium           High           New           Active/Open           Resolved/Fixed           QA In progress           Reopen           Closed/Completed 

MVC Architecture

Model-View-Controller (MVC) is a design pattern recently most popular among software engineers for applications which are needed to provide multiple views with using same data. I am suggesting MVC is better than WCF, because of this module separation. For an examples       ·          Multiple views and controllers can interface with same model for modification even those never exist before add this model.       ·          It is supporting all type of HTML verbs.       ·          No view state and post back events.       ·          Easy integration with JavaScript framework.       ·          Helps to decrease complexity of project       ·          Provides RAD development ( http://en.wikipedia.org/wiki/Rapid_application_development ).