Professional Skills For Systems Analysis And Implementation

System Architecture for Willowbrook School

Discuss about the Professional Skills for Systems Analysis and Implementation.

Willowbrook School is a small private school that wants to retain their services as the system analyst in order to assist the development of new information system to do administrative as well as financial works. The system analyst should develop IT solutions for their businesses. The Director of the school, Victoria Owens discusses the possibility to set up a computer system in order to handle both administrative as well as financial tasks.

The report is based on designing system architecture for Willowbrook School with its proposed physical as well as logical network topology. It gives the list of the hardware required to design the system architecture. A well-proposed system design specification document is prepared which is helpful to design the application development methodology. A test plan as well as used data set is given. A training plan is also given based on the needs of the user groups. A data conversion and system changeover are well developed based on the proposed information system for the school.

System Architecture for Willowbrook School

Justification for the proposed system

The proposed new information system for Willowbrook School is based on the client server architecture. A three-tier architecture is considered to be the best option as the school is always within a scaling mode. The proposed information system is structured simple, and its three-tier should be useful for the process of development (Bajdor and Grabara 2014).

Client Server Architecture
Basic Architecture	The basic architecture of the proposed system is very flexible.
User environment	It empowers the user to improve the productivity of Willowbrook School.
Options for processing	The data processing can be shared as well as configured in any of the way (Yan et al. 2014).
Options for data storage	The data are placed close to the users.
Integration of hardware or software	The integration of both hardware, as well as software, is flexible.

Figure 1: Three-tier client server architecture for Willowbrook School

(Source: Vieru and Rivard 2014, pp-384)

The client system is useful as it contains the presentation logic and therefore it is helpful for the scaling process. Few resources are required for the client workstation. More resources for the server are required to address the request of the client (Davenport 2013). The server can address the requests of the clients with efficiency. For the Willowbrook school information system, the above system architecture is useful as it uses to reduce the data traffic on the network that allows the school to address requests within a shorter period (Arvidsson, Holmstrom and Lyytinen 2014). Due to business logic, the performance is high, and the database is physically closed which reduces the waiting time of the clients. It also lowers the initial as well as maintenance cost of the business operations.

Due to the implementation of the proposed information system within Willowbrook School, the changes within the business logic cannot be reflected on the server automatically. These new changes require distribution as well as an installation of the new client side software (Dingsoyr et al. 2012). The data those are generated by the use of the system are not ported to other database platforms. Therefore, the performance of the server is poor if the volume of request becomes too high.

Advantages of the proposed system

Cost-benefit issues of file and client server design

The cost-benefit issues are that it reduces the network load as well as improve the response times (Olsson, Bosch and Alahyari 2013). The expansion of the network as well as its maintenance is easy. Even the alterations of the ability of the large-scale central server are not required for the new information system.

Based on the architecture of the proposed information system of Willowbrook school, the physical, as well as logical network topology, is the bus. This bus topology contains the main run of the cable with the terminator at each of the end (Dingsoyr and Moe 2013). All the nodes such as the server, workstations as well as microcomputers are connected with the linear cable. The advantage of this linear bus topology is that it easily connects with the computer to the linear bus. It requires less cable length as compared to other topology (Simpson, Schraeder and Borowski 2015). The physical bus topology is the oldest network topologies that are associated with the Ethernet environments implementing the co-axial cables. As the bus topology is a distributed environment, therefore there is no single point of failure. The bus topology is the cheapest way to connect the computers in order to form a workgroup.

Figure 2: Logical and Physical Bus Topology

(Source: Simpson, Schraeder and Borowski 2015, pp-17)

List of the hardware

Serial Number	Hardware required for the proposed information system
1	Database server
2	Router
3	Web server
4	Application server
5	Access point for the internet
6	CPU
7	RAM
8	Networking hardware

System Design Specification Document

Purpose of the Document

The purpose of this document is to store the system design specifications details of the new information system for Willowbrook School. The new system should track the enrollments of the students, tuition, and payment as well as aftercare billing. This document gives the scope of the new information system with an overview of the components, modules, system design, structure and relationships, user interface issues and the schedule. It helps the project team to carry forward the implementation process within the school.

Scope of the Development Project

With the use of new information system, it creates customizable reports in the system and then eliminates the requirement to export the data into the external spreadsheets. The complete documentation is done in the system and eliminated the use of Word documents. The new information system monitors the account for tracking, reporting as well as reviewing the costs. It has the capability to review the individual transactions of the students with full details information within balance for more efficiency cost analysis (Hsieh and Lin 2016).

Overview of the Components/Modules

In the proposed information system for Willowbrook School, it consists of three components such as teachers, administrative as well as students. The key modules of the three key components are: After login into the information system, 1. School Admin manages the details of the student and the payment process. 2. Teachers manage the details of the exam as well as a subject within the school campus. 3. The students manage the details of the subjects and amount of the course fee managed by the system.

System Design for the Information System of Willowbrook School

The system is designed using the hardware such as database server, router, web server, application server, an access point for the internet connection, Networking hardware, CPU, and RAM. The physical and logical network topology based on the system architecture is bus topology. The proposed system is based on three-tier client server architecture. The three parts of the three-tier design consist of the client application, server application, and database related to managing the student’s details. This system architecture makes easier for the school to evolve the application as per the needs as well as opportunities for Willowbrook school. The existing system is permanently retained with the use of new three-tier architecture.

Structure and Relationships

There are some dependencies among the modules such as: All the students, teachers as well as school administration depend on the login module. There are two types of users within the login module such as: 1. Registered users: The users those have already registered with the school. 2. Unregistered users: Those are the guest users.

User Interface Issues

There are two of the interfaces within the implementation of the information system are the users as well as the administrator. It has a little learning curve, and it is easy to use. The login module allows the users to protect access to the data (Bowen and Hinchey 2012). After the preliminary investigation on the entire system design, the users and management teams can deliver both times as well as a cost estimate for the entire implementation plan.

Proposed Process

Component: Login 1.      Identification of the user 2.      The purpose is to entry the registered user within the system. 3.      The function of the component is to allow the authorized user to access the information system. 4.      Firstly, the user will connect to the client server of the school where the user will authenticate through a token. 5. Depends on the data of login; the server allows the user to access the system. 6. In order to perform the financial as well as administrative tasks, the user must have an internet connection. 7. The most important are that server authentication is needed to prevent the data from used by any unauthorized person. 8. My SQL database is also required within the system.

Application Development Methodology for Willowbrook system

The management team of the Willowbrook School uses agile software development methodology to plan, create as well as deliver the system. This methodology promotes continuous iteration of development as well as testing through the development of the software life cycle of the project (Gandomani et al. 2013). With the use of agile development methodology, the project requires handling the existing requirements to best suit with the requirements of the project. Within the agile development methodology, the tasks are to be delivered with specific features for the release.

Advantages of Structured Approach

The advantages of the structured approach are as follows:

• Reduces the complexity of the new information system
• Focuses on the ideal or logical system
• It provides with a future orientation of the new information system (Leau et al. 2012).

Disadvantages of Structured Approach

The disadvantages of the structured approach are as follows:

• If there are any changes in the requirements of the new system, then the system analysis should be done again (Wasson 2015).
• Using the structured approach, it takes a lot of time as well as money for the Willowbrook school in order to analyze the system.
• If there are huge changes within the system, then the staffs should be given training that is also wastage of both times as well as money (Valacich, George and Hoffer 2015).

Advantages of Object Oriented Approach

The advantages of the object oriented approach are as follows:

• The object-oriented approach reduces the cost of maintenance as most of the procedures in the system are to be summarized; the system behaviors are reprocessed as well as incorporated into new behaviors (West, Nanz and Meyer 2015).
• It improves both reliability as well as the flexibility of the system. As the objects are accessed dynamically, then new objects can create anytime.
• This application is scalable as the object interface provides with a roadmap to reuse the object within a new information system.

Disadvantages of Object Oriented Methodology

The disadvantages of the object-oriented approach are as follows:

• The challenges of this approach are that in the conversion of the legacy system, it builds within the structured programming languages (Dennis, Wixom and Tegarden 2015).
• It is difficult to reduce the effects of the structural systems on the new information system.

Advantages of the Agile Development Approach

The advantages of the agile development approach are as follows:

• An agile methodology is a realistic approach to the development of the software.
• It promotes teamwork as well as cross training (Dyba and Dingsoyr 2015).
• The requirements of the resources are minimum.
• This methodology enables concurrent development as well as delivery in an entire planned manner (Givoni et al. 2013).
• This methodology is to be divided into individual models that the team members work on.

Disadvantages of the Agile Development Approach

The disadvantages of the agile development approach are as follows:

• This methodology is not appropriate for handling of compound dependencies.
• It has the threat of maintainability, extensibility as well as sustainability.
• This methodology has a high individual dependency, and therefore it requires minimum documentation generation (Hsieh and Lin 2016).
• Due to lack of documentation, transmission of the technology to the new team member is moderately challenging.

Disadvantages of the proposed system

Willowbrook uses the application testing for their new information system. The school is not keeping anything from the old system except the hardware. The staffs those are presenting for the testing plan will be any staff those are using the new system as well as a team of quality assurance (Stephens et al. 2015). Firstly, unit testing should be completed. During this phase of testing, the team runs in order to identify the errors. After the correction of the error, an integration testing should be completed. The two phrases for the system are fixed billing phase as well as aftercare phase (Galliers and Leidner 2014). After the testing of each of the phrase separately, the phrases are to be integrated as well as tested together. The integrated system is functional, and this new information system is tested using the current system of Willowbrook School such as the operating system, computers as well as networks (Givoni et al. 2013). The testing of the system is to be done for checking the compatibility of the system. Lastly, the system is tested using the similar data to what the Willowbrook School is using. After completion of the necessary testing of the new information system, the staffs are trained to handle the system. After the training of the staffs, another testing is to be done by the staffs to make sure that they understand the system as well as its functionality.

The new information system requires training of the staffs. The training should be based on site as well as within small groups. The user groups of the Willowbrook School are categorized as follows:

Essential staffs: The essential staffs such as Kathy, Susan and others require training on the entire system. If they are trained on the entire system, then it allows the other staffs to seek assistance from them before they are calling for the support (Simpson, Schraeder and Borowski 2015). The topics those should be covered within the training procedures are requesting enhancements, reports as well as user training.

Teachers: They have required training on the topic such as startup as well as the shutdown of the system. It also requires training on the topics such as the major functioning of the system, menus as well as troubleshooting.

Volunteers: They are trained on the working as the volunteer. The Willowbrook School requires the volunteers those assist them with fundraising. They should be trained on the aspects of fundraising of the system. The volunteers are trained by both Kathy as well as Susan.

Cost-benefit issues of file and client server design

Data Conversion and System Changeover

Data Conversion

The excel data of the Willowbrook school should be exported into the new information system. All the data are to be exported into the proposed system. The information of the student are the most important data that are required to enter into the system (Schadow 2013). Once the data of the student is entered, the monthly billing of the particular student is also entered. The data those are entered next are the parent data, information of the block, lastly attendance of the student. 

Categories
Data entry order	Student	Billing	Parent	Block	Attendance
1	Name of the student	Pay dates	Household Number	Year	Information of Student
2	Student Number	Information of Student	Information of Student	Student Number	Block ID
3	Fixed fee	Bill dates	Contact Number
4	Household number
5	Information of Parent
6	Contact Number

System Changeover Method

Willowbrook requests a direct cutover method that is timed around the academic year. Willowbrook school uses a schedule for their billing purpose is: the fixed fee billing is to be completed in April as well as begins in the month of July. The drop-in aftercare billing does not end until the second week of June. Therefore, this period allows the system to be installed as well as functional in the month as well as half. The school uses the direct cutover method for the system (Schadow 2013). However, due to a use of this method, significant issues are raised within the system. The allocation of time in order to complete the changeover is not a significant amount to be tested as well as corrected the potential issues. Therefore, the system analyst recommends not using the cutover method for their new information system.

The system analyst recommends using the phased operation that would allow the system to install in phrases and allow more time to test the system as well as correct the issues that arise. Firstly, the phase is fixed fee billing for the financial task of the school. The initial phase starts in the month of April after the completion of the first fee bill (Bowen and Hinchey 2012). This phasing allows the system to be installed as well as tested within 1 and half months before the completion of the aftercare billing. After the completion of the aftercare billing, the system phase is being installed as well as tested (Chitchyan et al. 2015). It would allow a timeframe of 1 and half months to have an aftercare billing functional, installation as well as allow the entire system to be tested entirely.

Conclusion

It is concluded that the new information system for the Willowbrook School requires a client server architecture with a three-tier architecture as the school is within the scaling mode. The client application is to be executed on the same computer as it is more efficient as well as effective when the client, as well as server, are executed by a various computer connected with the use of the network. Agile methodology is used as the application development methodology for the Willowbrook system. Phase operation is used as the changeover method for the new system to complete the installation of the new information system for financial as well as transactional tasks. Testing is done to make certain that the new system should assemble the organizational goals of Willowbrook School. Staffs, teachers, and other management members are trained to handle the system to make sure that they understand the system as well as its functionality.

Physical and logical network topology for Willowbrook School

References

Arvidsson, V., Holmström, J. and Lyytinen, K., 2014. Information systems use as strategy practice: A multi-dimensional view of strategic information system implementation and use. The Journal of Strategic Information Systems, 23(1), pp.45-61.

Bajdor, P. and Grabara, I., 2014. The Role of Information System Flows in Fulfilling Customers’ Individual Orders. Journal of Studies in Social Sciences, 7(2).

Bowen, J.P. and Hinchey, M.G., 2012. High-integrity system specification and design. Springer Science & Business Media.

Chitchyan, R., Rashid, A., Sawyer, P., Garcia, A., Alarcon, M.P., Bakker, J., Tekinerdogan, B., Clarke, S. and Jackson, A., 2015. Survey of aspect-oriented analysis and design approaches.

Cooling, J.E., 2013. Software design for real-time systems. Springer.

Davenport, T.H., 2013. Process innovation: reengineering work through information technology. Harvard Business Press.

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

Dingsøyr, T. and Moe, N.B., 2013. Research challenges in large-scale agile software development. ACM SIGSOFT Software Engineering Notes, 38(5), pp.38-39.

Dingsoyr, T., Nerur, S., Balijepally, V. and Moe, N.B., 2012. A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software, 85(6), pp.1213-1221.

Dyba, T. and Dingsoyr, T., 2015, May. Agile project management: from self-managing teams to large-scale development. In Software Engineering (ICSE), 2015 IEEE/ACM 37th IEEE International Conference on (Vol. 2, pp. 945-946). IEEE.

Galliers, R.D. and Leidner, D.E., 2014. Strategic information management: challenges and strategies in managing information systems. Routledge.

Gandomani, T.J., Zulzalil, H., Ghani, A.A.A., Sultan, A.B.M. and Nafchi, M.Z., 2013. Obstacles in moving to agile software development methods; at a glance. Journal of Computer Science, 9(5), p.620.

Givoni, E., Ravitz, N., Ravitz, Z., Nguyen, T.Q. and Nguyen, T., Smartesoft, Inc., 2013. Automated software testing and validation system. U.S. Patent 8,347,267.

Hsieh, F.S. and Lin, J.B., 2016. A self-adaptation scheme for workflow management in multi-agent systems. Journal of Intelligent Manufacturing,27(1), pp.131-148.

Leau, Y.B., Loo, W.K., Tham, W.Y. and Tan, S.F., 2012. Software development life cycle AGILE vs traditional approaches. In International Conference on Information and Network Technology (Vol. 37, No. 1, pp. 162-167).

Olsson, H.H., Bosch, J. and Alahyari, H., 2013. Towards R&D as innovation experiment systems: A framework for moving beyond Agile software development. In Proceedings of the IASTED (pp. 798-805).

Schadow, G., 2013. Systems and methods for software specification and design using a unified document. U.S. Patent 8,347,276.

Simpson, J., Schraeder, M. and Borowski, M., 2015. Enhancing the value of training: creating closer time linkages between training acquisition, application and compensation. Development and Learning in Organizations: An International Journal, 29(5), pp.16-18.

Stephens, C., Coventry, L., Welsh, R.J., Sturrock, D.A., Strachan, A., Chiba, M. and Orr, A., Lifescan Scotland Limited, 2015. Analyte testing method and system. U.S. Patent 8,958,991.

Valacich, J.S., George, J.F. and Hoffer, J.A., 2015. Essentials of systems analysis and design. Pearson Education.

Vieru, D. and Rivard, S., 2014. Organizational identity challenges in a post-merger context: A case study of an information system implementation project. International Journal of Information Management, 34(3), pp.381-386.

Wasson, C.S., 2015. System Engineering Analysis, Design, and Development: Concepts, Principles, and Practices. John Wiley & Sons.

West, S., Nanz, S. and Meyer, B., 2015. Efficient and reasonable object-oriented concurrency. ACM SIGPLAN Notices, 50(8), pp.273-274.

Yan, Y., Xiong, S., Lou, X., Xiong, H. and Miao, Q., 2014. Design and Implementation of Educational Administration Information Access System Based on Android Platform. In Frontier and Future Development of Information Technology in Medicine and Education (pp. 2525-2533). Springer Netherlands.