Role performancereport template_refonly

School of Computer Sciences

CLT301 – Undergraduate System Development Project

Role Performance Report

P S HDelivering Tomorrow'sS o l u t i o n s T o d a y

[NAME OF PROJECT]

[Project Module (Individual)]

STUDENT’S FULL NAME

MATRIC NUMBER

Supervisor: [Name of Client]

External Client: [Name of External Client (if applicable)]

Examiner: [Name of PSH Manager]

2007/2008 Session

CLT301 Undergraduate System Development Project

DECLARATION

“I declare that the contents presented in this report are based on my own work, that

was done in partial fulfilment of the requirements of the Undergraduate Project for the

Bachelor’s of Computer Science (Honours) Degree at Universiti Sains Malaysia,

except where stated otherwise”.

Signature : ……………………………

Name : ……………………………

Date : ……………………….……

PSH-ROLE-2.02 ii


IN APPRECIATION

I would like to thank …

PSH-ROLE-2.02 iii


ABSTRAK

Abstrak mestilah menerangkan projek berkumpulan dan sub-projek individu yang

telah dijalankan secara ringkas. Nyatakan objektif keseluruhan projek dan hasil projek

hanya dalam satu perenggan dan satu muka surat sahaja. Kedua-dua abstrak dalam

bahasa Malaysia dan bahasa Inggeris mestilah setara isi kandungannya.

PSH-ROLE-2.02 iv


ABSTRACT

Abstract must explain briefly the group project and the individual sub project

conducted. Explain the overall objectives of the project and the outcome of the project

in one paragraph and page only. Both abstracts in Malay language and English

language must have similar contents.

PSH-ROLE-2.02 v


CONTENTS

DECLARATION...........................................................................................................ii

IN APPRECIATION....................................................................................................iii

ABSTRAK....................................................................................................................iv

ABSTRACT...................................................................................................................v

CONTENTS..................................................................................................................vi

LIST OF TABLES......................................................................................................viii

LIST OF FIGURES.......................................................................................................ix

LIST OF ABBREVIATIONS AND SYMBOLS...........................................................x

1. INTRODUCTION..................................................................................................1

1.1. Introduction to XXX......................................................................................1

1.2 Issues in XXX................................................................................................1

1.3 Other relevant topics......................................................................................2

2 PROJECT DETAILS.............................................................................................3

2.1 Introduction to Project or System XXXX......................................................3

2.2 Introduction to Subsystem/Module................................................................4

2.3 Objective........................................................................................................4

2.4 Specifications of Existing System..................................................................4

2.5 Technology and Software...............................................................................5

2.6 System Development Methodology...............................................................5

2.7 Task Assignment and Explanation.................................................................6

PSH-ROLE-2.02 vi


3 DISCUSSION........................................................................................................7

3.1 Effectiveness of Group Work.........................................................................7

3.2 Difficulties and Proposed Solutions...............................................................7

3.3 My Individual Experience..............................................................................7

3.3.1 Software Developer Role.......................................................................7

3.3.2 Other Roles.............................................................................................8

3.3.3 Supervision and Project Demonstration Issues......................................8

4 CONCLUSION......................................................................................................9

4.1 Report Summary............................................................................................9

4.2 Weaknesses and Proposed Enhancements to Module/System.......................9

REFERENCES.............................................................................................................10

APPENDIX A..............................................................................................................11

PSH-ROLE-2.02 vii


LIST OF TABLES

Table 2.1: An example of technology and software comparisons.................................5

PSH-ROLE-2.02 viii


LIST OF FIGURES

Figure 2.1: An example of a system and its environment..............................................4

PSH-ROLE-2.02 ix


LIST OF ABBREVIATIONS AND SYMBOLS

[Reminder: Remove this section if there are no abbreviations or symbols

used in your report]

HTML - Hypertext Markup Language

SPMP - Software Project Management Plan

PSH-ROLE-2.02 x

CLT301 Projek Pembangunan Sistem Prasiswazah

2.7Task Assignment and Explanation

I explained how the Systems Development Life Cycle (SDLC) operates in the

project paper. My Project paper is on Hotel Vistana Website whereby my mission is

to add value to the existing site.

The SDLC process is a Systems Development Methodology (SDM) “which is

basically the process most businesses go through to develop and maintain Information

System.” (Ross A. Malaga, (2005) Information Systems Technology, Published by

Prentice Hall.Page 285. Copyright 2005 Pearson Education) The SDLC contains

seven major phases;

I started on the first which is, Planning. Planning is the step taken to find out if the

current system can be updated or if there needs to be a new system created. To help

make that decision four feasibility analyses will need to be completed which are

technical, economic, operational, and schedule. The technical analysis will determine

what technologies are present and what can be created to solve the issue. The

economic analysis will find out if the Hotel can afford the new or upgraded

Information System (IS) and if it will benefit the Hotel at all. The operational analysis

will determine the reaction that humans will have with this new system. (Likes,

Dislikes, and Employee Cooperation) The schedule analysis will determine whether

or not the proposed completion time is realistic. All these steps must be completed in

order to move on to the next step.

The second step of the SDLC I explained is System Analysis. The System Analysis

step is where the systems analyst in the IT development team determines the exact

problems, then details an exact IS solution to the problem as well as a to-do list for

future reference in the SDLC. This step must be completed after the planning and

before moving on, to ensure the quality of the website being designed.

The third step of the SDLC is Systems Design. Once the Systems Development Team

understands the requirements needed in order to solve the issues at hand the systems

design phase can start. The Systems Design phase is meant to describe how the

Systems Development team will create this new system. They will examine what

functions it will have and what parts it could contain. There are two main steps in

PSH-ROLE-2.02 1


Systems Design; Logical Design and Physical Design. A Logical Systems Design is

mainly a rough draft of what the functions of the new and/or upgraded IS should do.

A Physical Systems Design is a document that describes the steps the Systems

Development Team will go through to meet the requirements of that functionality.

The fourth step of the SDLC is Development. The Development phase can only start

after the first three steps have been completed. Once the Systems Development Team

gathers a clear understanding of the design of the system they can begin building it.

Let’s say the option of purchasing a new system altogether is chosen then the new

system must still meet the needs and requirements of the Systems Design details. This

is the phase where Programmers, Network Engineers, and Database Developers will

come into position. Development functions will start occurring one after the other

until all the functions are met and maintained.

The fifth step of the SDLC is Testing. The Testing phase is only applicable once the

system is built. This phase is where the creators test their own work to ensure the new

IS runs as the system design wants it to be and to make sure it is working properly.

The sixth step of the SDLC is Implementation. The Implementation phase is where an

installation team installs all the needed components for the new IS. This is where any

important information is transferred from the old system into the new system. This

phase is crucial for most business because employees will have to work with a system

that they are not used to, this might cause frustration.

To avoid this there is four ways of implementing a new IS to this Hotel:

1. Direct Cutover occurs when an old system is being taken out of the equation and a new one put in.

2. Parallel Conversion is the gradual movement from an old system to a new system.

3. Pilot Testing is testing one area of an organization and if testing proves a positive effect then the whole organization moves into using this new IS.

4. Stage Conversion occurs when one part of the system is applied and operates properly then another part is installed until the whole system is in place.

The seventh and final step of the SDLC is Maintenance. The Maintenance phase is

intended to take care of the undetected errors in the Testing phase that only show up

after the system is being used. Maintenance mainly consists of correcting errors,

backing up and recovering data, supporting end users and enhancing the system.

PSH-ROLE-2.02 2

Vistana Hotel’s

website

Accommodation Amenities Meetings &

Events

Reservation Capture Guest’s

Contact/Autoresponder

Dining/Nightlife Entertainment Media Experience/

Testimonial

Mobile Site


For this Vistana website I intend to add a value added service for them which is doing

some SEO services and Online Marketing Services for them. I firmly believe even if

we have a very wonderful website, without SEO or Marketing, the website won’t get

a lot of online traffic. Without the traffic, the website is just like an information board.

Below are the value added strategies that I’m going to provide them :

The modules for the website :

PSH-ROLE-2.02 3


The design will look like this prototype: http://wansharinee.com/HeartFeltHotel/

For Mobile site :

I decided to design the system using a content management system which after doing

a few studies on few CMS( Content management System) engines such as JOOMLA,

DRUPAL, WORDPRESS and XOOPS. Finally we decided on using WORDPRESS

since I am quite familiar with it and because it is known to have quite a handful of

SEO friendly plugging. Moreover GOOGLE seems to favour WORDPRESS against

other CMS engines and 60% information is search from GOOGLE.

PSH-ROLE-2.02 4


I recommended my client to use hybrid marketing which is, the combination of online

and offline promotions. Apart of designing and creating website for the client, I will

also add values to the service by helping the client built the client’s presence on the

internet. In doing this, I have to optimize the website not just with the hotel’s name

but also with few keywords such as “hotel in Penang”, “Penang’s Hotels”, “best hotel

in Penang”, etc. These keywords are important because not all end user will directly

go to the hotel website. Most of the end users will use search engines to find hotel in

Penang, when they do this, hopefully the end users will find my client website on the

first few pages of the SERP (Search Engine Page Result). Besides doing the SEO

optimization, I will also be doing other types of Online Marketing to make sure my

client’s website get the traffic from the internet. Thus, my client will not only rely on

search engine traffic, but also will be getting end users from other forms of marketing.

Below are some of the services that we intend to employ :

1) article marketing - write articles about our client’s hotel and the activities that its

has and promote the articles to directories such as ezinearticles.com, goarticles.com

2) forum marketing

3) marketing thru social networking sites such as fb, myspace,

4) promote to social bookmarking sites such as digg.com, propeller.com,

stumbleupon.com

5) videomarketing- youtube,metacafe

6) marketing thru groups- google, msn, yahoo

7)image storing side- flickr.com

8)mktg thru PPC(pay per click) ads- google ad sense. facebook ad.

The purpose of doing all the above techniques are to get traffics to the website and to

get backlinks to my client’s website (Most Search Engines give page ranking

according to backlinks ( relevancy, authority, quantity ). The techniques listed above

is not comprehensive. I will keep using new promotional method as new technology

emerges.

Hopefully, by now I have presented everyone with a very clear understanding of the

Systems Development Life Cycle (SDLC) and how each step works together as a

domino effect.

PSH-ROLE-2.02 5

http://flickr.com/

http://stumbleupon.com/

http://propeller.com/

http://digg.com/

http://goarticles.com/

http://ezinearticles.com/


PSH-ROLE-2.02 6


2 DISCUSSION

2.1 Effectiveness of Group Work

In this section you need to discuss to what extent your project team was able to work

together effectively to complete the project, task division and milestone completion,

subsystems and modules integration, and so on.

2.2 Difficulties and Proposed Solutions

Any difficulties faced by you while role-playing as a software developer, or tasks

relevant to your other role, as well as difficulties faced by the project group while

undertaking the project should be presented in this section. Explain the approach you

or your group took to reduce or overcome the difficulties. Give suggestions on how to

improve, if any.

You should also discuss the effect and impact of the client feedback and PSH

Management during your client updates, reviews, and prototype demo, on the overall

progress of your project, the focus of your project team, the project schedule, and so

on.

2.3 My Individual Experience

Give your comments regarding the experience you gained while undergoing this

project, for example, in carrying out the tasks and roles given, the supervision

experience, project demonstrations and so on.

2.3.1 Software Developer Role

List and discuss the problems encountered during the software module development

process, and the solutions adopted to overcome them. Explain why you chose the

given solution in developing the software.

PSH-ROLE-2.02 7


2.3.2 Other Roles

List and discuss the problems encountered while undertaking your other roles, such as

project team leader, QA leader, system configuration leader, and so on, and the

solutions adopted to overcome them. Explain why you chose the given approach.

2.3.3 Supervision and Project Demonstration Issues

List and discuss the problems encountered, if any, relating to the supervision and

reviews and prototype demonstrations. Explain how these problems occurred, and

give suggestions on how to improve the situation in future, whether for yourself as a

student/developer or for the supervisor/client and examiner/project manager.

PSH-ROLE-2.02 8


3 CONCLUSION

3.1 Report Summary

This section should summarize the discussions in Chapters 1, 2, and 3.

3.2 Weaknesses and Proposed Enhancements to Module/System

State the limitations or weaknesses of your system that was developed or modified,

and especially within the modules or subsystems you were responsible for developing.

Explain how these weaknesses arise. Give suggestions on how to improve it in future.

PSH-ROLE-2.02 9


REFERENCES

[Reminder: The following list is just an example. Please list the references you used

and remove the example below. Each reference listed below must be cited within the

text or explanation of the report.]

Hendrix, T. D., Cross, J. H. II and Maghsoodloo, S. (2002). The Effectiveness of

Control Structure Diagrams in Code Comprehension Activities. IEEE Transactions on

Software Engineering. 28(5): 463-477.

Oman, P. W. and Cook, C. R. (1990). The Book Paradigm for Improved Maintenance.

IEEE Software. 7(1): 39-45.

Shaffer, C. A. (1997). A Practical Introduction to Data Structures and Algorithm

Analysis. New Jersey: Prentice-Hall.

Sulaiman, S., Idris, N. B. and Sahibuddin, S. (2002). Production and Maintenance of

System Documentation: What, Why, When and How Tools Should Support the

Practice. Proceedings of 9th Asia Pacific Software Engineering Conference (APSEC

2002). USA: IEEE Computer Society Press. 558-567.

Information Literacy Group, Leeds University Library (2006).

Harvard Style Bibliographies and References [online]. [Accessed 6 Sept. 2006]

Available from: http://www.leeds.ac.uk/library/training/referencing/harvard.htm.

PSH-ROLE-2.02 10

http://www.leeds.ac.uk/library/training/referencing/harvard.htm


APPENDIX A

[Reminder: Take this page out of the report if not relevant.]

Include any appendices after the reference section. If there are tables and diagrams

here, label them as Table A.1 or Figure A.1 and so on.

PSH-ROLE-2.02 11

Documents

Role performancereport template_refonly