Selection of SDLC
The information system is the part of information technology that assist organizations to manage vast amount of information/data. The technology also assist enterprises to evaluate raw data and generate information. The system is basically utilized by the organizations for assisting the management in decision making. Various organizations implement new information system and few update the existing information system.
This study covers various aspects of Information System implementation in the context of Brisbane Multi-Faith Temple. The organization is currently using manual process for carrying out the business process. The desired system consist of core system, online application and few others.
Selection of SDLC: Any project management method needs to be completed through a proper planning and adequate processes. In order to complete an Information Technology project various software development life cycle will be analyzed and one SDLC will be selected. The budget of developing the system is $225,000. Therefore, the cost of the project is not the issue. The system development process must be adequate and adaptive as the organization does not have any idea regarding the system development. Scope creep can occur very fluently through the project lifecycle. Little planning is required for completing the project. The developers will be in of working with flexibility so that the scope creep and other related issues cannot harm system quality. Brisbane Multi-Faith Temple is not concentrating on the documentation, instead it is concentrating on the results.
Justification against Selection: The main reason behind selecting the adaptive approach is that it is considered to be realistic method for system development. The agile model encourages teamwork and cross training. The cross training is significant for Brisbane Multi-Faith Temple as the employees does not have any idea regarding the system usage. The change in requirements is supposed to be frequent throughout the whole project. The project manager and business analyst may not get all the data regarding creating all the scopes of the system. This will result into scope creep. The adaptive methodology is designed in such a way that it may reduce the effect of scope creep on the project to minimal.
Functional Requirements: The functional requirements of the system describe the function and behavior of the system. The functional requirements of the system are as following.
- Authentication:The system will store the access-credentials regarding each of the users of the system. The user will request for various access and the system will authenticate the user access. If the credentials stored within the database match with the user input or any other data related to user, the authentication is successful.
- Authorization:The system will authorize the user to access various data or function after successful authorization.
- Database:The system will be connected to a central database that will hold all the raw data and produced information.
- Online Application:The system will be connected to an online application that will be used for donate money mainly.
Non-functional Requirement: The nonfunctional requirements of the system are as following.
- Security:The system must be secure from most of the cyber-attacks and protect its data from the physical attacks.
- Availability: The system will be available 24*7 so that the users can access the online application all the time.
- Real time:The data flow within the system will be in real time. These will allow the users to see data as soon as a data is inputted into the system.
- Usability:As the users of the system, mainly the employees of Brisbane Multi-Faith Temple does not have any idea regarding working on a system usability is very important.
Description: as
|
Cost/Benefit Analysis for the Enterprise Architecture |
||||||
|
Category |
Year 0 |
Year 1 |
Year 2 |
Year 3 |
Year 4 |
Year 5 |
|
Value of benefits |
$65,000 |
$60,000 |
$50,000 |
$45,000 |
$40,000 |
|
|
Development costs |
$225,000 |
|||||
|
Annual expenses |
$20,000 |
$27,000 |
$9,000 |
$11,000 |
$13,000 |
|
|
Net benefit/costs |
$50,000 |
$85,000 |
$87,000 |
$59,000 |
$56,000 |
$53,000 |
|
Discount factor |
$13,500 |
|||||
|
Net present value |
$56,000 |
$23,000 |
$11,000 |
$9,000 |
$0 |
$0 |
|
Cumulative NPV |
$55,000 |
$78,000 |
$89,000 |
$98,000 |
$98,000 |
$98,000 |
|
Breakeven analysis |
||||||
|
Yearly NPV Cashflow |
($50,000.00) |
$21,415.09 |
$53,221.79 |
$83,228.10 |
$111,535.94 |
$138,241.46 |
|
Overall NPV Cashflow |
($50,000.00) |
($28,584.91) |
$24,636.88 |
$107,864.98 |
$219,400.93 |
$357,642.38 |
The cost benefit analysis will allow Brisbane Multi-Faith Temple to make decisions based on the possible results of several courses of activities. It is a logical path to the decision making. Brisbane Multi-Faith Temple management will identify the potential options regarding actions to be taken. It has to be remembered that only one action can be chosen as it is mutually exclusive. The cost of the system development is US $2,25,000. The discount rate is a discount rate of 6% for the project.
Justification against Selection
|
Task Name |
Duration |
|
Brisbane Multi-Faith Temple IS Project |
120 days |
|
Selection of the Project |
9 days |
|
Identification of potential projects |
2 days |
|
Prioritize potential projects |
3 days |
|
Develop initial version |
1 day |
|
Consider project feasibility |
3 days |
|
Project initiation |
42 days |
|
Participation active stakeholder |
3 days |
|
Obtain funding and support |
2 days |
|
Team building initiation |
4 days |
|
Envision of initial requirements |
4 days |
|
Envision of initial architecture |
5 days |
|
Environment Configuration |
24 days |
|
Deploy System into Environment |
34 days |
|
Participation active stakeholder |
3 days |
|
Final testing of System |
8 days |
|
Final testing of acceptance |
5 days |
|
Document Finalizing |
2 days |
|
Pilot testing the release |
10 days |
|
Providing training to the users |
5 days |
|
Deploy System into Environment |
1 day |
|
Operate and Support Product |
35 days |
|
Operate the system |
14 days |
|
Supporting System |
12 days |
|
Recognizing enhancement and defects |
9 days |
The WBS is created based on the main deliverables defined in the Gantt chart. At first the Gantt chart is created using the project management tool. The project name will be set at first then the main deliverables will be defined. These deliverables will be level 1 entities of WBS. Then more activities will be defined under the main deliverables. These tasks will be the main deliverables of the Work Breakdown Structure. The Gantt Chart and WBS are connected to each other as all the deliverables of Gantt chart are processes of WBS.
The deliverables of Gantt chart has been designed in such way that it will assist the project manager to achieve the project aims and goals. As the agile methodology is iterative, there is always a possibility of inserting new requirements into the system. It does not matter at which stage the requirements are discovered.
Stakeholders Involved: The stakeholders are important part of this project and it is essential to identify all the stakeholders.
|
Stakeholder Name |
Description |
Priority |
Internal/External |
|
Systems Analyst |
This stakeholder analyze all the details found by the business analyst about the organization and design system |
High |
Internal |
|
Computer Engineer |
Hardware, network and system engineer are the example of this stakeholder This stakeholder design the computing devices |
Medium |
Internal |
|
Service Provider |
Various services that are required to complete the project is provided by the service provider |
Medium |
External |
|
Project Manager |
The project manager control the whole project, guide the team members and communicate with the client organization |
High |
Internal |
|
Sam Sharma |
Brisbane Multi-Faith Temple chairman |
High |
Internal |
|
Employees |
15 priests, 20 admin staff, 5 cleaners, 1 handyman and an accountant are the employees of Brisbane Multi-Faith Temple |
Low |
Internal |
|
Customers of Brisbane Multi-Faith Temple |
All the users who are related to Brisbane Multi-Faith Temple externally and donate money |
Low |
External |
Investigation Technique: Three investigation methods has been for system information requirement has been discussed below.
- One-to-One interview:This requirement gathering technique is one of the popular and easy among all. An interviewee will be sitting against an interviewer and the interviewer will be asking question to the interviewee regarding various system related things.
- Analyzing present documents:The documents often consist of important information that an interview or questionnaire participant cannot give. Often understanding the business properly becomes easy through this technique.
- Group interviews:In contrast with the one-to-one interview, the interviewer will be able to compare and analyze the information provided by the participants more easily.
Justification: Selected methods will be assisting the system analyst to gather most of the data. The interview with individual and in group will allow the system analyst to gather user requirements and on the other hand, the documentation analysis will offer insight to business requirements.
Conclusions:
The project will allow the Brisbane Multi-Faith Temple to process its business procedures more efficiently and effectively. Most of the business processes will be automated thus providing the employees the opportunity of carrying the core business process. The project does not cover implementing proper security measures so the severe cyber-attacks like DDoS can be prevented.
The study concludes that functional and non-functional requirements will be able to cover the parts required to system design. The agile methodology will be able to address most of the project related issues. The study does not cover any information of potential risks 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.
Vaidyanathan, S., Volos, C. and Pham, V.T., 2014. Hyperchaos, adaptive control and synchronization of a novel 5-D hyperchaotic system with three positive Lyapunov exponents and its SPICE implementation. Archives of Control Sciences, 24(4), pp.409-446.
Vasquez, J.C., Guerrero, J.M., Savaghebi, M., Eloy-Garcia, J. and Teodorescu, R., 2013. Modeling, analysis, and design of stationary-reference-frame droop-controlled parallel three-phase voltage source inverters. IEEE Transactions on Industrial Electronics, 60(4), pp.1271-1280.
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.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
