ICT239 The NSR has limited information on the problem and requirements for the application. Analyse the NSR in your group Canvas: Web Application Development Assignment, SUSS, Singapore

Question 2 (38 marks)
Part (a) of this question is a groupwork discussion with the start date being the first week of the Course Timetable available from e-Services through the Student Portal. If you do not see the Discussion link in the Canvas portal T-group by the end of the first week, please contact your tutor immediately.

You are asked to discuss with your fellow group members how to produce the structural model for the CRM system; i.e.:
 the class diagram; and
 the class description.

You must not post a complete class diagram to your group discussion board. The complete class diagram should only be submitted in your TMA solution document.

You should limit your discussions to identifying the classes, their attributes, the associations and relationships between the classes, and any invariants needed.

As part of your discussions, you are asked to submit TWO (2) or THREE (3) postings to the discussion board.

Examples of the types of postings that would gain you credit are:
 initiating a new thread of discussion about some significant aspect of the application; e.g., pointing out a problem in the requirements, suggesting how a particular aspect of the application might be modelled in terms of classes and associations or explaining why you think an invariant is needed;
 a response to a posting, where you attempt to resolve a problem that another group member has identified;
 a response to a posting, in which you state clearly and give evidence of why you agree or disagree with another group member’s suggestions, expanding significantly on what has been previously presented.

In all your postings, please maintain professional courtesy and avoid any comments that may give rise to unpleasant exchanges in the discussions. Remember that your comment may be correct even if someone else says it is incorrect.

Further notes:
 Do not include attachments in your postings.
 Justify each comment or suggestion you make. Simply saying “I agree. This is correct.” or “XYZ should be a class. What do you think?” is not enough. These are not meaningful discussions and will not be considered.
 Make postings that should be between a third and half a page long.
 Initiate a new thread of discussion in one of your postings.
 Focus on one aspect of the application, rather than attempting to cover all aspects of the application. For instance, an association, the attributes of a particular class or an invariant. Your posting should still leave scope for other members of your discussion forum to make a significant contribution.
 Postings that do not leave enough scope for the other members to contribute will be penalised.

Experience has shown that it is very difficult to obtain good marks for your postings if you attempt to make all your postings in a very short space of time. Time for reflection and measured judgement is an important part of this work.

(a) The NSR has limited information on the problem and requirements for the application. Analyse the NSR in your group Canvas discussion board and discuss possible classes, their attributes, the associations and relationships between the classes, and any invariants needed. Copy TWO (2) postings you have contributed to the discussion. For each posting, submit a screenshot AND a text copy of the posting.

(b) Develop a structural model for the system design by submitting the class description for the application.

Your answer should identify the classes, their attributes and any hierarchical
relationship(s), omitting any foreign key associations.
(14 marks)

(c) Complete the structural model for the system design, by appraising the associations among the set of classes in your solution to Question 2(b).

Construct the class association diagram in UML as your answer. Any derived association should be labelled, but you need not give the derivation.

Question 3 (52 marks)
Special note:
The information provided here is not necessarily applicable to the previous questions.
For the CRM system, the following requirement is given:

• Issue a cash voucher of amount dollars to the customer who is the highest spender for the month.
  From this, we extract the following information:
• Given a month and an amount, find the customer whose total sales transaction is the highest in the month and issue a cash voucher of this amount to this customer.
  From this, we can identify the use case: Issue Cash Voucher, with the following specification:
  Given: A month and an amount
  Goal: Create a cash voucher of amount dollars for the customer with the highest total sales transaction for the given month.

Figure Q3 shows a fragment of the class-association diagram with the Orchestrating Class relevant to this cas