MAT Solutions : Records Management System

Economic Feasibility

The RMA is being developed at a minimal cost mainly because of the nature of the project. At the initial stage of proposal to MIC, it was stated that no exchange of monies would be given for the development of the program and that all resources needed in terms of software and licenses to develop the program would be made available to us. The members of MAT solutions made this decision based on gaining experience and knowledge of building a system for a big company as MIC. In both instances it is economically feasible because MIC would be receiving a high tech solution without tapping into their financial resources whiles MAT Solution members although operating without profit, would definitely profit financially in the long run.

Technical Feasibility

The technical requirements for the functionality of the system are (1) Operating environment of XP professional, (2) Microsoft office suite 2003 and Structured Querying Language, these requirements are feasible for MIC because these are the current environment present. The need for new technology or upgrading of the existing technology is not needed for the system to be operable.

Organizational Feasibility

It is known that each company has its own culture and that adding a new system and automating the existing processes is one of the hardest tasks that actually may cause failure to an information system project, currently MIC has a high level of computer competency, but some of the problems that may occur are the reversal of long standing work procedures, a high level of computer phobia amongst the current staff members and high levels of reluctance towards change. In keeping with the company’s strategic plans staff members are being encouraged to embrace change, the company has even gone as far as running short computer literacy courses in order to familiarize the users with the computer and build their confidence with the use of any computerized system that may be installed. In terms of feasibility we believe that this era is the ideal time to introduce a new system.

Schedule Feasibility

The Schedule for the completion of the system is the month of April. With proper project planning and with the use of the iteration approach to system development life cycle the group plans on having the system fully functioning before the proposed completion date. However, days are preset in order to accommodate any problems that may occur during the project life cycle.

 The system should be initially installed on one user’s machine within each relevant department where data entry would be made and actual reports would be generated to ensure that the database can support the user requirements and to ensure that the server end is stable.

Once the database has been thoroughly tested to support the data, and is able to generate all required reports and can support networking between the various departments, user training can then begin.

Data entry users must be trained to operate within the database system to do basic tasks such as entry, query, delete and update.  Users may be reluctant toward the change from the old system to the new system so training must show the positive aspects of the new system so as to encourage them. Authorized users would be trained to generate and print reports based on trainee information. A database or systems administrator would be required to maintain the system on a daily basis. This job function would include archival backup of data as well as troubleshooting and the administering and controlling of user access privileges through the use password restrictions. The final step would be full system integration across the network.