How to Resolve “Memory Card Error” From Canon IXUS 130

Canon IXUS 130 is a sophisticated digital camera that has a resolution of 14.1 megapixels. The camera is inbuilt with almost all advanced features, including fully wide-angle 4x zoom lens and motion blur technology. The IXUS camera is compatible with SDHC (Secure Digital High Capacity) and SDXC (Secure Digital Extreme Capacity) cards, with storage capacity as high as 2TB.

Since the storage memory of the cards is huge, data loss from these cards is simultaneously huge. One of the main reasons for data loss from cards is corruption of these cards. In most cases, you receive an error message after your card gets corrupted. However, an updated backup allows you to overcome card corruption. It allows you to restore data. But in case of unavailability of backup, you can use recovery software to recover data from a corrupted card.

As a practical case, you view the below error message on Canon IXUS 130 while attempting to view some previously stored photos on your SDHC card:

“Memory Card Error”

Every single photo saved in the memory card becomes inaccessible after the above error message appears. In addition, no more photo can be saved on card. In short, the card can not be read or written upon.

Cause:

The above error message that makes all the photos inaccessible is primarily caused due to corruption of card. Few reasons that are accountable for the above error message are virus infection, interrupted read/write operation, and human errors.

Resolution:

The resolution for the above error message is formatting of memory card in the camera itself. The process deletes all the previously saved data and allows you to save new data. While formatting proves a good resolution for users who do not require the old data, it becomes fatal for users, like photographers, detective agents, etc, who save critical data in their memory card. However, recovering formatted data now-a-days is an easy process. To do so, you need to use an advanced third-party Photo Recovery Software. A Image Recovery tool is readily available on the Internet by just one single click.

Posted in general | Comments Off on How to Resolve “Memory Card Error” From Canon IXUS 130

Double Towel Racks – The Easy Way To Increase Space

Bathrooms almost always pose a storage challenge. They often have minimal space to do all the jobs we need to do in there and to store everything we use while we're in there.

When a bathroom is shared by a couple of people, or even an entire family, unique storage challenges come up, and they require unique solutions. When, say, four people use the same room for bathing, an obvious problem is: where do you put all the towels? Bathroom hardware manufacturers came up with a better solution: double towel racks.

A traditional single towel rack provides sufficient space to dry one towel. If you've got four people using four towels each day, and you have a typical bathroom, you'll need a wall covered with towel rods to provide enough drying space.

Double towel racks provide an innovation solution to this all-too-common bathroom storage problem. You'll find double towel racks come in traditional finishes like polished chrome and polished and antique brass, and popular finishes like brushed nickel and oil-rubbed bronze. You can find economic versions of double towel racks in unfinished wood and ceramic-and-plastic. Regardless of the amount the wall space you have available to install this hardware, you'll find one to fit your space; They come in the range of standard sizes.

If your bathroom is short on storage, you'll usually be open to considering any new space-saving solutions. You can find bathroom suites with a double towel racks installed below. Imagine-in the space where you could normally dry a towel or two, you can double your hanging space, and have room to store a few fresh folded towels and other bathroom essentials, too.

Double towel racks are an excellent solution when you've got lots of damp towels to handle, but other solutions do exist:

• Install a row of pegs or hooks along the wall of the bathroom.
• Install one or more multi-prong hooks on the back of the bathroom door.
• Buy a shower curtain rod with a towel rack incorporated in its design.
• When you purchase shower doors, look for ones where the handles double as towel bars.
• Install suction-cup hooks inside the tub surround.
• Place a swing-arm towel bar to the wall next to your tub or shower. This way, the towel bars extend into the room; They are not limited to hanging against a wall.
• Hang a hook over the bathroom door, linen closet door, or the door of the water closet. These over-door hooks come in single, double, and multiple hook versions in colors and finishes that either stand out or blend in.
• Repurpose an old-style coat rack and use it to hang towels in the bathroom. It takes up only a single square foot of precious floor space.
• If you want to add furniture to your bathroom, look for a hall tree, which is usually reserved for use in the foyer or a mudroom. They come in many styles and finishes, equipped with hooks, mirrors, storage benches, and shelves.
• If you've fortified enough to have a sizable linen closet in your bathroom, visit the closet organization section of your home improvement store. These stores have trained personnel who can help you look at the space you have and redesign it to suit your needs.

Installing a couple of double towel racks can provide a simple way to add storage space to your bathroom. But investigate all the possible storage options for your unique bathroom design challenges. You're not limited to one solution-think creatively and combine them to make a bathroom that works for you.

Posted in general | Comments Off on Double Towel Racks – The Easy Way To Increase Space

Microsoft Access and Medical Private Practice

For physicians medical office software installation could be nerve-wracking, not because they want to avoid electronic medical records, but because the majority of the software packages are too complicated and very expensive for them.

The good news is, you can make your medical office software system uncomplicated and relatively easily maintained with one of the popular database software packages being used today, the Microsoft Access.

Microsoft Access is a relational database system developed by Microsoft. Microsoft Access is one of the easiest and most flexible database management solutions for the medical office and provides data validation and user-friendly features on data entry screens. It has been the dominant lightweight database system used for the last decade and has continued to grow with additional features. Access is a productive and very customizable solution for small medical practices and comes with MS Office (or standalone). However the next step up in a medical environment would be MS SQL Server but small medical offices usually only has need of a lightweight application and the added functionality with MS SQL Server, comes with a heavy price.

With this relational database system you can be up and running in one hour, which means that it is not necessary for your practice to spend lot of money to purchase, configure, update and maintain an SQL Server solution. Microsoft Access includes without any additional costs, points of integration with popular software packages including: Microsoft Word, Excel & Outlook and provides a free runtime version.

MS Access network setup is very easy. A medical office with 2-8 users is up and running within ten minutes, while installation and application maintenance is extremely simple. Virtually any user with a basic knowledge of Microsoft Access can handle all maintenance procedures without the assistance of IT personnel.

Keep also in mind that SQL Server is the flagship database system from Microsoft and it is suitable for use in environments with up to thousands of users. Microsoft Access can handle 2- 8 users and it is limited to 2 GB data storage.

We are convinced that the best way for private medical offices around the world to enter the world of electronic medical records is to purchase a professionally designed but inexpensive and affordable Microsoft Access based software solution.

Posted in general | Comments Off on Microsoft Access and Medical Private Practice

Learn How to Fix “Runtime Error 53 File Not Found” Easily

Computer errors generally plague us a lot. They have to be removed immediately before they can cause any further problems. One such error is the run time error 53. It shows the message “runtime error 53 file not found”.

In this error, problem occurs when a software program that is installed on the PC shows this error because it is trying to reach a DLL file that has been removed from the windows registry. This registry contains all the files that are used by Windows for executing any kind of commands by human users. This DLL file might have never been installed on the computer itself.

To fix runtime error 53 from your system, some simple steps have to be followed. Such steps include clicking on the start menu and then landing at the control panel. After you reached the control panel, open the programs and features icon. Open up all the programs stored in the computer through it. Uninstall the program, which produced the run time error 53 message. A window will also open up telling the user that the program has been removed from the system.

To make sure that the DLL file is stored again on the computer, one has to remove the program and then put it back. The program can be reintroduced into the system through a hard disk or a CD. Instructions will appear on the screen as this program gets installed. After clicking on the install it now option, the user will see the option of terms and conditions on the screen. Click on the “I agree” choice to continue with the installation. The operating systems that generally display this error are Windows XP, Windows Vista and Windows 7.

Run the program to ensure that runtime error 53 is not displayed again. If the error is still being produced, then contact the company, which supplied you with the software.

It is also intelligent on your part if you find out about the compatibility of your software with the operating system of your computer or other software. You can find out about this compatibility through an online research. The website of the software developer can also yield you such details. Tell the software developer about the intricacies of your system to get an adequate response from him about the runtime error 53.

However, the last and most easy solution to fix “runtime error 53 file not found” error is using windows registry cleaner software. Registry cleaner software can always eradicate any registry errors produced by wrong entries, which cause a runtime error 53. It can delete all the useless entries in the registry that are causing such an error. Using such software can ensure that you get an error-free system.

Posted in general | Comments Off on Learn How to Fix “Runtime Error 53 File Not Found” Easily

How to Repair DBF Files by Using DBF Recovery Software

As a computer user you must have heard about a DBF file or some of you have used it. DBF is a database file format used by various database software programs, such as: Visual FoxPro, Clipper, dbFast, CodeBase, MultiBase, dbXL, Arago and similar database programs. A database file is a collection of data organized in a tabular form. A DBF file can be easily opened, edited and saved by any of these database programs therefore, this file format is very popular among computer users.

The most common use of a database file is to store a large amount of data and information. The file is widely used in almost every sector, such as: corporate and educational sectors to store the data and information. It has become an essential file format for an individual and an organization.

Where this file format is very useful for users on the other hand, it may create some serious problems as well. Sometimes a DBF file may become inaccessible or invalid due to corruption. DBF is not immune to corruption; in fact, this file format is prone to corruption due to its large size and complex file structure. It might be easily corrupted due to various reasons, such as: virus attacks, malfunction in database application, hard disk drive failure, software collision, unexpected cancellation of DBF, human errors and many more. These are some common reasons which can play an important role in database file corruption.

While opening a corrupt DBF file you may receive some error messages something like these:

  • “File .dbf does not exist”.
  • “The fields in table did not match the entries in the database”.
  • “Access to table disabled due to previous error”.
  • “Database file appears corrupt: Page is of wrong type.
  • “Corrupt table”/ “index header”.
  • “Filename .dbf has become corrupted”.

These are some common errors which frequently take place at the time of corruption. For example: you are working on your DBF file, everything is fine. But all of a sudden your database application (Visual FoxPro or other) starts hanging. You have no other option other than restarting the system. But when you restart your system and open the same DBF file, in which you were working earlier, it does not open or you get an error message saying the file is corrupted or damaged. This must be very frustrating situation for any user since all the hard work will go into the vain. All the data and information stored in the file might be lost forever. You have to re-create the file, which might not be possible in some cases.

In such critical state a BKF file will definitely help you. If you have backed up the database file (which is now corrupted), then you can easily restore it from the BKF file. But sometimes the BKF file may not be available or corrupted or invalid. In this situation you can use third-party DBF recovery software. This is one of the most efficient and effective solutions to fix corrupt DBF files. The DBF recovery software is designed to repair an extremely corrupted DBF file and to restore maximum data from it. It is highly capable to resolve or fix all the errors from corrupted DBF files. The software supports all popular database applications, such as: dBase III, dBase IV, dBase V, Visual FoxPro, Clipper, dBFast, CodeBase, MultiBase, dBXL and Arago. The best feature of the software is its self-describing user interface. It requires no technical knowledge or skills to use this software. Any tech savvy and a novice user can easily and comfortably use this software to repair corrupted DBF files. The DBF Recovery software is available with free demo version. Users can download the demo version before buying the full software. This helps users to examine the features and performance.

Posted in general | Comments Off on How to Repair DBF Files by Using DBF Recovery Software

Effective Job Numbering And Cost Code Systems

Overview

Many companies have a sequential job numbering system, but have you considered the possibility of altering the numbering sequence so you can pull reports for a certain type of project or projects by year and the informational reports that could be generated?

And, are your cost codes sufficient to cover the details you need to see in your reports? Do you lump all site related travel and subsistence into one code, or do you have the details of hotels vs. Housing and meals vs. Subsistence?

Not all software programs are sophisticated enough to allow for customized job type numbering sequences; However, even the basic job cost software systems can be adapted to allow for an advanced numbering system.

Specific Job Numbering Sequences

Advanced reporting techniques can yield a wealth of information. How jobs are numbered so ease the reporting burden so projects of a certain type and / or year can be easily excluded from the software. Samples of numbering sequences could be based on the following criteria:

· Year project was awarded

· Public vs. Private works

· Commercial vs. Residential

· Construction vs. Service

· Division (s) of the Company

If your software allows, you may start the job number with the year awarded, followed by the job type and then a sequential number. Management may request a report for gross revenue on all the commercial contractor improvement projects in 2013. If you have a numbering sequence, this would be an easy report to pull, rather than go through all your 2013 projects and manually add the numbers to obtain the Results.

The job cost master file is another good source of information if all fields are completed and there is a common usage of custom fields that can be used to pull reports.

Cost Codes – Too few or Too Many?

Often we see cost code lists that spill onto multiple pages. Most job cost software programs allow for use of one cost code for multiple categories (Labor, Materials, Direct Job Expense, etc.).

A good source to use for establishing a cost code list is the bid recap and detail sheets used when bidding projects. This will yield the different stages of labor, types of materials to install associated with that labor, the different types of equipment to be rented, categories of subcontractors and the details of direct job costs to be incurred.

These activities can be "numbered" to establish a list of cost codes. If the software allows for use of one code across multiple categories, give thought to not duplicating descriptions, but arranging codes together by "type" of work being performed, rented equipment, direct job expenses, work typically contracted out, etc.

Keeping your cost codes consistent will then allow even more sophisticated reporting – management can now ask for all commercial contractor improvement projects in 2013 and the total cost of crane rentals for the year on those specific projects.

Why Go Through These Steps?

History is a great source of information when anticipating the future. Cost details can be analyzed for specific types of jobs when preparing to bid a similar project. Historical information can be analyzed for margins on certain types of projects or a division of the company to make decisions on whether or not a certain type of work is profitable.

If fields are available in the job cost master file, reports can be declined not only by type and year but by project manager as well to look at performance and estimate vs. Actual results.

Conclusion

When developing any numbering system, consistency is important in order to maximize the reporting results. Management should determine the information they wish to see and develop job numbers and cost codes that will allow for advanced reporting not only to themselves but provide useful information to estimating, project managers and accounting as well.

Posted in general | Comments Off on Effective Job Numbering And Cost Code Systems

Introduction to Silk Test Architecture

Normal use of an application consists of a person manipulating a keyboard and mouse to initiate application operations. The person is said to be interacting with the GUI (Graphical User Interface). During Silk Test testing, Silk Test interacts with the GUI to submit operations to the application automatically.

Thus Silk Test can simulate the actions of a person who is exercising all the capabilities of an application and verifying the results of each operation. The simulated user (Silk test) is said to be driving the application. The application under test reacts to the simulated user exactly as it would react to a human rest. Silk Test consists of two distinct software components that execute in separate processes:

The Silk Test host software

The 4Test Agent software

Silk Test host software

The Silk Test host software is the program you use to develop, edit, compile, run and debug your 4Test scripts and test plans. This manual refers to the system that runs this program as the host machine or the Silk Test machine.

The Agent

The 4Test Agent is the software process that translates the commands in your 4Test scripts into GUI-specific commands. In order words, it is the Agent that actually drives and monitors the application you are testing. One Agent can run locally on the host machine. In a networked environment, any number of Agents can run on remote machines. This manual refers to the systems that run remote Agents as target machines. This manual refers to the systems that run remote Agents as target machines. In a client/server environment, Silk Test drives the client application by means of an Agent process running on each application’s machine. The application then drives the server just as it always does. Silk Test is also capable of driving the GUI belonging to a server or of directly driving a server database by running scripts that submit SQL statements to the database. These methods o directly manipulating the server application are intended to support testing in which the client application drives the server.

Posted in general | Comments Off on Introduction to Silk Test Architecture

Schedule Slippage – Root Causes

“The single most important task of a project: setting realistic expectations. Unrealistic expectations based on inaccurate estimates are the single largest cause of software failure.”- Futrell, Shafer

Introduction

With global and competitive market, it is very important to launch a product or service in the market on time, ahead of competitors. Definitely, timely launch depends on on-time-completion of the product development projects. Project planning has lots of challenges to overcome in order to finish the project on time – right from schedule predictability, envisioning future/possible risks and coming up with mitigation plans.

This article talks about some of the challenges, often faced in the Software Product Development industry that causes the schedule slippage.

Schedule slippage: Delay in the project completion from its initial estimated date of completion.

Each project plan will have a planned completion date (NRA, RA), and a bounding box or upper limit in schedule. Nowadays, it is a common practice to have three dates associated with any project plan:

  • Non-Risk Adjusted (NRA) date: Project completion date assuming no hurdles – Ideal conditions.
  • Risk Adjusted (RA) date: Project completion date assuming some risks will come on the way and will need extra time to attend to them.
  • Bounding Box (BB) or upper limit: The upper limit on the project plan before which the project has to be finished under any circumstances – Generally decided by the top management based on product/services roadmap and launch in the market.

Under ideal circumstances, any project is scheduled to complete by NRA date. Considering some risks that may come on the way and would eat some time off the schedule, the project should be over by RA date. If the risks were not envisioned and hence not planned well, then project may get delayed and would complete after RA date. Project completion crossing the RA or upper limit is neither good nor expected out of a well-planned project.

Root Causes

As we always plan for a project to get over before RA date, seldom is the case it happens as expected. There are multiples reasons for schedule slippage, right from improper planning, lack of resources to unplanned requirements and rework that eat away vital time off the planned schedule.

A typical project development process – Each project will have a team (development, testing and other functions) that will work through a process (requirement analysis, schedule estimation, design, implementation and testing) to deliver a product to the customer/end user. Each entity that participate in the project – directly or indirectly affect the schedule.

From the development process, we can identify the items that can cause delay in the execution of the project – for example, misinterpreted or unclear requirement adds up to completion time, unavailability of development tools or resources can prolong the project duration. Various processes like schedule estimation, detailed design and product development if not executed skillfully, may significantly blow up the project cycle.

For better understanding all these possible causes that may result in schedule slippage are categorized .

Let’s have a detailed look at the root causes of schedule slippage category wise.

1) Schedule Estimation: “The key is not to prioritize what’s on your schedule, but to schedule your priorities.” – Stephen Covey

For a project to be executed on time, it is very important to have it planned very well. Any mistake in project schedule estimation reflects as delay in the project completion from its deadline. There are several factors that contribute to improper schedule estimation:

· Underestimation of technical complexities: At the start of the project, many of the team members may not have thorough knowledge of technical complexities and hence their estimation would be incorrect. Sometimes it may so happen that the person giving estimates for a particular task is having no idea about the technical challenges involved in carrying out that particular task. You might hear, towards the mid/end of the project life cycle when the task is not finished on time – “Oh, I didn’t know that this feature also requires 5 more tasks to be done!” or “I was thinking this task to be so simple, but I under estimated it!”. · Lack of Design/Big picture: It is important to have a bigger picture / overview of the complete project to understand how a particular module/feature would fit in to complete project. Product or system level design helps in understanding the interfaces among other modules and the required coordination for product assembly and hence, a better insight into the work involved. Often, estimates without focus on detailed design tend to deviate more from the actual time taken for finishing the job. · Integration Testing: While making a project plan, testing also needs to be accommodated in the schedule. At times, the unit testing or testing done by individual contributors on their module is taken into account but not the system level testing. Toward the release, when all the individually tested modules are brought together, a system level or integration testing is a must. Having the time for integration testing not accounted in the overall project schedule will cause delay in the project completion.

· Unplanned dependencies: Project planning is not only about breaking the project into minute tasks and managing them. A well-planned project schedule also needs to consider certain unplanned dependencies. Some of these are:

o People: Optimum utilization of human resources calls for same set of people working in multiple projects. A person may not be available to work for currently planned/assigned project due to extended/unplanned work in another parallel project. Another issue related to people could be unplanned/unexpected attrition that will affect the project plan. Time is also lost in mentoring of new member by a senior (more experienced) person which goes unaccounted if not planned.

o Tools & Equipments: Project can be delayed if team is waiting for release of upgrade or procurement of any vital tool (hardware or software being used in the project) or if the equipments required for development and testing are not available. “We had a 3-months project for validating our existing solution on new product platform using customer DUT (device under test). We had to wait for the DUT for nearly 1.5 months as it got stuck in customs. After getting the DUT, we realized that it’s been damaged partially during transportation. As a result we had to ask for another DUT and whole project took more than 5 months to get finished.” – I am sure that such cases will be quite familiar to many organizations. Other reason for timely unavailability of tools / equipments is that they are shared among various projects to reduce the operating cost. Any unplanned dependency on their usage or wrong assumption about availability of these shared resources would cause delay in the program. Team members might have to work on shifts to optimize the usage of shared resources which can cause reduced work hours and/or productivity loss and results to schedule slippage.

“I was waiting for Matlab license to be released by another person in the team but he left the office without doing so and I lost 3 hours figuring out what to do?” – is it something you faced before?

o Other programs: If multiple programs have deliverable dependencies, then delay in one project will have cascaded effect on other projects, which directly or indirectly depend on its deliverable. “We got delayed because we had to wait for a critical UI component from the framework project team” or “We didn’t plan for bug fixes for a component which was supposed to be delivered defect free for our usage” are the common scenarios for delays in program which are dependent on other program deliverables. Parallel programs may affect the schedule of your program in a different way as well – Sometimes, management changes the priority of the programs running in parallel. If your project is considered as a low priority one then there might be lack of resources assigned to your project that may result in schedule slippage.

· Beta releases: How many times we seek feedback on our product during development? And how often we allocate time for it? It’s important to plan beta releases if we desire to have our product validated by expert users or lighthouse customers during development. Getting feedback from beta customers becomes important especially when their requirements echo that of a mass customer base. Process of giving workable releases to customers, collecting their experience, having their feedback analyzed, and then incorporating in the final product version takes significant time.

· Risk mitigation and plan B: Every project will have some or the other risks. These risks can be of varying severity and probabilities. While making project plan, it is important to treat the risk individually based on their severity and probability of occurrence. If high probable risks with higher severity are not planned with their mitigation plan (or plan B), they will have huge impact on schedule deviation from planned one. As in one of the previous examples quoted, getting a DUT on time for validation was a risk. Had there been a mitigate plan (plan B) like – Validate with other DUT or if DUT is not available here, let one developer travel to customer’s place and finish the validation on time, the schedule slippage would have been avoided.

2) People: Ultimately, projects are executed by people who may not be skilled or talented. Hence, looking for perfection in projects involving human beings may not be a feasible thought. Certain unpredictable and hence unavoidable issues under this category are:

· Poor leadership: Before thinking of project execution, it is project planning that actually would set the platform of success. Execution of the project depends on its team while planning is taken care by the project leader. The project leader is expected to have enough technical know-how to understand the project goals and to the details of the tasks involved. Poor leadership and superficial knowledge of assignments often results in invalid effort estimation and ad hoc task delegation causing stress and possible delay in project execution. People leading the team are also responsible for keeping the team spirit and motivation level upbeat. Poor personal commitment due to lack of motivation results in loss of productivity and may cause schedule to slip. Another reason that adds up to delay in projects is inability of leadership team to track the schedule progress and take the correction action.

· Attrition: If the project duration is large and job market is hot, it may be difficult to retain people in the project till its completion. Attrition may further delay the completion especially if the person leaving the job was in critical path. A person leaving the organization would leave a gap in the project that a new person may not fill immediately, which in turn causes sudden reduction in the task force.

· Learning curve: When ever a new person or team member is included in the project, he or she may require some time to understand the project to keep in pace with other members. Learning curve is needed for new team members, joining the team either due to attrition or due to any specific technical competency requirement. · Context switching: In smaller organization or groups where people work on multiple projects simultaneously, it is important to have some buffer for context switching. A person planned to work in project ‘A’ for two hours after a gap of two weeks, would take more than scheduled time to complete that task. Gap of two weeks and the fact that he or she was involved in other project would require some time for the member to get back to the context of current project. · Global development teams: In an era of globalization and outsourcing, it is common these days to have development team distributed over different geographical regions. Project plan needs to account for different time zones and working culture. You might expect an input for your task on Monday morning your time but it may be Sunday late evening for that person and finally when the input arrives, you might be on your way to home after work.

Sometimes schedule estimation might go completely wrong if you have not understood the work culture of the region your teammate belongs to – “In my previous work, I was given a task to be completed with a heads up that its very critical task and needs immediate attention’. When I asked my project lead how many days/hours I have for it, I had been time for 2 weeks for high priority and ‘immediate-attention’ work.” Definition of ‘urgent’, ‘high priority tasks’ changes with culture and region.

· Communication Issues: People communicate differently. If important issues are not brought to the notice of the team members, or are not escalated on time, the entire project may suffer. Often fear of embarrassment stops team members from reporting issues faced during execution leading to more time being spent on that task that can easily be executed additional help.

3) Customer Involvement: These issues are quite serious if customer or end users of the product are involved in the development phase. Understanding customer’s priorities, defining your expectation from their involvement needs to be clear and in agreement with both the parties.

· Expert user testing: In the beginning of the project, expert user testing cycle needs to be planned. Process of giving builds or releases for testing and collecting their feedback, analyzing and incorporating them in your product takes significant time which, if not planned, can delay your program. · Timely feedback: “I got feedback from customers for features, delivered in development milestone-1, after milestone-5 towards the release. These feedbacks are critical but now I am worried how to incorporate them without affecting the schedule.” It sounds like a common problem. Incorporation of feedback from customers needs to be planned well taking a commitment from the customer. · Product requirement specification review: Having a product requirement review planned and executed will keep you on right track throughout the project. Reviewing the requirement specification will avoid requirement related defects fixing which otherwise would have delayed, the project.

4) Ambiguous Project Requirement: For any project to be initiated, the first thing is to have requirements for it. In the product development life cycle, requirement phase acts like a foundation. Clear requirement or vision for the project navigates the team to success. However, requirements may not be clear at the time of estimation and may result in delay in the project completion. Issues related:

· Evolving specs: If you are making a product based on a standard which is not yet matured or still evolving, you are more prone to have this risk. Frequency changes in the specs will change the requirement for the project during different stages of product development and team will continue to work on something that is not yet evolved. This results in rework that would delay the project if time for dealing with these changes is not accommodated in the schedule. “We developed an algorithm and hence measurement that was based on certain industry standard. Towards the release of the product, the specs changed and our measurement was no more valid. We had to redo the algorithm to reflect the changes in the specs. This caused our product release delayed by 2 months.” · New requirements: Sometimes new requirements are added as the project evolves towards completion. Implementation of new requirements is not planned at the beginning of the project and hence is not accounted in schedule. Adding new feature without revising the schedule may result in delay.

· Untold expectation: Requirements from the customers may be of two types – implicit or explicit. It is important to have the requirements well documented. Implicit requirements needs to be better defined and documented to avoid any confusion towards the end of the project. Customers may not describe their requirements related to system performance, memory issues, user interface quality and usability but they are very keen on providing feedback in those aspects once the product is given for expert user testing. If we are not clear about such requirements, out design might not address them. Addressing them towards the end of the project may call for design changes and extra work that would delay the project.

5) Unplanned Tasks / Reworks: Bounding box for the project is set by higher management and often lack buffer for unplanned task(s). Having more of unplanned task that creep up at different phases of project can cause schedule slippage. The unplanned tasks or rework may arise due to:

· Sustaining work: In smaller organizations, some of the project team may also be responsible for sustaining / customer support of existing products. These unplanned tasks, which come on event basis, related to customer support are always of high priority. Excess or prolonged sustaining work may take resource out of the planned project causing a potential threat for schedule slippage. · Defect fixes: Defects are bad as they degrade the product quality and consume extra time/effort to fix them. It is good to have testing of the intermediate releases of the project to find and fix defects sooner in the development life cycle. If the fixing-cycle for such internal-milestone defects is not planned, then either the project is either going to slip or product is going to be of poorer quality. Poor programming skill of the team, not adapting to modern programming practices and having ad hoc development processes may lead to higher number of defects which would take more time to fix then planned and cause slippage.

· Task spillover from previous milestone: Tasks that are not completed in previous milestone, due to whatever reason (inefficiency, vacation of the team member, resource crunch etc), will have to be completed in the next milestone thereby increasing the load on the team. If adequate buffer is not planned, these tasks spilled from previous milestone over to next, can delay the project. · Requirement change / refinement: Requirement changes during the product development will result in rework of what has been previously done with first version of requirement(s). Addressing changes in the requirements needs extra time and effort and may cause schedule slippage. In some cases, the requirement from customer is misunderstood resulting in wrong system design and implementation. Additional, unplanned time is lost in correcting the design/implementation which causes schedule slippage.

Conclusion

On time delivery is the challenge software development companies are facing globally. To have a complete control over estimated schedule, it is very important to identify the elements in the development cycle that cause schedule slippage. This article uncovers and explains the root causes of delay in programs using examples from real world. Having an insight to the root causes will help the program managers to make good decisions to avoid future schedule slippage.

Posted in general | Comments Off on Schedule Slippage – Root Causes

Computer Engineer Salary

A report by CNNmoney states that students who majored in computer engineering were the top earners of the class of 2011. On top of that according to the Bureau of Labor Statistics, the demand for computer software engineers is expected to grow by nearly 38% by 2016 You may have just stumbled upon your new career!

There are two types of engineers, hardware and software. A hardware engineer deals with physical components. They research, design, and test the physical components of a computer including circuit boards, chips, and keyboards. A software engineer, called developers, create programs for users to perform task. They create the software that translates the commands from applications into instructions that the hardware can understand. They create the operating systems and computer interfaces for desks and consumer electronics.

95% of jobs are located in metropolitan areas. Positions are located in research labs and manufacturing labs. Some work in computer system design firms, research and develop firms, or federal government. Just as there is a range of potential work environments you may end up being in, there are also a large variety of things you may be creating programs for. Computer engineers create on computers, cell phones, navigational systems in your car, video games, and etc. If you're creative, love computers, and do not mind making a lot of money in the process then this just might be for you!

Some of the highest income makers coming directly out of college are graduates in the computer engineering field. This is a great incentive to buckled down and stay focused on those late nights studying in your dorm. This will literally pay off .. BIG TIME! The average salary for computer engineer job postings nationwide are 29% higher than average salaries for all jobs nationwide. Sound good yet? Let's get into the specifics.

The overall computer engineer salary is $ 87,000. To be even more specific let's discuss what you can expect if you enter involved in hardware or software. Starting with the low end of what you can expect. As a software engineer the lowest 10% average $ 45.44 / hr or $ 57,810 annually. The highest 10% average $ 65.28 or $ 135,780. As a hardware engineer the percentages or a slight bit higher. A hardware computer engineer salary on the low end can on average expect $ 48.73 / hr or $ 62,400. The highest 10% of hardware engineers make $ 70.07 / hr or $ 147,610. Not a bad day's work!

Posted in general | Comments Off on Computer Engineer Salary

Strengths and Weaknesses of Waterfall Approach for Software Development

One of the most famous and widely used approaches for software development is the waterfall model. Waterfall approach is an old technique that has been in use for quite some time, but in modern times agile approach is gaining prominence.

Waterfall approach, as is evident from the name, refers to a systematic approach where one step comes after the other. It cannot go the other way round. The process works like the waterfall effect that flows in one direction, which is from up to down.

In this process the life cycle of the development process is predetermined. All the steps are defined before the start of the project. The approach is predictive, where the team is well aware of the order of each step and therefore works accordingly. It starts from the requirement analysis, the design phase and then proceeds on to the implementation, testing and the maintenance phases.

The waterfall approach can be quite beneficial for those who are quite clear on their requirements. A planned approach works for them because they want fixed processes and budget. Where fixed processes are beneficial, at the same time they can be inconvenient at times. In cases where the client is not clear on the requirements and finds in the middle of the project that he/she wants to change course, this approach can prove to be quite problematic.

Another point of the waterfall approach is that the requirement analysis and design of architectural structure can consume a lot of time. Extensive research is done initially as the next phases depend completely on the planning strategy. However, the good thing is that everything is thoroughly worked out and each aspect is studied beforehand. The developers in such cases know what is expected of them.

A waterfall approach works in a systematic order, with one step following the other and the testing phase comes in the end. If there are any big problems encountered in the testing phase, it means a long process to make the amends. The process can consume extra time and money.

We cannot conclude that one approach is better than the other, as every method would have its own strengths and weaknesses. The determination of success for each method depends on how it is being used and whether the approach suits the scope of work being undertaken. While one approach may be suitable for a particular project, it might become totally useless under different circumstances. For example, some believe that agile methods are not well suited for offshore development, as they require a closer contact and communication that is not possible in an offshore project.

Posted in general | Comments Off on Strengths and Weaknesses of Waterfall Approach for Software Development