Projects fail

Software projects fail because of constant emerging requirements and change in scope of the project. Many times modules fail because of the scalability and interoperability issues with the target software. There at times replication problems and system environment problems which in turn is nothing but architecture scalability problem.

It is a combination of System and Software Engineering issue where the original system cannot be interfaced with the new module.

I have a very interesting experience to share: Currently I am working with senior design Team under the Guidance of Prof. Bernstein on a medical hospital based Software system called as RRNL( Research Registry for Neonatal Lupus ).The original software and related confidential information is stored in a Research laboratory and specimens are logged in and identified by the monopolized Software called as Freezerworks.

I am not having any problems in declaring that the research project failed at the current level because consolidation of database (Integrating the original Excel sheets with the newly created Oracle Database was the biggest hindrance to the team).

I would term this is as a flaw in the architecture design and pattern reconfiguration and also a re factoring and reuse difficulty as merging the newly made product with the existing software was a software Environmental and language consolidation barrier.