In Progress

Custom Project Dec 5 2011 16:14:26 COMPLETED BY 08/12/2011

This

assignment

reflects

a

common

task

for

business/systems

analysts;

that

is

understanding

and

documenting

an

existing

system.

The

system

you

are

to

document

is

a

“Rare

Book

Collectors

Community”,

[url removed, login to view]

The

purpose

of

the

system

is

to

enable

rare

book

collectors

to

offer

books

for

sale,

exchange

news

and

views,

and

to

provide

other

facilities

for

a

community

of

collectors.

The

system

is

‘co-­‐owned’

by

David

Chan

the

Director

of

the

Centre

for

Information

Leadership

here

in

the

School

of

Informatics,

and

he

has

kindly

agreed

to

let

you

all

‘investigate’

his

system.

In

order

to

be

able

to

document

the

system

properly

you

will

have

to

subscribe

as

a

standard

member

(free)

to

explore

the

features

of

the

system.

Standard

members

can

list

up

to

10

books

for

sale

for

free,

and

you

may

want

to

list

that

unloved

and

unwanted

old

paperback

novel

to

see

how

that

part

of

the

system

works

in

detail.

When

you

have

finished

your

exploration

of

the

system

you

can

unsubscribe

and

have

your

details

removed

using

the

contact

form

[url removed, login to view]

to

send

a

request

to

be

removed

from

the

system.

Your

task

is

to

produce

three

different

types

of

system

documentation

and

a

short

evaluation

of

the

system.

The

system

documentation

should

consist

of:

• One

diagram

showing

the

interaction

of

the

system

with

the

environment,

e.g.

use-­‐case

diagram

or

DFD

context

diagram

• An

Entity-­‐Relationship

model

of

the

system

data,

including

attributes,

relationships,

cardinalities

and

participation

constraints.

• UML

Class

diagrams

and

sequence

diagrams,

or

Data-­‐Flow

Diagrams

to

document

the

main

functions

of

the

systems

and

how

they

interact.

The

evaluation

required

is

a

short

critique

of

the

system

(400-­‐500

words),

identifying

good

and

bad

features

of

the

system,

giving

your

reasons.

The

marks

for

the

different

deliverables

are:

1. Environment/context

diagram

(20

marks)

2. ER

model

(30

marks)

3. Diagrams

documenting

functions

(30

marks)

4. System

evaluation

(20

marks)

The

marking

scheme

for

each

of

deliverables

1,

2

&

3

is:

• The

individual

elements

described

in

the

model

are

consistent

and

together

describe

a

feasible

system

that

is

an

accurate

representation

of

the

‘rarelist’

system

with

few

inaccuracies

or

inconsistencies.

The

modelling

technique

chosen

is

applied

correctly

with

few

or

no

notation

errors.

At

least

80%

of

the

externally

visible

features

of

the

system

are

modelled.

(21-­‐30

marks

for

deliverables

2

&

3,

and

13-­‐20

marks

for

deliverable

1)

• Most

of

the

individual

elements

described

in

the

model

are

consistent

and

they

accurately

describe

key

features

of

the

‘rarelist’

system

albeit

with

some

errors

or

inconsistencies.

The

modelling

technique

chosen

is

applied

consistently,

showing

an

understanding

of

the

modelling

concepts,

but

with

some

notation

errors.

At

least

60%

of

the

externally

visible

features

of

the

system

are

modelled.

(11-­‐20

marks

for

deliverables

2

&

3,

and

7-­‐12

marks

for

deliverable

1)

• Few

of

the

individual

elements

described

in

the

model

are

consistent

and

their

collective

representation

of

the

‘rarelist’

system

is

poor

with

many

inaccuracies

or

inconsistencies.

The

modelling

technique

chosen

is

applied

inconsistently

and

notation

errors

are

common.

At

least

40%

of

the

externally

visible

features

of

the

system

are

modelled.

(1-­‐10

marks

for

deliverables

2

&

3,

and

1-­‐6

marks

for

deliverable

1)

• Less

than

40%

of

the

externally

visible

features

of

the

system

are

modelled.

(0

marks

for

deliverables

1,

2

&

3)

The

marking

scheme

for

deliverable

4

is:

• Both

positive

and

negative

aspects

of

the

system

are

identified

with

clear

and

reasoned

arguments

to

support

opinions

leading

to

a

coherent

summative

evaluation

(13-­‐20

marks)

• Positive

and

negative

aspects

of

the

system

are

identified

with

convincing

reasons

given

and

a

summary

(7-­‐12

marks)

• Some

aspects

of

the

system

are

identified

as

positive

or

negative

but

the

reasoning

is

unclear

or

unconvincing.

(1-­‐6

marks)

Skills: UML Design

See more: use of use case diagram, use of sequence diagram in uml, use of sequence diagram, use case types, use case to class diagram, use case sequence diagrams, use case sequence diagram, use case sequence, use case interaction diagram, use case diagrams in uml, use case diagram sequence diagram, use case diagrams, use case diagram purpose, use case diagram of, use case diagram for, use case diagram documentation, use case diagram details, use case and class diagram, understanding use case diagrams, understanding sequence diagrams, uml use case class diagram, uml use case and class diagram, uml task, uml model types, uml diagram use case

About the Employer:
( 0 reviews ) london, United Kingdom

Project ID: #1326209

Awarded to:

Nidagold

Hired by the Employer

$50 USD in 3 days
(26 Reviews)
5.2