1
Q
Systems Analysis Phase
A
- understands the project
- ensure that it supports business requirements
- builds a solid foundation for system developement
2
Q
System Analysis Activities
A
- requirements modeling
- data and process modeling
- object modeling
- development strategy
3
Q
Requirements Modeling
A
uses fact-finding describe the current system and identification of requirements such as output, input, process, performance, and security
4
Q
Output
A
refers to the electronic or printed information produced by the system
5
Q
Input
A
necessary data that enters the sysem
6
Q
Process
A
logical rules applied that transforms data into meaningful information
7
Q
Performance
A
system characteristics such as speed, volume, capacity, availability, and reliability.
8
Q
Security
A
hardware, software, and procedural controls that safeguard and protect the system and its data
from internal or external threats
9
Q
Data and Process Modeling
A
graphically shows the data and processes using tradional structured system techniques
10
Q
Object Modeling
A
- Create objects to represent things, transactions and events
- combines data and the processes that act on the data into things called objects.
11
Q
Development Strategy
A
software trends, acquisition and development
alternatives, outsourcing, and formally documenting requirements for the new system.
12
Q
System Analysis Skills
A
needs strong analytical skills and interpersonal skill to build accurate model of the system
13
Q
analytical skills
A
enables you to identify the problem, evaluate elements, and provide a solution
14
Q
interpersonal skills
A
work with people at all organizational levels, balance conflicting needs of users, and communicate effectively.
15
Q
Team-Based Techniques: JAD, RAD, Agile Method
A
goal is to deliver the best information system in the least possible cost in the shortest time
16
Q
Joint Application Development (JAD)
A
- popular fact-finding technique that brings
users into the development process as active participants. - user-oriented technique for fact-finding and requirements modeling.
17
Q
User Involvement
A
users should be involve the the development process
18
Q
JAD group contains
A
- project leader with strong interpersonal skills and organizational skills
- one or more members to record results and descisions
19
Q
JAD Disadvantages
A
- more expensive than traditional methods
- cumbersome if the file is too large
20
Q
JAD Advantages
A
- allow key users to participate in requirements modeling process
- users feel the some sense of ownership in the results and supports the new system
- produce more accurate results
21
Q
Rapid Application Development
A
- fast-track approach to a full spectrum of system development
- team-based technique that speeds information systems development and procedures functining information system
22
Q
JAD Produces
RAD Produces
A
requirements model
new system
23
Q
RAD Four Phases
A
- Requirements Planning
- User Design Tasks
- Construct Tasks
- Cutover Tasks
24
Q
Requirements Planning
A
- refers to the combination of elements of SDLC planning and analysis
- users, managers, IT staff agree on business needs and requirements
- management authorization must be applied tp continue
25
User Design
users interact with the system analysts to develop models, prototypes to represent the system process, output, and input
26
RAD group or subgroups typically use a combination of
JAD techniques and CASE tools
27
Construction
focuses on program or application development tasks similar to SDLC, however users can suggest chnages for further improvement
28
Cutover
similar to SDLC implementation phase that includes system chnages, data conversion, testing
29
RAD Objectives
cut development time and expenses by involving users in every phase of the system development
30
RAD Advantage
can be developed more quickly with
significant cost savings
31
RAD Disadvantage
* does not emphasize company startegic business needs
* less time to develpo quality, consistency, and design standards
32
Agile Method
* intense interaction between system developers and users
* develop a system incrementally by building series of prototypes and consistently adjusting them according to user requirements
33
Scrum
* members play a specific role and the term came from rugby
* specific guidelines that emphasize time blocks, interaction, and team-based activities that result in deliverable software
* **pig** refers to facilitators, product owner, development team
* **chicken** refers to users, other stakeholders, management team
34
Agile Team
refers to series of scrums that pauses action and allows players to reset the game until next scrum
35
Scrum session
follow a specific guideline thta emphasizes time-blocks, interaction, and team-based activitites
36
Agile Method Advantages
* Very flexible and efficient in dealing with change
* stress team interaction and reflect a set of communiry· based values.
* frequent deliverables constantly validate the project and reduce risk
37
Agile Method Disadvantages
* team members need a high
level of technical and interpersonal skills
* lack of structure and documentation
can introduce risk factors
* subject to significant change in scope as user requirements continue to evolve during the project.
38
Modeling Tools and Techniques
graphical methods and nontechnical language that represent the sytem at various stages of development.
39
Functional Decomposition Diagrams
(FDD)
* refers to a top-down representation of a function or process
* similar to an oragnizational chart
* show business funcations and break them down to low level organization
40
Business Process Modeling
refers to one or more business process
41
business process modeling notation
includes various shapes and symbols to represent events, processes, and workflows.
42
* pool
* swim lanes
* overall diagram
* customer designated areas
43
Data Flow Diagrams
* shows the system stores, processes and transforms data
* additional levels of information are also depicted
44
Unified Modeling Language (UML)
* widely used method of visualizing and documenting software systems design
* object-oriented design concepts, but it is independent of any specific programming language and can be used to describe business processes and requirements generally
* provides various graphical tools, such as use case diagrams and sequence diagrams.
45
Case Diagram
interaction between users and the
information system
46
Sequence Diagram
shows the timing of interaction between objects as they occur
47
System Requirements
* characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users
* benchmarks to measure the overall acceptability
of the finished system
48
System requirements fall into five general categories
1. input
2. output
3. procedure
4. performance
5. security
49
Scalability
system's ability to handle increased business volume and transactions in the future
50
Total Cost of Ownership
* important especially if development team are assessing other alternatives
* cost estimates tend to understate indirect costs such as user support and downtime productivity losses
51
Rapid Economic Justification (REJ)
framework to analyze IT investments
52
Fact-finding
* find identity of information by asking specific questions
* develop a fact-finding plan by by asking who, what, where, when , why, and how questions or use Zachman Framework
53
Zachman Framework
helps managers and users understand the model and ensures that overall business goals translate into successful IT projects
54
Interview
planned meeting during which you obtain information from another person.
55
Interview steps
1. Determine the people to interview
2. Establish the objectives of the interview
3. Develop the interview questions
4. Prepare for the interview
5. Conduct the interview
6. Document the interview
7. Evaluate the intervew
56
Determine the people to interview
select the right people to interview and ask them the right questions.
57
informal structure
interpersonal relationships and can develop from previous work assignments, physical proximity, unofficial procedures, or personal relationships such as the informal gathering
58
Establish Objectives for the Interview
* general areas to be discussed, and then list the facts you want to gather.
* Upper-level managers can provide the big picture and help you to understand the system as a whole.
* Specific details about operations and business processes are best learned ftom people who actually work with the system on a daily basis
58
Establish Objectives for the Interview
* general areas to be discussed, and then list the facts you want to gather.
* Upper-level managers can provide the big picture and help you to understand the system as a whole.
* Specific details about operations and business processes are best learned ftom people who actually work with the system on a daily basis
59
Develop Interview Questions
standard list of interview questions helps to keep you on track and avoid unnecessary tangents.
60
open-ended questions
encourage spontaneous and unstructured responses.
61
close-ended questions
limit or restrict the response.
62
rapid-response questions
closed-ended questions that ask the person to evaluate something by providing limited answers to specific responses or on a numeric scal
63
Prepare for the Interview
* Careful preparation is essential because an interview is an important meeting and not just a casual chat
* limit to one hour
* verify essential details via email
* send a list of topcs days prior
64
conduct the interview
* develop a specific plan for the meeting
* introduce youreself and objectives of the meeting
* concentrate on what is said and notice any nonverbal communication that takes place **(engaged listening)**
* summarize main points covered in the interiew
65
Document the interview
* keep the writing minimum
* record the information quickly
* send memo of appreciation
* memo must contain location, time, date, purpose, main points or the written summary
66
Evaluate the interview
in addition to recording information, evaluate if there are possible biases
67
Unsuccessful interview
* No matter how well you prepare for interviews, some are not successful.
* you and the interviewee did not get along well.
* misunderstanding or personality conflict could affect the interview negatively
* e interviewee might be afraid that the new system will eliminate or change his or her job.
68
Document Review
* you understand how the current system is supposed to work
* Review old and current forms and documentation
69
Observation
* Seeing the system in action gives you additional perspective and a better understanding of system procedures
* Personal observation also allows you to verify statements
made in interviews and determine whether procedures really operate as they are described.
70
Hawthorne Effect
determine how various changes in the work environment would affect employee productivity.
71
Questionnaires and Surveys
* document contain ing a number of standard questions that can be sent to many individuals.
* can be tradional or fill in form
72
Sampling
is to ensure that it represents the overall population accurately
73
systematic sampling
select every 10th customer
74
stratefied sampling
select 5 custoners on each four postal codes
75
random sampling
select 20 random customers
76
Research
Can include the Internet, IT magazines, and books to obtain background information, technical material, and news about industry trends and developments
77
The Need for Recording Facts
* Record information as soon as you obtain it.
* Use the simplest recording method possible
* Record your findings in such a way that they can be understood by someone else
* Organize your documentation so related material ilocated easily
78
Software Tools
softwares that are available to use and record in documenting information
79
CASE Tool
use in every stage of development
80
Productivity Software
word processing, spreadsheet, database management, presentation graphics, and collaboration software programs
81
Histogram
showing the distribution of questionnaire or sampling results is a vertical bar chart
82
Graphic Modeling Software
Microsoft Visio is a popular graphic modeling tool that can produce a wide range of charts and diagrams.
83
Personal Data Management
* Microsoft Outlook that has a personal calendar and to-do list of priorities and capability to check off completed items
2nd Sem
flashcards
Decks in class (21)
# Cards
-
Rizal Intro75
-
Web Systems 180
-
SAD332
-
Rizal 210
-
Integrative Programming 315
-
Integrative Programming 426
-
Integrative Programming 554
-
Information Management - 173
-
Information Management - 252
-
Networking 162
-
Networking Chapter Exam33
-
Networking 222
-
Networking 344
-
Networking 418
-
Networking 61
-
Information Management - 337
-
Information Management - 428
-
Integrative Programming 116
-
SAD484
-
SAD557
-
NLP 10
