Table of Contents 1. Introduction……………………………………………………………………………………………....3 2. Approaches to System Development……………………………………………………………………………………………………3 2.1 Reasons for the Selection Approach………………………………………………………………………………………………3 3. System Requirements 4 3.1 Functional Requirements 4 3.2 Non-Functional Requirements 4 4. Project Cost Benefit Analysis 5 4.1 Project Costs 5 4.2 Project Benefits 5 4.3 Summary of Costs and Analysis 6 5. Project Schedule 6 5.1 Work Breakdown Structure (WBS) 6 5.2 Gantt chart 8 5.3 Reasonability of the Project Schedule 8 6. System Information Requirements Investigation Techniques 9 6.1 Project Stakeholders 9 6.2 Investigation Techniques and their Usefulness 9 6.3 Interviews 9 6.4 Document Review 10 6.5 Questionnaires and Surveys 11 7. Reflections and Conclusion 11 8. References 11   1.Introduction Data Science School (DSS) is a Registered Training Organization (RTO) that is a private set-up. The organization currently uses manual operations in most of its business activities and it is because of this reason that there are various drawbacks that are emerging due to the same. There is an automated system that has been proposed in order to prevent the issues with the existing system and the proposed system will be in the form of a web application. 2. Approaches to System Development There are numerous development methodologies and approaches that have been created by the system experts to be followed in the projects. The approach that would be most applicable in this case is the agile methodology for software development. Data Science School (DSS) shall first identify the drawbacks that are associated with the current system. There are various issues that are present in the manual system that is followed such as bottlenecks while accessing the information by the staff members, replicated and duplicated data, inefficiency to keep an adequate account of the details and information associated with the deadlines and deliveries and likewise. Such issues shall be complied and the specifications for the projects shall be designed thereafter in the form of functional and non-functional requirements. It would be important for DSS to identify the types of users such as staff members, students, recruitment agents and admin. The expectations of each of the user type shall be studied and analyzed after that in order to have adequate requirements set in place. The agile software development approach shall be followed during the development and other project activities to incorporate all the specifications, requirements and expectations. 2.1 Reasons for the Selection of Approach The agile software methodology has been selected in case of the system development of Data Science School (DSS) because of the numerous benefits that would come along with the same. There would be several users of the system with varied requirements and expectations and it would be troublesome to incorporate such wide range with other development methodologies. Also, this methodology would be ad-hoc and value based in nature and it would be easy to incorporate any of the changes in the requirements in the later stages of the system development. The feedback and the comments from the clients will also be included in the project at any project stage. 3. System Requirements 3.1 Functional Requirements • Ability to allow the users of the system to access the automated DSS system by logging in to the same. The user types that shall be implemented shall include students, staff members, recruitment agents and the administrator. • Ability to allow the students to file online application on the portal regarding the admission in the school (Mallery, 2011). • Ability to allow the recruitment agents and staff members to file online application on the portal. • Ability to allow the recruitment agents to attach documents on the portal. • Ability to allow the recruitment agents to track the status of the application through the online portal. • Ability to allow the users to lodge online claims for the commissions through the online portal. • Ability to allow the system to save and manage the information through the portal. • Ability to manage the accounting activities and services through the portal such as management of accounts, billing activities, invoice activities and many more. 3.2 Non-Functional Requirements • Usability would allow the users with the ability to have the ease of usage along with easy layouts and navigation (Chang, 2013). • Reliability would allow the users with the ability to have valid information in front of them at all times. • Performance would allow the users with the ability to experience amazing performance in terms of response time and throughput time. • Supportability quality would allow the users with the ability to allow the system to be scaled up or scaled down as per the requirements. • Adaptability would allow the users with the ability to allow the system to function equally well on all the platforms. • Availability would allow the users with the ability to remain available at all times without any lags or breaks (Rozenes, 2011). 4. Project Cost Benefit Analysis 4.1Project Costs 4.2Project Benefits 4.3 Summary of Costs and Analysis 5. Project Schedule 5.1 Work Breakdown Structure (WBS) 5.2 Gantt chart 5.3Reasonability of the Project Schedule The project schedule that has been designed and illustrated above is as per the project scope, requirements and goals of the project. As per the project goals, it would be essential to design and deploy an automated system for DSS that shall fulfill all the functional and non-functional aspects. Also, it would be necessary to deliver the project with minimum risks and conflicts. The schedule that has been designed has the time duration allocated as per the required time to accomplish the same. Also, the resources have been accordingly allocated to make sure that the requirements are fulfilled as per the project scope without any risks associated with the schedule overrun. 6. System Information Requirements Investigation Techniques 6.1 Project Stakeholders • Project Client • Project Manager • End User • System Developer • System Designer • UI Designer • Implementation Analyst • Testing Engineer 6.2 Investigation Techniques and their Usefulness 6.3 Interviews • Step 1: Listing of people for carrying out the interviews o The step would involve the selection of people for the investigation regarding the DSS system o There will be various phases that will be involved in the DSS system project and investigation shall be done with the managers at various levels regarding the project activities to be targeted in each phase o Interviews shall be carried out in the sets of people and in the form of groups (Lind and Culler, 2011). • Step 2: Listing of Interview Objectives o There will be various specifications regarding the DSS system in terms of its design, non-functional aspects and likewise. The interview objectives shall be designed in terms of the specifications. • Step 3: Setting up of Interview Questions o A basic list of the questions to be covered in the interview questions shall be covered. o The question types shall also be of varying style to cover all the aspects (Badiru, 2010). • Step 4: Interview Preparation o The next step in order to investigate the information regarding the DSS systems shall be the preparation for the interviews. o A meeting invite for the interview shall be sent to the interviewer and the interviewee (Parry and Lind, 2016). o The reference materials that may be useful shall also be circulated to both the parties. • Step 5: Process of Interview Conduction • The order of questions to be followed shall be designed. • There shall be attempts made to make sure that the comfortable atmosphere is created. . • The tone must be polite and friendly while asking and discussing the questions. • Step 6: Documentation of the Interview • Recording of the response is essential during the interviews. However, there shall not be complete noting down of each and every detail of the interview. • Step 7: Evaluation process during the Interview • An evaluation of the entire interview shall be carried out such as evaluation of the questions, evaluation of the response and likewise. 6.4 Document Review • The details of the DSS system application will be investigated and understood with the help of this technique. • There will be many of the documents that will be available regarding the application that shall be studied (Peslak, 2012). 6.5 Questionnaires and Surveys • The stakeholders and many of the resources with several other entities will be involved with the system development project for DSS. • Questionnaire will be an information investigation technique that would be applicable in this case as it would be easy to circulate the same and record the response that will be provided in return. • There are a set of guidelines that are associated with the DSS system that would be essential in order to follow during the preparation of the questionnaires. These guidelines shall include the ease of understandability along with the ease of providing the response (Goodwin, 2014). 7. Reflections and Conclusion System Development for Data Science Solution is a step towards the adaptation of advancements in the technology. There are numerous approaches to such projects and the applicable approach in this case is the agile software development. The requirements of the project shall be fulfilled according to this methodology and the testing phase shall be included across every step instead of including it after the development work is completed. Investigation of information is necessary as it would allow the project resources to have adequate details with them. 8. References Badiru, A. (2010). Half-Life of Learning Curves for Information Technology Project Management.International Journal of Information Technology Project Management, 1(3), pp.28-45. Chang, J. (2013). Perceived Required Skills and Abilities in Information Systems Project Management.International Journal of Information Technology Project Management, 4(1), pp.1-12. Goodwin, S. (2014). Changing communication on researchgate through interface updates. Proceedings of the American Society for Information Science and Technology, 51(1), pp.1-4. Lind, M. and Culler, E. (2011).Information Technology Project Performance.International Journal of Information Technology Project Management, 2(4), pp.14-25. Mallery, M. (2011).Project Management Portal (PMP) from the University of Washington Information Technology Wiki - https://wiki.cac.washington.edu/display/pmportal/Project+Management+Portal.Technical Services Quarterly, 28(3), pp.365-367. Parry, V. and Lind, M. (2016).Alignment of Business Strategy and Information Technology Considering Information Technology Governance, Project Portfolio Control, and Risk Management.International Journal of Information Technology Project Management, 7(4), pp.21-37. Peslak, A. (2012). Information Technology Project Management and Project Success.International Journal of Information Technology Project Management, 3(3), pp.31-44. Rozenes, S. (2011). The Impact of Project Management Methodologies on Project Performance.International Journal of Information Technology Project Management, 2(2), pp.64-73.