FYP : Comment from another lecturer about FYP

Week 1 comment (11/09/2009)
==============================
Lecturer 1 :
=================================
Section
-should include projection background section
Problem statement
-not clearly spelled out
Objectives
-those are not objectives but problems with the current system
Methodology
-waterfall model is not suitable for FYP because of time and activities usually do not really follows phrases in the model, choose more suitable methoodology such as RAD
Scope
-does not clearly spelled out
Project Significant
-not clearly spelled out
Project schedule
-please also prepare in Gantt Chart form
Project outcome
-not clearly spelled out, should be system and also other outcomes expected from the project such as FYP report.


==============================
Lecturer 2 :
=================================
1. Please redo the proposal. The whole proposal is not correctly written. Please refer to supervisor on this matter.

FYP : Link Video Presentation

Link Video Presentation Final Year Project I
http://www.youtube.com/watch?v=GwQtzpX5ihk

FYP : Chapter 1: Introduction

Chapter 1.0 : Introduction

1.1 Introduction

Nowadays, computer is an important machine for most of the organization or company. By using internet connection, administrator can monitor and know what user doing. The problem is not all place can have internet accessibility in their areas. Today, internet is communication with other people anywhere place. In this globalization era, information technology is very important because of the growing economy at our country. With the expanding of the Information technology section giving more development opportunity for other activity that can’t be archive before this.

Realizing that other sector such as the education, tourism and others whom doesn’t want to be left back in developing their sector to cope with the development of the IT sector, many systems have been developed to ease the management of the company.

1.2 Problem Statements

Initially, this system has been researched in Universiti Malaysia Sarawak (UNIMAS). The main focus of the system is to improve the working performance of Faculty Computer Science and Information Technology (FCSIT) staff especially academician, administrator and technical staff.

Basically, the idea in developing this system using web-based is the availability for the FCSIT employee to perform administrative tasks and store information in the system. The main idea is to implement the system as a web-based system by eliminates the need to install application and at the same time to ease the maintenance and update of the system by the web administrator.

The existence of this system also due to:

· Communication problem among workers in the organization.

· Problems which workers’ faced in their workplace normally involving the application. For example yahoo messenger, worker’s most install application first and then used. They can consult web administrator for the solution to their problems once the system is implemented.

· Problem in monitoring daily activities of staffs.

1.3 Objective

Some of the problem occurs when applying the manual ­systems are:

· Lost of important data due to worker carelessness.

· Data redundancy might occur.

· The current systems giving slowly respond to the user. For example used system manual is slowly.

· High cost and take too much time.

· The data that have been gathered is difficult to process.

1.4 Methodology

Waterfall methodology will be applied as the system method. This methodology is chosen because it is simple and easy to understand. Each stage ends with a verification and validation activity to minimize any problems in that stage. Arrows go back and forth only one stage at a time. This represents the iterative development between two adjacent stages in order to minimize cost. It is assumed that all information necessary for a stage is known.

1.4.1 Requirements definition

Analysis the problem in develops system and set the requirements needed in the system. Problem statement and information will be collected to analyze the system. The analyst will try to analyze details of the organization procedure and information system that have been used to execute every task in organization.

1.4.2 System and software design

Plan design interface system. Design system follower requirement. The design phase is separated into two sections, which is logical design and physical design. The logical design involves the designing of the system during the first and second phase. Meanwhile in the physical design phase, it is more on the designing the system on paper that is consist of some aspect like input, output, and database. All the design will be implemented with taking consideration of the successful rate on the system and to make sure that it is implemented within the timeframe. During this phase, it will also try to explain how the system works from start to end on paper such as the Entity Relationship Diagram (ERD), Data Flow Diagram (DFD), and chart. A research will be conducted to solve a problem if occurred.

1.4.3 Implementation and unit testing

When the design is fully completed, an implementation of that design is made by programmer. The system design will be written into real coding which is realized as a set of program. The coding will be modified repeatedly until the users satisfy with the system. Some code is written and then fixed when it does not work correctly. This execution will execute by the internet programmer first that will include Hypertext Markup Language (HTML), then database programming and Hypertext Preprocessor (PHP) to link HTML programming with database.

1.4.4 Integration and system testing

Finds any error occurs in this system. Fix error in the system. The testing method that is going to use is white box testing and black box testing to test the complete system.

1.4.5 Operation and Maintenance

Each phase of implementation will be tested which is to find the problem that occurred in the program. The system will be tested for validation and verification. Training for the system begins.

1.5 Project Scope

The scope focused to FCSIT staff especially academician, administrator and technical staff. The system is communication other staff. For example staff can communicate with other staff. The scope focused on this website is giving satisfaction in every aspect of:

1. The user scope:

· User gives feedback.

· Management will manage the information system and create the database.

2. The system scope:

· The information that is given by the user will be stored into the database.

· To provide user friendly interface.

1.6 Significance of Project

Through this system usage, it will make job easier and more efficient. With the system can reduce more problems dealt by staff. Cost, crime, and can make people live in hinterland know and expose them to learn and get experience with the current technology.

1.7 Project Schedule

This Final Year Project 1 was initially started from 1^st of July 2009 and will be due for submission on 10^th of November 2009.

Week	Description
Week 1	Register
Week 2	Find supervisor for final year project
Week 3	Discuss topic of project with supervisor
Week 4	Prepare proposal and find information, prepare poster
Week 5	Submit proposal and poster
Week 6	Proposal Exhibition
Week 7	Find information for report and prepare draft report for chapter 1
Week 8	Write report for chapter 1: Introduction
Week 9	Find information for chapter 2 and prepare draft report for chapter 2
Week 10	Write report for chapter 2: Background study / literature review
Week 12	Find information and prepare draft report for chapter 3
Week 13	Write report for chapter 3: requirement analysis and design
Week 14	Submit final year project 1 report

Table 1.1: Project time schedule

1.8 Expected Outcome

Employee Information System (EIS) is developed to replace the existing system. This system will make work easier and more efficient. The user cannot install application to used this system because the system only online system. This system is easy to understand due to the system usability and simplicity.

1.9 Outline of Project Report

There have five chapters within the final year report. In the report will include the details about the system plan that will develop. Below include the summary of the five chapters for final year report.

Chapter 1.0: Introduction. In this chapter will be consist the introduction of Employee Information System (EIS) for FCSIT. Beside that, problem statements, objective, methodology, project scope, significance of project, project schedule, expected outcome and outline of project report would include within this chapter.

Chapter 2.0: Literature Review In this chapter we consist the review study regarding the existing system compared to the Employee Information System (EIS) for FCSIT. Comparing will be carrying out between the proposed systems with the other similar system. Beside that, comparison also includes the programming code, system interface, system features and implementation tools.

Chapter 3.0: Requirement Analysis and Design In this chapter will be consisting the requirement details such as user’s requirement, software and hardware requirement for the proposed system. Besides that, step to obtain the requirement and design of the system such as programming codes, interface design and features will be include in this chapter. User’s requirement and the reason to design the system also include in this chapter.

Chapter 4.0: Implementation and Testing In this chapter will be consisting the implementation of the system. The way of the system will functions, example of the data input and output of the system will be show out. Beside that, testing and analyzed of the system will carry out and include in this chapter. All the result and feedback according to the proposed system will record chapter.

Chapter 5.0: Conclusion and Future Work In this chapter will consist the strengths and weaknesses of the system by determine whether all the objective and project scopes have been achieved and covered. Besides that, some suggestions will be carrying out for the future works to the PC control system for monitoring user’s activities usage.