Object Orientated

Analysis, Design and

Implementation
7CS091

Dr. Hong Qing Yu (Harry)

Fundamental Facts and 4FFXXX
Contents
Module Leader......................................................................................................................................3
Key dates and details.............................................................................................................................3
Description of the assessment...............................................................................................................3
Assessment Content..............................................................................................................................4
Assessment Rubric.................................................................................................................................4
Anonymous Marking.............................................................................................................................6
Assessment Regulations........................................................................................................................6
Formative..............................................................................................................................................6
Module Leader
Dr. Harry Yu
Email: [email protected]
Phone: 01332592404
Office Hours: Monday 11-12 and Thursday 11-12

Key dates and details

Assessment Type: System requirement analysis, design and Development

Assessment weighting: (CW1 60%, CW2 40%)
Word Count Up to 2500
Learning Outcomes: 2
Submission Method: Turnitin
Date Set:
Submission Date: CW1 at 4pm, end of week 7 at 12/11/2021 (Friday)
CW2 at 4pm, end of week 12 at 14/01/2022 (Friday)
Provisional Feedback Release Date: In 14 days

Description of the assessment

This coursework is completed in 2 parts, you need to apply suitable industrial approaches to the
design and implementation of a software system using Object Oriented principles. This information
system uses a web server to manage the data for multiple people and can be accessed by
web/mobile client application. The system design and development will involve design pattern, UI
implementation and database design.
Assessment Content
Derby University Computer Knowledge Specialists (DUCKS) have a number of projects that they need
to develop:

1. A web survey generation and data collection site – allowing clients to host data collection on
Duck servers.
2. A generalised Auction Software site – allowing clients to host auctions on DUCKS servers.
3. A generalised Rental Software site - allowing clients to rent stuff (lawnmowers, cars, tools
etc.) using DUCKS servers
4. A simple banking (savings and loans) system for Credit Unions.

You must provide design and prototype for the following basic functions through CW1 and CW2:

 Collect data into databases.

 Registration for users and administrators

CW 1 (Learning outcome 1, 2) 60%

Deliverables:

A design portfolio for the indicated system: The outline below provides the structure for the design
report; during the lectures you will learn about the steps required to successfully design and
implement the system using Object Oriented principles. You are also expected to do your own
research on what should be included in the report. 1.

Introduction (10%) Week 3 Sprint 1

1.1 Purpose, Scope and Objectives of the Project

1.2 Project Description
1.3 Project Deliverables with detailed time planning
1.4 Development Environment (detail the tools and techniques used)

2. Software Requirements Specification (Assignment 1) (10%) Week 7 Sprint 2

2.1 Functional Requirements

2.2 Non-Functional Requirements

2.3 Domain Requirements

3. System Design (60%) Week 7

3.1 Software Model

 Use cases and use case models 10%

 Class diagrams (optional stub code for review) 30%

3.2 Architectural Design (Client/Server Organisation of components) 10%

3.3 User Interface Design (Presentation Layer UX Screen Designs) 10%

Critical Review (1000 – 1200 words) (20%) Week 7

o Critical reflection on the use of design patterns within the project (10%).

o Critical review and reflection on the use of software engineering techniques within the software
community (10%).

There is no penalty for exceeding the word limit as it is just guidance, not a rule.

CW1: What you are expected to submit Friday in Week 7:

o Appropriately formatted text document containing all relevant information.

Submission must be in Word (.doc, .docx) file format if you don’t want written feedback to provide a
PDF document.

All these will be reviewed, assessed and feedback provided with the tutor in Week 7 in the
practical.

CW 2 (Learning outcome 3,4) 40%

Deliverables:

The implementation of this design within a suitable application paradigm using OO programming
language.

Implementation 100% 14/01/22

Demo (Friday 14th Jan 2022): Implemented code for the project designed for CW 1 in appropriate
language (including databased modelling and simulations of the communication), which include:

functional implementation of features indicated in the design plan 20%

Appropriate use of design patterns and OOP and web techniques 15%

User Interface/Presentation Layer 10%

Completeness of System in relation to the design 20%

testing strategy and results 10%

Demonstration of the System 10%

Conclusion 15%

(What has been learnt and Critical Evaluation of the System 1500 words max.)
CW2: What you are expected to submit:

o A zip file containing the fully demonstrable prototype

o An appropriately formatted text document

o Screencast demonstrating functionality (mobile phone recording is fine)

o An appropriately formatted text document containing all relevant information. PDF or Word file
preferred.

The work should be no more than 2500 words in total. There is penalty for exceeding the word limit.
 Assessment Rubric
The assessment rubric on the next page shows the complete criteria of the CW and how you will be
assessed. We will explore the content of the rubric together in a synchronous session on first week
session.

When the assessment is returned you will receive a digital version of the rubric showing how you
performed against each criterion. You will also receive a short individual audio file that highlights
both the strengths of the work and your key areas for development. There will be an opportunity to
discuss these with your personal academic tutor.

Sensitivity: Internal
CW1 Rubric
20-39 40-49 50-59 (Passing grade band) 60-69 70-100

Introduction plans clear enough to see mostly

(10) what will be done and when. If Good justification and plans clear Very well thought out and
Minimal justification and planning plans someone else were to take these enough to see what will be done when. planned. If someone else were
Not thought out, or not clear enough to see what will be plans they could likely complete the If someone else were to take these to take these plans they too
planned. Impossible to done when, although what will be done project on time, although there are a plans they too could mostly complete could complete the full project
see where this is going is articulated. few gaps. the project on time on time

Software Appropriate use of just

Requirements one of the following: Appropriate use of a least two of the Excellent use of patterns, client
(10) patterns, client server following: patterns, client server Satisfactory application of patterns, good use of patterns, client server server solutions and OOP
solutions and OOP solutions and OOP including client server solutions and OOP solutions and OOP including including
including polymorphism polymorphism principles. polymorphism/abstraction polymorphism/abstraction

User Interface Complete set of Screen Designs,

Design (10) Most screen designs present, Complete set of Screen Designs, good Excellent Layout, Creative
Screens present, not well Most screen designs present, Satisfactory Excellent Layout, good intuitive Layout, good Intuitive design choices, Intuitive design choices,
thought out. No natural Layout, good intuitive design choices, design choices, satisfactory good/intuitive navigation between excellent navigation between
flow/navigation. poor navigation between screens. navigation between screens. screens. screens all implemented.

Architectural Client side code with little server side The system works client-side and Good client server software with Excellent client/server
Design(10) Minimal Client Code only working server-side with some limitations. persistence. persistent solution.

Software Model excellent multiplicities and

(40) Use Cases and Class diagram with relations and a formal
Use Case and Class Diagram with all appropriate multiplicities and relations representation of attributes and
Use – case only and poor classes identified but not in the correct Use Cases and satisfactory Class and formal representation of attributes functions on the class diagram
class diagram. way. diagram and functions with inheritance with inheritance and interfaces

Critical Review A report with little or no A thorough critical analysis of

(20) research. A very limited the technologies and tools and
review of tools, Some critical analysis of the A good critical analysis of the process to be used in producing
technologies and technologies and tools. A good set of technologies and tools. A good set of the App. A comprehensive set
processes. Some critical analysis of the design tools. references. references. of references.
 CW2 Rubric

20-39 40-49 50-59 (Passing grad band) 60-69 70-100

Functional A couple of weeks behind development

Implementati milestones. No fundamental bugs The App is completed on time Excellent progress against
on (20) Not much progress made on though there may be some gaps in with some bugs. Functionality The App is completed on time with development milestones. The App is
development milestones. functionality. A clear strategy for is as expected with some bug some minor bugs but all functions completed on time with almost no
Hardly any functionality. completing the assignment. and gaps in functionality. implemented. bugs.

Patterns, Appropriate use of just one of Appropriate use of a least two of the
OOP, the following: patterns, client following: patterns, client server Satisfactory application of good use of patterns, client server Excellent use of patterns, client
Client/Server server solutions and OOP solutions and OOP including patterns, client server solutions and OOP including server solutions and OOP including
(15) including polymorphism polymorphism solutions and OOP principles. polymorphism/abstraction polymorphism/abstraction

UI/User Most screen designs present,

Experience Most screen designs present, Excellent Layout, good Complete set of Screen Designs, good Complete set of Screen Designs,
(10) Screens present, not well Satisfactory Layout, good intuitive intuitive design choices, Layout, good Intuitive design choices, Excellent Layout, Creative Intuitive
thought out. No natural design choices, poor navigation satisfactory navigation good/intuitive navigation between design choices, excellent navigation
flow/navigation. between screens. between screens. screens. between screens all implemented.

Completeness The system works client-side

of System Client side code with little server side and server-side with some Good client server software with Excellent client/server persistent
(20) Minimal Client Code only working limitations. persistence solution.

Testing No change in the design since Some well thought out

Strategy (10) first Phase. Superficial does it testing strategy, a few bugs
run? Some well thought out testing strategy found. Some Bugs found through testing All bugs found through testing

Demonstratio A limited set of functions, A good set of functions, a mostly

n (10) Some limited functions A satisfactory set of functions, an some testing, the demo is complete program, well tested, a A good set of functions, an original
evident but not sufficient in incomplete App, some testing, some satisfactory, convincing, sells small no. of bugs. The demo is well System, well tested, may have
the time allocated. Nowhere bugs. The demo is ready but the the idea but not well thought out, convincing, sells the insignificant bugs. The demo is
near complete, little or no program is limited and incomplete it is prepared. The App is mostly idea okay. A good feel for what the polished, convincing, and sells the
testing. barely acceptable. complete. system brings. idea well.

Critical A report with little or no A thorough critical analysis of the

Analysis (15) research. A very limited Some critical analysis of the Some critical analysis of the A good critical analysis of the technologies and tools and process to
review of tools, technologies technologies and tools. A limited set of technologies and tools. A technologies and tools. A good set of be used in producing the App. A
and processes. references. good set of references. references. comprehensive set of references.

Sensitivity: Internal
 CW2 Rubric

Anonymous Marking
You must submit your work using your student number to identify yourself, not your name. You must not use your name in the text of the work at any
point. When you submit your work in Turnitin you must submit your student number within the assignment document and in the Submission title field in
Turnitin. A video showing how to do this can be found here (link).

Assessment Regulations
The University’s regulations, policies and procedures for students define the framework within which teaching and assessment are conducted. Please make
sure you are familiar with these regulations, policies and procedures.

Formative
CW1: What you are expected to submit Friday in Week 7:

 Appropriately formatted text document containing all relevant information.

 Submission must be in Word (.doc, .docx) file format if you don’t want written feedback to provide a PDF document.
 All these will be reviewed, assessed and feedback provided with the tutor in Week 7 in the practical.
 No more than 1200 words

CW2: What you are expected to submit:

 A zip file containing the fully demonstrable prototype

 An appropriately formatted text document
 Screencast demonstrating functionality (mobile phone recording is fine)
 An appropriately formatted text document containing all relevant information. PDF or Word file preferred.
 The work should be no more than 1300 words in total. There is no penalty for exceeding the word limit.

10

Sensitivity: Internal