Current Problems and Requirements
Question:
Discuss about the Information Systems Analysis Design And Development.
This report emphasizes on the development of an Information system for “Data Science School”. The organization is a registered training facility which offers specialized training to domestic as well as international students. The aim of this report is to develop an Information system for the organization to transform their manual process into automated one which will eventually facilitate the reduction in human errors. The development of an Information system is essential for increasing efficiency of the organization by supporting the current business processes.
The major problem that exists within the current organization is that only staff is able to access information that are important that often creates a bottleneck particularly when the staff is at a remote location. The discussion in this report are carried out to demonstrate upon the approach that can be taken for systems development and determination of the system requirements. Further, a project schedule has been prepared and evaluation of the project is done with Cost benefit analysis. The last section of this report is dedicated to discussion on the various techniques for System information requirement investigation.
The analysis of the current system describes that the present system is not capable to meet the requirements of the organization. The requirement analysis showed that the traditional approach will be suitable for the organization to overcome the problems with existing system. A feasibility study for adoption of traditional approach has been conducted to determine the risks and preparing mitigation plans against the identified risks for efficient development of the Information system. Various types of data have been collected to reduce the time for development as well as cost such as different software and resources to design and develop the system by integrating different plug-in.
The development of the project will be initiated with the help of a system development model which is traditional. The system will be developed aligning with the business processes and requirements of the organization. Hence, the iterative model has been chosen as the approach to systems development for developing the Information system. This approach will facilitate development of the Information system with the help of repetitive cycles (Vaishnavi and Kuechler 2015). The development of Information system using this approach will be divided into various phases as well as modules. It will be dependent on validation of the requirements along with testing after each phase is complete to ensure that the system meets the desired goals and objectives. The system developer is aware of the system requirements that needs to be fulfilled so, iterative model has been chosen to be used for development of the Information system. The selection of iterative model is suitable for this project in terms of functionality and flexibility to incorporate new technology to develop the Information system (Richey and Klein 2014).
The determination of system requirements mainly comprises of two types of requirements that is functional and non-functional requirements. For this project to develop the Information system for “Data Science School” (DSS) the system requirements have been categorized and provided as below:
Approach to System Development
Functional requirements
The major functional requirements that have been identified for developing the information system of DSS are tabulated as below:
|
Functional Requirements |
Description |
|
Registration |
This functionality will help the students as well as agents to register or enrol themselves into the system for accessing the services of DSS. |
|
Login |
It is required to ensure that authorized persons can only access the system and the agents are also able to use the system by logging in with the help of specific username and password. |
|
Searching |
The data of the students and the agents can be looked by the administrators and receipt of the specialists can be sought utilizing the develop information system. |
|
Logout |
The session of the client’s lapses on tapping the logout button and the client would be diverted to the landing home page. |
|
Status update |
The status of the receipt and the instalment is required to be appeared on the information system and a notice ought to land to the administrator with respect to the due date of a critical occasion. |
|
Tracking |
The system administrator ought to have the capacity to track the records of students and accumulate their subtle elements for expanding the productivity of the information system. |
|
Mail services |
A mail administration is required to be designed for empowering intercommunication with the students as well as agents associated with the DSS. |
|
Automatic report generation |
The information system ought to have the capacity to produce month to month report comprising of all the instalment action of the agents as well as the students. |
Non-functional Requirement
|
Non-functional Requirement |
Description |
|
Security |
The information system database is required to be secured from unapproved authorization and it is required to be encrypted for expanding the security of the framework. |
|
Authorization |
The DSS information system users ought to be provided with specific username as well as password to access the system. |
|
Storage |
The information is required to be put away in cloud server for remote openness and accessibility. |
|
Availability |
The accessibility of information is imperative in light of the fact that the inaccessibility of information may stop a particular group of users from utilizing the system. |
This section comprises of the calculation of total costs that will be incurred for the project as well as the benefits that will achieved from the project in the form of profits over 5 years (Nas 2016). In this section, the analysis is done by listing the project expenses and then calculating the profits that will achieved in return for 5 years.
Costs and Benefits
|
Tangible Benefits |
|
|
Category |
In $US |
|
Savings on costs for staffs |
$ 30,000.00 |
|
Reduction in costs for overpaid agents |
$ 48,000.00 |
|
Total Tangible Benefits |
$ 78,000.00 |
|
Tangible One-Time Costs |
|
|
Category |
In $US |
|
Total costs for development |
$ 150,000.00 |
|
Total Tangible One-Time Costs |
$ 150,000.00 |
|
Tangible Recurring Costs |
|
|
Category |
In $US |
|
Costs for maintenance related activities |
$ 60,000.00 |
|
Total Tangible Recurring Costs |
$ 60,000.00 |
|
Benefits of option |
Year 1 |
Year 2 |
Year 3 |
Year 4 |
Year 5 |
|
Savings on costs for staffs |
$ 30,000 |
$ 30,000 |
$ 30,000 |
$ 30,000 |
$ 30,000 |
|
Reduction in costs for overpaid agents |
$ 48,000 |
$ 48,000 |
$ 48,000 |
$ 48,000 |
$ 48,000 |
|
Total Benefits |
$ 78,000 |
$ 78,000 |
$ 78,000 |
$ 78,000 |
$ 78,000 |
|
Costs of option |
Year 1 |
Year 2 |
Year 3 |
Year 4 |
Year 5 |
|
Total costs for development |
$ 150,000 |
$ – |
$ – |
$ – |
$ – |
|
Costs for maintenance related activities |
$ 60,000 |
$ 60,000 |
$ 60,000 |
$ 60,000 |
$ 60,000 |
|
Total Costs |
$ 210,000 |
$ 60,000 |
$ 60,000 |
$ 60,000 |
$ 60,000 |
|
Net benefits/costs |
$ (132,000) |
$ 18,000 |
$ 18,000 |
$ 18,000 |
$ 18,000 |
|
Cumulative benefits/costs |
$ (132,000) |
$ (114,000) |
$ (96,000) |
$ (78,000) |
$ (60,000) |
|
Net benefits/cost (NPV @ 5%) |
($125,714.29) |
$16,326.53 |
$15,549.08 |
$14,808.64 |
$14,103.47 |
|
Cumulative NPV |
($125,714.29) |
($109,387.76) |
($93,838.68) |
($79,030.03) |
($64,926.56) |
Table 1: Cost benefit Analysis for the development of Information System
Figure 1: Cost benefit Analysis graph
(Source: Created by Author)
The above graph represents the analysis of cost and benefit for the project to develop the Information system for “Data Science School” (DSS). The red line in the graph indictaes the net benefits that will be achieved over the next 5 years at a discount rate of 5% and the greem line represents the cumulative net present values for the project.
|
WBS |
Task Name |
Duration |
Start |
Finish |
Predecessors |
|
0 |
DSS Information System Development |
125 days |
Mon 5/1/17 |
Fri 10/20/17 |
|
|
1 |
Project Startup |
1 day |
Mon 5/1/17 |
Mon 5/1/17 |
|
|
2 |
Requirements Analysis Phase |
17 days |
Tue 5/2/17 |
Wed 5/24/17 |
|
|
2.1 |
Arrange meetings with stakeholders |
4 days |
Tue 5/2/17 |
Fri 5/5/17 |
1 |
|
2.2 |
Gather required information |
5 days |
Mon 5/8/17 |
Fri 5/12/17 |
3 |
|
2.3 |
Preparing project plan |
6 days |
Mon 5/15/17 |
Mon 5/22/17 |
4 |
|
2.4 |
Approval of project plan |
2 days |
Tue 5/23/17 |
Wed 5/24/17 |
5 |
|
3 |
Procurement phase |
90 days |
Thu 5/25/17 |
Wed 9/27/17 |
|
|
3.1 |
Arrange for resources |
7 days |
Thu 5/25/17 |
Fri 6/2/17 |
6 |
|
3.2 |
Procure equipment’s |
15 days |
Mon 6/5/17 |
Fri 6/23/17 |
8 |
|
3.3 |
Setup of inventory system |
12 days |
Mon 6/26/17 |
Tue 7/11/17 |
9 |
|
3.4 |
Selecting suitable SDLC model |
4 days |
Wed 7/12/17 |
Mon 7/17/17 |
10 |
|
3.5 |
Developing the project team |
6 days |
Tue 7/18/17 |
Tue 7/25/17 |
11 |
|
3.6 |
Preparing a plan for communication |
10 days |
Wed 7/26/17 |
Tue 8/8/17 |
12 |
|
3.7 |
Identifying the functional module |
3 days |
Wed 8/9/17 |
Fri 8/11/17 |
13 |
|
3.8 |
Coding for development of functional module |
18 days |
Mon 8/14/17 |
Wed 9/6/17 |
14 |
|
3.9 |
Integrating the module |
8 days |
Thu 9/7/17 |
Mon 9/18/17 |
15 |
|
3.10 |
Testing to check functionality of the module |
4 days |
Tue 9/19/17 |
Fri 9/22/17 |
16 |
|
3.11 |
Deploying the Information system |
3 days |
Mon 9/25/17 |
Wed 9/27/17 |
17 |
|
4 |
Training phase |
16 days |
Thu 9/28/17 |
Thu 10/19/17 |
|
|
4.1 |
Development of training program |
7 days |
Thu 9/28/17 |
Fri 10/6/17 |
18 |
|
4.2 |
Prepare user manuals |
4 days |
Mon 10/9/17 |
Thu 10/12/17 |
20 |
|
4.3 |
Identifying the staffs for training |
3 days |
Fri 10/13/17 |
Tue 10/17/17 |
21 |
|
4.4 |
Hiring of trainers |
2 days |
Wed 10/18/17 |
Thu 10/19/17 |
22 |
|
5 |
Project Closure |
1 day |
Fri 10/20/17 |
Fri 10/20/17 |
23 |
FIGURE 2: Gantt chart for the project
(Source: Created by Author)
For development of the Information system to support the business processes of DSS, the following stakeholders will be associated with the project:
|
Stakeholders |
Impact |
Interest |
|
Me John Smith (Owner / Project Sponsor) |
High |
High |
|
Project Manager |
Medium |
High |
|
Agents |
Low |
High |
|
Students |
Low |
High |
|
Resource Manager |
Medium |
Low |
|
System Analyst |
High |
Medium |
Interviewing: The partners related with the association are met for breaking down the prerequisite and it done by organizing gatherings with the partners. Meeting the partners, for example, the sponsor for project would comprehend the monetary allowance designated for the advancement of the project and the time inside which the project is required to be finished (Martinelli and Milosevic 2016).
Questionnaires: An arrangement of inquiries is required to be readied and they can be sent to the partners through email to get input from them. The polls are utilized for taking criticism from the partners remotely without direct meetings. This lessens the investigation time and precise information can be found with the utilization of an arrangement of legitimate questionaries.
Observation: Observing authoritative process would comprehend the prerequisite of the project and in this manner expanding the likelihood of fruitful improvement. The present procedure took after by the association is required to be checked for comprehend the necessities of the present business processes (Hale and Stanney 2014). This helps the team for development to build up the Information system by adjusting the necessities of the association.
Reflections and Conclusions
The limitation confronted in terms of developing the Information system for DSS is that it ought to record the whole operator and the understudy data and would have the capacity to react to any question made with respect to the understudy and the specialists. The execution of the data framework in the present business procedure of the association would help the association to expand its effectiveness and lessen the activities required to deal with the records physically.
From the above report it can be reasoned that for the improvement of the framework a project plan and a work breakdown structure is required to be readied that would help the project administration group to effectively build up the project. An analysis of cost benefit is additionally performed on the project to discover the time in which the project cost would be recuperated.
References
Burke, R., 2013. Project management: planning and control techniques. New Jersey, USA.
Galliers, R.D. and Leidner, D.E., 2014. Strategic information management: challenges and strategies in managing information systems. Routledge.
Grinsven, M., Heusinkveld, S. and Cornelissen, J., 2016. Translating management concepts: towards a typology of alternative approaches. International Journal of Management Reviews, 18(3), pp.271-289.
Hale, K.S. and Stanney, K.M., 2014. Handbook of virtual environments: Design, implementation, and applications. CRC Press.
Heagney, J., 2016. Fundamentals of project management. AMACOM Div American Mgmt Assn.
Kerzner, H., 2013. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Lientz, B. and Rea, K., 2016. Breakthrough technology project management. Routledge.
Martinelli, R.J. and Milosevic, D.Z., 2016. Project management toolbox: tools and techniques for the practicing project manager. John Wiley & Sons.
MINE, P.O. and AREA, C., 2015. Cost Benefit Analysis.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking project management performance and project success. International Journal of Project Management, 32(2), pp.202-217.
Nas, T.F., 2016. Cost-benefit analysis: Theory and application. Lexington Books.
Pritchard, C.L. and PMP, P.R., 2014. Risk management: concepts and guidance. CRC Press.
Richey, R.C. and Klein, J.D., 2014. Design and development research: Methods, strategies, and issues. Routledge.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Stark, J., 2015. Product lifecycle management. In Product Lifecycle Management (pp. 1-29). Springer International Publishing.
Turner, J.R., 2014. The handbook of project-based management (Vol. 92). New York, NY: McGraw-hill.
Turner, R., 2016. Gower handbook of project management. Routledge.
Vaishnavi, V.K. and Kuechler, W., 2015. Design science research methods and patterns: innovating information and communication technology. Crc Press.
Valacich, J.S., George, J.F. and Hoffer, J.A., 2015. Essentials of systems analysis and design. Pearson Education.
Wasson, C.S., 2015. System Engineering Analysis, Design, and Development: Concepts, Principles, and Practices. John Wiley & Sons.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
