Software Development And Systems Analysis And Design

Front 1

computer application (app)

Back 1

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

Front 2

information system

Back 2

a set of interrelated computer components that collects, processes, stores, and provides as output the information needed to complete business tasks

Front 3

systems analysis

Back 3

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

Front 4

systems design

Back 4

those activities that enable a person to define and describe in detail the system that solves the need

Front 5

project

Back 5

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

Front 6

Systems Development Life Cycle (SDLC)

Back 6

the entire process consisting of all the activities required to build, launch, and maintain an information system

Front 7

information systems development process

Back 7

the actual approach used to develop a particular information system

Front 8

Agile Development

Back 8

an information systems development process that emphasizes flexibility to anticipate new requirements during development

Front 9

iterative development

Back 9

an approach to system development in which the system is "grown" piece by piece through multiple iterations

Front 10

subsystem

Back 10

an identifiable and partitioned portion of an overall system

Front 11

technology architecture

Back 11

a set of computing hardware, network hardware and topology, and system software employed by
an organization

Front 12

application architecture

Back 12

the organization and construction of software resources to implement an organization’s information systems

Front 13

system requirements

Back 13

the activities a system must perform or support and the constraints that the system must meet

Front 14

functional requirements

Back 14

the activities that the system must perform

Front 15

nonfunctional requirements

Back 15

system characteristics other than the activities it must perform or support

Front 16

FURPS

Back 16

a requirements classification framework (acronym stands for functionality, usability, reliability, performance, and security)

Front 17

FURPS+

Back 17

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

Front 18

usability requirements

Back 18

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

Front 19

reliability requirements

Back 19

requirements that describe system dependability

Front 20

performance requirements

Back 20

operational characteristics related to measures
of workload, such as throughput and response time

Front 21

security requirements

Back 21

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

Front 22

design constraints

Back 22

restrictions to which the hardware and software must adhere

Front 23

implementation requirements

Back 23

constraints such as required programming
languages and tools, documentation method
and level of detail, and a specific communication
protocol for distributed components

Front 24

interface requirements

Back 24

required interactions among systems

Front 25

physical requirements

Back 25

characteristics of hardware such as size, weight, power consumption, and operating conditions

Front 26

supportability requirements

Back 26

how a system is installed, configured, monitored, and updated

Front 27

model

Back 27

representation of some aspect of a system

Front 28

textual models

Back 28

text-based system models such as memos, reports, narratives, and lists

Front 29

graphical models

Back 29

system models that use pictures and other graphical elements

Front 30

mathematical models

Back 30

system models that describes requirements numerically or as mathematical expressions

Front 31

Unified Modeling Language (UML)

Back 31

standard set of model constructs and notations
defined by the Object Management Group

Front 32

stakeholders

Back 32

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

Front 33

internal stakeholders

Back 33

persons within the organization who interact with the system or have a significant interest in its operation or success

Front 34

external stakeholders

Back 34

persons outside the organization’s control and influence who interact with the system or have a significant interest in its operation or success

Front 35

operational stakeholders

Back 35

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

Front 36

executive stakeholders

Back 36

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 37

client

Back 37

person or group that provides the funding for a system development project

Front 38

open-ended questions

Back 38

questions that encourage discussion or explanation

Front 39

closed-ended questions

Back 39

questions that elicit specific facts

Front 40

workflow

Back 40

sequence of processing steps that completely handles one business transaction or customer request

Front 41

activity diagram

Back 41

describes user (or system) activities, the person who does each activity, and the sequential flow of these activities

Front 42

synchronization bar

Back 42

activity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent paths

Front 43

swimlane heading

Back 43

activity diagram column containing all activities for a single agent or organizational unit