Nothing going on here, move along…

Archive for the ‘SW Dev’ Category

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

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

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

Dream getaway assignment requirements

Charts/ diagrams needed

  • Organization chart to show who is involved in DG
  • ID and describe info gathering techniques that could be used to gather info needed for DG project
  • Use case diagram for procedures and functions at DG
  • Use case description for booking a vacation at DG
  • Activity diagram for booking a vacation at DG
  • Use above three to construct an entity relationship model, should include all  required entities, relationships between entities and attributes I believe they should contain using the paper based forms

Analysis report

Requirements fall into five categories: Outputs, inputs, processes, timings and controls. ID requirements for each category for attached scenario.

Investigation items

  • Intro
  • Systems request summery
  • Findings
  • Scope statement
  • Feasibilty study
  • Recommendations (we go ahead with report and need a data base)
  • Project roles
  • Time and cost estimates
  • Expected benefits

**Using UML and ERD for report

Preliminary investigation report

  • Booking
  • Suppliers
  • Customers/ clients

Scope statement

  • Things you will definately do
  • Things you will definately not do
  • Things you may do if you have time
  • Different options/ costs

The team needs:

  • An analyst
  • A team manager
  • Hardware
  • Software
  • Other stakeholders, owners etc

Info gathering

Organisation chart for the business

Techniques used:

Interviews

JAD sessions

Documentation

Design

Use cases for all functionalities eg. Making bookings, get reports, update suppliers

Design use case descriptions for bookings:

  • What is the use case for
  • What tasks/ steps are needed
  • Use parts of the use case diagram to help

Activity diagrams

These are based on the use cases

ERD’s

  • Entities
  • Relationships
  • Cardinality/optionality

Models and diagrams

RUP – Rational Unified Process

Lifecycle

Analysis, design and implementation

Models

Waterfall, semistructured, structured, RAD, BOEHMS spiral, incremental and iterative (this is a real model not a prototype.)

Phases for UML/RUP

Inceptions – Identity

Elaboration – Design

Construction – Build

Transaction – Roll out

Diagrams and their contents

Use case diagram – ID system boundry, fuctions and events, how the user sees the system,not behind the scenes

Activity diagram – Use case diagram details

Sequence diagram – Use case timing

Class diagram – Developed from the use case

State transition diagram – Models the behaviours of subsystems

Actors

These are users which affect the system eg. In a bank system there would be a ‘banker’ actor and a ‘customer’ actor.

In diagrams actorsare shown as stick figures

Primary elements are actors processes are use cases.

Titles are used but not names

Use cases

A use case diagram is a visual representation of a distinct business functionality

Each business fuction can be classified as a use case but some may be sub cases

A use case is represented by an oval

The system boundry is an oblong that surrounds the use cases but not the actors

Each use case has a limit defined by the boundry

Use cases share different kinds of relationships:

Association – communicates a relationship. Shown with a line __________

Include – Used to indicate a use case needs another use case to work. Shown with a broken line arrow and <<include>> sign on the line ———>. Goes from child to parent

Extend – The child case add to the functionality of the parent case the same as the include funtion, this functio is not always needed to complete a transaction, has <<extend>> sign instead of include

Genralizations – Inheritance of an object in UML, an enhancement of the parent case. Uses a closed arrowhead with an unbroken line     |>

Dream getaways assignment

Scope statement

We will create a system to organise bookings, customer files and supplier files

Customer files and supplier files will be able to be updated

It will contain a login page for security purposes

We will provide training for use of the new system

It will be connectable to any future upgrades that are made to the system

We will not be connecting it to any current systems in this project

Object modelling and diagrams

Use cases go on the diagram, remember to add actors and show relationships.

UML version diagram

Sequence diagrams

These contain Classes, lifelines, messages, focuses – the processes.

Use assumptions which means assuming that the objects will have the info/items needed to complete a task.

State transition diagrams

Shows how objects change from one state to another depending on influences on them.

Activity diagrams

These show the steps needed to do a task

We will mostly be using the following diagrams:

Use

Class

Sequence

Activity

Tag Cloud