• Tidak ada hasil yang ditemukan

University Support System

N/A
N/A
Protected

Academic year: 2023

Membagikan "University Support System"

Copied!
58
0
0

Teks penuh

We hereby declare that the work presented in this report is the outcome of the project carried out by us under the supervision of Khadija Islam, Lecturer, Department of Computer Science and Engineering, Sonargaon University, Dhaka, Bangladesh. Although the delivery of the University Support System (USS) may vary between institutions, some aspects of student support should be considered in all e-support programmes.

USS (University Support System)

Knowledgebase

These tools can stand alone and are functionally interrelated and integrated with the support system automation systems. Users who interact with the Support System often form a general perception of the information system group.

Theoretical/Conceptual Framework

Further improvements can be made to the system prototype and will be implemented depending on the time available.

Project Background

Although this is an academic assignment, it is also a live project that can bring real benefits to our group. It is argued that the only way to build a complete scenario of the project is to capture every fragment of detail as early as possible.

Development Methodologies

As such information gathering will be required at the start of each phase to ensure it is carried out effectively and in a timely manner. However, lessons can be learned from the methodology, and being based in Leeds, it is probably a good idea to organize meetings when key decision makers will be nearby; this should help the communication process and ensure that decisions are made by the relevant people. While the approach is generally appropriate for the project at Southtech Limited, it is felt that a prototype may be necessary to gauge initial user feelings about the interface design and system functionality.

Software prototyping allows developers to quickly visualize system functionality. It can be classified as disposable or evolutionary, i.e. the prototype is discarded after it has been demonstrated to the user, or used in the next stage of development.

Summary

The process has the advantage of being able to determine exactly what stage the project is at. For this reason, the general aspect of the Waterfall cycle will be adopted for this project, although it will be modified somewhat in the coding and testing phases. Documentation, system testing, and efficient programming can be bypassed if the final prototype is deemed acceptable to implement by the project sample.

The decision was made to use the best features of the waterfall model with evolutionary prototyping to shape the implementation and testing stages of the project.

System Requirements

Requirements Analysis

Where necessary, the analyst will use a combination of these methods to determine the exact requirements of the stakeholders, so that a system is produced that meets the business needs. Use tools that promote a better understanding of the desired end product, such as visualization and simulation.

Requirements Capture

Research

Requirements Analysis

Use Cases

Functional Requirements

Non-Functional Requirements

Best Practice Guidelines

Confirm with the student that we have accurately gathered all business requirements and, with the student's approval, begin designing and building the application. It can be used by the designers and developers as a reference while building the application. This allows the student to verify whether the final application actually corresponds to what was initially agreed.

Components of System Analysis

User Interface

Obviously, an information systems education will not cover all areas preferred in HCI, but it is possible to pay careful attention to the design of the system to increase usability as much as possible.

Task Identification

Short Term Memory

Execution-Evaluation Cycle

In theory, it should be as easy as moving a pen to the appropriate area on a paper form. While this may not be possible in practice, simply ensuring that the 'Tab' key results in the cursor moving to the next field and not a random space is a step towards a workable system.

Menu’s

While this may not be possible in practice, simply ensuring that the 'Tab' key results in the cursor moving to the next field and not a random space is a step towards a usable one.

System Options

Student / Server Architecture

Any updates to the application also result in a requirement for redistribution throughout the university – far from ideal. While the current architecture takes the load off the server, much more data will be transferred between the student and the server than with a thin student. It is therefore assessed that a transition to a thin-student architecture will entail a number of advantages which must be utilized in the new system.

As Southtech Limited does not have the infrastructure in place to support this style of thin student architecture, a student server approach will be used in the form of a locally hosted intranet site using the existing infrastructure.

Figure 4.9: Current and proposed architectures
Figure 4.9: Current and proposed architectures

Web Technologies

Active Server Pages

Throughout this section a number of options were considered and the decision to embrace the PHP & MySQL platform was made. Although this is not the preferred method of Southtech Limited, the decision was made based on the merits of the technology itself as it is a smaller part of our Tiny Coders group. It is assumed that whatever tool is chosen, there would be something of a learning curve during implementation.

Obviously, whatever method is chosen will result in a learning curve, but the choice has been made because of the qualities the technology brings to the project, not because of an understanding of syntax - this can be easily learned.

Figure 4.12: The execution model for Web architecture
Figure 4.12: The execution model for Web architecture

System Design

System Block Diagram

  • Application Architecture

The application architecture is designed to fit into Southtech Limited's infrastructure, leading to a distributed multi-tier application. Choosing the n-tier route also leads to a number of advantages created by internal infrastructure integration. Although the system architecture is relatively complex, it leads to many advantages for Southtech Limited that will simplify the management of the new system.

Furthermore, unless the application itself is changed, significant improvements to the implementation may be made in the future without the users of the system being aware of the details of those changes (eg, the database may be moved to a faster server; users would not know the details of the change except the fact that their queries had been completed in less time).

Database Modelling and Design

Conceptual Database Design

Logical Database Design

Data Dictionary/Database Files

Data Elements

Functional Design

System Maintenance

With the aim of providing an acceptable user interface that addresses the HCI issues discussed in Section 5.1, a page template has been developed using popular CSS and JavaScript. This design has not included the use of any HTML markup, but instead simply positions the components on the page where they are deemed most appropriate. The page template is divided into five distinct areas, header, menu bar, sub menu, page options menu and main content.

The header and menu bar will remain the same throughout the site and will not change The sub-menu sections and page options will depend on the selected page and the content will clearly be the content of the selected page.

System Implementation Development Environment

It is not entirely necessary for the environment at Southtech Limited to be replicated for the development of the first prototype. For the purposes of the project, the author already had an unused domain name, skiint.com, and decided to use it in this setting. While this may have negative effects on system performance, it is not a release environment and only has one person interacting with it.

As such, the performance issues are not apparent, although it is not a true reflection of the final use of the application, how many users can simultaneously interact with the system.

Data Access

This is beneficial for evaluating the new system because users will have an understanding of the functionality that will exist in the final product as early as possible. Perhaps more compelling than this is that creating the environment for the system to sit as soon as possible ensures that the final product will work within the infrastructure at Southtech Limited without the need for excessive reconfiguration or coding. At Southtech Limited these are usually hosted on different servers, but in this development environment they are all packed on the same machine.

Second, the details of the query are hidden from the application, creating a new layer of abstraction.

Page Template

Stored procedures are used in the MySQL server, so query strings are not required in the code. First, less data is transferred between the learner and the server, so execution is more efficient.

System Function & Outcome

Functional Testing

User Acceptance Testing

Usability Testing

However, it is recognized that interface design is an iterative process and that it is unlikely to address the issues of being able to learn the system quickly and create an intuitive user interface in the first iteration of development. However, by running the tests more than once, it is possible to make judgments about how easy the system is to learn. The test was carried out with a sample of four administrative staff, as they are the ones who require the most functionality and use the system most often.

It can also be argued that they do not have such a deep understanding of computer systems as the support technicians and as such provide a better example for testing the learning aspects of the system.

6. 4 System Outcome

Outcome Interface Log in

Registration

User Panel

Admin Panel

Admin Task

Academic Supporter

Academic Supporter TASK

CONCLUSION AND FUTURE WORK

Conclusion

Future work

This is a complex area of ​​research and will not be discussed further, although, in the final version it is essential that some method is implemented. This is something that is considered relevant and should actually be implemented at a future date. Once implemented, the system can go one step further than any other package on the market by including Remote Control Students such as PC Anywhere, VNC or Microsoft Remote Desktop.

Another option could be to integrate the system with Instant Messaging technology to send messages over the Internet or even via SMS.

Gambar

Figure 4.9: Current and proposed architectures
Figure 4.12: The execution model for Web architecture
Figure 5.2.1: System Block Diagram
Figure 5.1: Application Architecture - UML Deployment diagram

Referensi

Dokumen terkait

Figure 6 Test Case Video Table 2 below is the comparison of first parameter time that needed to process whole video that already made between the application that use a multithreading

Gambar Use Case Diagram Utama 4.8 Diagram Sub Use Case GambarSub Use Case Diagram 4.9 Diagram Activity GambarActivity Diagram 4.10Sequence Sub Use Case Diagram 4.11 Class