COIT20248: Information Systems Analysis and Design
Table of Contents
Approaches to Systems Development. 2
Project Cost/Benefit Analysis. 5
Add your Project Cost Benefit Analysis table here.Project Management and Scheduling. 7
System Information Requirement Investigation Techniques. 11
Reflections and Conclusions. 12
Introduction
The objective of this report is to perform system analysis for Repair-Made-Easy. The RME is a company which provides spare parts for computers and related services in Melbourne, Australia. The purpose is to suggest an information system for RME through a system development approach. Also, this report will refer to the primary system requirement for a new information system. Besides, a feasibility study will also be performed through cost/benefit analysis. The report will also present WBS for the project.
Project Objectives:
- Perform Cost-Benefit Analysis for RME
- Determine WBS and Project Schedule for RME
- Investigation Techniques for System Information
Approaches to Systems Development
It is essential to design an approach for system development at Repair-Made-Easy. They work on a manual system which makes difficult to operate on spreadsheets. Henceforth, a system development approach for an information system is necessary. I suggest two important approaches for system development like ISDM and ADDIE model. Furthermore, there are two obstacles in the manual system. Firstly, RME needs an online information system to provide their services. Secondly, the there system should have a centralized database server. To address the above issues, the ISDM approach will be more effective for RME’s web application. ISDM approach is a process where goals, concepts and methods are identified for a project (Iivari et al 1998, p. 165). This approach will be highly effective in the proposed information system. The project development depends on systematic system requirement specification. The goal is a better principle which determines the system requirement for an information system. The system requirement follows functional and non-functional specifications. There are three important objectives for RME’s information system. Firstly, to reduce the operational cost by cost/benefit analysis. Secondly, to create a web application for RME as management will open new stores across Melbourne. Finally, to provide a centralized database for customers, suppliers and business data. Another system development approach which is applicable for system development is ADDIE – analysis, design, development, implementation and evaluation. This iterative process takes previous analysis and jumps into next. This approach is highly effective to plan steps for an information system. Henceforth, both the approach is currently used for system development.
Systems Requirements
The system requirements are divided into two specifications – functional and non-functional. While functional requirements determine what a system should do for working, non-functional requirement specifies how a system will perform a certain function (Eriksson 2019). RME is a repair providing service for computer accessories in Melbourne. They need a web-based application with a centralized database server to store information. The functional and non-functional requirements were gathered after following system approach mentioned above.
FUNCTIONAL REQUIREMENTS
The functional requirements will show what system will perform such as payment gateways, customer receipt generation, as well as database storage and management.
- Customer Sign Up and Login
- Tabs – Service, Return/Refund, Make Payments, Receipt Generation
- Services Tab – Repair and Spare Services
- Customer can choose between any service
- Customer Section – Return or Refund Service
- Office Manager Sign Up and Login
- Tabs – Service, Cancel/Refund, Fill customer and Supplier detail, Generate Receipt
- Services Tab – Order Approval, Store Customer and Supplier Information
- System Admin Sign Up and Login
- Tabs – Manage Database, Backup Database
- Admin Service Tab – Store or retrieve information of customer and supplier in database
- Payment Gateways (COD)
- Online Payment Gateways
- Database Administration
- Receipt and tax-deductible certificate generation
NON FUNCTIONAL REQUIREMENTS
The non-functional requirements show how the system will perform security, maintenance, and database storage as well as the navigation process.
- Privacy and security for customers, suppliers and RME managers
- Security for online payment gateway.
- Development and maintenance of database.
- Backup storage for Database.
- System compatibility with browsers such as Internet Explorer, Google Chrome, Mozilla Firefox.
- Navigation on all web pages.
- Provide an easy graphical user interface for simplicity.
- Flexible Information System
Henceforth, functional and non-functional requirements for the RME information system is determined.
Project Cost/Benefit Analysis
Cost/Benefit Analysis is widely performed to evaluate decisions for tax, trade, income policies, and licensing of private investments (Dreze & Stern 1987). In this project scenario, CBA analysis will determine the project’s financial outcome. Such analysis is essential to determine the financial feasibility of the project whether it is increasing the overall cost or not. The cost which will be required to develop this project should be understood properly. The cost-benefit is essential so that the project can be imitated by taking overall estimation. The annual sale income of RME is $2.0 billion while annual system maintenance cost is $12000. Therefore, the total estimated development cost for this project completion is $0.8.
Table 1: Excel File for cost-benefit calculation
The above specification clearly shows that the benefit is decreasing with passing time as the recurring cost for maintenance and other overall cost is increasing. The application is a software application and is developed to support the organization in its business processes in a seamless manner. The software does not have an aging but the hardware has aged so the maintenance cost will increase rapidly. All the calculation has been done according to the specification provided. The net present value after the calculation has been given at the end of the calculation. It is also observed that the net benefit is decreasing but not on a high scale. Similarly, the present value is also decreasing but according to the time it is not a big figure that will put a huge impact on finance. It can be concluded that by adopting this project the organization will be benefited. The problem of recurring maintenance cost can be eliminated by adopting new technology in the application.
Project Management and Scheduling
Work Breakdown Structure (WBS)
The work breakdown structure (WBS) bifurcate work activities for information system into small manageable tasks for budget schedule and assigned responsibility (Tausworthe 1979). In RME’s work break down structure, role and responsibility for an information system is shown. This WBS is essential to understand the project management schedule. The structure is then utilized in the creation of a Gantt chart.
WBS Level
Level 1: Project Planning and Feasibility Study
- Appoint Software Consultant
- Determine Project Goals
Level 2: System and Requirement Analysis
2.1 Define functions and operations
2.2 CBA Analysis
2.3 Get Project Approval
Level 3: System Design
- Appoint Business Analyst
- Design Layouts, Process Diagrams, SRS
Level 4: Development and Implementation
4.1 Appoint Software Programmer
4.2 Implement code
Level 5: Integration and Testing
5.1 Appoint Tester for System Testing
5.2. Alpha Testing
5.3 Beta Testing
Level 6: Deployment and Maintenance
6.1 Deploy Project for RME
6.2 Operate and Maintain Information System
Project Schedule
The project management schedule presented below shows the six-month duration for RME. The project duration is estimated six months in which 180 days are equally divided. The research analysis takes less time as compared to development, and testing. The project schedule is reasonable because development and testing take more time. Therefore, time for designing, coding, and testing have assigned more months over requirement gathering study.
System Information Requirement Investigation Techniques
System Information Requirement Investigation is an SDLC process where project details are gathered (Mahmood 1987). Similarly, in this project also, investigation techniques are used to determine the requirements of the information system. After an investigation of the project, there are two stakeholders in this project. The internal stakeholders are employees who face problem in the delivery of the product. The external stakeholders are customers who are kept unavailable on booked products. RME provides spare and repairs computer accessories in Melbourne, Australia. To understand their major requirements, three investigation techniques were performed.
Face-to-Face Interviews
This investigation technique comes under requirement gathering of software life cycle process. The purpose of this investigation was to understand the problem with the manual system. As a software consultant, I took interviews with staff and management at RME. This investigation concluded that the manual system of spreadsheet confuse salesman. Additionally, there is a need for database storage.
Observations
This investigation technique is essential for understanding the customer’s needs. The customers visit the shop and decide to buy or repair a computer accessory. The manual system was understood by considering the customer’s requirement. This RME system was observed from start to end.
Questionaries
The survey was done among customers on whether they are happy with the current services of RME. This survey was in the form of questions where they were asked about the online system. The results showed that fifty per cent of customers agreed that the online system will make their problem easily. The travelling distance will the main problem for them to reach a local store every time.
Reflections and Conclusions
I have understood that Repair-Made-Easy needed a web-based platform for their local stores. Their major necessity was to have an online system from which they can attract more customers. Additionally, I have also understood that this system should be highly secure for customers. We have successfully designed the system requirements after getting in discussion with RME owner John. His major requirement to make a web application with database storage. The project schedule was designed as per the time constraint of six months to one year. I have gathered that information system for repair and spare services were necessary. This system will help people to search for computer accessories online. Still, I believe risk management techniques for the project should be progressed further. I am satisfied with the project schedule of six months which will effective for successful delivery. To conclude, the proposed system will provide a better online information system
Reference List
Drèze, J. and Stern, N., 1987. The theory of cost-benefit analysis. In Handbook of public economics (Vol. 2, pp. 909-989). Elsevier.
Eriksson, U. 2019. The difference between functional and non-functional requirements | ReQtest. [online] ReQtest. Available at: https://reqtest.com/requirements-blog/understanding-the-difference-between-functional-and-non-functional-requirements/ [Accessed 16 Aug. 2019].
Iivari, J., Hirschheim, R. and Klein, H.K., 1998. A paradigmatic analysis contrasting information systems development approaches and methodologies. Information Systems Research, 9(2), pp.164-193.
Mahmood, M.A., 1987. System development methods-a comparative investigation. MIS Quarterly, pp.293-311.
Trustworthy, R.C., 1979. The work breakdown structure in software project management. Journal of Systems and Software, 1, pp.181-186.