I'IFIITIIBIFI UNIVERSITY OF SCIEI'ICE FII'ID TECHNOLOGY DEPARTMENT OF INFORMATICS FIRST OPPORTUNITY EXAMINATION. (Including this front page)

Transcription

1 Fl I'IFIITIIBIFI UNIVERSITY OF SCIEI'ICE FII'ID TECHNOLOGY Faculty of Computing and Informatics DEPARTMENT OF INFORMATICS QUALIFICATION: Bachelor of Informatics and Bachelor of IT in Business Computing QUALIFICATION CODE: O7BA F and 8OBSBC LEVEL: 7 COURSE: Enterprise Web Application Development COURSE CODE: EWD621S DATE: November 217 SESSION: 1 DURATION: 3 Hours MARKS: 1 FIRST OPPORTUNITY EXAMINATION EXAMINER(S) Mrs. Katazo Amunkete and Mr. Eliazer Mbaeva MODERATOR: Mr. Kandetu Tengovandu THIS QUESTION PAPER CONSISTS F 6 PAGES (Including this front page) INSTRUCTIONS Answer ALL the questions. S- F P Nl Write clearly and neatly. Number the answers clearly. All marks are indicated in brackets at the end of each question. The length of the answer/s must be guided by the available mark/s.

2 SECTlON A: STRUCTURE. QUESTlQNS [ll-d Marks] Question 1 Discuss any two [2] elements a Web Application Developer must consider when deciding on the implementation of an Enterprise Web Application. [4 Marks] Question 2 Before implementing an Enterprise Web Application, it is important to have all the necessary stakeholders prepared. Discuss three [3] possible ways to do so. [6 Marks] Question 3 Discuss the three (3) evolutionary stages of the web. [6 Marks] Question 4 Distinguish between server-side and client-side scripting. Provide an example of a technology of each. Question 5 There are three (3) factors that have led to the need for integrating Enterprise Web Applications. State any two (2) of them. [4 Marks] Question 6 Discuss the three (3) ways in which Enterprise Web Applications can be integrated. [6 Marks] Question 7 Describe the role of business processes in Web Application Development. Justify your answer with a specific business process example. [6 Marks] Question 8 State three (3) requirements needed to carry out secure communications over the internet. [3 Marks] SECTION B: SHORT QUESTIONS [1 Marks] Question 9 (a) You have a file called exam1.txt. Provide the commands/functions that would achieve the following: 1. Open the file in read write mode [1 Mark] 2. Close the file [1 Mark] 3. Read a single character from the file [2 Marks] 4 Read the entire content of the file [3 Mark] (b) Write down the command to create a session called examl [1 Mark] (c) What is the significance of the variable specified in the action attribute of the following form tag: <form method="post" actin="$_server[php_self]"> [2 Marks]

3 SEQIlQN C: PRACTHCAL QUESTHONS [35 Marks] instruction: You are advised to comment on your scripts code. Question 1 _ Study the following sql script. Supposing that the database exist within a WampServer environment, design the table view (as it should appear in phpmyadmin) created. Insert into yourtable at least one record. [5 for the table to be Marks] CREBTE DATABASE IF NOT EXISTS Products; USE Products; [ll BCREETE TABLE IF NOT EXISTS orders { 25 order_id INT UNSIGNED NOT NULL AHTO_IHCREMENT, T user_id INT UNSIGNED NOT NULL, 5? total DECIMEL {5,3} NOT NULL, order_date DATETIME NOT NULL, '13: BRIBERY HEX" {order_id} L L i ; Question 11 Produce a php/mysql connect script for the connection to the localhost server and database. Question 12 Write an HTML form code named rders_form.php that could be used to collect data from your users into the orders table. [8 Marks] Question 13 Design a view of your HTML form code in the previous question. Question 14 Write a PHP script called order_prcess.php that can process data captured via your form to the database. On successful entry of record, your script should display a feedback message or an error message in cases where error occurs. [12 Marks]

4 Building SECTHON D: CASE STUDY [15 Marks] Instruction: Read the following case study and answer all the questions below it. Extract from - your own [ERMS by Jason C. Simon Like many successful projects, this one started with a different objective. The Fitchburg State University library Web site had only an alphabetical listing of databases, which was hand coded in HTML. There was a clear need, agreed on by all librarians, to provide subject resources. While the alphabetical list is helpful if a access to these student or faculty member already knew exactly which database they needed. However, because typically most users do not know which database best serves their needs but do know their area of study, organizing databases into subject categories seemed logical. It would have been possible to hand code this information in HTML. While initially easy to do at the outset, many databases suit the needs of multiple subjects. If using this approach, any future updates would also mean updating the same information in multiple places, and would require remembering where each database lived, thus exposing us to the likelihood of inconsistent information. For this reason, I decided that a central database would handle this information more efficiently; all items could be managed from a central location and pages for each subject could be dynamically generated. In the process of building the front end, I realized that it would be helpful to have a central place for managing other information associated with each item which did not necessarily need to be displayed publicly. The database grew to include non public data, including various metadata such as vendor, provider, access information and usage and expense data. As the databases were able to be managed effectively this way, the project was then expanded to include management of all periodical titles, both electronic and in print. Soon other gaps were filled in by including links to data via various vendor application program interfaces (APls). Holdings data for periodicals were already stored by Serials Solutions, so each item could connected via ISSN to these records. Expense data could be pulled directly from Ebsco Invoices based on the Ebsco order number. Fairly soon, I found I was creating a rudimentary electronic resource management system (ERMS). To build a small ERMS, there are of course a few basic skills that are required. The system created for this project was an implementation using open source tools, such as Hypertext Preprocessor (PHP) and MySQL. While there are other options available, in this case, these are what I used. The basic skill set needed includes the following: Understanding of database structure; Basic understanding of Entity Relationship Design; Understanding of your metadata; HTML; MySQL; PHP; and/or Willingness to learn the above on the fly. The last point needs to be stressed, as the only true prerequisite for this sort of project is the desire to learn and to experiment. With only some small level of knowledge of these skills, it is possible to get a start, and build in enhancements as needed. When skills are needed to be learned for the task, they can be attained either through introductory texts or through free online tutorials.

5 The following list includes the materials that I used; however, as mentioned earlier, there are of course many ways to accomplish these goals. All are open source and freely available for download: 9 Local server: For this purpose I used XAMPP, which comes with a self installer and will work equally well in Windows, Macintosh or Linux environments. All that is necessary is to spend approximately a half hour installing and setting it up so as to have a development environment. It comes with MySQL and PHP pre installed. a MySQL: The core of all of the functions and organization of the ERMS will be stored within MySQL. This is probably the most important piece of knowledge. If it is well-structured, any coding required becomes minimal. (Note: there are other SQL systems available; I choose this one because it is free with a large community of support available online). PHP: While there are many languages that one can use, used PHP because it integrates well with MySQL. This tool will enable creating a customizable interface for accessing and managing the SQL database using any Web browser. This will make it possible to manage the data without having to write customized queries each time you wish to add, or manage an item. A database was created and to display the contents of the database in a Web browser, the interface was created using PHP. With a few simple commands we can generate the necessary HTML for each piece of the data. Sample code require_once (../dbconnect.php ); $dbc = mysqli_connect(db_host, DB_USER, DB_PASSWORD, DB_NAME) or die( Error connecting to MySQL server. ); Conclusion This article is, of course, just a beginning, and not intended to be a full tutorial. There are many other aspects such as modifying data and reporting that can be done, but the principle remains the same. Following these guidelines, using just a few simple tools, you can see that it is possible to customize and create an ERMS that will work fairly well for simple purposes scaled as needed. but also can be... END OF CASESTUDY Question 15 Describe the system the University library used before the ERMS was introduced. [2 Marks] Question 16 Discuss the development environment used for the system and the technologies it comes with? Question 17 State two (2) reasons why Enterprise developers choose to use open source technologies. [2 Marks]

6 I Question 18 Explain the code below, line by line (1 3): [6 Marks] 1 require_once (../dbconnect.php ); 2 Sdbc = mysqii_connect(db_l IOST, DB_USER, DB_PASSWORD, DB_NAME) 3 or die( Error connecting to MySQL server. );... END OFPAPER