Thursday, September 2, 2010

Enrollment Input Form (PRF) and the Enrollment University Interface

The enrollment input form (PRF) which mainly use every semester such that students merely write out the information needed. Data inputs such as name, gender, section, ID number, types (if you are old student or new and if you belong to a day or evening class), subjects to be enrolled (consisting of the code, title, description, unit, day, time and room), course, year, school year, the scholarship organization, semester, and the student’s address are the all needed information for the enrollment. As we will observe the PRF, the structure is truly a simple paper with computerized labels of identification. Actually, it serves as guide for encoders of the real enrollment input form which is an automated system is used. This basically acts as the finalization of input that will also be the basis of the registrar.

I find the enrollment university interface is structurally the same as of that the enrollment input form such that I have a glimpse of it during the enrollment. I can say that a draft is never a “nothing” to the co-existence of an automated system because as I believe the draft is the beginning of an idea wherein automated system builds that idea. Considering the fact that until now, we are still using the both and not just the other one alone. The mere fact stressing that those come first in existence or the common thing people got to do when making systems is by starting with a scratch, thus, can be use as basis or if you want to understand the system (automated), you can as well trace back to where it starts. And we all know about that!

I already observe this kind of a situation even when not talking about the enrollment input form (manual or automated) such when I do programming. Before I coded the program, I would first visualize the image since I cannot do it by mere imagining. Mostly, we will get a piece of paper and pen then structures the output of the program. What I realize about it when I have read the question is that I kind a found that I have done a proper way of doing my program. If one will try on their own without considering having a draft for their program, how will they code it without having any guide? For sure if one can do it, basically the mind is good in visualization. Truly, its kind a hard to do that, seriously! So, from the situation I have cited, may someone appreciate and find the real importance of just a single draft though it is something meant to forget because there are new things that is good in the eyes, still it contributes more to what have now being implemented.

For the encoder’s part when inputting data, I said a while ago that he or she is guided by the PRF. Come to think of it that students are the major users of it. Students were asked by advisers to write down information being asked on the PRF because what has been written is what would also reflect on to the enrollment system interface. Encoder will just record the information needed then as it finishes, the encoder will just put the PRF on the trash. Simply because the data has already been stored and what has been stored in the system (automated) will automatically record on the database itself, in other words final.

Since I have already pointed out the structure of the system (manual and automated), I come to think about the appearance, how labels are arranged and used. I find that both systems appear to be the same; they are just unlike on the arrangement of labels. To sum it up, still both have the same meaning; they are just different on how they are organized.

What I learn about contrasting and discussing the enrollment system (manual and automated), we tend to understand certain things by midst of comparison. And I think it is not bad since from that experience or situation, a person way of approach especially when it comes to making system, do not depart from what is really intended. Though certain things are put into detail still the relation of one component to another must be as one and that is meant for the system itself. Taking an example of filling up an application where an automated system do not coordinate with its draft or works the other way around. It means to say that the structure of the application system is really different from the draft that is being filled up. Considering that kind of a scene, the application form just turned out a waste because what is a sense of having a form that electronic form itself cannot follow. I just want to point out that drafts are guide and by means of a draft, the electronic system will get the information from it. If ever the information needed and structure of input from the draft is the same, therefore, there is nothing wrong with it. With the fact that the two means of storing or getting information were the same then mistakes or falsification can be avoided. That is for sure the big reason I can merely say why it is suppose to be the same. I do agree with the idea of using both since both were just helping each other and without the other one, the process would really be difficult to handle. In other words, the other feels empty without the other ones presence.

To sum it up, everything in the world of work, a draft is always being put into first since ideas are all started here. The draft when planned, some would meant it will be successful in terms of giving service to people. The product would not have been achieved if it was not been planned that well in a draft. In other words, the sharing and binding up of ideas is in the draft itself. We all know that when new things will come to take part or improve the work of draft still the way of having it is like a tradition that will never fade forever.

ACCION, HONEY LYNNE C.
BSCS-4

blog: