Difference between revisions of "IS480 Team wiki: 2012T1 One-hit Wonder Final Wiki Project Quality"
Jump to navigation
Jump to search
Line 139: | Line 139: | ||
| style="background-color: #BDD8DA; font-weight: bold;" | 1 | | style="background-color: #BDD8DA; font-weight: bold;" | 1 | ||
| Play! Framework | | Play! Framework | ||
− | | * Besides the knowledge on the MVC framework, our team did not have any previous background knowledge on utilising frameworks in the development of web applications. | + | | |
+ | * Besides the knowledge on the MVC framework, our team did not have any previous background knowledge on utilising frameworks in the development of web applications. | ||
* Play community is still new. | * Play community is still new. | ||
* Their documentation is not entirely completed | * Their documentation is not entirely completed | ||
Line 148: | Line 149: | ||
| style="background-color: #BDD8DA; font-weight: bold;" | 2 | | style="background-color: #BDD8DA; font-weight: bold;" | 2 | ||
| Implementation of resume creation | | Implementation of resume creation | ||
− | | * Creation of additional fields in the resume form is difficult to implement due to the constraint of the play framework | + | | |
+ | * Creation of additional fields in the resume form is difficult to implement due to the constraint of the play framework | ||
* Resume form is made up of many forms embedded in it, this increased the complexity of the creation of additional fields in the resume form, as it is harder to process the request in the back-end | * Resume form is made up of many forms embedded in it, this increased the complexity of the creation of additional fields in the resume form, as it is harder to process the request in the back-end | ||
* Team spent a considerable large amount of time trying to resolve the issue | * Team spent a considerable large amount of time trying to resolve the issue | ||
Line 154: | Line 156: | ||
| style="background-color: #BDD8DA; font-weight: bold;" | 3 | | style="background-color: #BDD8DA; font-weight: bold;" | 3 | ||
| Search | | Search | ||
− | | * Unlike the revolutionary Google search, our team implemented a basic text based search with 575 lines of self-written codes. This search was implemented in the Company’s side of our application, allowing company users to search for the job applications which are relevant to their search keywords. In the scenario whereby the list of received job applications gets longer, this function will bring convenience to our end users as it allows them to retrieve the relevant job applications within the shortest time span. | + | | |
+ | * Unlike the revolutionary Google search, our team implemented a basic text based search with 575 lines of self-written codes. This search was implemented in the Company’s side of our application, allowing company users to search for the job applications which are relevant to their search keywords. In the scenario whereby the list of received job applications gets longer, this function will bring convenience to our end users as it allows them to retrieve the relevant job applications within the shortest time span. | ||
* Each search will execute 6 SQL queries which would search through the 6 different tables in the SQL database in a sequential manner. The 6 SQL statements illustrated below will retrieve all data in each table, after which codes would be executed to compare the search words input by the users, to the data in the table. If the data in the SQL table contains the searched key words, the specific object will be returned in the search results. To allow a more dynamic search, in the search process, we used the concept of “contains” instead “equals”. | * Each search will execute 6 SQL queries which would search through the 6 different tables in the SQL database in a sequential manner. The 6 SQL statements illustrated below will retrieve all data in each table, after which codes would be executed to compare the search words input by the users, to the data in the table. If the data in the SQL table contains the searched key words, the specific object will be returned in the search results. To allow a more dynamic search, in the search process, we used the concept of “contains” instead “equals”. | ||
* Due to the usage of “contains” in our codes, search which contains undefined keywords might return multiple repeated search results. To resolve this issue, we employed several techniques such as the use of “If- Else” statements and exception catching but they are still unable to completely resolve the issue. Hence, we finally employed the usage of a “HashSet” to remove any duplicated elements before populating them in the search results. | * Due to the usage of “contains” in our codes, search which contains undefined keywords might return multiple repeated search results. To resolve this issue, we employed several techniques such as the use of “If- Else” statements and exception catching but they are still unable to completely resolve the issue. Hence, we finally employed the usage of a “HashSet” to remove any duplicated elements before populating them in the search results. | ||
+ | |- | ||
+ | | 4 | ||
+ | | Instant Resume Template | ||
+ | | | ||
+ | * Lots of jQuery plugins and javascripts have to be coded in order to make the resume template interactive and "instant". | ||
+ | * Team spent a large amount of time trying to research and implement the interactive features such as drag and drop and sorting resume components around. | ||
|} | |} | ||
</div> | </div> | ||
<div style="background: #7D9C9F; border:3px solid #7D9C9F; -webkit-box-shadow: 0px 0px 6px #7D9C9F; padding: 10px;"></div> | <div style="background: #7D9C9F; border:3px solid #7D9C9F; -webkit-box-shadow: 0px 0px 6px #7D9C9F; padding: 10px;"></div> |
Revision as of 21:41, 28 November 2012
Project Quality
Immediate Deliverables |
Stage | Specification | Modules |
Project Management | Meeting Minutes | Team Meeting: Minutes 1-22 |
Supervisor Meeting: Minutes 1-8 | ||
Client Meeting: Minutes 1-10 | ||
Requirements | Storyboard | UI Mock Ups |
Analysis | Use Case | Use Case Diagrams & Descriptions |
Design | System Architecture | System Architecture Diagram |
Database | Logical Diagram & ERD | |
Heuristic Evaluation | Heuristic Evaluation Feedback Report | One-hit Wonder Heuristic Evaluation Report |
User Testing 1 | UT 1 (Internal) Test Cases | One-hit Wonder Internal Test Cases UT1 |
UT1 Test Cases & Overall Experience Feedback (For Testers) | One-hit Wonder UT1 Test Cases | |
UT 1 Results and Analysis | UT 1 Results | |
User Testing 2 | UT 2 (Internal) Test Cases | One-hit Wonder Internal Test Cases UT 2 |
UT2 Test Cases & Overall Experience Feedback (For Testers) | UT 2 Test Case - Easy Template UT 2 Test Case - Difficult Template | |
UT 2 Results and Analysis | UT 2 Results | |
Slides | FYP Mid-term Presentation Slides | One-hit Wonder Mid-Term Presentation Slides |
FYP Final Presentation Slides | One-hit Wonder Final Presentation Slides |
Quality |
Deployment |
Technical Complexities |
No. | Task/Function | Description |
1 | Play! Framework |
|
2 | Implementation of resume creation |
|
3 | Search |
|
4 | Instant Resume Template |
|