CHANGES IN REPORT PROPOSAL

here are several changes that have been made during the presentation. it includes the changes on the timeline, the third objectives and methodology used.


  PROJECT OBJECTIVE

1.     To identify the requirement of store management system
2.    To analyze the requirement of store management system
3. To verify and validate the requirement of store management system

TIMELINE

timeline for csp 600

timeline for csp 650

METHODOLOGY

week of report submission

25/ 11/2011- Proposal Presentation

two week after the presentation- submission of report proposal which is 9/12/2011

Progress:

1. complete with chapter 1, 3, 4 and 5 (chapter 4- hardware and software required while chapter 5 - research plan)
2. conclusion and literature review still not completed yet
3. trying to complete all the report as soon as posssible

NEXT PROGRESS

23 / 11/ 2011

• Review the content of slides with supervisor
• Make a correction of the slide

24/11/2011

• Prepare for presentation on the next day
• Make another correction on the research approach and methodology as well in the research background send the slides to Dr. Ariza Nordin

25/11/2011

• Presentation day
• Compete the report and to be submit 2 weeks after presentation

27/11/2011

• Chapter 3 almost done
• Continue with the chapter 2 to make several changes on the content

Preparation for final presentation

This week will be final presentation for project proposal and I will present in the first day...so nervous but hope the presentation going well.
Slides almost done and will be sent to Dr. Ariza by today (23/11/2011) and discussion on the slides with supervisor. Here some pictures of my slides.

Figure 1. Research Background

Figure 2. Project Timeline for semester 5 only

Figure 3. Significance of research 

New Objectives

There is a changes in the objectives such as below:

1. to identify the requirement of stores management system
2. to analyze the requirement of stores management system
3. to describe how the Soft System Methodology will be applied  in the stores management system

Progress in 1st week of November

2/11/2011 - 12.30 pm

•  Meet supervisor and discuss the 1st draft of proposal that have been submitted last thursday. 
•  Read an article about Soft System Methodology with detail explanation for each process in SSM and  how to draw a rich pictures.
• Make correction on the objectives. 

another csp's progress

24/ 10/2011

Interview with Pejabat Tanah & Galian Selangor. Also having an interview with Jabatan Kerja Raya Selangor regarding to final year project which is focus on stores management system. Based on the interview, several problems have been identified and now needs to come out with complete problem statement, research background and objective. It must be completed before this Thursday as it must be submitted for the 1st draft of proposal.

Progress

This week's progress..


17/10/2011

• Discussion with supervisor regarding to research background, problem statement and objectives  as well as methodology used.
• Contact with Bahagian Senggara Persekutuan Negeri (BSPN) JKR Selangor to get confirmation with whom need to interview to get the requirements. 

Requirement Engineering for Stores Management System using ORDIT modeling

Actually this topic just come in my mind after reading an article "USERS' INVOLVEMENT IN THE REQUIREMENTS ENGINEERING PROCESS " by Daniela Elena Herlea. In this article it stated the details of requirement engineering process and until one part the author mention about ORDIT (Organisational Requirement Definition for Information Technology System) in the subtopics which is in the requirement engineering methodologies. 

This is my first time hearing about this methodology and its quite interesting and I started to search about the topic. Unfortunately, around 2 or 3 article only that I've got. It's quite disappointing as I think that this methodologies can be used.From what I've read about ORDIT, it focused more on the needs of the organization. The purpose is too support the precise statement from organizational requirement which are from the identification before transform it into an exactly what the organization needs. Furthermore, it is a contrast of waterfall model. In waterfall model the output from one stages can be used as the input for the next stages and so on but in ORDIT model all of the stages followed a predetermined order.

Analysis from other thesis

Today's story from me...

Today I have read a thesis from Mohd Arizan Abdullah from Universiti Teknologi Malaysia about Sistem Pengurusan Penyelenggaraan Peralatan IT in Majlis Perbandaran Johor Bahru Tengah. Actually this thesis was written in 2009 and the writer was a Bachelor student of Science in Computer Science.

Based from my reading, this thesis quite good which is he stated the details of what he was doing from the gathering information till deployment of the system. In the beginning, he identify what is the problem statement that arise in the organization and how to solve the problems. He also done a few research from other resources on what techniques that most suitable in order to solve the problems. The next chapter, the author focus on the methods or way to identify problems in that organization. Some methods that he found were research from the Internet, interview with people who involve in the system development or stakeholder and observation. 

Furthermore, this thesis discuss on the methodology that he used which is using a prototype model evolution. It was used to solve weaknesses that involve in waterfall model. This methodology is actually a process that iterate several phases in SDLC which are analysis, design, implementation and evaluation. 

Next, he wrote details about every phases of prototype model which consists of six phases. The phases are as below:

1. Planning the system
2. Analysis requirement
3. Design 
4. Implementation
5. Testing and Evaluation
6. Operational and maintenance

The next part was the system development which the writer's aim is to producing system that is able and capable of meeting all of the requirements and needs as well as can achieve all the objectives. Lastly an appendices about the system, all of the diagram and other data that have been collected during the development of this system.

Enterprise Storage Management System (Mohamed Fayad)

This journal is a detailed of enterprise storage management system of Lincoln Telephone Company. It is used to monitor the file system in storage, backup automatically, recover data and provide statistic information. Other than that, this journal explains about the issues that will arise in order to develop a storage system. The issues discussed such are the network, backup, analysis report, efficient mechanism to format available disk, identify resources that are added or deleted to the network and many more. Furthermore, it describes about the details requirement that the company needed and a use case diagram were provided to illustrate the real actor and what does they do towards this system. Lastly, the author describe about the interface of the system. The author said that this system does not required interface with other applications that the company are using as the system does not directly change the data. This system also protect any data created by any application in a better way.

Research Background CSP 600

PROJECT TITLE: STORES MANAGEMENT SYSTEM
PROJECT AREA: REQUIREMENT ENGINEERING

Research Background


Stores Management System can be defined as a system and processes that identify inventory requirements, set target, provide replenishment techniques and report actual inventory status. The main things that this system can do is determining and controlling the stocks of the equipments. Stores management system usually used in retail and manufacturing industry. It helps the manufacturer or retailer having problems to manage the stocks.
There are several issues that need to take into consideration in store management system. It can be divided into four major issues such as backup issues, network issues, platform issues and other risk issues. In term of backup issues, store management system needs to have an efficient way to backup and recover the data. It can be done by using a distributive or centralized backup and certain backup could fail due to network failures.
The next issue is focus on platform that will be used. This issues focus on what type of platform that can run the system either it can be run on multi-platform or suitable just in one platform.
Other risks that do not mentioned above can take into consideration as an additional issue for this system. Such risks are the person who in charges of the system quit the job, additional cost to maintain the system and natural disaster.
There are several requirements that are important in order to develop an inventory system and most of the requirements is comes from the user. Improper requirement or lack of information in requirement stages will leads to system failure. The most important part in requirement is on how the data that will be collected, who will involve and what user actually needs. In this topic area of requirement engineering, the focus is actually in requirement elicitation and analysis.