The system can be further developing for forecasting as well. So it will reduce most of the management time and money. The client’s main concern goes for forecasting in the next stage they are looking forward to enhance the system for forecasting.
Section 8
Conclusion
Conclusion
To conclude the objective of the project is to build a web based stock management control system for the Royal Fernwood Porcelain Company in Kosgama. This objective was carried out with a scope of making a network within the company as well as with clients and the supplies.
We plan our work using work break down structure, work load matrix and according to that we made the Gantt Chart where we were able to get a clear picture of what work needs to be done at which time and which should be given priority.
In this newly design system the requirements were identified doing an investigation as well as fact finding using interview with the higher management, providing questioners for the administration staff. In the requirement specification we were able to identify the week points in the current Ms Dos version they are using in General Stores. Other departments don’t use a computerised system at all. In our first half of the process was to introduce a system mainly for general stores where most stock handling is done by them. And we were able to identify how we should link the other function through the system.
Feasibility of the project was done to identify how worth carrying out the project. In this analysis we identified that the benefits are more than the cost involved with the project.
Shedule feasibility was done in terms of making work easier. So we identified it is highly technically and economically feasible. Operational feasibility was carried out using PIECES framework where we identified it is worth while carrying out the project further.
According to our plan we were able to design our system using different techniques like Data Flow Diagrams and the Data Dictionaries where we identified how data should be transformed through the system to the end user.
In this case entities and process combined with data flows should be identified in detail to make the design a user friendly as well as according to the standards.
The proposed design was reliable, cost effective, efficient and secure system which the organization is in need of for their burning management problems like decision making.
And the system was uniquely design for the Royal Fernwood Porcelain Ltd where all the requirements were met in the implementation pace.
Section 10
Appendix
10.1 User Manual
1) Edit the config.php file to suit your mysql database settings.
Insert 'rfpl' as the database name. (this name must match with name of the database you are going to create)
2) Upload all the files and folders to the server
3) Open WampServer
4) Go to phpMyAdmin -> Create a new database called 'rfpl'
Import the SQL file "SQL.sql"
5) The system is ready to use. Go to the directory in which you have installed the files via a web browser.
Sample User accounts you can use to login to the system
Username Password User type
manager 123 Manager
pd 123 User at planning
department
fg 123 User at Finished Goods
stores
rm 123 User at raw material stores
gs 123 User at general stores
10.2 Group Meetings Report 1
Date : 16/03/2009
Time : 11.00 A.M -12.30 P.M
Venue : Syndicate Room 5
Meeting called by : Praveena Sarathchandra Attendees : Praveena Sarathchandra
Ayodya Piyaruwan
Chathura Wickramasinghe
The meeting was called by to get the basic idea of what we are planning to do. As we all have discussed in this meeting each one in the team had an idea about a system that was a stock control system for hardware shop, Public Library as well as the stock control system for the porcelain manufacturing company.
Finally we agree on developing a stock control system for the Royal Fernwood Ltd. As we all realized the scope and the work comes handy in this particular system. So we decided to on this and discuss the handout to get a broad idea about the deliverables of the project.
We discuss the work break down structure and create work load matrix.
In this meeting we agreed on reading books to get an idea about the system development as well as documentation.
And at the same time we decided to make the Gantt chart according to our work load matrix.
The meeting was adjoined and decided to have our next meeting on 27/03/2009.
Report 2
Date : 27/03/2009
Time : 3.00 P.M -4.00 P.M
Venue : Lab 4
Meeting called by : Praveena Sarathchandra Attendees : Praveena Sarathchandra
Ayodya Piyaruwan
Chathura Wickramasinghe
This particular meeting was held in the lab 4 to make the Gantt chart as we discussed in the previous meeting.
Each member in the team presented what they have learnt out of the research regarding the documentation and the required techniques to go through with the life cycle of the project. Discussed about SDLC and cleared our doubts.
Members were given a basic idea about the PHP and MySQL which is used in designing the system and each member agreed to go through the pdfs which contains basic idea about PHP.
We decided to discussed and arrange the date to go and investigate the current system in the next meeting.
The meeting was adjoined and decided held our next meeting on 02/04/2009.
Report 3
Date : 02/04/2009
Time : 11.00 A.M -12.30P.M
Venue : Syndicate Room5
Meeting called by : Praveena Sarathchandra Attendees : Praveena Sarathchandra
Ayodya Piyaruwan
Chathura Wickramasinghe
The meeting was held mainly to discuss the method which should be used to gather requirements of the client.
As fact finding methods we decided to have the interview with Mr.Sarathchandra General Manager of the factory.
We agreed to prepare a questioner to be given to the administration in the organization.
We all discussed and agreed that we should observe the manufacturing process and their system as a result of that we decided to arrange a day to visit the factory. On the same day we agreed to have the interview as well.
The date was set as 04/04/2009.
Meeting was adjoined and our next meting will be on the 22/04/2009.We decided to start analyzing the facts we have gathered.
Report 4
Date : 22/04/2009
Time : 10.00 A.M -12.00 P.M
Venue : Syndicate Room5
Meeting called by : Praveena Sarathchandra Attendees : Praveena Sarathchandra
Ayodya Piyaruwan
Chathura Wickramasinghe
This was one of the most important meetings in which we discussed the requirements we gathered from our visit to the organisation. There were quite a lot we observed and we need to be discussed in detail.
We basically arranged this meeting to discuss our system further in detail. The factory is highly automated in terms of machines and process but they are not in a network and don’t have a system to keep track of up to date information from head office.
Our system going to be very useful for the General Stores, Planning Department as well as the head office as well.
As the management of the factory highlighted we define our scope which can be overcome by the time span of the project.
We decided to start documentation as we have gathered requirements.
The meeting was adjoined and decided to have it on 06/05/2009 and we will be discussing the progress of the project.
Report 5
Date : 06/05/2009
Time : 10.00 A.M - 12.00 P.M
Venue : Syndicate Room5
Meeting called by : Praveena Sarathchandra Attendees : Praveena Sarathchandra
Ayodya Piyaruwan
Chathura Wickramasinghe
We have discussed the outlay of the system which should be in the general stores as it was quite important for the factory.
And we have completed upto introduction in the documentation. All of us carried a copy of the documentation which should be rechecked.
And we discussed about the data flow diagrams and the data dictionaries as we all have to get a clear understanding what need to be done according to our system.
We adjoned our meeting and decided to have our next meeting on 18/05/2009 after we have completed data flow diagrams and the data dictionaries.
Report 6
Date : 18/05/2009
Time : 4.00-7.00 P.M
Venue : Syndicate Room5
Meeting called by : Praveena Sarathchandra Attendees : Praveena Sarathchandra
Ayodya Piyaruwan
Chathura Wickramasinghe
We call this meeting to finalise the system and the design and development. We were almost at the part of the documentation.
Finalise the documentation.