Assignment Cover Sheet
Qualification Module Number and Title
HND in Computing/HND in Software Introduction to OOP- SEC4207
Engineering
Student Name & No. Assessor
Hand out date Submission Date
Assessment type Duration/Length of Weighting of Assessment
Coursework Assessment Type 100%
Report and Demo
Learner declaration
I certify that the work submitted for this assignment is my own and research sources are fully
acknowledged.
Marks Awarded
First assessor
IV marks
Agreed grade
Signature of the assessor Date
1
FEEDBACK FORM
INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY
Module:
Student:
Assessor:
Assignment:
Strong features of your work:
Areas for improvement:
Marks Awarded:
2
Coursework
Learning outcomes covered
1. Understand Object-Oriented Programming concepts and techniques
2. Design the Object-Oriented Programming solution
3. Implement Object-Oriented Concepts
4. Test the system and make the documentations for develop solution
Scenario and the Task
The Stock Management System is a complete dispensing workflow management system that is
designed to improve accuracy and efficiency. But the “Asian Paints” still use the manual
system. This manual system requires the Store Keeper to manually monitor each item request
that is available in different stocks.
“Asian Paints” face difficulties on maintaining records and applying security for the manual
records. Therefore, the most urgent concern of “Asian Paints” is to develop an automated Stock
Management System which helps them to improve inventory management and sales process.
There are different types of users involve with many operations, they are:
Manager – Creating and managing user accounts, view stock, sales and customer details,
if necessary update stock, sales and customer details.
Stock Keeper – add, view and update stock details.
Cashier – add, update and view customer records, add sales records and view stock
details.
3
Main requirements of the system
User authentications – ex – manager, stock keeper, cashier
Managing stocks – add and update stock details
Sales process.
Create and add new models.
Managing customer information.
Viewing Stock details, sales details and customer information
Assume you are an individual to develop this system, which leads you to perform as a project
manager, system analyst, developer, etc…
Students are free to make necessary assumption on system design & granting access
permissions other than mentioned within the scenario, but all suggestions must be well
explained with the valid reasons.
Task 1. Identify situations where you can introduce OOP concepts in developing a system for
the above given scenario (Classes, Objects, Inheritance, Abstraction, Polymorphism,
Encapsulation & etc.). Include necessary screen shots from your system, backed by required
explanations to support your answer Criteria (LO1) (Marks 10)
Task 2.Provide suitable Use Case diagram, a class diagram and sequence for the given scenario
with clear explanations on the design decisions. Whenever necessary document the relevant
assumptions you made (LO2) (Marks 15)
Task 3: Develop suitable system for the above scenario an interactive set of interfaces to get the
necessary user inputs. Make sure to implement proper validation mechanisms in order to restrict
4
invalid entries to the system. Implement a proper database to store information (LO3) (Marks
40)
Task 4: Document the test plan and explain with appropriate test cases. Explain the different
testing techniques and select the suitable technique to test your solution with the justification
Create user and technical documentation for the developed solution (LO4) (Marks 15)
Task 5: Provide appropriate conclusion including program strengths, weaknesses and
enhancement that can be accomplished with the given solution. Provide justification for the how
effectively you have use the OOP concept for the proposed solution (LO4) (Marks 10)
Task 6: Documentation should be done according to the given documentation guide lines. Also
need to maintain good academic writing throughout the report (Marks 10)
Guidelines for the report format
Paper A4
Margins 1.5” left, 1” right, top and bottom
Page numbers – bottom, right
Line spacing 1.5
Font
Headings 14pt, Bold
Normal 12pt
Font face- Times New Roman
Referencing and in-text citation should be done strictly using Harvard Referencing.
Referencing Guidance
To use Harvard referencing for citation and compile reference list you can go through
following guidance provided by Anglia Ruskin University.
5
In the Harvard system, the author's surname and year of publication are cited in the text
of your work. The full details of the source are included in a reference list at the end of
the assignment.
(Anglia Ruskin University,2013)
Assessment Criteria
This submission will be assessed as follows Total marks Marks obtained by
Allocated the student for the
answer provided
Task 1: Out of 10
POOR
No or very poor explanation give of using OOP 0-4
concepts for the given scenario.
No or very poor example given form the given
scenario to justify the answer
SATISFACTORY 4-6
Poor explanation give of using OOP concepts
for the given scenario.
Poor example given form the given scenario to
justify the answer
GOOD 6-7
6
Good level of explanation give of using OOP
concepts for the given scenario.
Good level example given form the given
scenario to justify the answer
EXCELLENT 7-10
Excellent explanation give of using OOP
concepts for the given scenario.
Excellent set of example given form the given
scenario to justify the answer
Task 2: Out of 15
POOR 0-6
Poor use of Object Oriented Design Methodology
Use case Diagram
Poor or no identification of use cases
Poor or no Identification of Actors and
associations
Sequence Diagram
Poor or no identification of set of use cases as
sequence diagrams.
Class Diagram
Poor or no identification of associated
methods, with correct signatures and attributes
in each class
Poor or no identification of relationships
SATISFACTORY 6-9
Proper use of Object Oriented Design Methodology
Use case Diagram
Has identify few of correct use cases
Has identify few correct Actors and
associations
Sequence Diagram
Has identified set of use cases (about 3) as
sequence diagrams.
Class Diagram
Identification of associated methods, with
correct signatures and attributes in each class
Correct identification of relationships
7
GOOD 9-11
Average Design
Clear identification of private, public access
modifiers & it is visible in the class diagram
Accurate use of <<include> <<extend>> stereo
types in use case diagram
Appropriate use of lifelines, messages and
objects in proposed sequence diagrams
Correct use of UML notations with minor
mistakes
Evaluation
Student has given basic description about the
design and given a reasonable justification
Effective judgements have been made about the
content and levels of information to be included
EXCELLENT 11-15
Excellent Design
Highly detailed diagram
Use of OO concepts clearly visible
Backed by relevant assumptions
Multiplicity, navigability aggregation &
compositions visible in class diagrams
Excellent use of UML notation
Evaluation
Good justification of the design
Judge validity of results
Use critical reflection to evaluate the work and
justify with valid explanations
Fluency (Of design)
Evidence of critical analysis on different perspectives
covering how, use case, class & sequence diagrams
support in designing
Task 3: Out of 40
POOR 0-16
Very poor or no user interface design
Poor clarity of the user interface
8
User interface are not user-friendly
Has not use the user control effectively
Poor color schema
Poor navigation scheme
Limited number of user interfaces
SATISFACTORY 16-24
Basic simple user interface design
Basic Database Applications with JDBC
Use a database (simple design)
Basic validation
GOOD 24-28
Good level of user interface design
Good clarity of the user interface
User interface are user-friendly
Has use the user control effectively
Proper color schema been used
Good navigation scheme
Sophisticated database design and queries
Sophisticated use of JDBC
Has applied proper validation schema for the
propose system
Eg:
User Input validations
Empty filled validation
Data type validation
Simple range and constraint validation
Code and cross-reference validation
Proper comprehensive help features(Eg: electronic user
mannual)
9
EXCELLENT 28-40
Effective security mechanisms have implement
for the proposed system. Such as proper logins
and role based security to protect the system’s
integrity.
Applied Advance features
Eg: 3-tier architecture
Task 4: Out of 15
POOR 0-6
No or poor test plan
No or Insufficient number of test cases
SATISFACTORY 6-9
Basic level of test plan
Appropriate test cases for the test plan
GOOD 9-11
Average level of test plan with all possible
requirements
Every test case should define expected results
as a result of the defined inputs
EXCELLENT 11-15
Traceability showing how each requirement is
met by the design in the test plan.
Appropriate test cases according to the test
plan. Every test case should define expected
results as a result of the defined inputs
Evaluation of overall success or failure and
lessons learned.
Task 5: Out of 10
POOR 0-4
Poor conclusion with very few or nor strength
weaknesses and enhancement
10
No or very poor justification has provide how
effectively OOP concept have use for the given
scenario
SATISFACTORY 4-6
Basic level conclusion with considerable
number of strength weaknesses and
enhancement
Basic level of justification has provide how
effectively OOP concept have use for the given
scenario
Very few recommendation has given
GOOD 6-7
Average level conclusion with considerable
number of strength weaknesses and
enhancement
Average level of justification has provide
how effectively OOP concept have use for the
given scenario
Good set of recommendation given with few
examples
EXCELLENT 7-10
Excellent conclusion with considerable number
of strength weaknesses and enhancement
Excellent justification has provide how
effectively OOP concept have use for the given
scenario
Excellent set of recommendation given with
sufficient examples
Task 6: Out of 10
POOR 0-4
Errors in the documentation.
No or few referencing list
No or few citation provided
Referencing list does not match with the
citation given
11
4-6
SATISFACTORY
Basic standard of documentation with poor
explanations
Proper referencing list given
Proper citation has provided but Referencing
list does not match with the citation given
GOOD 6-7
Acceptable standard of documentation with
poor explanations
Proper referencing list given
Proper citation has provided
Referencing list does match with the citation
given
EXCELLENT 7-10
Professional standard of documentation with
screen shots and proper explanation
Has followed Harvard correct referencing
No overlapping content
Total Marks 100
12
13
