Monday, 24 October 2011

Progress : Catering Ordering System

Project Background
Catering Ordering System is a system that provide customer catering packages that can be customized according to customer preferences. Currently, catering packages is advertise through website and customer is required to make order manually, either via email or call. Most of the customer make orders by giving insufficient / incomplete information regarding their personal and ordering details.

Problem Statement
Since customers is required to make orders manually, most of them provide insufficient / incomplete information regarding personal and ordering details. It will cause a problems when the caterer want to process the orders.

1)  To gathered and analyze requirement for customizing catering packages according to customer   preferences.

2) To obtain requirement verification.

Friday, 14 October 2011

Motivation : Light in the dark

After met Puan Suriati this evening, i have a thought that..

"I believe there will always be a light in the dark"

Thank you.. 

Reading : Requirement Engineering.

Some very useful info found today~~

"Requirements Engineering (RE) is a set of activities concerned with identifying and communicating the purpose of a software-intensive system, and the contexts in which it will be used. Hence, RE acts as the bridge between the real-world needs of users, customers, and other constituencies affected by a software system, and the capabilities and opportunities afforded by software-intensive technologies."

Requirements’ suggests that there is someone out there doing the ‘requiring’ – a specific
customer who knows what she wants. In some projects, requirements are understood to be the
list of features (or functions, properties, constraints, etc.) demanded by the customer. In
practice, there is rarely a single customer, but rather a diverse set of people who will be affected
in one way or another by the system. These people may have varied and conflicting goals. Their
goals may not be explicit, or may be hard to articulate. They may not know what they want or
what is possible. Under these circumstances, asking them what they ‘require’ is not likely to be

Engineering’ suggests that RE is an engineering discipline in its own right, whereas it is really
a fragment of a larger process of engineering software-intensive systems. The term
‘engineering’ also suggests that the outputs of an RE process need to be carefully engineered,
where those ‘outputs’ are usually understood to be detailed specifications. It is true that in some
projects, a great deal of care is warranted when writing specifications, especially if
misunderstandings could lead to safety or security problems. However, in other projects it may
be reasonable not to write detailed specifications at all. In many RE processes, it is the
understanding that is gained from applying systematic analysis techniques that is important,
rather than the documented specifications.

Tuesday, 11 October 2011

Reading : Requirement Analysis

Requirements analysis includes three types of activity:
  • Eliciting requirements: The task of communicating with customers and users to determine what their requirements are. This is sometimes also called requirements gathering.
  • Analyzing requirements: Determining whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolving these issues.
  • Recording requirements: Requirements might be documented in various forms, such as natural-language documents, use cases, user stories, or process specifications.
Systematic requirements analysis is also known as requirements engineering. It is sometimes referred to loosely by names such as requirements gathering, requirements capture, or requirements specification. The term requirements analysis can also be applied specifically to the analysis proper, as opposed to elicitation or documentation of the requirements, for instance. Requirements Engineering can be divided into discrete chronological steps:
  • Requirements elicitation,
  • Requirements analysis and negotiation,
  • Requirements specification,
  • System modeling,
  • Requirements validation,
  • Requirements management.