System Information Requirement Investigation Techniques

Approach to Systems Development

Australian OAGDS partners with the International charity foundation for the development of an information system and help the little girls from overseas. The information system is developed for motivating the young people in realizing their potentials using educational and medical assistance in different countries. The positive impact of the support are analysed and the different approaches that can be applied for the development of the information system and are discussed in the report. The current problems faced in the manual process are analysed for eliminating the errors and getting the desired output from the developed information system.

There are different software development lifecycle model that can be used for the development of the information system such as waterfall model, prototype model, unified process model, agile modelling, etc (Valacich, George and Hoffer 2014). Each of the model have its advantages and disadvantages but most of the models are developed based on the steps involved in the SDLC methodology (Chopra 2017). For completing the project in less duration of time different activities should run in parallel. The current manual process should be evaluated and it should be transformed such that problem in the project is defined. The project is divided into different phases and the phases for reduce the effort of management and the phases are given below:

Project Planning – It is used for defining the objectives of the project and identification of each of the activity for the completion of the project (Eason 2014). In this phase a project schedule, resource plan and the budget of the project is created

Project Analysis – In this phase the different needs of the business are analysed for the development of the information system. The information should be gathered for the development of the information system and prototype should be created for discovering the requirement (Azar and Vaidyanathan 2015). The requirement should be prioritized and alternatives should be created for the management and reviewing the requirements.

Design – This phase is dependent on the analysis phase and decision should be taken for the integration of the design with the created framework of the system. The user interface and the system interface should be designed for enabling system controls (Dennis, Wixom and Tegarden 2015). The database should also be designed for the development of the prototype and development of the modules.

Implementation Phase – In this phase the components are tested multiple times according to the requirement for ensuring that the exact result is obtained. The users of the information system should be trained such that the organization is benefitted with the development of the information system (Laudon and Laudon 2016).

 Maintenance phase – It is used for eliminating the errors and manage the system upgrades. In this phase the capabilities of the system is enhanced and new features can be added for the management of the user request (Endsley 2016). 

Functional requirement

• The information system helps in allowing the youth to enrol into the information system.
• The details of the personnel and the staffs are recorded into the information system.
• Separate login accounts should be created for management of the information of the users and increase the efficiency of the database (Vaishnavi and Kuechler 2015)
• To automate the management of the stocks and supply chain for the improvement of the current business process

Non-Functional Requirement

• To secure the information such as the personal details and the bank account from illegal users
• To handle large number of request from different users and reduce the errors in the current business process
• To develop a simple interface such that the user does not face any difficulty for using the information system.

Project Cost-Benefit Analysis
Analysis Variables:
Discount Rate Used	10.00%
Annual Benefits	$  1,80,000.00
Annual Operational Costs	$      7,100.00
One-Time Development Cost	$  2,48,000.00
				Year of Project
		0	1	2	3	4	5	TOTALS
Economic Benefit		$0.00	$    1,80,000.00	$     1,80,000.00	$    1,80,000.00	$    1,80,000.00	$   1,80,000.00
Discount Rate		1.0000	0.9091	0.8264	0.7513	0.6830	0.6209
PV of Benefits		$0.00	$1,63,636.36	$1,48,760.33	$1,35,236.66	$1,22,942.42	$1,11,765.84
NPV of all BENEFITS		$0.00	$    1,63,636.36	$     3,12,396.69	$    4,47,633.36	$    5,70,575.78	$   6,82,341.62	$    6,82,341.62
One-Time COSTS		$   (2,48,000.00)
Recurring Costs		$0.00	$       (7,100.00)	$         (7,100.00)	$       (7,100.00)	$       (7,100.00)	$       (7,100.00)
Discount Rate		1.0000	0.9091	0.8264	0.7513	0.6830	0.6209
PV of Recurring Costs		$0.00	$       (6,454.55)	$         (5,867.77)	$       (5,334.34)	$       (4,849.40)	$       (4,408.54)
NPV of all COSTS		$   (2,48,000.00)	$   (2,54,454.55)	$    (2,60,322.31)	$   (2,65,656.65)	$   (2,70,506.04)	$  (2,74,914.59)	$   (2,74,914.59)
Overall NPV								$    4,07,427.03
Overall ROI
								1.4820

Table 1: Cost benefit Analysis

WBS	Task Name	Duration	Start	Finish	Predecessors
0	Development of ICF information system	107 days	Sat 11-08-18	Mon 07-01-19
1	Planning and Analysis	10 days	Sat 11-08-18	Thu 23-08-18
1.1	Scope Statement	5 days	Sat 11-08-18	Thu 16-08-18
1.2	Business Objectives	5 days	Fri 17-08-18	Thu 23-08-18	2
1.3	Project Overview	5 days	Fri 17-08-18	Thu 23-08-18	2
1.4	Project Approach	4 days	Fri 17-08-18	Wed 22-08-18	2
1.5	Cost Estimation	3 days	Fri 17-08-18	Tue 21-08-18	2
1.6	Project Schedule	4 days	Fri 17-08-18	Wed 22-08-18	2
1.7	Risk Analysis	5 days	Fri 17-08-18	Thu 23-08-18	2
2	Design and Development	36 days	Fri 24-08-18	Fri 12-10-18
2.1	System Design Document	6 days	Fri 24-08-18	Fri 31-08-18	3,4,5,6,7,8
2.2	Coding	11 days	Mon 03-09-18	Mon 17-09-18	10
2.3	Unit Testing	10 days	Tue 18-09-18	Mon 01-10-18	11
2.4	Customer Feedback	4 days	Tue 02-10-18	Fri 05-10-18	12
2.5	Change Implementation	5 days	Mon 08-10-18	Fri 12-10-18	13
3	Testing	33 days	Mon 15-10-18	Wed 28-11-18
3.1	Test Plan Creation	6 days	Mon 15-10-18	Mon 22-10-18	14
3.2	Test Cases Creation	5 days	Tue 23-10-18	Mon 29-10-18	16
3.3	Test Execution	11 days	Tue 30-10-18	Tue 13-11-18	17
3.4	Defect Reporting	7 days	Wed 14-11-18	Thu 22-11-18	18
3.5	Implementation of changes	4 days	Fri 23-11-18	Wed 28-11-18	19
4	Implementation	11 days	Thu 29-11-18	Thu 13-12-18
4.1	Change Management	3 days	Thu 29-11-18	Mon 03-12-18	20
4.2	Release Planning	4 days	Tue 04-12-18	Fri 07-12-18	22
4.3	Implementation in all the project environments	4 days	Mon 10-12-18	Thu 13-12-18	23
5	Release and Monitoring	17 days	Fri 14-12-18	Mon 07-01-19
5.1	Go-Live of the System	5 days	Fri 14-12-18	Thu 20-12-18	24
5.2	Post-production monitoring	4 days	Fri 21-12-18	Wed 26-12-18	26
5.3	Collection of Feedbacks	4 days	Thu 27-12-18	Tue 01-01-19	27
5.4	Implementation of necessary changes	4 days	Wed 02-01-19	Mon 07-01-19	28

FIGURE 1: Project Schedule

There are different investigation techniques that can be applied in the development process of the information system for the management of the security requirement, design constraints, supportability requirement, interfaces and implementation requirement of the project. The system requirement is used for the management of the constraint identified for the development of the information system (Pedrycz 2016). The requirement of the information system should be classified into functional and non-functional requirement. Different models and modelling techniques can be used for the development of the high level overview and identification of the input and the outputs for the management of the complexity of the model.

Systems Requirements

It is important to develop a communication model for identification of the requirement and document it for proceeding with the maintenance of the information system (Hollnagel 2017). The arrangement of the stakeholder interview and creating a set of questionnaires can help in identifying the requirement. It should be noted that the questions should be open ended such that it can encourage the stakeholders for more involvement in the discussion. The close ended questions can also be used for concentrating on the specific fact (Oinas-Kukkonen and Harjumaa 2018). A research should be performed on the available information system and collection of the active user comment from the system for the mitigation of the errors and develop an efficient information system. Different diagrams such as activity and workflow diagrams should be used for the identification of the flow of the information between the different elements of the system (Urquhart and Fernandez 2016). The business process should be evaluated for reviewing the inputs and outputs in the system and management of the different business operations.

Reflections and Conclusions

The development of the information system would benefit the user to reduce the manual effort manage the supplies such that there are no errors in the supply management. The information system is designed for recording the details of the users and the funds for generating automated receipt and share it to the individuals for the management of the query of the users. The efforts of the staffs for the management of the multiple programs can be reduced with enrolling the children under different programs. The personal details recorded on the database of the information system can be used for providing them support. The information system would also help the sponsors to fetch the details and make online payment from remote location and supporting the young people for medical and educational assistance.  

References:

Azar, A.T. and Vaidyanathan, S. eds., 2015. Chaos modeling and control systems design (Vol. 581). Germany: Springer.

Chopra, A.K., 2017. Dynamics of Structures. Theory and Applications to. Earthquake Engineering.

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

Eason, K.D., 2014. Information technology and organisational change. CRC Press.

Endsley, M.R., 2016. Designing for situation awareness: An approach to user-centered design. CRC press.

Hollnagel, E., 2017. FRAM: the functional resonance analysis method: modelling complex socio-technical systems. CRC Press.

Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education India.

Oinas-Kukkonen, H. and Harjumaa, M., 2018. Persuasive systems design: key issues, process model and system features. In Routledge Handbook of Policy Design (pp. 105-123). Routledge.

Pedrycz, W., 2016. Granular computing: analysis and design of intelligent systems. CRC press.

Urquhart, C. and Fernandez, W., 2016. Using grounded theory method in information systems: the researcher as blank slate and other myths. In Enacting Research Methods in Information Systems: Volume 1 (pp. 129-156). Palgrave Macmillan, Cham.

Vaishnavi, V.K. and Kuechler, W., 2015. Design science research methods and patterns: innovating information and communication technology. Crc Press.

Valacich, J., George, J. and Hoffer, J., 2014. Essentials of systems analysis and design. Prentice Hall Press.