SDLC

System Development and Life Cycle is the application of analytical processes to the planning, design and implementation of new and improved information systems to meet the business requirements of customer organizations. There are eight steps involved in developing a new computer system from scratch.
Fact finding. A feasibility study. An analysis phase. System design. Testing Implementation. Documentation. Evaluation.
[email protected]

Sir Mazhar

1.Fact Finding
Facts about existing systems can be found out so computers are already used but not to their full extend. It may be that manual system exists which needs computerising. There are following four ways
Asking questions (Interviews with users). Questionnaires (Completed by users). Observation (Watching how the work is done at present). Inspection (Looking at existing paperwork, screen displays, and filing systems).
Sir Mazhar [email protected]

2. Feasibility Study
The aim of a feasibility study is to see if it is possible to devise a system that can be implemented and that will work at a reasonable cost. The study ends when a decision whether or not to proceed with the new system has been made. The results of the study are usually presented as a feasibility report.
Sir Mazhar [email protected]

Feasibility study Include

The feasibility study will normally include:
A description of the tasks the system is required to do. A preliminary design and initial costs for the system. Alternative designs so that the most appropriate can be chosen. Cost/benefit analysis which looks at the benefit and makes sure that they out weigh the cost. The conclusion, which states whether it is worth going ahead with the project and which design has been chosen.
Sir Mazhar [email protected]

Feasibility Report
Is a written report given to the directors It is a summary of feasibility study. Usually the report is written but it can also be given in the form of spoken presentation. It include the following Brief description of the business Details of what part of the business is being looked The objectives of the proposed system. A list of some of the alternative solutions The human, technical and economic factors A plan for the implementation A proposed course of action
Sir Mazhar [email protected]

3. Analysis phase
The feasibility study outlines what is required from the system and in the analysis phase this study is used to design the new system. To perform the analysis, the system analyst will need to look at the system in greater detail than for the feasibility study. When the present system is investigated, the systems analyst will find more weaknesses in it. The analysis phase includes:
The drawing of system flow charts and data flow diagrams. The identification of the proposed systems objectives. Facts about the system that is going to be replaced. An outline of any constraints or limits (e.g. lack of time, money, or staff training). An updated cost/benefit analysis. An outline of any further developments of the system.
[email protected]

Sir Mazhar

4. System Design
If the project director of the company is convinced that a new system will be worth having, work can be started designing the new system. The system design will identify:
What outputs are required. What inputs are required. What data preparation is required (including verification and validation). What codes (e.g. M for Male; for Yes) can be used to reduce data inputting and storage. What file structure and file design should be implemented. How the hardware should be configured. What software should be used.
Sir Mazhar [email protected]

(a) What Output

Since the output from the system determine how the rest of the system operates, these are looked at first . 1. What output is needed? Which includes an invoice which is sent out to customer. a copy of invoice to be sent account office A dispatch note to be sent with the goods A picking list for the storekeeper A screen display to see if a item is stock. 2. What needs to be on these documents and screen? 3. How frequently do these documents need producing? 4. What is the volume of output? 5. How many orders are dealt with each day?
Sir Mazhar [email protected]

(b) What Input

Questions the systems analyst will need to answer are as follows: 1. What does the data comes from? 2. What data needs to be input into the system? 3. How much data needs to be entered and how often it needs entering? 4. Which input device should be chosen?
Sir Mazhar [email protected]

(c ) Data Preparation
Data preparation involves getting the raw data into a form that can be processed by the computer. Verification and validation are included in data preparation. Verification makes sure that there is no keyboard mistake if use. Various validation methods can be used to trap some of the errors ,which is performed by programmer.
Sir Mazhar [email protected]

(d ) Code design
We can use codes to save time typing and also save storage space. Codes need to be carefully designed if there are to be useful.

(e) File design

We need to decide how many files are needed. When designing files we should make sure that we do not duplicate any of the information.
Sir Mazhar [email protected]

(f) What hardware

More than one computer is used , it makes sense to network them. Hardware configuration also includes deciding on the type of computer.

(g) What Software

We could hire someone to write it specially which is very expensive or use a software package. There are many database packages available and each would need to be evaluated. Once the application packages is chosen we then need to look the operating system it requires.
Sir Mazhar [email protected]

5. Testing the system

Once the system has been designed it should be thoroughly tested before being implemented. This testing will include:
Inputting error free data into the system to see if error free outputs can be produced. Inputting data that contains errors into the system to see if the validation procedures will identify the errors. Inputting large quantities of data into the system to test whether or not the system can cope with it. Testing all the regular and occasional processing procedures. Inputting data that contains extreme ranges of information to check that the validation procedures can cope with it.
Sir Mazhar [email protected]

6. Implementing the system

Once the system has been thoroughly tested it can be implemented. Implementation depends upon the size, solutions range from a microcomputer two, to a system that uses a number of networked PCs or even a system Implementation can be done in one of three ways: Direct Implementation Phased Implementation Parallel Implementation
Sir Mazhar [email protected]

Ways of Implementation
Direct implementation: (use of the whole
system starts on a given date suitable for small systems). Phased implementation: (use of each part of the system starts on different dates so that problems can be sorted as they occur suitable for large systems). Parallel running: (both old and new systems operate alongside each other so that if the new system fails data is not lost suitable for systems where there are doubts about the ability of the new system to function flawlessly).
Sir Mazhar [email protected]

7. Documentation
Any new system needs documentation. The two main types of documentation are: I.User documentation or guide :
A user guide or manual is documentation that the user can turn to for learning a new procedure or for dealing the problem. It cover that how to load a software How to perform certain functions, how to save and how to print. Include examples and exercises to help the user understand the system. Since user is non technical, so any technical language should be avoided. Users have the best view of a system and so should be Sir Mazhar [email protected] asked to evaluate any proposed user guide.

II. Technical documentation

Is used to explain a system to a specialist, either a programmer or a system analyst. Since these people understand computer jargon this guide does not need to be simple. This documentation is very important for those who is new to the project. Changes always need to be made to a system at a later date so this documentation will be needed when the system is improved or upgraded.
Sir Mazhar [email protected]

8. System evaluation
Once a new system is up and running it should regularly be reviewed to ensure that it continues to do the job for which it was designed. This can be done in a variety of ways, one of which includes asking the people who use it whether or not it needs improvement. There are always constraints placed on the system and these might include . Time , money and lack of qualified staff involved in the project. Hence the solution has some limitations placed on it.
Sir Mazhar [email protected]