Systems Development, Requirements, And Project Management For Brisbane Multi-Faith Temple

Task 1: Approaches to Systems Development

The information system is referred to as the technical equipment that collects desired data from various input devices and process those data. IS also stores those data and information in a storage system called database.

Brisbane Multi-Faith Temple is looking forward to implement an information system into its environment so that it can facilitate its business process. The organization is currently appointing a project team to implement the project. The study covers various system designing and mostly analysis related aspects. The selection of SDLC is always big factor in project management as improper methodology can make a project failure.

Selection of SDLC: The SDLC refers to the process of completing a project from scratch through combination of various interconnected activities. SDLC is the abbreviation of Software Development Life Cycle. Various SDLC are present for carrying out software projects. For Brisbane Multi-Faith Temple System Development Project, the Waterfall model will be the best option. The waterfall model is based on the method of going to another phase after complete completion of previous one. This SDLC is a predictive approach so it is essential to recognize the scope and requirements at the beginning of the project.

Justification against Selection: The waterfall model is best suited for small and simple projects. In this case, the system development is a simple and straight forward project. The methodology is suitable for those clients who wants proper documentation of the phases, Brisbane Multi-Faith Temple is concerned about the proper documentation. The cost of the project which is US $2,25,000 is perfect for the project. In addition to that, as the project is short time project, this perfectly matches with the characteristics of Waterfall Methodology. Waterfall model does not produce a working prototype before completion of project but it is not an issue in this case as Brisbane Multi-Faith Temple wants the system to be deployed only after completion.

Functional Requirements:

1. Authentication:Authentication is the process of checking the cardinalities stored within the system database with the user input data. If the data matched then the user will be able to go to the next process called authorization.
2. Authorization:The user will be authorized by the system so that it can access system functions.
3. Database:The database will be able to store the data into a paramagnet data storage.
4. Online Application:The system will be using an application based on web or mobile to get connected to users.

Non-functional Requirement:

1. Security:Security is a prior part of system. The organization will be appointing third party security providers.
2. Availability: The system will be accessed by the user all the time so it has to be running 24*7.
3. Real time:Real time dataflow will aid end users to all the data as soon as it will be inputted into the system, before storing it to the database.
4. Usability:The usability is a very important part. The end users of the organization did not use any system before so it has to be user friendly.

Description: The cost benefit analysis will permit Brisbane Multi-Faith Temple to produce choices on the basis of the probable results of several classes of activities. It is just a rational path to your choice making. Brisbane Multi-Faith Temple administration can recognize the potential possibilities regarding activities to be taken. It should be recalled that only 1 activity might be picked since it’s mutually exclusive. The expense of the device progress is US $2,25,000. The discount charge is just a discount charge of 6% for the project.

Task 2: Systems Requirements

Cost/Benefit Analysis for the Recovery project
	Year of Project
year 0	year1	year 2	year 3	year 4	year 5	TOTALS
Net economic benefit		$42,500.00	$39,650.00	$48,650.00	$59,560.00	$67,250.00
Discount Rate 6%	1	0.9434	0.8900	0.8396	0.7921	0.7473
PV Of Benefits	$0.00	$40,094.34	$35,288.36	$40,847.48	$47,177.10	$50,253.11
NPV of all BENEFITS	$0.00	$40,094.34	$75,382.70	$116,230.18	$163,407.28	$213,660.39	$213,660.39
One Time Costs	($225,000.00)
Recurring Costs	$0.00	($11,250.00)	($14,570.00)	($13,250.00)	($10,250.00)	($9,750.00)
Discount Rate 6%	1.0000	0.9434	0.8900	0.8396	0.7921	0.7473
PV Of Recurring Costs	$0.00	($10,613.21)	($12,967.25)	($11,124.96)	($8,118.96)	($7,285.77)
NPV Of All Costs	($60,000.00)	($70,613.21)	($83,580.46)	($94,705.41)	($102,824.37)	($110,110.14)	($110,110.14)
Overall NPV							$103,550.25

Breakeven analysis
Yearly NPV Cash flow	($225,000.00)	$29,481.13	$62,415.45	$105,105.22	$155,288.32	$206,374.62
Overall NPV Cash flow	($225,000.00)	($195,518.87)	$133,103.42	$27,998.20	$127,290.12	$333,664.74
Project Breakeven occurs between year 1 and 2							4.13

Task Name	Duration	Start	Finish	Predecessors
Brisbane Multi-Faith Temple System Development	58 days	Wed 12/20/17	Fri 3/9/18
Project Planning	18 days	Wed 12/20/17	Fri 1/12/18
Project Charter Generating	1 day	Wed 12/20/17	Wed 12/20/17
Generating Project Scope	1 day	Thu 12/21/17	Thu 12/21/17	2
Identification of Potential Members of Team	1 day	Fri 12/22/17	Fri 12/22/17	3
Role and Responsibility Definition Generating	1 day	Mon 12/25/17	Mon 12/25/17	4
Kickoff Meeting Schedule	1 day	Tue 12/26/17	Tue 12/26/17	5
Project Plan Distribution	1 day	Wed 12/27/17	Wed 12/27/17	6
Third Party System Vendor Contracts	1 day	Thu 12/28/17	Thu 12/28/17	7
Scope Baseline Creation	1 day	Fri 12/29/17	Fri 12/29/17	8
Schedule and Cost Baseline Creating	2 days	Mon 1/1/18	Tue 1/2/18	9
Identification of risks	1 day	Wed 1/3/18	Wed 1/3/18	10
Risk Management Strategy Development	2 days	Thu 1/4/18	Fri 1/5/18	11
Development of Time Management Approach	1 day	Mon 1/8/18	Mon 1/8/18	12
Resource Management Method Generating	1 day	Tue 1/9/18	Tue 1/9/18	13
Project Scheduling	1 day	Wed 1/10/18	Wed 1/10/18	14
Estimating Budget of the Project	2 days	Thu 1/11/18	Fri 1/12/18	15
Project Plan Completion	0 days	Fri 1/12/18	Fri 1/12/18	16
Requirement Analysis	7 days	Mon 1/15/18	Tue 1/23/18
Finding Method Selecting	1 day	Mon 1/15/18	Mon 1/15/18	17
Collecting Data	1 day	Tue 1/16/18	Tue 1/16/18	19
Evaluating Data	1 day	Wed 1/17/18	Wed 1/17/18	20
Defining System Requirements	2 days	Thu 1/18/18	Fri 1/19/18	21
System Requirements Evaluating	1 day	Mon 1/22/18	Mon 1/22/18	22
System Requirements Documentation	1 day	Tue 1/23/18	Tue 1/23/18	23
Requirement Analysis Completion	0 days	Tue 1/23/18	Tue 1/23/18	24
Designing Phase	12 days	Wed 1/24/18	Thu 2/8/18
System Requirements Collecting	1 day	Wed 1/24/18	Wed 1/24/18	25
System Requirement Evaluating	2 days	Thu 1/25/18	Fri 1/26/18	27
System Functions Designing	3 days	Mon 1/29/18	Wed 1/31/18	28
Designing Unit of the System	1 day	Thu 2/1/18	Thu 2/1/18	29
User Interface or UI Designing	2 days	Fri 2/2/18	Mon 2/5/18	30
System Architecture Generating	1 day	Tue 2/6/18	Tue 2/6/18	31
Database Designing	1 day	Wed 2/7/18	Wed 2/7/18	32
Network Designing	1 day	Thu 2/8/18	Thu 2/8/18	33
Design Phase Completion	0 days	Thu 2/8/18	Thu 2/8/18	34
Development Phase	14 days	Fri 2/9/18	Wed 2/28/18
Coding	2 days	Fri 2/9/18	Mon 2/12/18	35
Initiation of System Development	3 days	Tue 2/13/18	Thu 2/15/18	37
Database Implementing	2 days	Fri 2/16/18	Mon 2/19/18	38
System Network Implementation	2 days	Tue 2/20/18	Wed 2/21/18	39
User Interface Generating	1 day	Thu 2/22/18	Thu 2/22/18	40
Establishing Connection between System and Database	1 day	Fri 2/23/18	Fri 2/23/18	41
Establishing Connection between System and Website	2 days	Mon 2/26/18	Tue 2/27/18	42
Establishing Connection between System and Network	1 day	Wed 2/28/18	Wed 2/28/18	43
Completion of Development Phase	0 days	Wed 2/28/18	Wed 2/28/18	44
Testing Phase	6 days	Thu 3/1/18	Thu 3/8/18
Design/Requirements Review	1 day	Thu 3/1/18	Thu 3/1/18	45
Test Planning	1 day	Fri 3/2/18	Fri 3/2/18	47
Test Design	1 day	Mon 3/5/18	Mon 3/5/18	48
Test Environment Setup	1 day	Tue 3/6/18	Tue 3/6/18	49
Test Execution	1 day	Wed 3/7/18	Wed 3/7/18	50
Test Reporting	1 day	Thu 3/8/18	Thu 3/8/18	51
Testing Phase Complete	0 days	Thu 3/8/18	Thu 3/8/18	52
Deployment Phase	1 day	Fri 3/9/18	Fri 3/9/18
Deploying System in Brisbane Multi-Faith Temple Environment	1 day	Fri 3/9/18	Fri 3/9/18	53
Deployment Complete	0 days	Fri 3/9/18	Fri 3/9/18	55

The WBS is initiated on the basis of the principal deliverables explained in the Gantt chart. Initially the Gantt information is initiated utilising the challenge management tool. The challenge title will probably be collection originally then the principal deliverables will probably be defined. These deliverables will probably be stage 1 entities of WBS. Then more activities will probably be explained beneath the main deliverables. These projects would be the principal deliverables of the Perform Breakdown Structure. The Gantt Chart and WBS are related together as the majority of the deliverables of Gantt information are techniques of WBS.

The deliverables of Gantt information has been developed such way that it can support the challenge manager to attain the challenge seeks and goals. Whilst the agile methodology is iterative, there is generally a chance of putting new demands in the system. It doesn’t matter where period certain requirements are discovered.

Stakeholders Involved: The stakeholders are important part of this project and it is essential to identify all the stakeholders.

1. Project Manager:The project manager is responsible for handling all the process of the project. The project manager communicates with the management of Brisbane Multi-Faith Temple.
2. System Analyst:The system analyst is responsible for analyzing all the information gathered by the business analyst and identification of requirements for system.
3. Software Engineer:This stakeholder is responsible for most of the coding tasks. Engineer may not write a single block of code, he/she will write the algorithm and connect the parts of the system.
4. Coder:The coder does the coding part and removes the bugs from the codes.
5. Tester: The testing personnel is responsible for testing the system.

Investigation Technique: Three investigation methods has been for system information requirement has been discussed below.

1. One-to-One interview:This necessity gathering approach is among the common and easy among all. An interviewee will undoubtedly be sitting against an interviewer and the interviewer will undoubtedly be wondering question to the interviewee regarding different program connected things.
2. Analyzing present documents:The papers often contain important info that the interview or questionnaire participant can’t give. Often knowledge the business enterprise correctly becomes easy during that technique.
3. Group interviews:On the other hand with the one-to-one interview, the interviewer will have the ability to assess and analyze the information furnished by the participants more easily.

Justification: Picked methods will undoubtedly be aiding the unit analyst to gather a lot of the data. The interview with specific and in party enables the unit analyst to gather person demands and on another hand, the paperwork analysis will give you understanding to company requirements.

Conclusions:

The undertaken project permits the Brisbane Multi-Faith Temple to method its business procedures more efficiently and effectively. All of the business operations is apt to be computerized therefore providing the workers the chance of holding the primary business process. The challenge does not protect implementing correct safety measures therefore the extreme cyber-attacks like DDoS can be prevented.

The study entails that functional and non-functional needs will have the ability to protect the pieces needed seriously to program design. The agile system will have the ability to deal with lots of the challenge related issues. The study does not protect any data of potential dangers of the project.

Abel, J.R., Deitz, R. and Su, Y., 2014. Are recent college graduates finding good jobs?.

Bogers, M. and Horst, W., 2014. Collaborative prototyping: Cross?fertilization of knowledge in prototype?driven problem solving. Journal of Product Innovation Management, 31(4), pp.744-764.

Cagiltay, N.E., Tokdemir, G., Kilic, O. and Topalli, D., 2013. Performing and analyzing non-formal inspections of entity relationship diagram (ERD). Journal of Systems and Software, 86(8), pp.2184-2195.

Dabbagh, M. and Lee, S.P., 2014. An approach for integrating the prioritization of functional and nonfunctional requirements. The Scientific World Journal, 2014.

Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-oriented approach with UML. John Wiley & Sons.

Olayan, N. and Yamamoto, S., 2014. A Consistency Check of Dependability Case (D-case) Produced from Data Flow Diagram (DFD). In Joint Conference on Knowledge-Based Software Engineering (pp. 603-616). Springer, Cham.

Rahman, M. and Ripon, S., 2014. Elicitation and modeling non-functional requirements-a POS case study. arXiv preprint arXiv:1403.1936.

Soto, A., 2016. Centennial Celebration–An Interview With Dr Ana Soto on 25 Years of Research on Endocrine-Disrupting Chemicals. Mol Endocrinol, 30(8), pp.829-832.

Wei, F., Roy, S. and Ou, X., 2014. Amandroid: A precise and general inter-component data flow analysis framework for security vetting of android apps. In Proceedings of the 2014 ACM SIGSAC Conference on Computer and Communications Security (pp. 1329-1341). ACM.

Zikmund, W.G., Babin, B.J., Carr, J.C. and Griffin, M., 2013. Business research methods. Cengage Learning.