PSB260CT
PSB - CU 1 08/2020




MODULE 260CT Software Engineering
ASSESSMENT TYPE Assignment / Lab Test (Coursework)
ASSESSMENT MODE Individual / Group
WEITAGE (x/100%) 50/100
HAND-OUT DATE 18 August 2020
DEADLINE 29 September 2020


Assignment Deliverables and Conditions:
• Final Documentation must be word processed. The maximum of 3000 words is recommended.
• Please consider the environment and don't print unnecessarily.
• Late submissions will be awarded ZERO marks. If you have a genuine reason for needing to submit late, you can request
an extension from faculty registry (at reception).
• Your document should be submitted as a PDF in the form NAME_260CTSECW.pdf, where NAME is your name in camel
case.
• Citation of facts is mandatory. Obtain your facts from credible sources into references / bibliography. Avoid ‘dumping
of data’. Instead the facts that you discuss should be made relevant to your case/project.

LEARNING OUTCOMES COVERED TASK
Describe and apply appropriate concepts, tools and techniques to each stage of the software
development
Task 1.1, 1.2, 1.3, 2.1,
4.1 & 5.1
Describe and apply design patterns and software components in developing new software Task 3.1, 3.2
Use a CASE tool to produce user requirements, conceptual domain/analysis models, design
specifications and code for a software solution
Task 1.2, 1.4, 2.2, 3.2



PLEASE CONSIDER THE ENVIRONMENT AND DO NOT PRINT THIS DOCUMENT UNNECESSARILY.
QUICK TIPS; UPLOAD ALL FINAL WORK INTO THE DEDICATED WEB PORTAL. CONVERT TO SLIDE FOR DISCUSSION or
PRESENTATION, DISTRIBUTE SOFT-COPY ONLY, PRINT DRAFT, PRINT CONTENTS ONLY, PRINT DOUBLE-SIDE, PRINT 2IN1,
USE RE-CYCLED PAPERS ONLY. THANK YOU.

PSB260CT
PSB - CU 2 08/2020

Case Study:
PureWater.com.sg
PureWater is an established local retail and distributor of water filter systems. It controls over 50 percent of the
market and remains a market leader amidst a growing number of competitors. The company currently operates a
shop located at Tampines Mall to serve walk-in customers. Customers can also opt for home delivery by placing their
orders via phone or email. The company takes feedback from its customers very seriously and will move quickly to
meet their needs. The company uses spreadsheets and manual processes for much of its data gathering and reporting.

In view of the growing number of customers opting for home delivery, PureWater is planning to establish an online
store within a year. The company recognises that there is a need to improve its systems for inventory, supply chain,
purchasing and customer service. Stocking and managing inventory are a growing concern as the inventory changes
dramatically depend on product line updates. The management of PureWater aims to be a market leader in the use
of technology to provide the best possible customer service with the broadest range of water filter systems. It has
plans in the future to expand its business into neighboring countries such as Indonesia and Malaysia.

Your team is assigned the project to develop the online store which among other standard functions will have the
following functions:

• Suppliers send their lists of inventories frequently to the store manager of PureWater. The store manager reviews
and compiles a list of water filter systems needed and sends an order to the supplier. The supplier delivers the
ordered water filter systems to the warehouse. The store manager records the quantity and details of the water
filter systems. The store clerk can then update the website.
• Customers can browse the website for water filter systems. In addition, they can read reviews and compare the
water filter systems. Those who wish to purchase online will need to initially register as a member for free. Being
a member has privileges such as discounts, gifts, etc.
• A member who wishes to purchase can easily select the item online and this will be captured in the website’s
shopping cart. The cart will show the summary of the selection and total cost to be paid. Once the payment is
made, the customer will be able to print or save the receipt. The store will deliver the air purifier to the customer
within 5 business days.
• The system should manage the information about all products (water filter systems and accessories) and it
should also store information about user opinions and product ratings. Staff should be able to manage online the
inventory and the customer delivery.

Task:
Assuming you are an IT professional employed by PerformSoft and your company is hired to develop the above
system. You have been given the task to analyze, design and develop a prototype for the given project. The following
tasks observes the SDLC flow for Software Engineering.

1. Project Planning
1.1. Problem Statement - Discuss the problems of the existing systems including the cause and the effects of it.
Briefly explain your proposed solutions.
1.2. Scheduling - Create a Gantt chart using a CASE tool, showing your planned project scheduling for the
proposed project, following a standard Software Development Model. (Caution; The Gantt Chart should
reflect the main and the sub-stages of developing your proposed project and NOT the development of this
coursework).
1.3. Requirement Gathering - Describe TWO techniques of information gathering (investigation or
requirement gathering) that you would apply for this project. Describe how each method would be used to
collect information. Discuss the benefits and setbacks of methods chosen. Attached some sample questions
where applicable.
1.4. Concept Diagram – Describe the new system for the above project. Conceptualize the new system with a
Use Case Diagram. Include at least TWO Use Case Description for vital processes. Use CASE tool to produce
the diagram.
PSB260CT
PSB - CU 3 08/2020
2. Analysis
2.1. SRS (System Requirements Specification) – Analyze the possible requirements for the new system.
Present the requirements, mainly Functional and Non-functionals. You may include other requirement
categories if applicable.
2.2. Analysis Class Diagram - Create a Class Diagram for the system based on the given requirement. Use CASE
tool to produce the diagram.
3. Design
3.1. Design Pattern – Identify an appropriate Design Pattern for the new system. Illustrate the design using a
diagram. Explain the design pattern in detail including its benefits and application to the system.
3.2. Design Class Diagram - Create a detailed Design Class Diagram for the system based on the given
requirement. Show components of the diagrams including aggregation and compositions. Use CASE tool to
produce the diagram
4. Implementation
4.1. Testing - Suggest a few Testing Methods suitable for your system. Create a simple Test Plan to show test
areas and expected results.
5. Selection of Methodology
5.1. Select and explain ONE IS development methodologies which you consider suitable to be used for this
project. Include any frameworks and/or diagrams as aid. State the reasons for your choice. Explain in detail
how your project will be developed according to the methodology stages.

Assignment Deliverables and Conditions:
• Final Documentation must be word processed. The maximum of 3000 words is recommended.
• Please consider the environment and don't print unnecessarily.
• Late submissions will be awarded ZERO marks. If you have a genuine reason for needing to submit late, you can
request an extension from faculty registry (at reception).
• Your document should be submitted as a PDF in the form NAME_260CTSECW.pdf, where NAME is your name in
camel case.
• Citation of facts is mandatory. Obtain your facts from credible sources into references / bibliography. Avoid
‘dumping of data’. Instead the facts that you discuss should be made relevant to your case/project.

Marks Allocation

Chapters Marks Allocated
1. Project Planning
1.1. Problem Statement 5
1.2. Scheduling - Create 5
1.3. 1.3. Requirement Gathering 10
1.4. Concept Diagram 10
2. Analysis
2.1. SRS 10
2.2. Analysis Class Diagram 10
3. Design
3.1. Design Pattern 10
3.2. Design Class Diagram 10
4. Implementation 10
4.1. Testing
5. Selection of Methodology 10
6. Overall Documentation 10

PSB260CT
PSB - CU 4 08/2020

Marking Criteria

A (80% and above)
The below requirements PLUS;
• General Compliance - This grade will be assigned to work where the documentation is complete and describes in detail, with
little or no errors, the following components: introduction, feasibility study, usage of SDLC, selection and application of
investigation techniques and analysis / logical design in accordance with excellent documentation standards. To obtain this
grade, the candidate’s individual assignment should show all techniques of process applied with little or no errors. All
deliverables of the individual component should be coherent with detailed description to explain the diagrams. In order to
obtain a grade at this level, individuals should be able to address all issues with regards to not only their own component of
the module but also be those of the other group members (if applicable). Individual’s contribution to the project, at this level
should be more than 75% and overall peer evaluation should indicate excellent standards.
• Problems and Solution - Core and hidden problems should be identified and clearly explained. Solutions should be of multiple
angle instated only one.
• Schedule Planning - Complete list of relevant tasks and sub-tasks are identified and relevant to project. Tasks duration and
well planned.
• Conceptual Design – Use case show all major and relevant tasks. Notation are accurately used. Task association is well
described. Use Case Description complete.
• RE – justification and methods of conduct clearly explained. Example or questions given a relevant/useful to projects
development.
• SRS – Excellent requirement elaboration excluding details of implementation including good technical references and
involved tasks.
• Analysis – Class diagram shows complete discussion of relevant class, supposedly based on SRS. Notation used are accrue.
• Design Diagram Complete diagram showing all possible tasks/components. Associated tasks/links are clearly shown an
explained. Detailed description of tasks included.
• Testing – Test challenges added with solution. Test plan is complete with additional information such as RISK indication.
• Methodology – Selection of methodology well justified. Benefits towards development is well explained. Tools and techniques
within methods addressed.

B (70% - 79%)
The below requirements PLUS;
• General Compliance - This grade will be assigned to work where the documentation is complete and describes briefly, with
some errors, the following components: introduction, feasibility study, selection and application of investigation techniques
and analysis / logical design in accordance with good documentation standards. To obtain this grade, the candidate’s
individual assignment should show all techniques of methodology applied but some errors. All deliverables of the individual
component should be coherent with detailed description to explain the diagrams. Overall documentation standards for both
the group project as well as the individual assignment should be of excellent quality (where applicable). In order to obtain a
grade at this level, individuals should be able to address most issues with regards to not only their own component of the
module but also be those of the other group members. Documentation should be fully cited.
• Problems and Solution - Core problems should be identified and clearly explained. Solutions should be explained in detail.
Multiple problem and solution expected.
• Schedule Planning - Major development tasks and sub-tasks are identified and relevant to project.
• Conceptual Design – Use case show most major and relevant tasks. Notations are mostly accurate. Task association is shown.
Use Case Description well described.
• RE – methods are well defined and justified, relevant information to be obtained explained. Basic sample question provided.
• SRS – Vital requirement included, good elaboration excluding details of implementation. Requirements categories in specific
group order.
• Analysis – Class diagram shows good discussion of relevant class, supposedly based on SRS. Notation used are mostly accurate
and present.
• Design Diagram – Good construction of diagram showing all possible tasks/components. Detailed description of tasks
included. Accurate notation used as per standard.
• Design Pattern – Good introduction of pattern concept and components. Advantages of pattern discussed. Application of
pattern into project is well described with relevant examples.
• Testing – Testing methods explained well, relevant to specific part of the system. identified. Problems during testing identified.
• Methodology – One or more methodology identified, good explanation of benefits to projects. Selection well justified.

C (60% - 69%)
The below requirements PLUS;
PSB260CT
PSB - CU 5 08/2020
• This grade will be assigned to work where, most of the basic requirements of the documentation listed above, such as
introduction, feasibility reports, logical process models are of adequate standard. The documentation should be of adequate
standard in terms of language, layout and flow. Some accurate, relevant and up-to-date referencing was visible. Where
applicable - Group presentation of the team should have adequate visual aids with relevant information presented and
adequate coordination among group members. Individuals should display an adequate level of professionalism and project
knowledge. Referencing and citation should be accurate.
• Problems and Solution - Common problems should be identified and clearly explained. Solutions should be explained in brief
and relevant to the system to be built. At least 3 problems-solution expected.
• Schedule Planning - Major development tasks are identified and relevant to project. Parallel and sequential tasks should be
indicated clearly.
• Conceptual Design – Use case shows relevant tasks. Notation mostly accurate. Task association is shown but not necessary.
Use Case Description has some discussion.
• Re – Methods are identified and explained well. Relent details of the event provided such as where, why, how, etc.
• Analysis – Class diagram shows major classes. Notation used are mostly accurate and present.
• Design Diagram – Good construction of diagram showing many major tasks. Basic description of tasks included. Acceptable
notation used as per standards.
• Design Pattern – Brief introduction and/or advantages outlined. Application of pattern into project is attempted.
• SRS – Good / useful requirement included, basic elaboration excluding details of implementation.
• Testing – Accurate testing methods identified. Benefits of testing discussed.
• Methodology – One or methodology identified, explanation relevant to project.


D (50% - 59%)
The below requirements PLUS;
• Basic information of the required section / question addressed. The documentation is of average standard in terms of
language, layout and flow. Acceptable referencing was done.
• Problems and Solution - Problems and solution and identified and explained in brief. At least 3 problems-solution expected.
• Schedule Planning - Basis planning is indicated. Chart is poorly constructed, parallel and sequential tasks should be indicated.
• Conceptual Design – Use case shows some tasks. Notation adhered but not following exact standard. Task association is not
properly shown. Use Case Description incomplete.
• RE – Methods are identified, basic explanation given with no/less relevance to case.
• SRS – Basic requirement included, simple elaboration.
• Analysis – Class diagram acceptable with few notation / conceptual errors.
• Design Diagram - Basic diagram included with few/major tasks. Tasks relevant to case.
• Design Pattern – Brief introduction outlined. Application of pattern into project is very brief
• Testing – Basic testing identified. Basic test plan included with limited details.
• Methodology – One methodology identified with basic elaboration irrelevant to project.

E (40% - 49%)
• Some / most components not discussed. Points are short and not justified. The documentation is of poor standard in terms of
language, layout and flow. Minimal referencing was made.
• Problems and solution - discussed but not relevant to system/solution. Less than 3 points discussed.
• Schedule Planning - Planning not clear or wrong tasks identified.
• Conceptual Design – Use Case (+Description) error - facts, notation and concept.
• SRS – Non / Basic requirement included, not elaborated.
• Analysis – Class diagram inaccurate / irrelevant.
• RE – Methods is poorly explained with no justification.
• Diagrams – Basic diagram included.
• Design Pattern – Explanation not relevant.
• Testing – basic testing outlined.
• Methodology – one methodology identified but generic / limited explanation.

Fail (0% - 39%)
• Component not attempted / missing / inaccurate.
• High Similarity from referencing check.