Systems Development Life Cycle (SDLC)
Systems development could be seen as the simple process of writing programs to solve the needs of the user. Unfortunately the user knows what he wants but has no technical expertise while the programmer understands the computer but not the user environment. This communication gap between the customer and the service provider must be handled by middle, the systems analyst. The systems analyst translates user’s needs into detailed specifications for implementation by the programmer. The SDLC normally covers the activities shown in figure below, each with a primary purpose.
1- Preliminary Investigation
The preliminary investigation is carried out to determine the scope and objectives of the new system and to investigate whether there is a feasible solution. At this stage an analyst or small project team is authorized to investigate the real potential of the new application. During this brief study the analyst must investigate the problem and the existing system sufficiently to be able to identify the true extent and purpose of the new application.
2- Systems Analysis
In this stage the analyst investigates the needs of the user and develops a conceptual solution to the problem. The analysis phase should include the following discrete steps: Understand how the existing system operates. Document the current physical system. Define the problem areas. Identify new requirements. Identify possible solutions. The conclusion of the analysis stage is the preparation of the formal user requirement specification (URS) that incorporates a logical model of a system that will meet the user’s requirements. Management is required to review the status of the project and to make its go/no-go decision.
3- Systems Design
The objective of the design stage is to determine exactly how the new system will work, and to communicate this information in a document referred to as the detailed systems specification. There are three main objectives which the designer has to bear in mind while evolving and evaluating a design:
• Performance. How fast the design will be able to do the user’s work given a particular hardware resource.
• Control. The range to which the design is secure against human errors, machine malfunction.
• Changeability. The ease with which the design allows the system to be changed to, for example, meet the user’s needs to have different transaction types processed.
المادة المعروضة اعلاه هي مدخل الى المحاضرة المرفوعة بواسطة استاذ(ة) المادة . وقد تبدو لك غير متكاملة . حيث يضع استاذ المادة في بعض الاحيان فقط الجزء الاول من المحاضرة من اجل الاطلاع على ما ستقوم بتحميله لاحقا . في نظام التعليم الالكتروني نوفر هذه الخدمة لكي نبقيك على اطلاع حول محتوى الملف الذي ستقوم بتحميله .
|