This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.
Within this chapter the researcher looks at the current application and improvements are required in order for it to serve the needs of the university better. The aim of this project is to design and produce a web based application system for the university that will improve the application process for both the potential students and staff alike.
4.2 Analysis Approach
The study adopted the object-oriented methodology. The phases of research have been described in Chapter 3. The following section presents the findings on each phases of the methodology.
This consists of two parts functional and non-functional. Below is the list of Functional, Non-Functional Requirements, and updated SRS.
Functional requirements show the planned behaviour of the new system. The behaviour may be shown as a service, task or function the system which the system will be required to perform. The Use case is useful function in showing and communicating the functional requirements. In addition to this non-functional requirements include constraints and qualities. Instead ,these need to be made precise and actionable.
126.96.36.199 Current System
The potential students who are interested in the University, can access website. All of the relevant information is available on internet. However, those who would like to apply at University have to send necessary application materials and application processing fee through post office/ bank. They are not able to apply via online.
After getting the application materials academic department has to key in the data into the system and a copy of the new application has to be sent to department. The department co-ordinator will go through the application and assess the applicant's suitability with regard to the admission criteria. Then following this the department co-ordinator will inform the academic department of the successful candidates. This department will send an offer in writing to the applicants. This is an arduous process. Through this system it is possible to lose the application and not inform the applicant of their application status.
188.8.131.52 Data Collection
A multi-method approach was implement in the gathering of information such as is observed the present system, interview with academic department staff, questionnaire distribution among academic department and (University AL JABEL AL GHARBE / LIBYA) students, documentation, and website and so on. Data have been gathered from staff and students from within the university.
Within this project, numerous interviews have been performed involving the faculty staff. The interview conducted was close-ended and further to this an open ended type.
Fifty questionnaires were given to both staff and students at the. The questionnaires were in multiple choice question format (MCQ) (Copy of questionnaire is attached in appendix).
4.3 Design Approach
4.3.1 Software Requirements and hardware
There are several requirements in terms of tools and equipments that were required for the completion of this project. Table 4.1 consists of Hardware requirements and Table 4.2 software requirements are shown in. Table 4.3 shows the list of software tools and programming languages used.
Computer Intel Pentium 2-8 GHz , Hard Disk Drive 120 GB or 160 GB , RAM 1GB , DVD Drive , 15" LCD Monitor.
Table 4.1: Software Requirements
Active Server Page (ASP)
Web Application Programming Language
Interactive website designing tools
Database Designer tools
DBDesigner and MyQL
Graphics Editing tools
Adobe Photoshop, Ulead PhotoImpact
Macromedia Flash, SWISHMax 4
Web Application Server
Internet Information Service (IIS) 7.0
Macromedia Dreamweaver CS3
Rational Rose 2005
MS Word 2007, Excel 2007
Table 4.3 shows the list of all software items and programming language that has implemented to perform the development activities of the future system.
Table 4.2: List of Software Tools and Programmer Languages
Item and Vendor
Rational Rose 2000
UML Modeling Tool
Schedule Management Tool
Macromedia Dreamweaver [Adobe]
User Interface Design Tool
Macromedia Flash CS3 [Adobe]
Animation Design Tool
Adobe Photoshop [Adobe]
Photo/Graphic Editing Tool
Photo Impact [Ulead]
NetBeans [Sun Microsystem]
Java Servlet Page (JSP)
[Acquired by Sun Microsystem]
Database Designing Tool
AJAX [Netscape & Mozilla]
Asynchronous Content Loading Tools
CSS [W3 Consortium]
Style Sheet Design Tool
XML [W3 Consortium]
Custom Mark-up Language
DHTML [Netscape & Mozilla]
Interactive and Animated Website Tools
4.3.2 Design Requirements Model
During this stage several design ideas have been created using the unified modeling language (UML).
UML is allows you to specify, construct, visualize and document the problems that could potentially be faced by the software system, it is called a visual modelling language. (Booch et al. 1998) .within the UML program Use case diagrams are used to attain requirements for a software design and development. An individual use case portray in informal (Sendall & Strohmeier, 2000). UML is accepted to be the most preferred diagrammatic tool used today in software engineering.( Nunes & Cunhas 2006 )
According to Eriksson & Penker (1999), UML could possibly be applied in different stages of system development as a follow on from the requirement specification and to the latter stages including the testing of the finished system. Whitten et al. (2001) describe that UML is conventions modelling language that specify a system in term of object. UML consists of number of graphical elements that comprises from diagram. One objective of UML is to provide general vocabulary of object-oriented and diagramming techniques that is suitable to model any project through its various development stages. (Dennis et al. (2000)
In this study proposed Rational Rose 2005 has been used to draw requirements model. Compton & Huggins (2003) showed that during requirements analysis and design many errors can occur these can be notice by means of execution.
184.108.40.206 Use Case Diagram
Fourteen (14) use case have been produced. These are Apply online, Pay Application Fees, Login, View Application Status, Update Application Info, Authorize Student, Edit Profile, Manage User Account, Add, Edit, Search User, and Delete User Account. Table 4.4 illustrates the use cases.
Table 4.4: Use Case Look-up Table
Use Case ID
Use Case Name
Apply online / Register
Pay Application Fees
View Application Status
Update Application Info
Update Application Status
Manage User Account
Add User Account
Edit User Account
Delete User Account
Figure 4.1: Use Case Diagram
There are two principal actors-Prospective student and Administrator as illustrated in Figure 4.1. Student can manage Apply online, Pay Application Fees, Login. Administrator can manage all of them including View Application Status, Update Application Info, Authorize Student, Edit Profile, Manage User Account, Add, Edit and Delete Account.
220.127.116.11 Use Case Specification
This provides detailed descriptions of the communication between the actor and the system. There are fourteen use cases specifications present which are based on the individual use cases identified. These are show below:
Apply Online (WPAS_UCD01)
Pay Application Fees (WPAS_UCD02)
View Application Status (WPAS_UCD04)
Update Application Info (WPAS_UCD05)
Update Application Status [WPAS_UCD06]
Authorize Student (WPAS_UCD07)
View Profile (WPAS_UCD008)
Edit Profile (WPAS_UCD09)
Manage User Account (WPAS_UCD10)
Add User Account (WPAS_UCD11)
Edit User Account (WPAS_UCD12)
View User Account (WPAS_UCD13)
Forget Password (WPAS_UCD14)
Use case specifications are based on both functional and non-functional requirements of the future system (Appendix 3: Use Case Specification.
18.104.22.168 Sequence Diagram
Numerous sequence diagrams are created. These are in the following section.
Apply Online (WPAS_UCD01)
Figure 4.2 shows the Apply Online sequence diagram of the system. Prospective students (User) can apply through online for admission. They need to enter all requirements and press "Apply" button. System will sendApplyRequest() to the ApplyController. ApplyController will verify all information for data validation and display confirmation page. Once user click "Confirm" button, the system will automatically produce a new user account and show a successful message. Figure 4.2: Sequence Diagram for Apply Online
Pay Application Fees (WPAS_UCD02)
Figure 4.3 shows the pay application fees sequence diagram. In order to proceed with application process student (User) need to pay application fee. On the OnlinePaymentBoundary user need to enter credit card no., card type, name and then press "Pay Now" button. OnlinePaymentBoundary will sendPayRequest () to the regulator. regulator will authenticate credit card and complete the transaction process as follows.
Figure 4.3: Sequence Diagram for pay Application Fees
Figure 4.4 illustrates the sequence diagram for logging into the system. The User will insert his Login details. Then click the "login" button. LoginUIBoundary will transmit a loginRequest(). The LoginController will receive the loginID and compare it to details already in the database. If matches data already in the database the login in details will be accepted and access will be accpeted. However if there is no match the message-"Incorrect loginID or Password" will appear. Figure 4.4: Sequence Diagram for Login
View Application Status (WPAS_UCD04)
Figure 4.5 illustrates the sequence diagram for view application status. Students are able to see their application status at anytime from anywhere. From the mainmenu click "View Status" button. MainMenuBoundary send the request to the MainMenuController. And display the view application status interface.
Figure 4.5: The Sequence Diagram for the View Application Status
Update Application Info (WPAS_UCD05)
Figure 4.6 shows the sequence diagram for update application info. Student can update their information time-to-time. There are six process to update application info such as-displayUserInfo, getUserInfo, sendUpdateRequest, validateInfo, setUpdateInfo, displaySuccessfulMessage.
Figure 4.6: The Sequence Diagram for Update Application Info
Update Application Status (WPAS_UCD06)
Figure 4.7 shows the sequence diagram for update application status. Only administrator can update application status. There are four process such as getApplicationInfo(), displayAppStatus(), sendUpdateRequest(), UpdateStatus().
Figure 4.7: Sequence Diagram for Update Application Status
Authorize Student (WPAS_UCD07)
Figure 4.8 illustrates the sequence diagram which is the authorize student. Only administrator can authorize student. There are five process/ activities as follows-
Figure 4.8: Sequence Diagram for Authorize Student
View Profile (WPAS_UCD08)
Figure 4.9 shows the sequence diagram for view profile. This sequence shows how user can view their own profile. Just simply click "View Profile" button on MainMenuboundary. The request will send to the controller and display user profile.
Figure 4.9: Sequence Diagram for View Profile
Edit Profile (WPAS_UCD09)
Figure 4.10 shows the sequence diagram for edit profile. Users are also allow to change their profile information. Form view profile interface, click "Edit" button. Request will send to controller and display edit profile interface. User modify information and press "Edit" button. Controller varifydata and seUserUpdateInfo. Finally, displaySuccessfull Message.
Figure 4.10: Sequence Diagram for Edit Profile
Add User Account (WPAS_UCD10)
Figure 4.11 illustrates the sequence diagram for add user account. Only administrator can add/ create new user account. Enter user information and press "Add" button. Controller will do these process-send addRequest, getUserInfo, validate, setUserInfo and displaySuccessful Message.
Figure 4.11: Sequence Diagram for Add User Account
Edit User Account [WPAS_UCD11]
The sequence diagram for edit user account is shown Figure 4.12. Only administrator can edit user account. Enter user new information and press "Edit" button. Controller will do this process-send EditRequest, getUserInfo, validate, setUserInfo and displaySuccessful Message.
Figure 4.12: Sequence Diagram for Edit User Account
Search User Account[WPAS_UCD12]
Figure 4.13 shows the sequence diagram for search user account. User can search user account. Enter search word and press "search" button. Controller will send searchRequest and getUserInfo from database. Finally, verify with search word and display result.
Figure 4.13: Sequence Diagram for Search User Account
Delete User Account [WPAS_UCD013]
The sequence diagram for delete user account is shown in Figure 4.14. Only administrator has the authority to delete a user's account. Select a user account and press "Delete" icon. System will notify-Are you sure you want to delete? [OKâ€¦.. Cancel]. If admin select "OK" button, it will be deleted.
Figure 4.14: Sequence Diagram for Delete User Account
Forget Password [WPAS_UCD014]
The sequence diagram for forget password is shown in Figure 4.15. It will enable all users find their passwords if it is forgotten. They will be required to insert the same email address which they enter to register the application. If the e-mail address does not go with an email address already in the database, the system will issue -"Email address doesn't exist".
Figure 4.15: illustrates the Sequence Diagram: Forget Password
Sequence diagram for change password is shown in Figure 4.16. the User is expected insert the Previous and new passwords, then click on the <<Change Password>> icon. Successful change of password will be accompanied with a confirmation message, if not an error message will appear.
Figure 4.16: illustrates Sequence Diagram for Change Password
22.214.171.124 Class Diagram
Figure 4.17 shows the class diagram for the WPAS.
Figure 4.17: Class Diagram for WPAS
4.3.4 Design User Interface
Login Interface [Sequence ID: WPAS_UCD003]
Figure 4.17 shows login interface. Sequence diagram shown in Figure 4.4. The user will enter the login details . Then click "login" icon. The system will check LoginID and password. Successfully match will allow to access to the system. Otherwise, display error message-"Incorrect loginID or Password".
Figure 4.18: Login Interface
Apply Online Interface [Sequence ID: WPAS_UCD001]
Figure 4.18 shows the Apply Online interface of the system. Prospective students (User) can apply through online for admission. They need to enter all requirements and press "Apply" button. System will verify all information for data validation and display confirmation page. Once user click "Confirm" button, system will create user account & display successful message.
Figure 4.19: Apply Online Interface
Pay Application Fees Interface [Sequence ID: WPAS_UCD002]
Figure 4.19 shows the pay application interface. In order to proceed with application process student (User) need to pay application fee. User need to enter credit card no., card type, name and then press "Pay Now" button. System will validate credit card and complete the transaction process.
Figure 4.20: Pay Application Fees Interface
View Application Status Interface [Sequence ID: WPAS_UCD004]
Figure 4.20 shows the view application status interface. Students are able to see their application status at anytime from anywhere. From the mainmenu click "View Status" button. And the system display the view application status interface.
Figure 4.21: View Application Status Interface
Update Application Info Interface [Sequence ID: WPAS_UCD005]
Figure 4.21 shows update application info interface. Student can update their information time-to-time.
Figure 4.22: Update Application Info Interface
Update Application Status Interface [Sequence ID: WPAS_UCD006]
Figure 4.22 shows update application status interface of the system. Only administrator can update application status.
Figure 4.23: Update Application Status Interface
Authorize Student Interface [Sequence ID: WPAS_UCD007]
Figure 4.23 shows authorize student interface. Only administrator can authorize student. Admin select the student matric no and click the authorize check box and finally click Authorize button to successfully authorize the student.
Figure 4.24: Authorize Student Interface
View Profile Interface [Sequence ID: WPAS_UCD008]
Figure 4.24 shows view profile interface. User can view their own profile. This done by simply Pressing the "View Profile" icon which available on the Main Menu. The system will show the specific user profile.
Figure 4.25: View Profile Interface
Edit Profile Interface [Sequence ID: WPAS_UCD009]
Figure 4.25 illustrates the edit profile portal. Users are also allowed to change their profile information. Form view profile interface, press the "Edit" icon. The system will show edit profile interface. User modify information and press "Edit" button. System wills varifydata and finally displaySuccessfull Message.
Figure 4.26: illustrates the Edit Profile Interface
Manage User Account Interface [Sequence ID: WPAS_UCD010]
Figure 4.26 illustrates the Manage user interface of the system. This interface extends three more interface such as-Add user account, edit user account, delete user account. User also able to search information in this interface.
Figure 4.27 shows Add user account interface, Figure 4.28 illustrates the Edit user account interface, Figure 4.29 shows the View user account interface, Figure 4.30 shows Delete user account interface and Figure 4.31shows search user account interface .
Figure 4.27: Manage User Account Interface
Add User Account Interface [Sequence ID: WPAS_UCD011]
Figure 4.27 shows add user account interface. Only administrator can add/ create new user account. Enter user information and click on the "Add" icon. The system will create new user account and show successful message.
Figure 4.28: Add User Account Interface
Edit User Account Interface [Sequence ID: WPAS_UCD012]
Figure 4.28 shows edit user account interface. As shown in Figure 4.12 is the sequence diagram for edit user account. Only administrator can edit user account. Enter user new data and click "Edit" button. The system will update user account data and show a successful message.
Figure 4.29: Edit User Account Interface
View User Account Interface
Figure 4.29 shows view user account interface. User can view his/ her account.
Figure 4.30: View User Account Interface
Delete User Account Interface
Figure 4.30 shows the Manage user interface of the system (Delete). Only administrator can delete user account. Admin select user account he/she wants to remove or cancel. Then select "Delete" button. System will display message-"Do you want to delete the selected record?". If admin select "OK" button, system will delete the selected account.
Figure 4.31: Delete User Account Interface
Search User Account Interface
Figure 4.31 shows the sequence diagram for search user account. User can search user account. Enter search word and press "search" button. Controller will send searchRequest and getUserInfo from database. Finally, verify with search word and display result.
Figure 4.32: Search User Account Interface
Forget Password Interface [Sequence ID: WPAS_UCD014]
the sequence diagram for forget password is shown Figure 4.15. All are able to find their password. They will have to enter same email address with which they created the account. If the email address in inconsistent a -"Email address doesn't exist" will appear.
Figure 4.33: Forget Password Interface
Change password interface of the system is shown in Figure 4.33. The User will be allowed to change their password. They will enter both the previous and new passwords at once. The user can press <<Confirm password>> button to change password. System will display confirmation message. If the both password mismatch, system will show error message.
Figure 4.34: Change Password Interface
4.4 Usability Testing
Usability factors are used in the testing, such as such as satisfaction, efficiency and effectiveness. Generally the usability characteristics are not used due to time constraints (Nielsen, 2007; Holcomb & Tharp, 1991).
The usability testing has been conducted for seven (7) days. The total numbers of respondents were 20, where 15 respondents were students and 5 respondents were Academic Department staffs.
During testing, participants have were asked numerous questions on numerous inorder to compare whether the system is better than the old. Appendix A shows the questionnaire used.
4.4.1 Usability Testing Result
Comments from twenty (20) respondents have been received and each was found to be different from each other. The questionnaire evaluates the prototype interns of effectiveness, efficiency and satisfaction.
It was found that respondents were concerned on the how effective the system was. 10 respondents (50%) said that the new system meets the requirements. Eight (8) respondents (40%) state that the system is efficiency However, only 2 respondents (10%) mentioned that the system is satisfied. The overall user acceptance result is as shown in Figure 4.35.
Figure 4.35: Percentage of the User Acceptance
. This chapter discussed on the findings of the study. A prototype has been produced and positive feedback has been achieved. The next chapter presents the limitation of the system, future works, recommendation and conclusion.