whistle stop tour of the module. this is a new module!

Whistle Stop Tour of The Module

This is a new module!

Stop and think!

What is the Module About?Learning outcomes

Create an advanced prototype with suitable database functionality

Create the beginnings of a professional portfolio of work

Demonstrate skills allowing them to act as a computing professional

Demonstrate problem solving skills allowing them to adapt to the challenges of changing technology

Application of skills from other modules on the course

Other OutcomesAn understanding of important

documentation artefacts Some idea of how to approach systems

development problems

A better sense of your skills reflected in your CV

A class library that you may use in other projects, especially your final year project

A business card to get you started as a computing professional

The Need for CourageFor every person and every project there is

some element of fear

Fear makes you tentativeFear makes you less communicativeFear makes you shy away from feedbackFear makes you shy away from mistakes

We need to address the culture of fear that comes with exploring the unknown

The Ethical Review3500 deathsTunisiaEgyptLibyaYemen

Keep it SimpleWrite for clarity of understandingDon’t write to try and impress

Dr. Abraham ErskineDocumentation is important

The Class Diagram

Better than Reading the Code

Initial ArtefactsSystem specificationEthical reviewEvent tablesUse case diagramsUse case descriptionsTest plansSmoke and mirrors prototypeClass diagramsSequence diagramsEntity Relationship DiagramsTest Driven Development

Remember Systems Development is DifficultGetting inside the head of the client (so that

they get the product they want)Coming to terms with the various tools you

need to use (e.g. Visual Studio, Enterprise Architect etc.)

Working with team members (They will drive you mad!)

Creating the documentation and understanding the notation

Writing the code!

Bad JokeQuestion – How do you eat an elephant?

The Project BankThe Project Bank is intended to be a Customer

Relationship Management (CRM) system. Customer relationship management is a system for

managing a company’s interactions with current and future customers. It often involves using technology to organize, automate and synchronize sales, marketing, customer service, and technical support.

 (Wikipedea)

Building on IMAT1604

Made more complicated by strict adherence to the three layered architecture

Use Case Diagram

True or False?Applications must follow the three layered

architecture

Differing ArchitecturesPresentation(Interface)

Data LayerDatabase

Middle LayerBusiness Logic(Classes)

Presentation(Interface)

Presentation(Interface)

Data LayerDatabase

Translated to Code

C# Code

Thick Middle Layer – Thin Presentation LayerAll code for the system goes in the middle

layerKeep presentation code to an absolute

minimum!

Thick Presentation – Thin Middle

Presentation(Interface)

Data LayerDatabase

Middle LayerBusiness Logic(Classes)

Which is Best?Three layeredTwo layeredOne layeredThick or thin layers

Issues to ConsiderDesign for Code Re-useDesign for ease of maintenanceAutomated testingConsider collaboration issues

Consider Version ControlFile Sharing

Creating a class library

The AssignmentsFor this module there are three assessments

you need to concentrate on. 

Assignment 1a Advanced Prototype (First deadline this week!)

Assignment 1b Prototype Presentation (Week 7 or 8)

Assignment 1c Final Report (Week 25)Assignment 2 TDD Phase Test (Week 15)

Assessment Schedules (Wks 1-8)Week Schedule A Schedule B

1 * Team Business Pack Deadline *

2 Feedback and Assessment (5 min)

3 Feedback and Assessment (5 min)

4 Feedback and Assessment (5 min)

5 Feedback and Assessment (5 min)

6 * Employability Conference *

7 Prototype Presentations

8 Prototype Presentations