Saturday 5 November 2011

WEEK 8

31/10/2011 – Search articles

·         Find some articles and conference paper.
·         Search in text book (System Analysis & Design in a Changing World, 2009).

3/11/2011 – Meet supervisor

·         Discuss problem statement and objectives.
·         Discuss a little bit about literature review.
·         Search articles, journal, conference paper, thesis, report and presentation.
·         Look into text book (System Analysis & Design in a Changing World, 2009).
·         Choose the right journal and conference paper as the review for literature.
·         Redo the chapter 1

 Research Background
Unit Keselamatan is one of the departments that manage the security of Uitm Shah Alam especially for visitors who comes in and out of this campus. Currently, the management of Unit Keselamatan for visitors is manual record process and does not have web-based system. Because of that, guards have faced difficulties to track the visitors, have an issue in storage record and cannot produce report systematically. The data are not integrated between post guards at two main gates with head office of Unit Keselamatan. 
 In order to solve the difficulties, Visitor Management System (VMS) is going to develop for Unit Keselamatan to increase the efficiency and more systematic in their management. VMS is a computer based system and in this research it focus on the design and development.

 Problem Statement
The requirements specification for VMS that has been done before is still not enough and incomplete in order to proceed with the next phases which are design and develop. The descriptions of requirements specification are not clear such as the use case diagram and use case descriptions is not fully understood.
                According to Rowen (1990), in the early phase, the requirements are not state clearly and this will leads to incomplete as well as incoherent of descriptions. Some researchers state that “when software engineers face incomplete requirements, they attempt to fill the gaps by information from the stakeholders or by assumptions” (Albayrak O., Albayrak D. and Kilic, 2009). Most of project failures are caused by incomplete requirements where the qualities of requirements affect the quality of project.
                A study was conducted by Mayumi Itakura Kamata and Tetsuo Tamaito, show the corresponding of software requirements specification (SRS) affect the project performance (2007). The study is analyzed by three cases which are normal project group, cost overrun and time overrun using different techniques. The final results indicate that there is relationship between SRS quality and project outcomes (Mayumi Itakura Kamata and Tetsuo Tamaito, 2007).

 Aim
To conduct Design and Development processes for VMS.

 Objectives of the Research
1.       To amend the requirements of VMS.
2.       To verify and validate the requirements of VMS with stakeholders.
3.       To design and develop VMS based on the requirements gathered.

 Research Scope
The scope of this project is for Unit Keselamatan UiTM Malaysia to manage the visitors coming in and out of UiTM via two main gates.

 Significance
This system will benefit three groups of stakeholders which are top management of unit keselamatan, staff of unit keselamatan and visitors.
From the top management perspective it will provide them with simple and effective way in visitor management system especially to register and to get statistic of visitors. These systems will ease the management of visitors.
Other than that, this system can increase the security of community in UiTM which including the staffs, lecturers and students. The staff can know that only valid visitors are welcomed besides knowing which building the visitor is and when they come in and out of UiTM. The community will have mind peaceful in term of security.
From the visitor perspective, this system will make the registration process faster and easier for them.


 ·         Write the literature review.

Author(s)
Type
Title
Purpose/
Objective
Important Quotes
Remarks/
Opinion
Mayumi Itakura Kamata and Tetsuo Tamai (2007)
Conference
How Does Requirements Quality Relate to Project Success or Failure?
To fill the gap of evidence concerning the relation between requirements quality and project outcomes.
‘When the hypothesis is refuted, it implies that the corresponding
SRS item can be a factor that affects the project performance’.
This conference shows the relationship of requirements quality and the effect of the project when the SRS is conducted using different technique.
Russell Appleyard (2006)
Conference
 Visitor Management System

‘The VMS is a system by which computerized visitor logs will be generated and temporary self-expiring paper badges will be issued for all visitors entering the TSA Headquarters Buildings and the TSOC’.
This paper state that they use VMS to implement the security of works for employees and visitors.
They also describe how, where, what, who, and why they used VMS.
Michael G. Christel and
Kyo C. Kang. (1992)
Conference
Issues in Requirements Elicitation

• achieving requirements completeness without unnecessarily constraining
system design
• analysis and validation difficulty
• changing requirements over time
The paper is discussed on how to enhance the requirements elicitation and the tasks that should be done.
Ksenia Ryndina (2005)
Thesis
Improving requirements engineering: an enhanced requirements modeling and analysis method


‘To improve requirements specification methodology by enhancing the approach that is most popular at the moment-use case modeling’.
This paper describes on how to improve the requirements specification, evaluates the tool that is used and provide the case study.
Özlem Albayrak, Duygu Albayrak andTuna Kılıç (2009)
Journal
Are Software Engineers’ Responses to Incomplete Requirements Related to
Project Characteristics?

When faced with incomplete requirements, software engineers attempt to fill the requirements’ gaps differently, either by getting feedback from the user or by making assumptions’.
This journal states that the effect faced by software engineer regarding to incomplete requirement and the results of conducting an experiments.
Edwin de Jong, Jozef Hooman and Jaco van de Pol
Case Study
Refinement in Requirements Specification and Analysis: a Case Study

During the
early phases of system development, where the exact requirements
are yet unclear, these techniques allow to write
incomplete and global specifications, which during successive
steps can be refined and completed’.
The case study is conducted by using techniques that refine the requirements specification.
Robert B. Rowen (1990)
Journal
Software Project Management Under Incomplete and Ambiguous Specifications

‘Requirements are assumed to be ambiguous and incomplete. The
contents of a requirements document are discussed with the perspective
that requirements will always be incomplete until late in the development cycle’.
This journal discuss about the major problems occur in classical life cycle and use the prototyping to success.
John satzinger, Robert Jackson and Stephen Burd (2009)
Book
System Analysis & Design in a Changing World

 ‘Design the solution system based on the requirements defined and decisions made during analysis’
This article gives the details of design phase and design activities that must be completed.

 Design
Design is the third phases in SDLC which comes after analysis phase. Design means general arrangement or pattern that is mapped onto diagram. Design shows the system engineer or developer to understand what system they should build that based on requirements specification which has been defined in previous phase. As stated in book name System Analysis and Design in a Changing World, objective of design activities is to “Design the solution system based on the requirements defined and decisions made during analysis” (pg 46). In design phase, there are activities that must be done which are design and integrate the network, design the application architecture, design the user interfaces, design the system interfaces, design and integrate the database, prototype for design details and design and integrate the system controls (Satzinger J.,Jackson R. and Burd S.,2009).

 Visitor Management System
Visitor is the person that comes into a certain place that has some business to do. Visitor management means the organization of visitors come in and out of the place. Mostly, visitors will go to front desk of building to get the pass or register by fill in form before they settle their problems. This is the procedure of the company or organization to implement the security of works for employees and visitors. According to Russell Appleyard he states that “VMS is a system by which computerized visitor logs will be generated and temporary self-expiring paper badges will be issued for all visitors entering the TSA Headquarters Buildings and the TSOC” (2006). This procedure is very important in order to track the visitors who entering the company and knows what the purpose they come. So that, the security guards can take an actions if anything happens in the company.

Incomplete Requirements Specification
Requirements mean the collection of data or information that is needed. Incomplete requirements mean the collection of data or information is not enough and not complete. As remarked by Jong E., Hooman J. and Pol J., the actual requirements are yet not stated clearly in early phases of system development. While Rowen R., B. (1990), assumed that requirements as ambiguous and will be incomplete till the final of process development.
Incomplete Requirements Specification may lead to project failures. According to Albayrak O., Albayrak D. and Kilic T., “when faced with incomplete requirements, software engineers attempt to fill the requirements gaps differently, either by getting feedback from the user or by making assumptions (2009)”. The experiments have been conducted by Mayumi Itakura Kamata and Tetsuo Tamai (2007). They have found that “when the hypothesis is refuted, it implies that the corresponding software requirements specification (SRS) item can be a factor that affects the project performance. Requirements specification need to be identified the whole in many aspects in term of objectives, stakeholders, and other information needed that is important in order to complete the requirements. This issue is important before proceed with design and development phases to ensure that the cost and time is not overrun.

·         The literature review is not done yet due to the ambiguous problem statement and objectives.

4/11/2011 – Submit 1st draft of chapter 2.

No comments:

Post a Comment