1. To provide the software skills and technical knowledge required to model software systems using the object-oriented approach to system analysis and design.  

2. To provide students with the ability to build models of software systems and criticaly analyse those models, using the object-oriented approach.

(LO1) A critical understanding of the theoretical concepts underpinning Object-Oriented (OO) analysis and design.

(LO2) A critical understanding of the use of the general-purpose Unified Modeling Language (UML) in the context of software system analysis and design.

(LO3) An understanding of the significance and practice of software requirements gathering.

(LO4) An understanding of the use OO models to communicate information about software systems.

(LO5) An ability to developed software models and evaluate critically  such models, using an object-oriented.

(LO6) Be ability to model a system's functionality using the concept of cases.

(S1) Skills in using technology - Online communications skills

(S2) Critical thinking and problem solving - Critical analysis

(S3) Working in groups and teams - Group action planning

Week 1: Introduction to object-oriented analysis and design
This seminar will review the basic concepts of object technology, introduce systems development ideas and introduce the case studies to be used throughout the module.  In relation to systems development ideas, issues and problems will be summarised and strategies for dealing with these will be introduced.  Two case studies are used throughout the textbook to provide examples of applying techniques; the business background for these case studies will be introduced this week.

Week 2: Modeling and gathering requirements
This seminar will look at what is meant by modelling and the purpose of using diagrams to describe models.  It will also look at requirements gathering, employing use cases as a technique for understanding and documenting what the client wants the system to do.

Week 3: Problem domain analysis
This seminar will look at analysing the problem domain.  In this seminar, you will learn how to find classes from the use case requirements and to produce an analysis class model of the problem domain

Week 4: System analysis
This seminar looks at the analysis model in more detail, considering how objects work together.  You will learn how to model the details of objects, including their actions and states.

Week 5: Object-oriented design
This seminar considers how to elaborate your existing analysis model to produce a concrete design model.  You will learn how to move from analysis to design, considering high-level issues such as software architecture and more detailed issues related to class structure.

Week 6: Design patterns and data persistence
This seminar covers analysis and design patterns in some depth, allowing you to start using patterns.  Most large systems, and almost all business applications, work with a large amount of data that are stored and used for long periods of time.  This seminar will consider approaches and strategies for storing and managing large volumes of data and how to work with this data in a program.

Week 7: Detailed design and implementation issues
This seminar considers how to design maintainable software with a clear separation between the user interface and the logic.  This seminar also deals with issues related to deploying and installing a software system.

Week 8: Component reuse and software development processes
This final seminar concludes the curriculum by pulling together the modelling techniques and UML diagrams and considering their use within a disciplined process or method of software development.  Issues related to the difficulties and benefits of reusing software components are also raised

Teaching Method 1 - Virtual classroom hours (for online modules)
Description:
Attendance Recorded: Yes
Notes: Number of hours per week that students are expected to attend the virtual classroom so as to participate in discussion, dedicated to group work and individual assessment is 8.75.

Teaching Method 2 - Non-classroom hours (for online modules)
Description:
Attendance Recorded: Yes
Notes: Number of hours per week that students are expected to devote to reading, research and other individual work to support engagement in the classroom is 10.