Object Oriented Software Engineering (OOSE) Project

Object Oriented Software Engineering

This project is designed to evaluate the learning objectives of the Object Oriented Software Engineering Module as outlined below:

LO1:  Demonstrate the conceptual, practical and technical skills of planning and monitoring a project plan using an appropriate case tool

LO2:  Describe in detail the theory, concepts and methods pertaining to Software Engineering such as Agile and UML.

LO3:  Create requirements using use case modelling concepts.

LO4:  Demonstrate conceptual and technical skills in the analysis, design, implementation and test of a software development solution individually or as part of a team.

LO5:  Employ tools and techniques for Software Engineering.

In this first part of the assessment you are expected to plan a project and apply UML diagrams to the resolution of the problem area identified above. You should produce a report detailing your design. The report should fulfil the following requirements:

1. Identify and describe the actors and construct a use case model. (15 marks)

2. Describe in detail one distinct use case from the use case model per team member. The use case must contain an alternate flow or exceptional flow. (15 marks)

3. Create a glossary in which all project-related terminology that requires clarification is both listed and fully defined. (10 marks)

4. Create a conceptual class diagram modelling the architecture of the proposed system. The conceptual class diagram should demonstrate the use of three or more of the following: attributes, relationships, navigability, association, multiplicity and composition.

5. Draw a system sequence diagram for one of the distinct use cases described.

6. Develop contracts for a minimum of two system operations.

7. Using appropriate design patterns, create communication diagrams based on the two contracts developed in task 6. (15 marks) One nominated team member will submit the report for this part of the assessment through the Project Report - Part A Turnitin link on Moodle.

-Each task in this section will be awarded a percentage of the total marks according to the scale shown on the following page.

-A poor answer that demonstrates little or no understanding of the theory and practice of Object Oriented Software Engineering and the use of UML.
An adequate answer that demonstrates a somewhat limited understanding of the theory and practice of Object Oriented Soft- ware Engineering and the use of UML.

-A good answer that demonstrates a reasonable understanding of theory and practice of Object Oriented Software Engineering and the use of UML..
A very good answer that demonstrates a complete understanding of the theory and practice of Object Oriented Software Engineering and the use of UML..

-An excellent answer that demonstrates an exceptionally in- depth understanding of the theory and practice of Object Oriented Software Engineering and the use of UML.

Any written work created by others must be properly cited and should be paraphrased or summarised where possible, otherwise it should be included in quotes. Figures not created by you should include an acknowledgement detailing the name(s) of the creator(s). Code found on the internet should not be claimed as your own, but instead a comment should be included in the source code indicating where you obtained it. Students are strongly advised to familiarise themselves with the Guide to Academic Integrity produced.

Note: All submissions will be electronically screened for evidence of academic misconduct, e.g. plagiarism, collusion and misrepresentation. Any submission showing evidence of such misconduct will be referred to the college’s academic misconduct committee for disciplinary action.