Sdlc Flashcards

1
Q

Reasons for sdlc?

A
  1. Make sure that the computer system works well
  2. Make sure that the computer system is up to date
  3. Make sure that the computer system does what needs to be done
  4. Continual improvement and development of computer system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the six steps used to perform a system development life cycle?

A
  1. Identify + investigate
  2. Analyse
  3. Design
  4. Implement
  5. Maintenance
  6. Evaluation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What areas will be looked at In the investigation stage?

A
  1. Existing hardware and software
  2. Definition of the scope of the present system.
  3. Major data processing functions and processes
  4. Identification of problems with the present system
  5. Identify user requirements for the new system
  6. Analysis of costs and benefits of the new system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How is information collected about the system before investigation starts?

A
  1. Interviews - talk with managers and staff- how existing system works + what are the problems, possible improvements?
  2. Observations - look at how workers interact with system, what do they do? How to they use it?
  3. Looking at records or documents - look at outputs e.g printed forms, orders created, manuals, user documents, job descriptions
  4. Questionnaires - hand out to employees, carefully designed
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What should the feasibility report include?

After investigation

A
  1. User requirements
  2. Existing system - use again or new?
  3. Processing issues - what needs to be done
  4. problems - limitations and issues with existing system
  5. Costs - how much? Equipment? Staffing?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is an entity? (Analysis)

A

An object of the real world, can be a person, product, customer, place

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is an attribute? (Analysis)

A

A single item of data which is a fact about an entity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What relationships In a system can there be?

A

One to one

One to many

Many to many

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is atomic attributes? (Analysis)

A

Broken down into three attributes

  1. Title
  2. First name
  3. Surname

Difficult to create a search for all people with JONES surname

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Data dictionary tables

A
Data is broken down stating the following -
Contents
Field names
Data types
Relationships
Text field length
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What happens at the design stage?

A
  1. Design of inputs and outputs for the system - user interfaces, data capture, forms, reports, graphs, printouts
  2. Networks required - best topology for system, speed of data transmission, wireless needs
  3. Types of hardware and software required - computers or laptops, monitors, printers, input devices
  4. Personnel issues - staff training needed, organisation of staff
  5. Security issues - data being stored, must be kept secure
  6. Types of hardware and software required - computers or laptops, monitors, printers, input devices
  7. Personnel issues - staff training needed, organisation of staff
  8. Security issues - data being stored, must be kept secure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What happens at the maintenance stage?

A
  • where the system is actually built
  • hardware bought and installed
  • computer programmers install software and programmes
  • testing system at all levels - security, with real data
  • training of staff to use system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is direct changeover? (Maintenance stage)

A
  • fast, efficient but great disruption if system turns out to be less than perfect
  • company cannot carry on if the system doesn’t work
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is parallel conversion? (Implementation)

A
  • old system continues to be used alongside the new system for a few weeks
  • this means staff have double the work to do
  • great advantage is that the results from the old system can be treated against results from the new system
  • business is able to carry on
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What’s phased conversion? (Implementation)

A
  • parts of the system is done gradually
  • if there is a problem with new set up then the problem can be sorted out before onto the next phase
  • only suitable if there is an existing system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is pilot conversion? (Maintenance)

A
  • part of the organisation pilots the new system and evaluates it
  • ideal for very large companies
  • areas can be piloted and evaluated before moving on with further changes
17
Q

Types of maintenance to be carried out?

A
  • perfective - fine tuning of system, improving speed, adding extra features
  • adaptive - adapt the system slightly to accommodate new requirements, company might require a new method of inputting data
  • corrective - faults in the system, software bugs, downloads patches to correct software problems
18
Q

Examples of perfective maintenance?

A

Security issues - new viruses etc
- particular part of the software awkward to use - creating and formatting tables

These could be fine tuned to perfect the system

19
Q

Examples of adaptive maintenance

A
  • adapt the system slightly to accommodate new requirements, company might require a new method of inputting data
  • change in business - new line of produce, system can be adapted to cater for this
  • new legislation - laws a - DPA
  • new printers - need new drivers to work the printers
20
Q

Examples of corrective maintenance?

A
  • faults in the system, software bugs, download patches to correct software problems
  • problems may become apparent when using the software in real life situations - formulas don’t work out averages etc
21
Q

What are user documentation and technical documentation?

A

User documentation
- user manual explaining to the employees how to input data, print reports, create searches, how to save, how to open software. Screenshots and examples are given.

Technical documentation
- these would be at programmer level, flow charts of system specification of system, user interface design. Programming language, installation guide

22
Q

What areas are looked at in evaluation stage?

A
  • see if system does what the initial requirements asked for
  • how happy are the clients
  • review cycle - constant checking to make sure that things are still ok
23
Q

What tools are used to gather evaluation information?

A
  1. Quantitative tastings - performance + speed of system. How easy is the system to use n- marks out of 10 by users [quantitative can be measured]
  2. Error logging - system can register every time part of the system fails. - analyst can look at these and determine what need to be done to improve the system
  3. Questionnaires - ask users and business questions on how satisfied they are with the system, ease of use and dependability etc
24
Q

Post implementation costs

A
  1. Training of staff
  2. Upgrading of hardware and software
  3. Correction of software bugs
  4. Help desks and support staff
  5. Modification of the system

(Ongoing costs, plan ahead and budget for them)