Systems Analysis and Design Unit 4

Pool

A BPMN term for the overall diagram of a process.

Swim Lanes

A BPMN term that designates specific customer areas within a pool.

System Requirements

A characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users. System requirements serve as benchmarks to measure the overall acceptability of the finished system.

Data and Process Modeling

A continuation of the modeling process that graphically represents system data and processes using traditional structured analysis techniques.

Brainstorming

A fact-finding technique for gaining information through the use of a small group discussion of a specific problem, opportunity, or issue.

Observation

A fact-finding technique where an analyst sees a system in action. Observation allows the verification of statements made in interviews.

Zachman Framework for Enterprise Architecture

A model that asks the traditional fact-finding questions in a systems development context.

Hawthorne Effect

A phenomenon where employees who know they are being observed are more productive.

Interview

A planned meeting during which the analyst obtains information from another person. Includes 7 steps: Determine the people to interview, establish objectives, develop questions, prepare, conduct the interview, document the interview, and evaluate the interview.

Joint Application Development (JAD)

A popular fact-finding technique that brings users into the development process as active participants. Results in a requirements model.

Sampling

A process where an analyst collects examples of actual documents, which could include records, reports, or various forms.

Document Review

A review of baseline documentation. Helps an analyst understand how the current system is supposed to work.

Fact-Finding

A step in the requirements modeling process that involves gathering facts about a systems project using techniques such as interviews, documentation review, observation, questionnaires, sampling, and research.

Rapid Application Development (RAD)

A team based technique that speeds up information systems development, but also produces a functional system, rather than just a requirements model. Relies heavily on prototyping and user involvement.

Fill-in Form

A template used to collect data on the Internet or a company intranet

Functional Decomposition Diagrams (FDD)

A top-down representation of a function or process. Using an FDD, an analyst can show business functions and break them down into lower-level functions and processes. Similar to drawing and organizational chart: start at the top and work downwards.

Documentation

Accurate records of interviews, facts, ideas, and observations.

Total Cost of Ownership (TCO)

All of the costs associated with the design, development, testing, implementation, documentation, training and maintenance of a software system. Will likely include indirect costs.

Advantages of JAD

Allows key users to participate in the requirements modeling process. Results in these key users feeling a sense of ownership and provides greater support for the system.

Agile Methods

An approach to managing projects that includes an iterative workflow and incremental delivery of software in short iterations

Research

An important fact finding technique that includes the review of journals, periodicals, and books to obtain background information, technical material, and news about industry trends and developments.

Object Modeling

Another popular modeling technique. While structured analysis treats processes and data as separate components, object-oriented (O-O) analysis combines data and the processes that act on the data into things called objects. These objects represent actual people, things, transactions, and events that affect the system. Analysts often use both Object Modeling and Structured Analysis techniques.

Unstructured Brainstorming

Anyone may speak at any time.

Range of Response Questions

Closed-ended questiosn that ask the person to evaluate something by providing limited answers to specific responses on a numeric scale.

Requirements Planning Phase

Combines elements of systems planning and systems analysis phases from the SDLC. Users, managers, and IT staff members discuss and agree on business needs, project scope, constraints, and system requirements. This phase ends when the team agrees on key issues and has authorization to continue.

CASE tools

Computer Aided Software Engineering

Development Strategies

Considers various development options and prepares for the transition to the systems design phase. Includes software trends, acquisitions and development alternatives, outsourcing and formally documenting requirements for the new system.

JAD Project Leader

Develops an agenda, acts as a facilitator of the JAD session

Questionnaires and Surveys

Documents containing a number of standard questions that can be sent to many individuals.

Recorder

Documents results of JAD sessions and works with systems analysts to build system models and develop CASE tool documentation

Analytical Skills

Enable the analyst to identify a problem, evaluate the key elements, and develop a useful solution.

Open Ended Questions

Encourage spontaneous and unstructured responses.

Interpersonal Skills

Especially valuable to a systems analyst who must work with people at all organizational levels, balance the conflicting needs of users, and communicate effectively.

Construction Phase

Focuses on program and application development tasks similar to the SDLC. Users continue to participate, however.

Productivity Software

Includes word processing, spreadsheet, and collaboration software programs

Team-Based Techniques for Requirements Modeling

Joint Application Development, Rapid Application Development, and Agile Methods

Disadvantages of JAD

More expensive than traditional methods, and can be cumbersome if the group is too large relative to the project.

Types of Requirements

Output, Input, Process, Performance, and Security

Structured Brainstorming

Participants speak only when it is their turn.

Personal Information Manager (PIM)

Personal Calendar, To-Do lists, and powerful contact management features.

Engaged Listening

Process of listening carefully and observing nonverbal communication

JAD Roles

Project Leader, Top Management, Managers, Users, Systems Analysts, Recorder

Managers

Provide department-level support for the project and understanding of how the project must support business functions and requirements

Users

Provide operational level input on current operations, desired changes, input and output requirements, user interface issues, and how the project will support day to day tasks

Systems Analysts and other IT staff members

Provide technical assistance and resources for JAD team members on issues such as security, backup, hardware, software, and network capability

Top Management

Provides enterprise level authorization and support for the project

Closed Ended Questions

Questions that limit or restrict the response. Useful when more specific information is needed, or when facts must be verified.

Leading Questions

Questiosn used during an interview that suggest or favor a particular reply. These should be avoided

RAD Disadvantages

RAD stresses the mechanics of the system istelf, and does not emphasize the company's strategic business needs. This could result in a system that works well in the short term, but long-term strategic goals might not be met. The accelerated development time might also mean lower quality.

Scalability

Refers to a system's ability to handle increased business volume and transactions in the future. Because it will have a longer useful life, a scalable system offers a better return on the initial investment.

Output

Refers to electronic or printed information produced by the system

Security

Refers to hardware, software, and procedural controls that safeguard and protect the system and its data from internal or external threats.

Input

Refers to necessary data that enters the system, either manually or in an automated manner.

Performance

Refers to system characteristics, such as speed, volume, capacity, availability, and reliability.

Process

Refers to the logical rules that are applied to transform the data into meaningful information.

Business Process Modeling

Represents one or more business processes, such as handling an airline reservation. During requirements modeling, analysts often create models that use a standard notation called Business Process Modeling Notation (BPMN).

Tasks of the Systems Analysis Phase

Requirements Modeling, Data and Process Modeling, and Object Modeling

RAD Phases

Requirements Planning, User Design, Construction, and Cutover

Cutover Phase

Resembles the final tasks of the SDLC implementation phase, including data conversion, testing, changeover to the new system, and user training. This is a much more efficient process than traditional techniques.

Sequence Diagram

Shows the timing of interactions between objects as they occur.

Project Data Management

Software that is powerful, flexible, and can handle many different types of inputs. Example: Microsoft OneNote

Systems Analysis Skills

Strong analytical and interpersonal skills are needed in order to build accurate models of systems.

Sample Types

Systematic, Stratified, Random

RAD Advantages

Systems can be developed much more quickly and with significant cost savings.

Agile Disadvantages

Team members need a nigh level of technical and interpersonal skills. Lack of structure and documentation can also introduce risk factors such as loss of corporate knowledge and scope creep.

Graphic Modeling Software

Tools that can produce many different types of diagrams and charts.

User Design Phase

Users interact with systems analysts to develop models and prototypes that represent all system processes, outputs, and inputs. The group working on this phase typically use JAD techniques and CASE tools to translate user requirements into working prototypes. Continuous process that often interacts and overlaps with the Construction Phase.

Scrum

Uses small teams to produce small pieces of deliverable software using sprints. Scrum sessions have team members playing specific roles with different, sometimes conflicting interests (e.g. Owners vs Users, Managers, and other Stakeholders).

Agile Advantages

Very flexible and efficient in dealing with change. They stress team interaction and reflect community-based values. Frequent deliverables constantly validate the project and reduce risk.

Use Case Diagram

Visually represents the interaction between users and the information system

Actor

What represents a user in a Use Case Diagram. An actor has a specific role that descripes how he or she interacts with the system.

Unified Modeling Language (UML)

Widely used method of visualizing and documenting software systems design. Uses Object-oriented design concepts.

Data Flow Diagrams (DFD)

graphically describes the flow of data within an organization

Requirements Modeling

involves fact-finding to describe the current system and identification of the requirements for the new system, such as outputs, inputs, processes, performance, and security.