co546 information systems analysis overview –system modelling unified modelling language (uml)...

33
CO546 Information Systems Analysis • Overview – System Modelling • Unified Modelling Language (UML) – Information Systems • From a business and management point of view • Assessment (100% coursework) – 50% UML assessments – 50% Group assessment

Upload: dustin-gilmore

Post on 21-Dec-2015

215 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

CO546 Information Systems Analysis

• Overview

– System Modelling

• Unified Modelling Language (UML)

– Information Systems• From a business and management point of view

• Assessment (100% coursework)

– 50% UML assessments

– 50% Group assessment

Page 2: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

CO600 Project

Dr. Caroline Ling LiEmail: [email protected]

Page 3: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Introduction

• All Computing students are currently required to undertake a 30-credit project.

• All Medway Students must take either a CO600 and a CO650 project as follows:

– Computing students must do CO600 and may chose to take CO650 as an option

– Computing(Con) must do CO650 and may choose to do CO600 as an option

– IT(SE), IT(Web Apps) and IT(MKC) must do CO600 and cannot do CO650

– BIT students may do either CO600 or CO650, but not both.

3

Page 4: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Introduction - cont’d

• Groups sizes between 3 and 5 inclusive allowed; ideally 4, but optimum will depend on the scope of the project.

• Individual CO600 projects are only allowed • when arising from an industrial placement (Must have the agreement

of the company particularly if dependent on company data source), or

• when arising from issues relating to a student’s ILP or when directed by the examination board

4

Page 5: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Module Generic Learning Outcomes

1. An appreciation of the dynamics of working in a group

2. Oral presentational skills3. Ability in writing technical reports4. Ability to acquire technical knowledge and

understanding in an independent fashion5. Ability to reflect on and evaluate work

performed.

5

Page 6: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Module Specific Learning Outcomes

1. An in depth understanding of particular technical topics (for instance, use of a particular programming language, or software development tool, component architecture or mathematical technique) beyond that obtainable from the rest of the programme.

2. An enhanced understanding (gained from practical experience) of project organisation, implementation and documentation techniques (as studied in other modules).

3. The ability:• to specify, design and implement a computer-based system;• to evaluate and choose between potential solutions to a

technical problem;• to evaluate and deploy appropriate tools and techniques.

6

Page 7: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Initial Meeting

• Agree a fixed time when weekly supervisory meetings will take place - mandatory and participation will form part of the assessment.

• Group should identifies a project leader or at least the person most likely to communicate with the supervisor and will distribute messages to the rest of the group.

• Discuss scope of project and look to identify the system boundaries or other constraints

• Request, as a priority, the group produces a requirements statement (or identifies the project’s objectives) and an initial project plan (schedule, maybe revisited during the project, version control-SVN)

7

Page 8: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Initial Meeting – cont’d

– A group will be provided with a group folder on Raptor (by cs-syshelp) and that this should be treated as the project group’s default respository.

• to store all documents, source code, etc. relating to the project (throughout the lifetime of the project)

• not to store file on a laptop• from which the final software will be run (unless there are justifiable reasons why this is

not practical)

• Everyone will be assessed individually in each learning outcome so must involve themselves in all aspects of the project, e.g. project management, programming, testing and documentation. This will not be likely if all the programming is performed by one or two people in the group.

• Agile method (i.e. paired programming)8

Page 9: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Initial Meeting – cont’d

• Plagiarism. Not only text, figures, this includes code, and that, if code from elsewhere is incorporated, it should be:

• appropriately referenced• delineated

• Assessment• they will be assessed individually based on their contribution to

supervisory meetings, identified contribution to the project, evaluation report and viva.

• the module is non-compensable. Failure will almost certainly result in a student having to repeat a different project over the following year. If a student fails, then they may be eligible for a ordinary degree provided they have passed 90 credits at level H.

9

Page 10: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Recommendations

• The group should identify a time when they will meet, other than supervisory meetings, on a regular basis

• Academics will keep logs of supervisory meetings: attendance, progress, issues, etc.

• The group should keep log books: attendance, document/identify tasks to be carried out by particular members and record agreed delivery dates.

• Academics will not recommend or instruct in approaches to overcome problems. Merely ask what approaches have been considered and the difficulties encountered.

10

Page 11: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Categorical marking

Page 12: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Last Year’s Deadlines – Check moodle for this year’s deadline – will be released end of this term via moodle

https://forum.cs.kent.ac.uk/forumdisplay.php?50-Undergraduate-Projects-2015-16

• Poster and Abstract deadline: 4.00pm of Wednesday Week 19

• Poster Fair: Friday of Week 21 @ Eliot Dining Hall, Canterbury

• Technical report and corpus: 4.00pm on Wed week 23

• Individual report: 4.00pm on Wed of Week 24

• Viva: Summer Term – Do not make travel plans within term time.

Page 13: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Grab a Form and have it signed

Page 14: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

“The protection afforded to an automated information system in order to attain the applicable objectives of preserving the integrity, availability, and confidentiality of information system resources (includes hardware, software, firmware, information/ data and telecommunications.)”

[NIST Computer Security Handbook, 1995]

CO634: Computer Security and Cryptography

Page 15: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Part I: Computer Security: Dr Matteo Migliavacca

Part II: Cryptography: Dr Palani Ramaswamy

Both parts run concurrently

Assessments- 2 hour exam (70%)

Two pieces of coursework: (30%) - Cryptography practice (15%) - code breaking - Computer Security (15%) - threat analysis

Module team at Medway

Page 16: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Computer Security• Questions such as "How do I know you are

who you say you are?" and "Why bother?" are explored throughout the first few topics

• Later in the course, we’ll look at high-profile attacks that were possible against internet-connected computers, look at how web servers are commonly secured, and at how firewalls work

Cryptography • Did you buy anything online? Used an

ATM machine?• You would have used cryptography

(perhaps you didn’t know!)• We’ll look at methods to encrypt data to

avoid eavesdropping • (Eg: Avoiding hackers from stealing your

credit card number during online transaction, even if the communication medium is insecure)

What is Computer Security and Cryptography?

Page 17: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Eg: you buy an item from Amazon using a credit card

Why do we need Security?

What are the possible attacks on this transaction?

Possible security issues

You will study protocols

An adversary could eavesdrop on the transaction

to ensure “confidentiality”

The attacker could send extra copies of your message: replay attack

to detects replays - provide “originality”

Even with originality guaranteed, an adversary could intercept your message and retransmit it with a delay

that detects such delaying provides “timeliness”

You could be directed to a fake web site - Phishing attack

that ensures that you are talking to whom you think you are talking provides “authentication”

An attacker could bomb Amazon with a big number of requests; customers will not be served: Denial of Service (DoS) attack

that ensures a degree of access provides “availability”

What protocols are required to prevent/safeguard the transaction?

Page 18: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Cryptography example

Approaches to perform the encryption will be studied

Page 19: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Julius Caesar used a cipher in which each letter of the alphabet was replaced by the letter three places on One of the cryptography methods to be studied Key here is ‘3 letters onwards alphabetically’

Example: KHOOR becomes?

Caesar cipher

H E L L O

Page 20: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Questions about the course?Contact either Matteo or Palani

[email protected] (room M3.17)

[email protected] (room M3.14)

Page 21: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

CO639 – E-Commerceoption talk

Matteo Migliavacca

Page 22: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Security + IT + Business

• Theory 50%– Web technology (HTTP(S), cookies)– Security and Vulnerabilities– Payment systems– Laws and frauds– Mobile

• Practice and Business 50%– Business and Internet– programming in PHP (sessions, PDO, transactions)– Web services and Paypal PHP SDK– Writing secure PHP applications– Impact of Internet on Business practices

Page 23: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Assessment

• 50% exams– 2 questions on theory, 1 on practice, 1 on

business. Choose 3 out of 4• 50% coursework, 2 pieces (25% each)

– Group case-study on e-commerce security– Individual programming in PHP: e-commerce

backend service

Page 24: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

co639: snog, marry, avoid ?

• Choose co639 to– learn a mix of web + security + money + business/law topics– understand practical aspects of security– learn how to develop backend web services (API)– understand solutions for being paid online

• Avoid co639 if– not interested in business/payment aspects– you have done web development (co539) + security (co634)

and do not care about web / payment services– do not like (a lot of) programming in vanilla PHP

Page 25: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Some comments from students

• Multiple concepts in one module is a bonus, even if other modules have been taken that cover them as well

• good range of assessments, both technical and theoretical

• The second assignment was a great learning experience

• Learning a new language, which I had no experience of previously

Page 26: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

CO656 – Computational Intelligence in Business, Economics and Finance

Michael Kampouridis

Page 27: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Outline

• Computational Intelligence– Nature-inspired computational methodologies to

address complex real-world problems• Problems come from the fields of business,

economics and finance– Portfolio optimisation– Financial forecasting– Timetabling– Optimal roll-out of a new service/technology

Page 28: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Requirements

• Java!• Coursework will include quite a lot of Java

programming for – Modeling the problem at hand– Creating and running the CI algorithm to solve the

problem

Page 29: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

The Graduates of TomorrowSupporting the Businesses of Today

Page 30: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Diagnostics Guidance Studies

WebsitesIdentifying areas of business that could

benefit from technological innovation.

Identifying a range of solutions to tackle real-

world business problems.

Implementing self-maintained web

solutions for a variety of client needs.

Page 31: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

• Join a team of Stage 3/MSc students at Canterbury and Medway

• Become an integral part of the KITC

• Support small- to medium-size enterprises in the Kent area

• Deal directly with real-world clients

Become a Student Consultant

Page 32: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

Benefits

• Continue your placement as part of a team, in a functioning business environment

• Continue to enhance employability skills

• Continue your professional development

• Work on multiple projects instead of just one

Page 33: CO546 Information Systems Analysis Overview –System Modelling Unified Modelling Language (UML) –Information Systems From a business and management point

• Any Computing student• CO650 can be taken in place of CO600 (Stage 3 Project)• Come and speak to us the Poster Fair to apply• Alternatively, email your CV and cover letter to:

Who Can Apply?

[email protected]