|
System Archietectural Steps
Computer technology is improving and changing at an astonishing age and now the computers are getting more powerful with each passing year. Despite all their current and future technological capabilities, computers owe their power and usefulness to people for their organizational needs. It is becoming more difficult for the computer professionals to keep up with the business processes and technological developments. Therefore the computer programmers and system analyst bridges the gap between business users and computer programmers.
Information systems belong to the end users who will benefit from these information systems. Generally speaking, these phases should be completed in sequence but these phases can overlap. Most software development lifecycle consist of phases and these are as follows:
System analysis
The software development lifecycle begin with a preliminary investigation of project scope and feasibility. It determines whether or not, a particular resource should be related and committed to other phases of the software lifecycle. During the research and survey phase, the scope of the project are discussed and evaluated including all end users, perceived problems and opportunities, business and technical issues and constraints, perceived overall project goals and possible solutions.
System design
Given by the selection or analysis phase, the approved and feasible solution, the structural design of the system is started. The computer outputs are designed first to evaluate what the end user is going to see that can affect the overall design of the input, files and methods of the proposed project. Next step is the construction of the new system which is the principal activity of structural design and construction of any information system. This phase includes the installation and modification of purchased software packages.
System implementation
In this phase, the new system is implemented and becomes operational. Therefore the system analyst must provide for a smooth transition from the old system to the new system and helps the end users to cope up with the normal start up problems. This phase also involves training and writing of technical documentation of the new information system.
Evaluation Phase
Once the system is implemented and placed into operation, the analyst’s role changes from developmental process to support level. This may include the periodic evaluation of the new system and reviews and he responds to maintenance and improvement requests submitted by the end users. Most errors are software bugs that were not caught and fixed during the developmental process or coding phase. Well maintained technical documentations significantly accelerate the study phase when the system is due for overhaul.
|
|
|
|
MEMBERS COMMENTS
|
|
|
|
|
|
|
