topic summaries Flashcards

1
Q

required skills of a business analyst

A

technique
people
business

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

User goal technique

A

simple and effective
identify all potential categories of users of the system
interview and ask them to describe the tasks the computer can help them with
go further and refine the tasks into user goals –> i need to, place order, track the order, pay for the order

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

Event decomposition technique

A

identify events that occur to which the system mush respond

for each event, name a use case (verb-noun) that describes what the system does when the event occurs

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

types of events

A

external–> outside the system, usually initiated by external agent or actor
temporal –> occurs as a result of reaching a point in time
state –> happens inside the system, trigger some process

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

Parts of an event table

A
Event 
trigger 
source case 
use case 
response 
destination
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

CRUD analysis

A

used for validating or refining all possible use cases

to match use cases and data entities (domain classes by including create, read, update and delete)

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

Context diagram

A

DFD –> summarizes all processing activities for the system or subsystem
Shows system boundaries
System scope is represented by a single process, external agents and all data flows, into and out of the system

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

Rules and guidelines of DFD

A
  1. DFD must have at least one process, and no freestanding objects, or objects connected to themselves
  2. a process must receive at least one data flow coming into the process and create at least one data flow leaving the process
  3. a data store should be connected to at least one process. it has to have data flows in and data-flows out
  4. External Entities should not be connected to each other. Although they communicate independent that communicates is not part of the system we design using DFD’s
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Evaluating DFD quality

A

Black holes
Data flow consistency
miracle
balancing

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

Data flow consistency

A

data outflows need corresponding data inflows

data inflows need corresponding data outflows

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

Black hole

A

process/datastore with data input where data element is never used to produce data output

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

Miracle

A

process/datastore where data element created out of nothing

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

balancing

A

DFD fragments = context diagram

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

Agile development

A

a guiding philosophy and set of guidelines for developing information systems in an unknown, rapidly changing environment

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

SDLC

A

framework that identifies all the activities required to research, build, deploy and often maintain an information system

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

predictive approach to SDLC

A

an approach that assumes the project can be planned in advance and that the new information system can be developed according to plan

17
Q

Waterfall method

A

SDLC approach that assumes that phases can be completed sequentially with no overlap

18
Q

Adaptive approach

A

an approach that assumes the project must be more flexible and adapt to changing needs as the project progresses

19
Q

traditional approach

A

system is a collection of processes
processes interact with data entities
processes accept inputs and produce outputs

20
Q

object oreinted approach

A

system is a collection of interacting objects
objects interact with people and each other
objects send and respond to messages

21
Q

Domain model class diagram

A

a class diagram that only includes classes from problem domain

22
Q

Use case diagrams

A

a graphical UML diagram that summarises information about actors and use cases
shows overview of functional requirements
can have multiple use case diagrams
- by subsystem
- by actors

23
Q

automation boundary

A

the boundary between the computerized proportion of the application and the users who operate the application

24
Q

activity diagram

A

create off of the flow activities

25
Q

system sequence diagram

A

shows the inputs and outputs for each use case as messages

26
Q

use case description

A
  • a textual model that lists and describes the processing details for a use case case. it provides details of preconditions, post conditions, sequence of activities and exception conditions in use case
  • describes actor interacting with computer system step by step to carry out business activity
  • may have several scenarios for a use case, each a specific use case instance
27
Q

functional requirements

A

the activities the system must perform to support the users work

28
Q

non-functional requirements

A

required system characteristics other than the activities it must perform or support

29
Q

Stakeholder

A

person who have an interest in the successful implementation of the system

30
Q

internal stakeholder

A

persons within the organisation who interact with the system or have a significant interest in its operations and success

31
Q

external stakeholder

A

persons outside the organisation control and influence who interact the system or have a significant interest in it operations or success

32
Q

operation stakeholder

A

persons who regularly interact with a system in the course of their jobs or lives

33
Q

executive stakeholder

A

persons who don’t interact directly with the system but who either use information produced by the system or have significant financial or other interest in its operations and success

34
Q

fact finding methods

A
reviewing reports, forms, procedures manuals 
interviewing 
observation prototyping 
questionnaires 
JAD 
vendor solutions