The paper “ Project Initiation Documents” is a fascinating example of a finance & accounting case study. The basic implementation of the system will draw a correlation with the present paper-based system. It will involve an in-depth analysis of the functionalities, limitations, and constraints that are associated with the current paper-based system and attempt to provide a solution to the impediments that are related to the present information system that is paper-based. The overall goal of these new proposed web-based system will be to facilitate the company operations towards the process of employee application of travel expenses claim and to reduce the response duration of the application by the involved company departments in the process (Andrew & Jennifer, 2005, pp. 78-104). The transitional approach will be on a continual basis rather than abrupt, in order not to completely jeopardize the business operations of the company; its implementation will be carried on while the company will still be using the traditional paper-based system, upon completion, there will be a system overhaul.
The new system will be evaluated for efficiency and ease of use, additional necessary requirements shall be included before the complete implementation of the system. The architectural approach will include three divisions: the user input/ interface, the internal processing of the submitted forms by the employees, and the feedback of the applications.
A side process will include keeping the employees updated on their application progress. The general approach to the implementation of the system will use the conventional system development life cycle (SDLC) which will include project planning and feasibility study, analysis of the system and determination of the systems requirements from a user point of view, the actual design of the system, implementation of the system, integration, and testing of the proposed system and finally maintenance of the system (Avison & Guy, 2003,45-59). Proposed System description/ briefWeb-based applications are resident on a central server and their services can be accessed through the use of a web browser; this implies that the access to the company data and information will not be limited by geographical locations.
Andrew, S., and Jennifer G.,2005. Applied Software Project Management. Cambridge, MA: O'Reilly Media, pp. 78-104
Avison, D. E. Guy F., 2003, Information systems development: methodologies, techniques, and tools. New York: Blackwell Scientific Publications, pp.45-59
Brian, B., Daniel, P., Juergen, K., Arnold, 2009, Software & Systems Requirements Engineering: In Practice. New York: McGraw-Hill Professional, pp. 101-106
Frank, L. Dieter, R., 2000, Production workflow: concepts and techniques. New York: Prentice-Hall, pp.45-74
Marie, K. Janis, G., 2002, Information systems development: advances in methodologies, components, and management. Moscow: Springer, pp.12-16
McConnell, S., 1996. Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press,pp. 45-58
Michael J. Oxford Institute of Information Management, PA Consulting Group, 1996, Information management: the organizational dimension. London: Oxford University Press,pp. 89-94
Richard, B. Rudy A. H., 1987, Critical issues in information systems research. New York: Wiley,pp. 85-95
Robert, G., Doro, E. L., 2003, Strategic information management: challenges and strategies in managing information systems. New York:Butterworth-Heinemann,pp.156-170
Scot W. A., The Object Primer 3rd Edition Agile Model-Driven Development with UML 2 [online] retrieved from http://www.agilemodeling.com/artifacts/dataFlowDiagram.htm accessed on 23 November 2010.
Walter, S., 2008, Sustainable Development Possible with Creative System Engineering. New Jersey: CassBeth,pp.89-100
With, W., 1999, Systems development methods for databases, enterprise modeling, and workflow management. Moscow: Springer,pp. 56-58