System Analysis And Design

Front 1

Information system

Back 1

a set of interrelated components that collect, process, store, and provide as output the information needed to complete business tasks.

Hint 1

I.S. a s o i c t c, p, s, a p a o t i n t c b t.

Front 2

Computer Application

Back 2

A computer software program that executes on a computing device to carry out a specific function or set of related functions.

Hint 2

C.A. a c s p t e o a c d t c o a s f o s o r f.

Front 3

Systems analysis

Back 3

those system development activities that enable a person to understand and specify what the new system should accomplish.

Hint 3

S.A. t s d a t e a p t u a s w t n s s a.

Front 4

System design

Back 4

those system development activities that enable a person to describe in detail how the resulting information system will actually be implemented.

Hint 4

S.D. t s d a t e a p t d i d h t r i s w a b i.

Front 5

Project

Back 5

a planned undertaking that has a beginning and an end and produces some end result.

Hint 5

A p u t h a b a a e a p s e r.

Front 6

System development life cycle (SDLC)

Back 6

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

Hint 6

a F t I a t A R t R, B, D, a O M a I S.

Front 7

System development process or methodology

Back 7

a set of comprehensive guidelines for carrying out all of the activities of each core process of the SDLC.

Hint 7

a S o C G f C O a o t A o e C P o t SDLC.

Front 8

Agile development

Back 8

a information system development process that emphasizes flexibility and Rapid Response to anticipate new and changing requirements during development.

Hint 8

a I S D P t E F a R R t A N a C R D D.

Front 9

Iterative development

Back 9

an approach to system development in which the system is "grown" piece-by-piece through multiple mini projects called iterations.

Hint 9

a A t S D i w t S i G P b P T M M P C I.

Front 10

Subsystem

Back 10

an identifiable and fully functional part of a complete system.

Hint 10

a I a F F P o a C S.

Front 11

Technology architecture

Back 11

a set of computing hardware, network hardware karma network hardware and topology, and system software employed by an organisation.

Hint 11

a S o C H,

Front 12

Application architecture

Back 12

the set of information systems (the software applications) the organisation needs to support it's strategic plan.

Front 13

System requirements

Back 13

all the activities the new system must perform or support and constraints that the new system must meet (functional + non-functional)

Front 14

Functional requirements

Back 14

the activities for sister must perform just for the uses' work.

Front 15

Non functional requirements

Back 15

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

Front 16

FURPS

Back 16

an acronym that stands for functional, usability, reliability, performance, and security requirements.

Front 17

Usability requirements

Back 17

the requirements for operational characteristics related to users, such as the user interface, related work procedures, online help, and documentation.

Front 18

Reliability requirements

Back 18

the requirements that describe system dependability.

Front 19

Performance requirements

Back 19

The requirements to describe operational characteristics related to measures of workload, such as throughput and response time.

Front 20

Security requirements

Back 20

The requirements to describe how access to the application will be controlled and how data will be protected during storage and transmission.

Front 21

FURPS+

Back 21

An extension of FURPS that includes design constraints as well as implementation, system interface, physical, and supportability requirements.

Front 22

Stakeholders

Back 22

Person to have an interest in the successful implementation of the system.

Front 23

Internal stakeholders

Back 23

Persons within the organisation who interact with the system or have a significant interest in its operation or success.

Front 24

External stakeholders

Back 24

Persons outside the organisations control and influence who interact with the system or have a significant interest in its operation or success.

Front 25

Operational stakeholders

Back 25

Persons who regularly interact with the system in the course of their jobs or lives.

Front 26

Executive stakeholders

Back 26

Persons who don't interact directly with the system but who either use information produced by the system or have a significant financial or other interest in its operation and success.

Front 27

Client

Back 27

A person or group that provides the funding for the systems development project.

Front 28

Open ended questions

Back 28

Questions that encourage discussion or explanation.

Front 29

Closed ended questions

Back 29

Questions that elicit specific facts.

Front 30

Model

Back 30

Representation or extraction of some aspect of a system.

Front 31

Textural models

Back 31

Text based system models such as memos, reports, narratives, and lists.

Front 32

Graphical models

Back 32

System models that use pictures and other graphical elements to create a diagram.

Front 33

Mathematical models

Back 33

System models that describes requirements numerically or as mathematical expressions.

Front 34

Unified modelling language (UML)

Back 34

A standard set of information system models constructs and notations defined by the Object Management Group.

Front 35

Workflow

Back 35

A sequence of work steps that completely handle one business transaction or customer request.

Front 36

Activity diagram

Back 36

A (UML) diagram that describes user (or system) activities, the person or component the complete each activity, and the sequential flow of these activities.

Front 37

Synchronisation bar

Back 37

Activity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent parts.

Front 38

Swimlane

Back 38

An activity diagram component that divides the workflow activities into groups showing which agent performs which activity.