Unit 7: Systems Development Life Cycle Flashcards
(88 cards)
1
Q
The aim of an ______________ is to give IT Project Managers the tools they need to assure the effective deployment of systems that meet the University’s strategic and business goals.
A
SDLC methodology
2
Q
● investigates, analyzes, designs, develops, installs, evaluates, and
maintains a company’s information systems
● On large projects, they work as a member of an IT department team
● Smaller companies often use consultants to perform the work
A
system analyst
3
Q
the process of defining, designing, testing and implementing a software application.
- includes a number of different phases, such as feasibility analysis, requirements analysis, software design, software coding, testing and debugging, installation and maintenance.
A
system development
4
Q
System Development Methods
A
- predictive approach
- use of process models
- process-centered technique
5
Q
System Development Life Cycle(SDLC)
A
planning
analysis
design
implementation
maintenance
6
Q
- initial stage in the systems development life cycle (SDLC).
- fundamental process of understanding why an information system should be built and determine how the project team will go about building it.
- describes how IT projects get started, how systems analysts evaluate proposed projects, the feasibility of a project, and the reasoning behind the proposed system development.
A
systems planning
7
Q
___________ must do analysis activities when creating a new system or improving an old system.
- If an information system is built properly, it will give the expected benefits to the company.
- To achieve this goal, system analysts define what the information system requires by performing the analysis activities.
A
SYSTEM ANALYSIS
System analysts
8
Q
Systems Analysis Activities
A
requirements modeling
object modeling
data and process modeling
development strategies
9
Q
consists of requirements modeling, and process modeling, object modeling, and consideration of development strategies.
A
systems analysis phase
10
Q
- involves fact-finding to describe the current system and identification of the requirements for the new system.
requirements:
A
requirements modeling
input
processes
outputs
performance
security
11
Q
refer to necessary data that enters the system, either manually or in an automated manner.
- Manufacturing employees must swipe their ID cards into online
data collection terminals that record labor costs and calculate
production efficiency
The department head must enter overtime hours on a separate
screen
A
input
12
Q
refer to system characteristics such as speed, volume, capacity, availability, and reliability.
- The student records system must calculate the GPA at the end of each semester. As the final step in year-end processing, the payroll system must update employee salaries, bonuses, and benefits and produce tax data required by the IRS
A
processes
13
Q
refer to electronic or printed information produced by the system.
- The Web site must report online volume statistics every four hours, and hourly during peak periods
The inventory system must produce a daily report showing the part number, description, quantity on hand, quantity allocated, quantity available, and unit cost of all sorted by part number
A
output
14
Q
refers to the logical rules that are applied to transform the data into meaningful information.
- The system must support 25 users online simultaneously
Response time must not exceed four seconds
A
performance
15
Q
refers to hardware, software, and procedural controls that safeguard and protect the system and its data from internal or external threats.
- The system must provide log-on security at the operating system
level and at the application level
An employee record must be added, changed, or deleted only by a member of the human resources department
A
security
16
Q
- shows the steps that make up a business process, along with who’s responsible for each step.
- useful for analyzing current processes, planning improvements, and crystallizing communication between process participants
A
business flowchart
17
Q
types of flowchart
A
document
system
program
18
Q
▪ Illustrates the flow of documents and information between areas of responsibility within an organization.
▪ ____________ is particularly useful in analyzing the adequacy of
control procedures.
A
DOCUMENT
document flowchart
19
Q
▪ __________ depict the relationship among the input, processing, and output of an AIS
A
System flowcharts
20
Q
▪ ___________ describes the specific logic to perform a process shown on a systems flowchart
A
program flowchart
21
Q
In the context of software development and system design, _____________ are statements that describe what the system should do or possess to meet the needs of its users and stakeholders.
2 types:
A
requirements
functional requirements
non-functional requirements
22
Q
● Allow users to register and log in to their accounts.
● Provide a search functionality to find products or information.
● Enable users to add items to a shopping cart and proceed to checkout.
● Allow administrators to manage user accounts and product listings.
● Display real-time stock availability for products.
A
functional requirements
23
Q
- define the attributes and qualities that describe how the system should perform, rather than what it should do.
- focus on aspects related to system behavior, performance, security, and user experience.
- answer the question, “How well does the system perform?”
A
non-functional requirements
24
Q
● Performance
● Scalability
● Security
● Usability
● Reliability
A
non-functional requirements
25
The website should load within 3 seconds to provide a good user experience.
performance
26
The system should handle an increasing number of users without significant
performance degradation.
scalability
27
User passwords should be securely hashed and stored to prevent unauthorized
access.
security
28
The website's interface should be intuitive and easy to navigate for users of all experience levels.
usability
29
The system should have at least 99.9% uptime, with minimal downtime for maintenance.
reliability
30
Systems Analysis Skills
Analytical skills
Interpersonal skills
31
Team-Oriented Methods and Techniques
Joint application development (JAD)
Rapid application development (RAD)
32
define what the system should achieve in terms of features and capabilities
functional requirements
33
ensure the system meets the desired levels of performance, quality, and user satisfaction
non-functional requirements
34
- third of five phases in the systems development life cycle
(SDLC).
- Now you are ready to begin the physical design of the system that will meet the specifications described in the system requirements document.
- tasks include output and user interface design, data design, and system architecture.
systems design
35
System Design Guidelines:
The systems analyst must understand the logical design of the system before beginning the physical design of any one component
● Data design
● User interface
● Architecture
● System design specification
36
System Design Objectives
The goal of systems design is to build a system that is effective, reliable, and maintainable
● A system is effective if it meets all user needs and business requirements
● A system is reliable if it adequately handles errors
● A system is maintainable if it is well designed, flexible, and developed with future modifications in mind
37
System Design Considerations
user considerations
data considerations
design trade-offs
38
◼ Carefully consider any point where users receive output from, or provide input to, the system
◼ Anticipate future needs of the users, the system, and the organization – hard-coded
◼ Provide flexibility
◼ Parameter, default
user considerations
39
◼ Data should be entered into the system where and when it occurs because delays
cause data errors
◼ Data should be verified when it is entered, to catch errors immediately
◼ Automated methods of data entry should be used whenever possible
◼ Audit trail
◼ Every instance of entry and change to data should be logged
◼ Data should be entered into a system only once
◼ Data duplication should be avoided
data considerations
40
◼ decisions come down to the basic conflict of quality versus cost
◼ Avoid decisions that achieve short-term savings but might mean higher costs later
design trade-offs
41
- The method by which a prototype is developed
- involves a repetitive sequence of
analysis, design, modeling, and testing.
- common technique that can be used to design anything from a new home to a computer network.
prototyping
42
Prototyping Methods
System prototyping
Design prototyping or Throwaway prototyping
43
- produces a full-featured, working model of the information system.
- Because the model is “on track” for implementation, it is especially important to obtain user feedback, and to be sure that the prototype meets all requirements of users and management.
system prototyping
44
- method of development that employs technical mechanisms for reducing risk in a project, when the project needs are vaguely and poorly laid out.
- The end product is a user-approved model that documents and benchmarks the features of the finished system.
Design prototyping or Throwaway prototyping
45
Prototyping offers many benefits
◼ Users and systems developers can avoid misunderstandings
◼ Managers can evaluate a working model more effectively than a paper specification
46
Consider potential problems
◼ The rapid pace of development can create quality problems
◼ In very complex systems, the prototype becomes unwieldy and difficult to manage
47
systems analysts can use powerful tools to develop prototypes
Prototyping Tools
case tools
application generators
report generators
screen generators
48
- technique that uses powerful software, called CASE tool, to help
systems analysts develop and maintain information systems.
Computer-aided systems engineering (CASE)
49
tool that supports the rapid development of computer programs by translating a logical model directly into code.
- Also called a code generator.
application generators
50
a computer program whose purpose is to take data from a source such as a database, XML stream or a spreadsheet, and use it to produce a document in a format which satisfies a particular human readership
report generators
51
or form painter, is an interactive tool that helps you design a custom interface, create screens forms, and handle data entry format and procedures.
screen generators
52
Limitations of Prototypes
● A prototype is a functioning system, but it is LESS EFFICIENT than a fully developed system
● Systems developers can upgrade the prototype into the final information system by adding
the necessary capability. Otherwise, the prototype is discarded
53
Future Trends in Software Development
Many software development tools and technologies are in transition
● Web services
● Open source software
● Service-oriented architecture (SOA)
● Loose coupling
● Software quality is more important than ever
54
Describes how users interact with a computer system, and consists of all the hardware, software, screens, menus, functions, output, and features that affect two-way communications between the user and the computer.
- requires the understanding of human-computer interactions and user-centered design principles.
user interface
55
uses visual objects and techniques that allow users to communicate
effectively with the system.
graphical user interface
56
user satisfaction, support for business functions, and system effectiveness
usability
process-control systems
user-centered systems
57
allow users to send commands to the system
process-control systems
58
how users communicate with the information system, and how the system supports the firm’s business operations
user-centered systems
59
describes the relationship between computers and people who use them to perform their jobs
human-computer interaction
60
Seven Habits of Successful Interface Designers:
1. understand the business
2. Maximize Graphical Effectiveness
3. Think Like a User
4. Use Models and Prototypes
5. Focus on Usability
6. Invite Feedback
7. Document Everything
61
- This phase begins once the client has tested and approved the system.
- The system is installed at this phase to support the specified business functions.
- The performance of the system is compared to the performance targets defined during the planning phase.
systems implementation
62
- a continuous operation that includes eliminating program and design flaws, updating documentation and test data, and updating user support.
systems maintenance
63
top-down representation of
a function or process
Functional Decomposition Diagram
64
graphically represent the flow of data in a business information system
Data Flow Diagrams
65
visually represents the interaction between
users and the information system. (CASE tools)
Use Case Diagrams
66
widely used method of visualizing
and documenting software systems design
Use case diagrams
Sequence diagrams
Unified Modeling Language
67
- shows the timing of
interactions between objects as they occur. A systems analyst
might use this to show all possible outcomes, or focus on a single scenario.
sequence diagram
68
- A scalable system offers a better return on the initial investment
- To evaluate, you need information about projected future volume for all
outputs, inputs, and processes
scalability
69
- is especially important if the
development team is evaluating several alternatives
- One problem is that cost estimates tend to understate indirect costs
- Rapid Economic Justification (REJ)
Total cost of ownership (TCO)
70
The first step is to identify the information you need
Develop a fact-finding plan
Who, What, Where, When, How, and Why?
Difference between asking what is being done and what could or
should be done
Fact-Finding Overview
71
for Enterprise Architecture
Helps managers and users understand the model and assures that overall business goals translate into successful IT projects
The Zachman Framework
72
__________ for Enterprise Architecture
Helps managers and users understand the model and assures that
overall business goals translate into successful IT projects
ZACHMAN FRAMEWORK
Interviews
Observation
Document Review
Questionnaires and Surveys
Research
Sampling
73
a data collection method for evaluation
includes a basic overview of documents
when to use it
how to plan and conduct it
how it affects the system and the business processes
its advantages and disadvantages
document review
74
Structured and Unstructured
the most important rule of all is to
make sure that your questions collect the right data in a form that you can use to further your fact-finding
Fill-in form
Questionnaires and Surveys
75
Can include the Internet, IT magazines, and books to obtain
background information, technical material, and news about industry
trends and developments
Site visit
research
76
Systematic sample
Stratified sample
Random sample
Main objective of a sample is to ensure that it represents the overall
population accurately
sampling
77
Interviews versus Questionnaires
Interview is more familiar and personal
Questionnaire gives many people the opportunity to provide input and suggestions
Brainstorming
Structured brainstorming
Unstructured brainstorming
78
The Need for Recording the Facts
Record information as soon as you obtain it
Use the simplest recording method
Record your findings in such a way that they can be understood by
someone else
Organize your documentation so related material is located easily
documentation
79
The process of confirming that a strategy, plan or design is possible and makes sense. This can be used to validate assumptions, constraints, decisions, approaches and business cases.
Feasibility Analysis
80
- Describes how easy or difficult it is to do something
- Taking into consideration relevant factors for the implementation of the project proposal
- Types of feasibility
Schedule (time)
Operational (business)
Technical (technology)
Economic (monetary)
feasibility
81
The probability of a project to be completed within its scheduled time limits
If a project has a high probability to be completed on-time, then its schedule
feasibility is appraised as high
May include the following methods or measurements:
Project Estimation
Gantt and PERT Chart
CPM (Critical Path Method)
Change Management
Schedule Feasibility
82
Gain an understanding of whether the proposed system will likely solve the business problems, or take advantage of the opportunities or not
Assess the following areas:
Project Size – number of users
IPO – inputs, processes, outputs
Management support
Environment assessment – are the users going to change
Operational Feasibility
83
refers to technical resources needed to develop, purchase,
install, or operate the system
Includes evaluating the ability of computer hardware and software to handle workloads adequately.
List all the specifications of all hardware and software currently in use by the company and
the proposed ones as well
Technical Feasibility
84
Method for evaluating the effectiveness of a new system
Procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs
Compute for the total costs incurred affected by the current system (hardware, software, utilities, overhead, operating costs, …) and compare with the costs incurred affected by the proposed system
Indicate proper sources of monetary values
Calculate for the Payback Period (pp) and the Return on Investment (roi)
Benefits (tangible or intangible)
Economic Feasibility
85
determines the amount of time required for an investment to generate sufficient cash
flows to recover initial cost
payback period
86
measured in monetary terms or in tangible assets (reduced costs,
assets not spent on)
tangible
87
have significant impact on the company (time saved, productivity, efficiency, data accuracy)
intangible
88
Projects where no choice exists are called ______________
Projects where management has a choice in implementing them are called _________________
______________ an ongoing task that must be performed throughout the
systems development process
nondiscretionary projects
discretionary projects
Feasibility analysis
