We design, build,
integrate and manage information systems that help organizations improve
customer service, increase productivity and achieve strategic goals.
TotalSoft is one of the most important Romanian software companies, able to design turn-key applications and information systems suited to specific customer activities.
The studies and analysis performed by us, the solutions proposed, have as a main goal customer's interest, TotalSoft being totally equidistant regarding the potential hardware equipment and software products suppliers.
The Systems Development Life Cycle (SDLC) is a 6-step procedure that is carefully followed in order to ensure an effective system.
The six steps of the SDLC are:
1. Analysis of the Current System
2. Define the new System Requirements
6. Evaluate and Maintain the System
Following this process, TotalSoft makes the Systems Development Process more straight-forward, and raises the chances for success.
1. Analysis of the Current System
Analysis of the current system is performed to determine problems, opportunities and objectives.
The goal of systems analysis is to obtain a clear understanding of the system and its shortcomings and to determine opportunities for improvement. Systems analysts must understand the system, and the users must educate them about the current system.
In order to achieve this fundamental goal, the new integrated informational system is defined on a three-layer model:
- base level - hardware infrastructure, communication systems, operating systems, office automation software, etc;
- operational level - software system providing support for distribution activity;
- managerial level - software system providing support for managerial decisions;
Base level
The solutions proposed at this level will lead to the achievement of an optimal rate between the resources needed at higher levels of the system and the costs implied by system functionality.
Thus, three main factors influencing the above mentioned rate will be defined as:
- global transaction volume performed by the system;- system topology;
- system "real time" (the minimum period at which the information transactioned at subsidiary level is needed at headquarter level)
The result of this analysis will allow proper choose of hardware configuration of servers (network servers, application servers and communication servers), as well as proper choose of operating system and data base engine.
Operational level
The analysis will present offers covering the specific needs of this level as well as those needed at managerial level to consolidate operative data. Factors took into consideration are the organization structure, the real time desired in the system, WAN connection possibilities of working points/subsidiaries, information and indicators to be used at managerial level.
The analysis will promote modern systems, based on adaptive client-server architectures taking into account scalability, adaptability, modularity, total cost of ownership and other criteria. The database engine used by the proposed solutions will have to adapt to the data exchange with the managerial level and to linearly respond to exponential grow of transactional data volume.
The managerial level uses the knowledge base accumulated at operational level through consolidation of databases at each subsidiary level. The study will analyze the possibility of a data-mart implementation for selling and marketing departments. This study will include the physical management database realization in which will be kept a long-term archive of transactions at operational level, will propose the mechanisms and access means to this information, will recommend the requirements imposed to a future administrator of this database, will analyze the requirements imposed by the hardware infrastructure and operating methodologies.
The managerial process is characterized as being of continuous type, the managerial decisions being taken in real time. This characteristic involves that at this level have to be provided information that can fundament decisions with respect to the concrete reality. More concrete, the group management can achieve directly, through an adequate interface to this goal, information regarding for example the status of stocks, sales amount, agents activity, various figures, etc., without asking (and most important without waiting) reports from departments and store places.
Possible improvement goals of a new MIS:
- Speeding up and streamlining processes- Combining processes
- Eliminating redundant input
- Reducing redundant output
- Cutting costs
- Improving security
Some of the methods used to gather information is:
- Conduct interviews and use questionnaires- Review procedures and policies
- Collect sample documents (forms, memos, reports, etc.)
- Observe operations
The system requirements are determined: input, storage and output. These can be hardware and/or software. At this point, the availability of hardware and technology and their costs have to be taken into consideration. Alternatives will be discussed and evaluated.
A business could improve its MIS so that it could handle more time cards per week. In addition, it might want to add some features. All of these would require changes to its MIS.
Some required features could be:
- Automatically update personnel file- Automatically calculate regular and OT hours
- Automatically generate weekly/yearly to date figures
A systems flowchart will be used at this stage, and a report will be produced. Based on the report, the project will either continue or end. The report can also be used as a basis for bids from vendors of equipment and software.
A computer specialist will be brought in, and s/he will design the new system.
The computer specialist has two goals to meet:
1. Design of the new system: Using design tools, as well as systems flowcharts, program flowcharts, etc., the computer specialist will design the new system.2. Controls and Security: Controls and security passwords must be established here.
Another report for acceptance is also created based on the design.
After the system has been designed and approved, it must be developed. This is when the hardware and software is actually acquired.
Certain decisions must be made. Should the software be bought, or written? Who supplies the hardware? Here open bids for tenders may be made.
In addition, users must be trained on the new system. TotalSoft give training seminars. Also, any new procedures or polices must be taught.
Lastly, the system must be tested. Prototyping is used. The system is tested with minimal prototype data to catch bugs and errors. This is a very time consuming, painstaking process and may take several months.
According to the type of organizations, there are different ways to accomplish this.
There are four main implementation methods:
Direct Implementation
The change to the new system is made all at once. This method is used in a small business or in a larger one where a model was previously developed and thoroughly tested.
Parallel Implementation
Both the old and the new systems are up and running at the same time. When the operation of the new system is satisfactory, the old system is shut down.
Phased Implementation
Implementation of a part of the system and when it is running satisfactorily, another part follows. This is used for extremely large and complicated systems.
Pilot Implementation
If a company has many widely dispersed locations, the new system is implemented in one location at a time. Some of the trained staff would then be moved to the new location
6. Evaluate and Maintain the System
After the system has been implemented, and has been running for a few months, an evaluation is made to determine if it is meeting its objectives.
Changes in government regulations often necessitate periodic changes in the processing requirements of the system. In addition, the system is adjusted and enhanced.
For this phase to be effective, users must have a basic understanding of the Systems Life Cycle to communicate their requirements to the systems analysts. Repeated or major changes then necessitate going back to step one
