Section 6 – Milestones and Deliverables based on Date and Dependencies

profilepxmptee
IT487_Charles_Williams_Week1IP.docx

Running Header: 1

APPLICATION DEVELOPMENT METHODS 2

Unit 1 Group Project

Application Development Methods

Group 4

John Holmberg, Sean Austin, Christian Dillon, Charles Williams, Matthew Serdy, Frank Opoku

April 10, 2019

IT487 – IT Capstone 1

Nolyn Johnson

Table of Contents Section 1 - Overview of Company and Client Business Case 3 Section 2 - Application Requirement Elicitation Strategy 5 Section 3 - System Components and Design Requirements 7 Section 4 - Methodology for Application Development Process 8 Section 5 - Complete Features and Trade-off Analysis 10 Section 6 - Milestones and Deliverables Based on Date and Dependencies 11 Section 7 - System Architecture Aligned with System Requirements 12 Section 8 - Technical Design Document 13 Section 9 - Design Review Checklist 14 Section 10 - Testing and Deployment 15 References 16

Section 1 - Overview of Company and Client Business Case

The company Education Information Systems. (EiS) is an information and management company that specializes in the creation and care of large-scale educational information and technology systems. EiS has implemented and managed systems ranging from the pre-K to 12th year primary school systems, and is developing larger scale systems to facilitate collegiate, graduate and post graduate educational institutions. EiS is a privately held organization that has the primary focus of providing the best possible systems to help grow the educational sector. Previous clients have implemented system wide software replacement and upgrades. With a stellar track record of previous educational institutions, and references, EiS has completed all the projects on time, and within budgetary guidelines. All problem issues or negative feedback from clients were handled in professional and timely manner that resulted in a completely satisfied client.

Moving toward post high school educational institutions, EiS is working with an extremely talented development team to move into the graduate and post graduate sector with ease. With new projects being developed, and more clients, EiS also works to recruit the best talent in the development, and technical aspects of information technology.

The information system to be developed by EiS for the institution will allow for all student, and faculty to store, share, and secure data. Utilizing a web-based UI, the information will be easily accessed, with the proper credentials. Data can be shared among staff, and students with preferences designed to mitigate corruption of data, loss of information, especially personal and financial information. All faculty and staff can be added to the application via an admin portal and all security is designated there. All remote access to the application will require a 2 factor

authentication system for another level of security to ensure that the proper access protocols are being followed. All information that is stored will be designed to the student or faculty member, and kept throughout the students’ academic career or the faculty member’s tenure. The system will also track course credits for the student and all previous history from that student. Including previous course work, and any materials uploaded into the system.

By utilizing the new system supplied by EiS, this will allow the educational institutions to move forward with the latest in software development, move to and adapt as the needs change, as well as keep a history of past data to ensure that the students and faculty have the best chances of success in the ever changing world of online learning.

(Christian Dillon – Monday, 08 April 2019)

Section 2 - Application Requirement Elicitation Strategy

At the start of the requirement phase of the project is just that the beginning of all involved in the discussion of requirements by the business, stakeholders, IT personnel, fellow project designers, vendors, finance personnel, and those personnel that take on different sections of the project to bring it all together. There are a number of ways to elicit information from everyone involved. To include interviews with a select group of people, mainly our target audience. During these interviews, each person will begin by answering a ten-question survey aimed at gathering information about the project about to be developed. Some example questions are listed below:

· Question 1: What problems/issues does this project solve.

· Question 2: How would you solve the problem/issues?

· Question 3: What will it cost to implement the project?

· Question 4: Will this project solve those issues and make greater improvements for all?

· Question 5: What are the risk factors?

· Question 6: With risks comes issues of side effects, if the risks cause problems, will the project be on time?

· Question 7: If the risks are minimal, will the implementation perform as needed by the university?

· Question 8: Granted you are not formulating a solution to an existing problem you are improving a viable system to have greater performance and student satisfaction. How would you implement this new system?

· Question 9: Can you express your opinions on how to ease the access of information to all users on all platforms?

· Question 10: How can we make this new system user friendly, so that any skill level in dealing with it can access the right information on all levels of access in the university while keeping all information secure?

These are just some sample questions that could be asked with each person during the interview process. After all interviews are conducted, the interviewees will meet based on their schedules and skill levels in terms of technology and project management. Each brainstorming group will be headed by a member of the project team that has been briefed on the project at hand and has reviewed the information presented in the surveys.

The main questions that need to be answered are all encompassing efforts involved with project information, collaborating and sharing pertinent information so that the university has a viable system for keeping information secure but at the same time available for all students, faculty, and professors to access.

· Who is the target audience based on the results of all surveys and brainstorming sessions?

· What is the timeline for implementation of work that needs to be done on the project?

· When will the time for information gathering stops, and project development begins?

· Where is all of the project development taking place? On campus ground? Will students be actively involved with the development and implementation of the school’s own system?

· Why, is a question that comes to mind. Why is the project necessary? This will not only provide a learning experience for students currently attending, but will also provide the school with a much-needed upgrade to its processes.

(John Homberg and Sean Austin – Sunday, 07 April 2019

Section 3 - System Components and Design Requirements

Based on the elicitation results, finalize the system components and design requirements that are needed for your business case.

The information and management systems that are essential in my company, Education Information System which is concerned about provision and care of large-scale information on education and technological systems. For this my business case, the system components that will be required include the hardware, software and the interface, (Guanfu & Ershun, 2018)

a) Hardware

My business hardware configuration in concern with information and management will have these components are the entry data overview devices which will help run the information.

My business will also have one LAN network which will allow the interconnection of all devices in the company. I will also ensure I have units that hoard information It is also necessary to implant Information display equipment.

b) Software

Software applications are also necessary for designing an appropriate EIS. The elementary software needed for my business case are; graphics software, basic software-text, and database.

c) Interface

I believe that an interface is an Executive Information System that will be necessary for my management and information company. This must be designed to ensure that the information presented is comprehensible and easy to make an interpretation, (Walls, et al., 2015). This interface is necessary for representing the component of contact between us as the users and the relevant information stored. This will aid my business in that the individual who relates to the information will be capable of monitoring the processes and receive the response needed for decision making. I need the exit-allows users to see the consequences of their interface with the input system.

The system design requirements for my business case will require that the designer will have to take the following strategy decision.

a) Development procedure: this is the innovative stage that allows both the customers and employees to come up with strategies.

b) System advancement technique: Any way to deal with the framework improvement operational versus utilitarian, Accounting versus examination, database versus different databases c) Resources for framework advancement: concentrate on the inside users versus outsider. At this point, the design should be meant for the improvement and the utilization of bundles, (Collins, et al., 2015).

d) Manpower structure: Analyst, software engineer expertise and ability. Plausibility studies can influence arranging of MIS, the equipment and programming which is chosen for MIS plan ought to be in fact sound and modern, determination of legitimate equipment and programming ought to be a piece of key dimension choices.

Does the design solution support all the customer needs?

Yes, this design is meant to be customer-oriented, in that it focusses mostly on the needs of the customers. The development procedure allows the client to be free to comment on the ways in which the company can develop according to their point of view, (Davis, et al., 2018). The system advancement method is meant to make the customer work easy and understandable. The resource framework is meant to reduce the amount of data that our customer will be incurring when looking for information regarding our company.

Provide specifics that the proposed application should address

The UI idea incorporates intuitive viewpoints that encourage framework task and connection with its segments

Teachers, this proposed business idea is meant to address the teacher in that it will be easier for them to access information regarding the curriculum and the management board at large, (Alvarado, et al., 2018). 

Board of management, this idea is meant to attract the board of management in schools or learning institutions to inform them about any changes regarding information, the new technology, and the new management methods.

Learners; this system is meant to also target learners in all educational institution. This system is meant to provide the necessary information regarding research, new software and efficient hardware for their studies.

(Charles Williams- Wednesday, 10 April 2019)

Section 4 - Methodology for Application Development Process

Through collaboration we will see our final successes come to fruition. With this in mind the methodology that best suit our needs, and has proven successful for our previous development, and will continue for the foreseeable future as a successful system is the Spiral Methodology. At EIS we have entrusted our software development to Spiral methodology, in this marketplace it has proven the most successful and the most decisive when it comes to risk and in being able to maintain trust with our project sponsors and team members. Our focus continues to rely eliminating risk and being able to deal with risk as it arises while we develop our ever-expanding system. We strive to be agile enough to handle any challenge that take place and being able to handle any hurdle leads us to need the benefits that come from a methodology that the Spiral Model brings. In essence what the Spiral model does for our development rests heavily on the ideals of designing a great product.

We invest the time and resources into the planning stage of our system which include a strong initial outline of the goals of our desired outcome. Utilizing the session in which our outline is developed we then move into a preliminary design and prototype. Utilizing our first prototype to try and understand the needs our software is attempting to mitigate we have a team session and utilize our collaborative environment to really understand the direction of our project. From this point after our first prototype is developed, we move into the stage of our second prototype. When we plan the stage of our second prototype, we are given the chance to make any changes in our direction. What worked and what didn't, as well as, during the development or our first prototype did something new occur in the market. After the second prototype is completed, we partner with our project sponsors. Numerous trials are completed and

any feedback is recorded and changes are notated. At this point the project sponsor, in collaboration with our team at EIS, will decide if we continue with the project. This is to mitigate risk and to make a determination regarding to continue or to abort. Some of the risk factors would entail the budgetary concerns or the risk of a poor final product. We produce a third prototype based on these meetings and trials and continue until we have a product that meets the conditions of the sponsor and our team. As a company we will also allocate resources and a dedicated team invested in the maintenance of the program and a team that is available to handle any need that arises. (Matthew Serdy – Sunday, 07 April 2019)

Section 5 - Complete Features and Trade-off Analysis

Section 6 - Milestones and Deliverables Based on Date and Dependencies

Section 7 - System Architecture Aligned with System Requirements

Section 8 - Technical Design Document

Section 9 - Design Review Checklist

Section 10 - Testing and Deployment

References

Software Engineering | Requirements Elicitation. (2018, April 09). Retrieved from https://www.geeksforgeeks.org/software-engineering-requirements-elicitation/

Alvarado, D., Bailey, E. I., & Carver, W. R. (2018). U.S. Patent No. 9,880,592. Washington, DC: U.S. Patent and Trademark Office.

Collins, N., Theurich, G., Deluca, C., Suarez, M., Trayanov, A., Balaji, V., ... & Da Silva, A. (2015). Design and implementation of components in the Earth System Modeling Framework. The International Journal of High Performance Computing Applications19(3), 341-350.

Davis, W. S., & Yen, D. C. (2018). The information system consultant's handbook: Systems analysis and design. CRC press.

Guanfu, S., & Ershun, Z. (2018). Research and Development of Components Geographic Information Systems [J]. Journal of Image and Graphics4.

Walls, J. G., Widmeyer, G. R., & El Sawy, O. A. (2015). Building an information system design theory for vigilant EIS. Information systems research3(1), 36-59.