4.5 Input Specifications
The Input specification and design of the student information system is for students and
lecturers to navigate in various interfaces of the system to undergo their school activities online. The design network requires the following for new users:
The user shall input the necessary information in the tab labelled “Student†or “Lecturer†in the system’s interface. The system has five (5) types of data in which the operator must input to access the system.
a. The first and second fields are designated the first name and last name. A string of characters shall be the type that will be required.
b. The Email of the user shall be the third type of information that the operator must input. This Email must be in the format of text.
c. The password is the fourth set of fields in which the operator shall input information.
Two fields exist under “Passwordâ€. The first is for the main password while the second is a text field where the operator shall retype the password
4.7 Choice of Programming Language
Advantages of AngularJS over other frameworks for the front-end. (Gutierrz,2007)
a) It is supports two-Way data binding: The two-way data binding is probably the coolest and most useful feature in AngularJS. In a simple way, data binding is the automatic synchronization of data between your view (HTML) and model
(JavaScript variables).AngularJS templates are created and binded in different components with specific models. So, whenever the model value changes, the view is automatically updated, and whenever the value of any view component changes (e.g. input text value) the bound model is also updated.
b) Routing Support: It supports Single Page Apps (SPAs) where everything comes in a single page. With AngularJS Single Page App can be implemented very easily with minimum effort. In fact, AngularJS was built with these things in mind. You can basically create different views for different URLs. AngularJS will then load the appropriate view in the main page when a specific URL is
requested.
c) Structure front end code: As web developers, sometimes we do not consider
any structure or pattern while writing client-side code. It’s just us and the browser refresh button until we get things working. But for a long run, we have to follow some structure which will save the maintenance nightmare.
d) Templating with HTML: AngularJS uses plain old HTML as the templating language. The workflow becomes much simpler with plain HTML as the templating language, as the designers and developers do not have to depend on each other. Designers can create user interface in the usual way and developers can use declarative binding syntax to tie different user interface components with data models very easily. For example, you can use an expression like
{{address}} to display an address in HTML.
e) Teach HTML new syntax with directives: A directive in AngularJS is what tricks HTML into doing new things that are not supported natively. This is done by introducing new elements/attributes and teaching the new syntax to
HTML. For example, with the help of directive we can create a new element and wherever we use this tag, it replaces the tag with a map.
f) Embeddable, testable, and inject able: One of the nice things about AngularJS is that it is a good team player. You can easily embed an AngularJS app within another app. AngularJS never requires full commitment. You can use it along with other technologies very easily. When you’re unit testing your app during development, you are fixing bugs right away, which you would have otherwise encountered unexpectedly further down the line. The Angular team built a plug-in for the Google Chrome browser called Batarang that improves the debugging experience for the applications which build in Angular.
g) Powered by Google and an active community: AngularJS is currently being maintained by the awesome developers at Google. Being open source software, the code is released under the MIT license and is available for download at GitHub. You can download the source and see if you can improve something. The documentation is also pretty good, and you can always ask questions on Stack Overflow or the Site Point forums to clear any doubts.
