IT261 Midterm | STUDY GUIDE
, Root causes of a problem Manpower, Methods, Machines, Materials, Measurement,
based on the 6Ms of the Mother Nature
Ishikawa diagram
A technique that starts with customer "givens"
Givens-Means-Ends (GME)
(desired outcomes), identifies means to achieve them,
analysis
and defines the system's required ends
Difference between informal The formal system is the documented process as
and formal systems intended; the informal system is how work is actually
done in practice, often with shortcuts or workarounds
Factors to select information Factors include: degree of user involvement, cost of
gathering techniques technique, depth of information, breadth of
coverage, or need for integration of multiple
perspectives
Requirements definition, use-case and process
Pieces of information in a
models, and feasibility analysis (technical, economic,
system proposal
organizational, or schedule)
Three types of models Functional models (e.g., use cases, activity diagrams),
used to depict system Structural models (e.g., class diagrams), and
requirements Behavioral models (e.g., sequence/state diagrams)
Non-functional Design constraints, implementation requirements,
requirements related to the interface requirements, or physical requirements
"+" in FURPS+
Software that meets functional requirements, satisfies
Quality software in systems
nonfunctional FURPS+ constraints, and is reliable,
development
usable, secure, and maintainable
Identifying the true requirements and resolving
Challenges of requirement
conflicting requirements among stakeholders
gathering
A statement of what the system must do or a quality it
Requirement
must have; captured as functional or nonfunctional in
the requirements definition
, Root causes of a problem Manpower, Methods, Machines, Materials, Measurement,
based on the 6Ms of the Mother Nature
Ishikawa diagram
A technique that starts with customer "givens"
Givens-Means-Ends (GME)
(desired outcomes), identifies means to achieve them,
analysis
and defines the system's required ends
Difference between informal The formal system is the documented process as
and formal systems intended; the informal system is how work is actually
done in practice, often with shortcuts or workarounds
Factors to select information Factors include: degree of user involvement, cost of
gathering techniques technique, depth of information, breadth of
coverage, or need for integration of multiple
perspectives
Requirements definition, use-case and process
Pieces of information in a
models, and feasibility analysis (technical, economic,
system proposal
organizational, or schedule)
Three types of models Functional models (e.g., use cases, activity diagrams),
used to depict system Structural models (e.g., class diagrams), and
requirements Behavioral models (e.g., sequence/state diagrams)
Non-functional Design constraints, implementation requirements,
requirements related to the interface requirements, or physical requirements
"+" in FURPS+
Software that meets functional requirements, satisfies
Quality software in systems
nonfunctional FURPS+ constraints, and is reliable,
development
usable, secure, and maintainable
Identifying the true requirements and resolving
Challenges of requirement
conflicting requirements among stakeholders
gathering
A statement of what the system must do or a quality it
Requirement
must have; captured as functional or nonfunctional in
the requirements definition
