Approach to Systems Development

The system implementation is the process of analysing the user and business, designing system, developing system and deploying on client organization environment. The information system is consisted of various parts like database, UI, processes, network and many other things (ElSawy, Hossain and Haenggi 2013). The most important part of the system developing is the requirement analysis as without proper requirement the project will surely create various big issues.

The system implementation process in this study is based on the Brisbane Multi Faith Temple’s case. The organization is currently getting hampered due to the existing manual process. The system development is considered by the organization as it is possible to handle employees easily through an automated system and the patrons can easily donate capital through online.

Approach to Systems Development 

The system development approach is crucial for any project as it defines the project success factor and percentage. Different approaches has different processes that needs to be followed strictly. The selected model in this Brisbane Multi Faith Temple IS development is Waterfall Model (Alshamrani and Bahattab 2015). The model is consisting of six phases planning, requirement analysis, designing, implementation, testing and deployment. The post implementation phase is not considered in this case. The model is based on the method of going to the next phase after completion of current one.

The waterfall model is suitable for the Brisbane Multi Faith Temple project. This is because the waterfall model is good for small and less complex projects like this case. The project manager is asked to develop proper documentation and share it with the organization management. This will allow the Brisbane Multi Faith Temple management to have proper idea of what is going on within the project. The project manager will be able to identify all the requirements (system and business) of the system in the early phases. The structure of the organization and simple business process will be assisting in collecting this requirements. The possibility of scope creep is very minimal. The milestones are defined very well in the waterfall model and it will be a great help for the project manager to guide the project.

The system has two kinds of requirements functional and non-functional.

The functional requirements of the system are as following.

1. Online Payment:The system will be consisting of an online payment system. The patron while donating money to the charitable organization, will be redirected to this payment gateway page.  The user will submit the required information and follow the predefined process.
2. Reporting:The system will be assisting the management of Brisbane Multi Faith Temple through generating reports. These reports will be employee attendance, payment, finance related, forecasting and many others. These reports will be generated and provided to the management monthly and if the management wants these reports can be generated for a selected period. Yearly reports will also be generated.
3. Authentication and Authorization: The system will secure user accounts through authentication and authorization. The user will request for data of functions stored in the system and based on the user Id (password at login time) the authentication will be decided. The authorization to access data or functionality will be approved only after successful authentication.
4. Online Application:The system will be connected to an online application (web app or mobile app) so that the patrons can connect to the organization. The information (personal and bank account) of the patron will be transferred to the system for verification and storage through this online application.

1. Security:The system will be consisting of user’s personal data and bank account information. Therefore, it is very essential that the user data must be protected. Along with the user data, business critical and crucial data can be stole if a cybercrime is successfully conducted. So the system will be secured properly and if needed a third party security will be appointed.
2. Availability:The system may be accessed by the patron at any time. For this reason, the system needs to be available to the users 24*7.
3. Scalability:The system must be able to utilize its resources as per business requirements. This will allow organization to gain more profit at some periods of year.

The cost benefit analysis allows the stakeholders of the project to decide whether to undertake the project or not. The net present value of the project clarifies that the project is safe of undertaking. This cost benefit analysis has allows the project manager to estimate the financial factors associated with the project. The cost benefit analysis is also easy to understand and this makes the project related cost and benefit factors to be understood by the stakeholders easily.

Table 1: Cost Benefit Analysis

Cost/Benefit Analysis for the project
Year of Project
	year 0	year1	year 2	year 3	year 4	year 5	TOTALS
Net economic benefit		$135,000.00	$90,000.00	$114,500.00	$134,000.00	$113,000.00
Discount Rate 6%	1	0.9434	0.8900	0.8396	0.7921	0.7473
PV Of Benefits	$0.00	$127,358.49	$80,099.68	$96,136.41	$106,140.55	$84,440.17
NPV of all BENEFITS	$0.00	$127,358.49	$207,458.17	$303,594.58	$409,735.13	$494,175.30	$494,175.30
One Time Costs	($225,000.00)
Recurring Costs	$0.00	($12,250.00)	($13,750.00)	($11,500.00)	($9,560.00)	($10,350.00)
Discount Rate 6%	1.0000	0.9434	0.8900	0.8396	0.7921	0.7473
PV Of Recurring Costs	$0.00	($11,556.60)	($12,237.45)	($9,655.62)	($7,572.42)	($7,734.12)
NPV Of All Costs	($45,000.00)	($56,556.60)	($68,794.05)	($78,449.68)	($86,022.09)	($93,756.21)	($93,756.21)
Overall NPV							$400,419.09
ROI							4.27
Breakeven analysis
Yearly NPV Cashflow	($225,000.00)	$115,801.89	$195,220.72	$293,938.96	$402,162.71	$486,441.18
Overall NPV Cashflow	($225,000.00)	($109,198.11)	$86,022.61	$379,961.56	$782,124.28	$1,268,565.46
Project Breakeven occurs between year 1 and 2							1.56

Task Name	Duration	Start	Finish
Brisbane Multi-Faith Temple Information System Development	103 days	Fri 12/22/17	Tue 5/15/18
First Phase	8 days	Fri 12/22/17	Tue 1/2/18
Project requirement identification	3 days	Fri 12/22/17	Tue 12/26/17
Project plan development	2 days	Wed 12/27/17	Thu 12/28/17
Project feasibility study	3 days	Fri 12/29/17	Tue 1/2/18
Closure of first phase	0 days	Tue 1/2/18	Tue 1/2/18
Second Phase	14 days	Wed 1/3/18	Mon 1/22/18
Project activity scheduling	4 days	Wed 1/3/18	Mon 1/8/18
Project resource identification	3 days	Tue 1/9/18	Thu 1/11/18
Allocation of resources	2 days	Fri 1/12/18	Mon 1/15/18
Project communication plan development	3 days	Tue 1/16/18	Thu 1/18/18
Team member responsibility and role determination	2 days	Fri 1/19/18	Mon 1/22/18
Closure of second phase	0 days	Mon 1/22/18	Mon 1/22/18
Third Phase	79 days	Tue 1/23/18	Fri 5/11/18
Deployment of system devices required	3 days	Tue 1/23/18	Thu 1/25/18
System prototype development	16 days	Fri 1/26/18	Fri 2/16/18
Test and evaluate the accounting software	8 days	Mon 2/19/18	Wed 2/28/18
Develop database for accounts	13 days	Thu 3/1/18	Mon 3/19/18
Establish connection with database	5 days	Tue 3/20/18	Mon 3/26/18
Test and evaluate the response time	1 day	Tue 3/27/18	Tue 3/27/18
Test the developed queries	3 days	Wed 3/28/18	Fri 3/30/18
Execute data migration	5 days	Mon 4/2/18	Fri 4/6/18
Test for acceptance of data	4 days	Mon 4/9/18	Thu 4/12/18
Test and evaluate the system	9 days	Fri 4/13/18	Wed 4/25/18
Testing and evaluation of data warehouse	10 days	Thu 4/26/18	Wed 5/9/18
Testing of connection between database and system	2 days	Thu 5/10/18	Fri 5/11/18
Closure of third phase	0 days	Fri 5/11/18	Fri 5/11/18
Fourth Phase	2 days	Mon 5/14/18	Tue 5/15/18
Project sign-off by stakeholders	1 day	Mon 5/14/18	Mon 5/14/18
Review documentation for the project	1 day	Tue 5/15/18	Tue 5/15/18
Closure of final phase	0 days	Tue 5/15/18	Tue 5/15/18

FIGURE 1: Gantt Chart of Brisbane Multi Faith Temple project

The Work Breakdown Structure is connected to the Gantt chart entirely. The activities that are defined in the WBS is used for scheduling the Gantt chart. As the level of the tasks gets low in the WBS, the subtasks are created in the Gantt chart. The WBS is the basis of Gantt chart.

As per the system goals, requirement and goals, the schedule is proper and perfect. The time period allocated to each of the tasks is very accurate.

System Information Requirement Investigation Techniques

The stakeholders of the project are as following.

1. The Brisbane Multi Faith Temple
2. The investors of Brisbane Multi Faith Temple organization
3. Organization employees
4. Patrons

The selected three investigation techniques are as following.

1. Questionnaire:In this investigating technique, the responsible person create questions for each of the selected stakeholders or all the stakeholders. This questions will be answered by the stakeholders and based on the answers the system specifications will be identified.
2. Document Analysis:The documentation analysis refers to the process of evaluating the business documents for gathering the business data.
3. Survey:The survey is based on the requirements needed to fill the gap of data collected from above two techniques.

Justification: The employees or executives are not able to provide all the details of business for that reason Document Analysis investigation technique is used. The survey will be able to gather huge amount of data from internal and external sources of organization. The questionnaire will be useful for gathering user requirements.

Conclusions

The main achievement of the project will be facilitating the business process of Brisbane Multi Faith Temple. The project will also be able to establish better communication among Brisbane Multi Faith Temple and patrons. The main constraints of the project will be stakeholder support. The project can be hampered by the wrong scheduling.

The project will be done within 103 days. The training to be provided to the users will be planned after prototype development. The investigation techniques will be able to gather all the required data for generating scope of the project and system requirements.

References 

Alshamrani, A. and Bahattab, A., 2015. A comparison between three SDLC models waterfall model, spiral model, and Incremental/Iterative model. International Journal of Computer Science Issues (IJCSI), 12(1), p.106.

ElSawy, H., Hossain, E. and Haenggi, M., 2013. Stochastic geometry for modeling, analysis, and design of multi-tier and cognitive cellular wireless networks: A survey. IEEE Communications Surveys & Tutorials, 15(3), pp.996-1019.

Johnson, F.R., Lancsar, E., Marshall, D., Kilambi, V., Mühlbacher, A., Regier, D.A., Bresnahan, B.W., Kanninen, B. and Bridges, J.F., 2013. Constructing experimental designs for discrete-choice experiments: report of the ISPOR conjoint analysis experimental design good research practices task force. Value in Health, 16(1), pp.3-13.

Jung, J.W., Vu, N.T.T., Dang, D.Q., Do, T.D., Choi, Y.S. and Choi, H.H., 2014. A three-phase inverter for a standalone distributed generation system: Adaptive voltage control design and stability analysis. IEEE Transactions on Energy Conversion, 29(1), pp.46-56.

Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Larson, E.W. and Gray, C., 2013. Project Management: The Managerial Process with MS Project. McGraw-Hill.

Mahalakshmi, M. and Sundararajan, M., 2013. Traditional SDLC Vs Scrum Methodology–A Comparative Study. International Journal of Emerging Technology and Advanced Engineering, 3(6), pp.192-196.

Pitsis, T.S., Sankaran, S., Gudergan, S. and Clegg, S.R., 2014. Governing projects under complexity: theory and practice in project management. International Journal of Project Management, 32(8), pp.1285-1290.

Schwalbe, K., 2015. Information technology project management. Cengage Learning.

Sugito, T.E., Amelia, T. and Sutanto, T., 2017. Design Of Information Systems On Salesman Operational Based On Android at CV. Dwi Star. Jurnal JSIKA, 5(8).

Turner, R., 2016. Gower handbook of project management. Routledge.