Client Server Architecture For Information System

Design Architecture

Discuss about the Information System of Client Server Architecture.

The information system proposed for the Willowbrook School would be based on the Client/ Server Architecture because the school remains in scaling mode as there might be modification in the school system from time to time. Three-tier client-server architecture is the best option for the information system.

Three-tier Client Server Architecture consists of the three main layers: Presentation Tier, Application tier, and Data Access or Database Tier. Each tier is separated from one another on the basis of complexity of users and how the data is being used which is there in the database. At the database tier, database is resided with its query processing languages. At application tier, usually the programs and the application server that make use of databases are resided. An abstracted view of database is presented at this tier i.e. any end user is not aware of the database at this tier. At the presentation tier, operation is done by the end users on this tier and they are unaware about the existence of database (Curtis, 1989).

Development process will be facilitated by the three-tier architecture. The advantages of the architecture are as follows:

• Only Presentation logic will be contained in the Client Program. Therefore, it can facilitate the scaling process.
• Security is increased using three tier client server architecture.
• Performance is superior for mainly medium to high volume environments.
• Client workstation does not require much of the resources and there are enough resources available for the server for addressing the request of client.
• Data traffic is reduced on the network due to which school can be able to address more number of requests in lesser time.
• Support cost provided by this architecture is comparatively lower.
• It has a hidden database structure i.e. requesters cannot see the actual structure of database.
• Since, all the components are independent and can be modified separately; therefore, the modification in on tier does not affect the modification in another tier.

The disadvantages of three tier architecture are as follows:

• Additional tools will be required to increase the performance if the volume goes high.
• There is a lot of difficulty to implement the complex business rules.
• Changes made in the business logic do not reflect in the server automatically. So, for reflecting the changes, there is a requirement for new client side software.
• There is no profit provided to the other database server platforms.

School is able to expand or shrink its scaling process with the help of client/server architecture. As much as branches of the school increases, school can be able to adjust the number for clients and also the processing functions can be easily managed instead of altering the capability of the large-scale central server(Curtis, 1989).  Using Client/Server, it is easy to reduce the network load and to enhance the response times.

Hardware Requirements

Hardware components which are required for the system are as follows:

• Database Server such as SQL, Oracle, Informix etc.
• Web Server such as Apache, IIS, Nginx etc.
• Application Server Glassfish, WebSphere, WebLogic etc.
• Router such as Cisco 800, Cisco 827 etc.
• Access point for the internet.
• Computer system.

System Design Specification is a document which is used to contain the information which is required to develop the system.

Outline of the various modules/components:

The system for the developed system architecture has been categorized mainly into three components i.e. Student, Teacher and School administrator. Key modules for these components are as follows:

• Main Module
• Login
• School Administrator
• Managing the details of the students.
• Managing exam schedules.
• Managing the details of the staff/teachers.
• Managing the details of payment.
• Managing the fees of students.
• Teachers/Staff:
• Managing the details of students.
• Managing the marks of students.
• Managing the question papers for exams.
• Managing the syllabus and lectures.
• Managing the subject details.
• Student
• Managing the details of the students which are entered by students in the system.

The dependencies between different modules are described as follows:

All the modules described above i.e. Students, staff/teachers and School Administrator relies on the single module i.e. the login module which provides various services to them. On the basis of login, users have been classified as (Dennis, Wixom and Roth, 2012)

Unregistered Users:

Cost-Benefit Issues

These users are the guest users who can just view the information about the school given on the site.

Registered Users:

These users are the authenticated users who are registered and can access all the services offered on the site. Registered users can be school administrator, staff members/teachers and students. New user can be created by signing up and approval is done by school administrator.

User Interface Issues

User Interface Issues are classified into the two types:

• One for User
• One for Administrator

• Element Name: Login Module

Purpose of this login module is to provide entry to the registered users in the system. Only authorized users are allowed to access the system. There can be two types of users for this module: Registered Users or Guest/Unregistered Users. User must have the connection of internet to access this module. When a user logs in to the module, first of all, user gets connected to the server of company and by checking the credentials of login, entry is allowed by the servers in the system (Howe, 2001).

If the user logs in as the registered user, then user is redirected to the page for which the user has privileges. If user is new and wants to create account, then user will be redirected to the registration page. Data of the login module would be stored in MySQL database.

• Element Name: Managing Student

Purpose of this module is to allow user to manage the details of students. Student can be edited, added or deleted in this module. Details of the student are sent to the server to receive the corresponding response. If staff logs in to manage student data, then details of students such as name, subjects etc. can be modified. Or if student logs in, then student is able to check the assignment given by the teacher or can edit his/her contact details. User must have the internet connection to access the module. New student can be added and data can be stored in the database if the details are correct and are able to pass the business rules. Student can be deleted on the matching criterion. The student data is stored on the MySQL database(Howe, 2001).

• Element Name: Managing the marks of students

Purpose of this module is to allow teachers to manage the marks of the students by uploading them and storing them into the database. Marks of the students are sent to the server. If the staff logs in to the module, then staff can upload the marks of the students. If student logs in to the module, then he/she can view their marks.

Hardware Requirements

Similarly, all the modules can work in the same way as above modules do. Internet connection is must for all the modules discussed.

Application Development Methodology decided for this information system is Structured Methodology (Maciaszek, 2001).

Advantages of Structured Methodology:

• It is easier to understand.
• It is a good industry standard.
• Milestones of methodology are unique and can be easily tracked.
• It is a mature type of methodology.
• Requirement validation is allowed in this technique.
• It follows the specific structure.

Disadvantages of Structured Methodology:

• Since it is process-oriented, therefore non functional requirements are avoided in this technique.
• There is less involvement of direct management in this technique.
• Since it is non-iterative, therefore a single modification would cause the system to restart the entire process.
• This technique has no other tool than DFD to measure the progress.
• User’s requirements are not always implemented(Maciaszek, 2001).

Advantages of Object-Oriented Methodology:

• System development is simplified using this technique in comparison to other techniques.
• Robustness and code reuse are enhanced.
• Because a clear mapping is provided between the real world entities and the corresponding objects, therefore it helps in enhancing the understanding of design.
• Since analysis phase does not get separated from design phase, so users have a high level of communication between them.

Disadvantages of Object-Oriented Methodology:

• The techniques emphasizes mainly on the code.
• Object Methodology has been more focused.
• Transforming the traditional SSAD to OOAD is very complex and more time consuming.

Advantages of Agile Methodologies:

• In Agile, Customer Satisfaction is provided through rapid, continuous delivery of useful software.
• Main emphasis on people and interaction rather than focusing on processes and tools.
• Face-to-Face Communication is the best method to discuss about the progress of the project.
• Scrum meetings are arranged on daily or weekly basis.
• Changing requirements are always welcome.
• Attention to good design and excellent technology is given.

Disadvantages of Agile Methodologies:

• Less focused on designing and documentation.
• Decisions can be taken by only senior programmers during the development process i.e. there is no importance of newbie programmers.
• High degree of uncertainty.
• Project can easily get taken off the track if customer is not clear that what final outcome is needed by them.

Types of testing which are performed for this proposed system are as follows:

• Unit Testing:

Unit Testing refers to testing a single or individual module at a time. Execution errors are eliminated which may terminate the program and logical errors are also eliminated.

• Integration Testing:

Integration Testing refers to testing a combination or group of modules combined at a time. There are further many types of integration testing such as Big-bang Integration Testing, Top-Down Approach, and Bottom-up Approach Integration Testing

• System Testing:

System Testing refers to the testing which is performed on the whole system i.e. whole system is tested. System is tested to assure that the system meets up with all required specifications and all required features are there in the system.

• Test Data: Test Data can be any live or sample data that is used for testing all the components of system whether it is related to validation or verification.

Training Plan:

In this information system for school, there will be three groups of users who require training. The groups of users are as follows (Howe, 2001):

Users (Teachers/Staff, Students and School Administrator) :

This group of users would be trained on the following topics:

• Overview of system i.e. flows of the information on system.
• Key terms related to system.
• Starting up and shutting down the system.
• Duties and Responsibilities towards the system.
• Main menu and further submenus.
• Frequently asked questions.
• Troubleshooting help.
• Handling problems.

Management:

• Origin of project.
• Business goals.
• Controlling changes in system.
• Training to users.
• Enhancement of reports.
• Cost Analysis.

Support:

• Documentation of system.
• Architecture of the system.
• Issues related to logging and resolving.
• Support of vendor.
• History and Justification of Project.
• Training for IT members.
• Training for user and management.

All the trainings discussed above may perform in in-house only; there is no need to perform training at vendor-side.

Data Conversion of the activities can be incremental as well as iterative.  Incremental approach is followed when the current system data has to be converted into the file system. Else if, the data has been completely transferred in the new system, iterative approach works.

Data Entry is done in the following way: First of all, the information related to school is entered. Then, the branches of school if any are entered in the iterative manner i.e. data related to branch i.e. its name, city, address, contact number etc. are entered. Different programs and subjects offered by the school are entered. Then data related to staff and teachers are entered. In the data, system stores the details of students. Data of students should be handled securely as it contains the sensitive or confidential information such as their contact and payments details. If the information of students are stolen, then it might lead to problem. During automated conversion process, some documents are to be handled such as missing files, missing field values, failure in automated editing, and data which requires manual validation(Howe, 2001).

System Changeover Approach

For this given scenario, school does not have enough budgets to manage the high costs of changeover method except for the Direct Cutover. Since IT team has to operate and maintain one system at the time, therefore, it is recommended the least expensive changeover approach. Using this approach, old system starts working as soon as the new system comes to work.          Abnormal errors may occur but they can be handled easily because of the simple implementation and development. As the school is not compatible with the old system, therefore this approach is only bet best option for the school system. It is difficult for the school to implement the parallel and other changeover techniques to implement for the school information system.

Conclusion

The analysis has been on an information system designed for a private school named as the Willowbrook School. The analysis report covers the type of system architecture the system will have, its advantages and disadvantages, system’s physical and network topology, system design specification for the system, type of application development methodology the system will have, what type of testing will be done and how training will be given to different users of the system. Therefore, the report covers all the aspects related to the school system.

References

Curtis, G. (1989). Business information systems. Wokingham, England: Addison-Wesley.

Dennis, A., Wixom, B. and Roth, R. (2012). System analysis and design. Hoboken, NJ: John Wiley.

George, J. (2004). Object-oriented systems analysis and design. Upper Saddle River, N.J.: Pearson Prentice Hall.

Hoffer, J., George, J. and Valacich, J. (1999). Modern systems analysis and design. Reading, Mass.: Addison-Wesley.

Howe, D. (2001). Data analysis for database design. Oxford: Butterworth Heinemann.

Kroenke, D. (2009). MIS essentials. Upper Saddle River, NJ: Prentice Hall.

Marmel, E. (2004). Microsoft Office Project 2003 bible. New York: Wiley.

Maciaszek, L. (2001). Requirements analysis and system design. Harlow, England: Addison-Wesley.

Valacich, J., George, J. and Hoffer, J. (2001). Essentials of systems analysis and design. Upper Saddle River, N.J.: Prentice Hall.