Avoiding Mistakes

1.15   Avoiding Mistakes

Some important points about SDLC are as follows:

1.     User Involvement

Users include any person for whom the system is developed. Users are real judges of the system’s usability. However, they may not express their needs properly. The system may not meet user need without user involvement.

2.     A Problem-Saving Approach

The following steps are required to create an effective system:

·         Identify the problem

·         Place the problem in context

·         Define the solution

·         Examine alternative solutions

·         Choose the best one.

Without this approach, the system may not fully address the underlying shortcomings of the existing system.

3.     Good Project Management Skills

Many projects fail due the following reasons:

·         Unrealistic expectations

·         Overly-optimistic schedules

·         Lack of solid backing from management

·         Inability to make decisions and stick with them

·         Lack of control over the insertion of new but unnecessary features

·         Interference from problem personnel

These problems occur due to poor managements.

4.     Documentation Required

Documentation is the recording of all information related to the project that is stored in a project notebook. It enables everyone to understand all the decisions that have been made. Documentation should not be put off until the end of the project, when important information or key personnel might not be available. The system cannot be supported or modified properly without documentation especially after development personnel have left.

5.     Use Checkpoints

The project must be critically and independently evaluated at the end of each phase to make sure it is on track. An organization should cancel the project or repeat a phase if results are not satisfactory. Some of the worst development disasters occurred when the project team concealed the face that the system could not possibly work.

6.     Design for Growth and Change

The system should be designed so that it should not break down or cause a major redesign if there is a change. Failure to anticipate change and growth could make the entire system useless in short order.

Here are some responsibilities of a system analyst.

Systems analyst is responsible for the selection of hardware and software packages, the design of computes files and training of end users. He is also responsible for recommending improvements to business procedures and designing new payroll check.

System analyst must create project plans. He estimates costs for the work to be accomplished. He also writes memos, reports and documentation to keep people informed of the progress. He must also give presentations and lead meetings.

Some skills required for system analyst.

A system analyst must have the following skills:

Education and Experience: Analyst should have at least a bachelor’s degree in information some experience as a programmer.

Communication Skill: He must have very good communication skill.

Convincing Power & Confidence: He should have convincing power to bring about the change.

Creativity and Analytical Skill: He must be comfortable dealing with complex problems, ambiguity and uncertainty. Creativity and analytical skills are important in these circumstances.

Desire to Learn: Business requirements and computer technology change rapidly in today’s world. The systems analyst must have a strong desire to learn to keep current with these rapid changes.