SysAnalyss Ch56

The Basics

1. Navgation

2. Layout

3. Content

4. Typefaces

5. Images

6. Table and Lists

Navigation

Easy navigation system - show how to move forward and backward, and where you are currently.

Layout

Balanced layout - use adequate spacing, margins, and clear labels.

Content

1. Meaningful titles

2. Meaningful information

Meaningful titles

Use clear specific, version information and current date

Meaningful information

Include only necessary information, with no need to modify.

Highlighting can include use of what 3 things

1. Notify users of errors in data entry or processing.

2. Provide warnings regarding possible problems.

3. Draw attention to keywords, commands, high-priority, unusual data values.

Highlighting can include use of what 12 things

1. Upper case

2. Bold

3. Italics

4. Underlining

5. Boxing

6. Size and color differences

7. all caps letters

8. blinking

9. reverse video

10. audible tones

11. intensity differences

12. offsetting nonstandard information

Form

A business document that contains some predefined data and may include some areas where additional data are to be filled in.

An instance of a form is typically based on one what?

database record

Report

A business document that contains only predefined data

(Report) It is a passive document used solely for what?

reading or viewing data

A report typically contains data from what?

many unrelated records or transactions.

Effective web design principles

1. Visual hierarchy

2. Divine proportions

3. “F” Pattern Design

4. Law of Proximity

5. Use of white space

(System implementation) Six major activities

1. Coding

2. Testing

3. Installation

4. Documentation

5. Training

6. Support

The first purpose of system implementation is to convert final physical system specifications into what?

working and reliable software

The second software of system implementation to document what?

work that has been done

The third system implementation to provide help for what?

current and future users

Coding

Physical design specifications are turned into working computer code.

Testing deliverables

• Tests are performed using various strategies

• Testing is performed in parallel with coding.

Installation

The current system is replaced by a new system

Coding deliverables

a. Code

b. Program documentation

Testing deliverables

a. Test scenarios (test plan) and test data

b. Results of program and system testing

Installation deliverables

a. User guide

b. User training plan

c. Installation and conversion plan

(Installation) 3 parts of installation and conversion plan

1. Software and hardware installation schedule

2. Data conversion plan

3. Site and facility remodeling plan

2 audiences for final documentation

• Information systems personnel who will maintain the system throughout its productive life.

• People who will use the system as part of their daily lives

User training deliverables

• Application-specific

• General for operating system and off-the-shelf software

Deliverables for documentation

a. System documentation

b. User documentation

Deliverables for user training plan

a. Classes

b. Tutorials

Deliverable for user training modules

a. Training materials

b. Computer-based training aids

Deliverables user support plan

a. Help desk

b. Online help

c. Bulletin boards and other support mechanisms

(Software Application Testing) A master test plan is developed during what?

the analysis phase

(Software Application Testing) During the design phase, unit, system, and integration test plans are what?

developed

(Software Application Testing) The actual testing is done during when?

implementation

(Software Application Testing) Written test plans provide improved communication among …?

all parties involved in testing

Categories of testing

1. Static or Dynamic

2. automated or manual

Static

Testing means that the code being tested is not executed

Dynamic

Testing involves execution of the code

Automated

Computer conducts the test

Manual

People complete the test

7 different types of testing

1. Inspection

2. Walkthrough

3. Desk checking

4. Unit testing

5. Integration testing

6. System testing

7. Stub testing

Inspection

A testing technique in which participants examine program code for predictable language-specific errors.

Walkthrough

A peer group review of any product created during the systems development process, including code.

Desk checking

A testing technique in which the program code is sequentially executed manually by the reviewer.

Unit testing

Each module is tested alone in an attempt to discover any errors in its code.

Integration testing

The process of bringing together all of the modules that a program comprises for testing purposes.

In integration and system testing, modules are typically integrated in a what?

top-down incremental fashion

System testing

The bringing together of all of the programs that a system comprises for testing purposes.

Stub testing

A technique used in testing modules, especially where modules are written and tested in a top-down fashion, where a few lines of code are used to substitute for subordinate modules.

Coding and testing often do what?

go together

Big companies have what?

dedicated test staff

With eXtreme programming (XP) a common technique is what?

refactoring

Refactoring equals what?

Making a program simpler after adding a new feature

Acceptance testing

The process whereby actual users test a completed information system, the end result of which is the users’ acceptance of it.

Alpha testing

User testing of a completed information system using simulated data.

Beta testing

User testing of a completed information system using real data in the real user environment.

4 types of alpha test

1. Recovery 

2. Security

3. Stress

4. Performance

Recovery testing

Forces software (or environment) to fail in order to verify that recovery is properly performed.

Security testing

Verifies that protection mechanisms built into the system will protect it from improper penetration

Stress testing

Tries to break the system

Performance testing

Determines how the system performs on the range of possible environments in which it may be used.

Installation

The organizational process of changing over from the current information system to a new one.

4 installation strategies

1. Direct

2. Parallel

3. Pilot

4. Phased

Direct installation

Changing over from the old system to a new one by turning off the old system when the new system is turned on.

Parallel installation

Running from the old information system and the new one at the same time until management decides the old system can be turned off.

Pilot installation

Roll out the system to only a subset of the users

Phased installation

Changing from the old information system to the new one incrementally, starting with one or a few functional components and then gradually extending the installation to cover the whole new system.

Considerations for planning installation

• Data conversion

• Planned system shutdown

• Business cycle of organization

Data conversion

• Error correction

• Loading from current system

Factors influencing system use

1. Personal stake of users

2. System characteristics

3. User demographics

4. Organizational support

5. Performance

6. Satisfaction

Project close-down

1. Evaluate team.

2. Notify all affected parties that the development project is ending and that you are switching to operation and maintenance mode.

3. Conduct post project reviews.

4. Close out customer contract

Evaluate team

Reassign members to other projects

Close out customer contract

Formal signoff