FEDERAL UNIVERSITY LAFIA

BSc. COMPUTER SCIENCE

CSC 411: SOFTWARE ENGINEERING

SEMESTER 1 2019/2020
Coursework Component 1

Learning Outcome Assessed Learning Outcome : 1

Discuss and analyze problems associated with
the development of large software.

Learning Outcome : 2
Find Solutions to computing problems

Learning Outcome : 3
Plan and carry out software engineering
processes to support the management and
development of quality software systems.

Learning Outcome : 4
Implement, test and document a
software system to professional
standards, making appropriate
implementation decisions

Learning Outcome : 6
Identify solutions to problem. Design and
Implement Graphical User Interfaces.

Learning Outcome : 7
Present Information in a clear, logical and
professional manner

Weightage 100%

Assignment Title Analysis and Design of Software Systems

Maximum Word Limit >2000 < 5000 words

1
Submission Deadline

To Be Handed In To GO2, GO3 Computer Science Department

2
A. Scenario

The General Manager of ABC Insurance Company wants to develop a web-based third-
party motor insurance system for handling quotation, order and payment of motor
insurance for its customers.

A customer can search for one-year third-party motor insurance plan by using the system.
The customer enters the reference number of an insurance plan (for customer who has
made a quotation request) or the following information: type (saloon, sport, or other),
engine size (in cc), NCB (no claim bonus in percentage, 0%, 20%, 30%, 40%, 50%, or
60%), year of manufacture, driving experience (in years) and involvement in any motor
accident or conviction of any driving offence during last 5 years (yes, no).

The system searches for all the possible insurance plans available and displays the
cheapest insurance plan to the customer.

The price of buying the insurance plan is the standard cost of the cheapest insurance
plan x (1 – NCB/100).

Each insurance plan contains the required range of value of each data attribute inputted
by the customer. The following are examples of insurance plans:

Plan A. Standard cost = HKD 2500 per year. Requirements: type: saloon, engine size <=
2000 cc, year of

manufacture >= 2002, driving experience >= 5, involved in accident or convicted of any
driving offence during

last 5 years = no.

Plan B. Standard cost = HKD 5000 per year. Requirements: type: any, engine size >
2000 cc, year of

manufacture = any, driving experience < 5, involved in accident or convicted of any

driving offence during last 5

years = no.

Plan C. Standard cost = HKD 10000 per year. Requirements: type: any, engine size =
any, year of manufacture

3
= any, driving experience = any, involved in accident or convicted of any driving offence
during last 5 years =

yes.

For example, Plan A requires that the driving experience is equal to or more than 5 years
and the engine size is

less than or equal to 2000 cc and the type of the car is saloon. If the system cannot find a
matching insurance

plan, the customer makes a quotation request by entering his/her name, email address,
phone number, and details of involvement in any accidents or conviction of any driving
offence. The system then saves the data inputted by the customer for searching
insurance plan as well as the data just inputted to create the quotation request.

The customer can buy an insurance plan by first searching an insurance plan as
described in previous paragraph. The customer then buys an insurance plan by entering
starting date of the insurance, his/her name, vehicle license number, engine number,
chassis number, and credit card information (card number, type, and expiry date). The
system charges the policy price to the customer’s credit card through an external
payment gateway.

The payment gateway returns an approval code if the credit card transaction is
successful. If the system receives the approval for the credit card transaction, it displays a
preliminary insurance policy which contains a policy number and all other information of
the customer and the car. Otherwise, the systems will ask the customer to reenter the
credit card information.

A sales representative of the company can handle quotation request with the system.
The sales representative selects a quotation request. The system displays the details of
the quotation request. The sales representative enters whether the company would
accept the quotation request and how much of the price for this tailor-made insurance
plan. If the quotation request is accepted, the system generates a unique reference
number of the insurance plan for the customer and notifies the customer the price and
reference number of the insurance plan through an email. The customer can then buy an
insurance plan with the procedure as described in previous paragraphs. If the quotation
request is not accepted, the system sends a reject message to the customer through an
email.
4
A customer can renew an existing insurance policy with the system if he/her has not
made any claim in the period of the existing policy. The customer enters the policy
number of his/her insurance plan. Based on the information from the insurance plan, the
system searches and displays the cheapest insurance price. If the NCB of the customer
is 0%, then the NCB for renewal of his/her insurance plan is 20%. If the NCB is between
20% to 50%, then the NCB for renewal is 10% more. If the NCB is already 60%, then the
NCB for renewal remains unchanged. The customer confirms the renewal of the
insurance policy and pays for the renewal of policy as described in the payment
procedure using credit card in previous paragraph

5
Tasks:

1. You are required to read carefully the scenario given above, then to provide a clear
system analysis, design, implementation, testing and documentation details which should
prove your understanding of the software development processes.

2. Guidelines including the activities and tasks you should perform and provide, are given
below:

• Planning:
3. System Request
4. Feasibility Study

• Analysis & Initial Design:

3. Analysis Strategy:
a. Analysis of the System
b. Proposed to be-System
4. UML diagrams
a. Use-case
b. Sequence
c. Class

• Design:
3. Design Strategy
4. Package Diagram

• Implementation:
3. Construction of the system and the appropriate GUI.
4. Testing

• System Documentation

6
ASSIGNMENT SPECIFICATION

 The answer should be in the report format addressing the given questions and
where necessary diagrams and charts must be provided. They are to be typed or
word processed and may include a bibliography.

 The report is to be 1.5 line spaced. It is easier for markers to read and to comment
on it.

 The report should be in font size 12 of Arial font face printed on single sided A4
paper.

 The report must contain the student matriculation number as the header and the
name of the module and page numbering as the footer.

7
 Matriculation Student Name:
No.
Course Name Software Engineering Type of coursework Assignment-
/reference no.
Title of the
coursework
Student’s I certify that this assignment is my own work and where materials have been used from other
Declaration resources, they have been properly acknowledged. I also understand that I will face all the
possibility of failing unit if the contents of this assignment are plagiarized.

Signed : ____________________ Date : __________________

Tick as appropriate Marks obtained

Year Year Year

One Two Three
Date handout 11 Feb, 2020 Date Due

Date received

Assessor’s
comments/
Feedback.

Student’s
comments

Name/Signatur Name & Signature of

e of Assessor Internal verifier.

Date Date

Additional Instructions

1. All coursework submitted must include

8
 a. a copy of the full brief given by the module leader (with the signed coversheet)
b. all source material must be cited in the text and a full bibliography of source material
(including author, title, publisher and date) listed at the end of the submission

2. All work must be submitted in the mode instructed by the module leader.
3. Work submitted under the student’s name must only be the work of that student. All information sources
must be acknowledged. Plagiarism is a serious offence and will render offenders liable to disciplinary
action.
4. Students MUST keep a copy of all submitted work for reference purposes prior to the original being
handed in and returned. This will provide proof that the work was completed, in the event that the work
goes astray.
5. Whenever a candidate submits work after approved deadline without an authorized extension, a mark of
zero (0%) will be awarded. Module Leader may comment on the quality of the work for learning
purposes.
6. Requests for extensions of submission deadlines must be made in writing prior to the submission deadline
to the module leaders and must be supported by documentary evidence.

9
 FEDERAL UNIVERSITYLAFIA
COMPUTER SCIENCE

ASSESSMENT CRITERIA AND GRADING SHEET

10
Self Evaluation – Group Number [ ]

S Matric Name Contribution

N Number

11