Nothing going on here, move along…

Archive for April, 2011

Assignment draft diagrams etc

Use case diagram

C=Customer

S=Staff

A=Admin

C will be on the left S and A will be on the right.

—-

C

Calls on phone or visits store

S

Checks for customer record

<<ex>> Opens customer file (if they have one)

<<ex>> Creates new file (if they don’t have one)

C

<<incl>> Provides personal details for creating a new file

—-

C

Gives details of when and where they want holiday

S

Provides holiday choices

C

Chooses preferred holiday

S

Books holiday

Updates customer profile

<<ex>> Restart holiday process (if customer wants to book another holiday)

<<ex>> Sends reports and logs to A (if customer doesn’t want to book another holiday)

—–

A

Sends customer booking confirmation

Files reports and logs

Use case description

  1. Customer either calls or visits the store
  2. Staff member asks if they have a profile
  3. If there is no profile customer details are taken and one is created
  4. If there is a profile it is found and opened
  5. Customer provides details of when and where they would like to holiday
  6. Staff member provides availible holiday choices
  7. Customer chooses preferred holiday
  8. Staff member books holiday
  9. Staff member updates the customer profile accordingly
  10. If the customer would like to book another holiday the process is restarted from 5.
  11. Staff member sends reports and logs to admin
  12. Admin sends holiday confimation/s to customer
  13. Admin file reports and logs

 

Activity diagram

Start ->

Customer calls or visits store->

Staff checks for profile-> If no profile take customer details and create

-> Profile is opened

*Customer provides holiday prefs->

Staff member provides holiday choices->

Customer chooses holiday->

Staff member books holiday->

Staff member updates customer profile->

If customer would like to book another holiday the * procedure is restarted

If the customer does not want another holiday the staff member sends the reports and logs to admin->

Admin sends holiday confirmation

Advertisements

Equation terms

Standard deviation – The standard deviation is the measurement for how spread out your data is and is shown with a σ symbol

Null hypothesis – The idea that you are trying to prove wrong eg. That too much of your budget is going on coffee.

Alternative hypothesis – The idea that you are trying to prove right eg. The goverment is taking too much money from your budget.

http://www.null-hypothesis.co.uk/science//item/what_is_a_null_hypothesis a cool random website I stumbled on along the way

JAG Assignment details

Need to create/ recommend a database

Designing output

Questions:

Purpose of output

Who wants the info, why do they need it, how the info will be used

What specifics will be included

Is the output printed, onscreen or both, what devices will the output go to?

Types of outputs

In systems design phase you create forms, reports, docs and other types of output these are used in different types of media such as internet, email, IM, wireless devices etc

User importance in report design

Recipients should approve all report designs in advance

You should submit each report as you design it for approval

Report design principals

  • Attractive, proffessional, easy to read
  • Report headers/ footers
  • Page headers/ footers
  • Column heading alignment
  • Column spacing
  • Field order
  • Grouping detail lines

Report design issues

  • Uniform and consistant
  • Each report should share common design elements
  • Document the design in a report analysis form

 

User interface design

Evolution of user interface

  • Process control
  • User centered system
  • Process use to rule how things were done, now it is more user based.

Human-computer interaction (HCI)

This is the relationship between humans and computers

The main objective is to create a user friendly design that is easy to learn and use

Basic principals of user based design

  • An understanding of the underlying business functions
  • Maximum graphic effectiveness
  • Profile the system users
  • Think like a user
  • Use prototyping
  • Use a storyboard/ mockup

 

Pricipal of user centered design

  • Usability metrics
  • Design a comprehensive interface
  • Continue the feedback process
  • Document the interface design

 

Input and data entry methods

Online data entry etc

Input volume: The guidelines will help with this

  1. Input necessary data only
  2. Do not input data that the user can retrieve from the system files or calculate from other data
  3. Do not input constant data
  4. Use codes

Data entry screens

The most effective method of online data entry is form filling

  1. You should restrict data access
  2. Use a descriptive caption for each field

More venn diagrams

Cartisan product – The two amounts of elements multiplied

Cardinality – How many elements in a set

Power set – All the combinations of a subset including 0

Trick for finding all the numbers in a venn diagram

If you know the combined eg. all three option put it in first

Venn diagram equations

∩ = And or Λ

υ = Or or V

– = not or ¬

Intersection – Where two circles connect and make another section

Union – All the numbers within the circles

Complement – The area outside of the circles but inside the box, specifically the numbers in this area

Disjoint – When the circles do not intersect

Power sets

If A = {1, {1}, {2}, 3}

The elements are each of the items within the outside brackets eg. 1, {1}, {2}, 3

The subset is the format of each item of a set eg. {1},{{1}}, {{2}}, {3}

Sets and relations

Sets

Any defined collection of items with something in common

Relationship

A relationship is how items of a set relate to each other. Most often used to define a subset within a group

Language of sets

If the set has only a few members you can write all the elements between curly brackets eg. P = {Peter, John, Paul}

If there is a clear pattern you can use three eclipses (dots) eg. S = {2, 4, 6, 8…}

N = Natural numbers

W = Whole numbers

J = Intergers

Q = Rational numbers

R = Real numbers

Subsets

Subsets are equal to their sets, so A=B and B=A

Use cases

Use cases is a container for information which communicates with other use cases.

An <<include>> use case starts up with its parent use case

An <<extend>> use case only starts up with an extra process

A general use case may or may not start up with another use case

An <<extend>> is used with a condition which decides whether activate or not eg. Verify credit card IF it is a credit card transaction

Generalizations explain inheritances

With extends a child can’t replace a parent, there can’t be orphans.

Focus degree of detail

Can be brief, casual or full dressed

Typical use case documentation sections include:

Use case name

Version

Summery

Actors

Pre-conditions

Triggers

Basic course of events

Alternative paths

Post-conditions

Assumptions

Author and date

Tag Cloud