In: Accounting
Management has decided that they want a top of the line financial information system. They need you to define the requirements that the system will need. How would you begin this process? Who might you need to talk with at the company and what questions might you need to ask them? What steps would you take to define the system requirements? What kind of items would be detailed in the RFP? What details should be outlined in the implementation proposal?
Please no repeated answers.
ANSWER:
A – To define the requirements the system will need, we have to do the system requirement analysis which involves the following steps –
To identify and consult the owners to determine their expectations and resolve their conflicts
To analyse requirements to determine priorities
To gather data or find facts using tools like – interviewing, research, document collection, observation etc.
To verify that requirements are consistent, testable and traceable
To document activities
B - The following steps ensures appropriate system requirement analysis –
Fact Findings – Every system is built to meets some needs of organisations for lower operational costs, better information for managers and smooth operations. We need to gather data or find facts using tools like – interviewing, research, document collection, observation etc.
Analysis of the present system – The present system should be analysed to obtain methods, procedures, historical aspects, inputs and outputs, internal controls etc.
System Analysis of proposed system – The proposed system should also be analysed as the analysis of present system is required
System Development Tools – We need to identify the tools needed for system developments, its feasibility and cost impact.
System specification – After all the analysis the new system specification should be provided
C - The following people must be consulted before any system development or changes in the current system –
Senior management
IT Team
Finance team
Other stake holders
D – The items details in RFP –
The complete specification about system
The cost components
Operational and financial feasibility
Need for change
Impact of new system
Savings in cost and time
E – Details outline in implementation proposal –
Conversion of data to the new system files
Training of end users
Completion of user documentation
System changeover
Evaluation of system at regular intervals