Unit 4 Flashcards
Project Identification and Selection
Projects are triggered when someone sees an opportunity to create business value (cost reduction, new products and services, improved productivity) from using information technology.
Users of Current System
IT/MIS group
Top Management
Externally imposed
System Request
Lists key elements of the project
Lists key elements of the project Project name Project sponsor Business need (Symptoms) Functionality (Objectives) Expected value Special issues or constraints (Scope)
Confirming Project Feasibility
Technological feasibility CanWe Build It? Economic feasibility ShouldWe Build It? Organizational and cultural feasibility If we build it, will they come?
Systems Analysis Activities
Gather Detailed Information about current system
Interviews, questionnaires, documents, observing business processes, researching vendors, comments and suggestions
Model the current (As-is) System
Analyze the Model to identify solutions to problems
Define Requirements
functional requirements and non-functional requirements
Develop a model for the proposed (to-be) system
Prepare a functional specification document
What Are Requirements?
System Requirements =
Functional requirements
Non-functional requirements
Functional Requirements–the activities the system must perform
Business uses, functions the users carry out
Non-Functional Requirements–other system characteristicsConstraints and performance goals
FURPS+ Requirements Acronym
Functional requirements Usability requirements Reliability requirements Performance requirements Security requirements
Look at FURPS+ Requirements Acronym Diagram
Do it
Information Gathering
1background information such as company’s overall objectives, goals, organization structure etc.
- employees, their duties and responsibilities within the unit.
- processes performed, process triggers, who performs those activities, what inputs/data are used, sources of inputs/data, how they are used, what outputs are produced, where those outputs are sent, who uses the outputs
- the sequence of processes
- volume and frequency of data and processes
- controls over input, process, and output.
- system boundaries
Information-Gathering Methods
Review existing reports, forms, and procedure descriptions
Interview and discuss processes with users
Observe and document business processes
Build prototypes
Distribute and collect questionnaires
Conduct joint application design (JAD) sessions
Review Existing Reports, Forms, and Procedure Descriptions
Source: External industry-wide professional organizations and trade publications
Source: Existing business documents and procedure descriptions within organization
Identify business rules, discrepancies, and redundancies
Obtain preliminary understanding of processes
Use as guidelines/visual cues to guide interviews
Look for user additions to forms/reports
Look for unused form/report elements
Conduct Interviews and Discussions with Users
Effective way to understand business functions and rules
Time consuming and resource expensive
May require multiple sessions to
Meet all users
Understand all processing requirements
Can meet with individuals or groups of users
List of detailed questions prepared
Observe and Document Business Processes
Varies from office walkthroughs to performing actual tasks
Not necessary to observe all processes at same level of detail
May make users nervous, so use common sense
Build Prototypes
Preliminary working model of a larger, more complex system component
Discovery, design, evolving prototypes
Prototype should be
Operative •Working model to provide “look and feel”
Focused to accomplish single objective
Quick•Built and modified rapidly with CASE tools
Distribute and Collect Questionnaires
Limited and specific information from a large number of stakeholders
Preliminary insight into business
Confirm understanding of the system with large user base
Not well suited for gathering detailed process information
Joint Application Design
Session leader trained in group dynamics and JAD group facilitation
Knowledgeable business and system users and policy makers
Technical staff representatives to handle
Computer and network configurations
Operating environments
Security issues
Project team members