Systems Analysis and Design, (X &L)3

Pataasin ang iyong marka sa homework at exams ngayon gamit ang Quizwiz!

Analysis Phase Steps

1.Develop an analysis strategy -Model the current system -Formulate the new system 2.Gather the requirements -Develop a system concept -Create a business model to represent business data and business processes 3.Develop a system proposal

Structured analysis

A traditional systems development technique that uses phases to plan, analyze, design, implement, and support an information system Processes and data are treated as separate components

CRUD

Acronym for create read update delete

process

Any part of an organization that takes inputs and transforms them into outputs

Arrow

Data flow

Planning

In which phase of the SDLC is the project plan developed?

Database Administration

Involves data design, management, security, backup, and access systems.

Expert systems

Knowledge management systems Systems that simulate human reasoning by combining a knowledge base and inference rules that determine how the knowledge is applied

fourth-generation languages (4GLs)

Non-procedural programming languages that are especially valuable in implementing an object-oriented system design.

True

Object nodes in an activity diagram are depicted using rectangles

Problem definitition

Problem statement

e-Commerce Law

R. A. No. 8792

SO

Sales Order

Symbols used in DFD

Square, Arrow, Circle, Open Rectangle

Deployment Team

Team that installs and configures workstations

Return on Investment (ROI)

The amount of revenues or cost saving results from a given investment(Total Benefits - Total Costs)/ Total Costs

True

The analysis phase of the SDLC ends when a system proposal for the new system is presented to the approval committee

Forms of Testing

Unit, Integration, Systems & Acceptance

Observation

Useful because users/managers often don't remember everything they do, checks validity of information gathered in other ways.

Modules

Whole or Modular

test system

a copy of the production system that is modified to test changes

database management system (DBMS)

a system software component that manages and controls one or more databases

Iteration data dictionary entries

become do while do until perform until structured english statements

What is the type of the data flow that contains data that are used between processes called?

internal

Little's Law

inventory = TR x flow time, inventory often measured as WIP, formula represents long term relationship among inventory, TR, and flow time

Schedule Feasibility

means that a project can be implemented in an acceptable time frame.

Economic Feasibility

means that the projected benefits of the proposed system outweigh the estimated costs usually considered the total cost ownership (TCO), which includes ongoing support and maintenance costs, as well as acquisition costs.

document metaphor

metaphor in which data is visually represented as paper pages or forms

make to order

producing goods in response to direct customer orders

object-oriented programming (OOP)

programming using object-oriented languages that support object classes, inheritance, reuse, and encapsulation

closed-ended questions

questions that elicit specific facts

open-ended questions

questions that encourage discussion or explanation

Technical Feasibility

refers to the technical resources needed to develop, purchase, install, or operate the system.

phases

related groups of development activities, such as planning, analysis, design, implementation, and support

Functional

relates to data, a function, process or behavior

Non-functional

relates to performance or usability

Non-functional requirement

relates to performance or usability

structured approach

system development using structured analysis, structured design, and structured programming techniques

user interfaces

system interfaces that directly involve a system user

present value

the current value of future cash flows

Discount rate

the rate of return used to compute PV

Generalization

"A-kind-of" relationships represent ...... relationships

What is a Scrum Master?

- Responsible for seeing that Scrum is done properly

What are tech stories?

- Tech stories are internal to the DT - They are things that must be done for the sprint goal (e.g. server building, network install) - Product Owner does not see them as delivering the goal (and PO says what must be done) - They are vital all the same - You have to find a way to get them done as part of the sprint

Work Practices

- must be organized in a logical order - must begin with who w/o adjectives and repetition - foundations for use cases

Project Selection

-Projects are approved, declined, or delayed based on value added vs. risks

Tangible

............. value can be quantified during the project initiation phase.

Economic

.............. feasibility is determined by identifying costs and benefits associated with the system.

Workplan

A dynamic and sequential list of all tasks needed to complete a project

User support

A function typically performed by individuals within an IT department Provides users with tehnical information, training, and productivity support

False

A fundamental disadvantage of the JAD sessions is that they are subject to be dominated by a few, e-JAD attempts to eliminate the disadvantage

Business Model

A graphical representation of business functions that consist of business processes, such as sales, accounting, and purchasing

True

A guard condition represents the value of the decision-test based on which a particular path from the decision node will be transversed

Knowledge base

A large database that allows users to find information by clicking menus, typing keywords, or entering text questions in normal phrases

Object class

A logical grouping of objects that have the same (or similar) attributes and behaviors (methods)

What is a mission statement?

A one sentence description of the reason for the existence of an organization.

Software

A program run by computers for a specific function or task

Enterprise Resource Planning (ERP)

A set of integrated programs capable of managing a company's vital business operations for an entire multisite, global organization.

System

A set of interrelated objects to achieve a common goal

report generator

A tool for designing formatted reports rapidly. Also called a report writer.

What is the primary goal of a Systems Analyst?

Accurately state the user's requirements for a new information processing system

systems implementation

Also known as conversion; four approaches are: direct, parallel, pilot, and phased.

Mission-critical system

An information system that is vital to a company's operations

Informal Benchmarking

Analyzes similar processes in other successful organizations

Systems Analysts

Analyzes the business situation, identifies opportunities for improvement and designs an information system to implement them.

Business-to-Business

B2B A commercial exchange (e.g. products or services) between businesses, typically enabled by the internet or electronic means

BOMS

Bill of Materials

tools for systems development

CASE tools. flowcharts. decision tables. project management: PERT, gantt charts, microsoft project.

CMMI

Capabilities Maturity Model

What three duties specifically should not be mixed?

Create a purchase order, show a physical receipt, and pay an invoice

Events - Video Store

Customer creates account Customer checks-out movie Customer returns movie Manager generates reports at end of day/week Time to issue reminder email for late movies

Data Flow Diagram

DFD Diagram that shows how the system stores, processes, and transforms data into useful information

Level-n

DFD that is the result of n nested decompositions from a process on a level-0 diagram

Level-0

DFD that represents a systems major processes, data flows, and data stores at a high level of detail

What is a Data Flow Diagram?

DFDs provide a graphical representation of how information moves between processes in a system

What is reference work of data about data compiled by systems analysts?

Data Dictionaries

Tools use in Structured Analysis

Data flow diagrams, Data dictionary, Decision trees, Decision tables, Structured english, Pesudocode

Processes

Describe the tasks and business functions that users, managers, and IT staff members perform to achieve specific results.

Database Administration

Duties in data design, management, security, backup, and user access, for a database system, usually performed by members of the IT department

Knowledge management systems

Expert systems Systems that simulate human reasoning by combining a knowledge base and inference rules that determine how the knowledge is applied

Use Case Scenario

Explain user navigation of the site

Events in use cases

External - occurs outside system boundary Temporal - occurs at a predetermined time

Systems Analyst

Focuses on the IS issues surrounding the system

Design

In which phase of the SDLC is the system specification developed?

Black Box Principle

Just having the inputs and outputs allows you to determine the function within the "box"

Intangible Business Value

Know it adds value and/or saves time, but may not be able to quantify or measure its benefits. ex) improved customer service.

Buy

Of The Shelf Software Package

systems analyst

Plans and designs information system.

Interface Technology

Provides the operational structure required to carry out the design objectives.

RFI

Request for Information, shorter version of RFP

Application Software

Software such as email, word processors, spreadsheets, and graphics packages used by employees

Screen Generators

Some user applications use this to allow users to design their own data entry forms

Square

Source or destination of data

Business Processes

Specific set of transactions, events, and results that can be described and documented.

Composition

Stronger- all or nothing

Information system

System that combines information technology, people, and data to support business requirements Five key components: Hardware, software, data, processes, and people

pilot approach

Systems implementation in which a new system is tried out in only one part of the organization. Later it is implemented throughout the rest of the organization.

parallel approach

Systems implementation in which old and new systems are operated side by side until the new one has shown it is reliable.

phased approach

Systems implementation whereby a new system is implemented gradually over a period of time.

User productivity systems

Systems that provide employees of all levels a wide variety of tools to improve job performance

Systems implementation phase

The fourth phase of SDLC Construction of the new system- Programs are written, tested, and documented, and the system is installed

Analysis

The second phase of the SDLC in which system requirements are studied and structured

Feedback

The user has the right to a system that provides clear, understandable, and accurate information regarding the task it is performing and the progress toward completion.

Installation

The user has the right to install and uninstall software and hardware systems easily without negative consequences.

Scope

The user has the right to know the limits of the system's capabilities.

Perspective

The user is always right. If there is a problem with the use of the system, the system is the problem, not the user.

Cloud Computing

This can be viewed as an online Software as a Service (SaaS) and data environment supported by supercomputer technology.

1950s to 1960s

This decade consisted of large computers, basic understanding of programming languages, and in introduction to 3rd generation languages, more faster and reliable computers.

Logical Desgin

This is a design that does not address the actual methods of implementation.

Benchmark Testing

This is a good way to measure relative performance of two or more competing products in a standard environment.

Systems Requirement Document

This is like a contract that identifies what the system developers must deliver to users.

Minimize Effort

Three clicks rule

List the four phases of the SDLC and the steps that occur in each

To identify the tasks for a work plan the project manager can ..............

Which of the following is not a problem when creating decision tables?

Too many conditions

Which of the following is not one of the main problems that can occur in developing decision tables?

Too many conditions

User Interface Design Process

Use Case Scenario, Interface Structure Design, Interface Standards Design, Interface Design Prototyping, Interface Evaluation

The importance of customer service

Use-case point-based estimation also has a set of factors that are used to adjust the use-case point value. Which one list in the following is not one of the technical factors:

Interface Evaluation

Walk-through & Interactive Eval plus formal usability testing

Outcome Analysis

What does the customer want in the end

semantic net

a graphical representation of an individual data entity and its relationship with other individual data entities

sprint

a time-controlled mini-project that implements a specific portion of a system

alt frame

notation on a sequence diagram showing if-then-else logic

remote wipe

security measure that automatically deletes sensitive data from a portable device when unauthorized accesses are attempted

Polymorphism

the same message can have different meanings

attribute value

the value held in a single table cell

Dynamic Binding

type of object is not determined until run time

B2B(Business to business) Types

◦ EDI ◦ Supply chain management (SCM) ◦ Supplier relationship management (SRM)

Technical Feasibility

"Does the technology exist out there?"

make to stock (MTS)

"Process activated to meet forecast (i.e., predicted) demand. Customer orders are served from target stocking level

make to order (MTO)

"Process only activated in response to an actual order. Both work-in-process and finished goods inventory kept to a minimum

Organizational Feasibility

"Will the organization accept this new information system?" "Will it be used? Why?"

Daily Scrum meeting

- 15 minutes time-boxed, standing up - DT asks itself - What was accomplished since last meeting? - What needs to be accomplished by next meeting? - Who needs help? - What obstacles are in the way? - DT adapts plan, for day to succeed - SM ensures meeting is held

Sprint Retrospective

- 3 hour time-box with DT + PO + SM - DT reflect on Sprint, plan improvements - Reflect on people, relationships, process, tools - Identify order: what went well and improvements

Sprint Review

- 4 hour time-box with DT and PO - Held at end of sprint - PO identifies PO items 'done' / not 'done' - DT discuss good, problems, solutions - DT demonstrates work 'done' - PO discusses PB as it stands - All collaborate on what to do next - Output is a revised PB

Sprint Planning meeting

- 8-hour time-box - Defines work to be done in Sprint (planned and agreed by entire DT) - Two halves (both 4 hour time-box) 1. What will be delivered by this sprint 2. How will the work needed to be done What will be delivered - Input is product backlog, latest increment, projected capacity of DT, past performance of DT. - Output is list of product backlog items in Sprint (a forecast) & Sprint goal - must be in terms of value to organisation How will chosen work be done? - Work breakdown - requires systems planning modelling and design (waterfall). - read down user stories into smaller stories or tasks

What is a product owner?

- A single person responsible for maximising the value of the product and managing the product backlog - Only person allowed to tell DT any changes in requirements PB management: - Clear expression of PB items - Ordering items - Ensuring value of DT work - Ensuring PB is visible, transparent, clear and shows what the scrum team will do next - Ensuring DT understands items

Agile Planning Game

- All items have a value estimate - Each item is written on a note card - Full team membership is known and available for planning - Each team member has a set of planning game cards

What is evolutionary in prototyping?

- Build a part - Get feedback from user - Alter it, get feedback (cycle) - Maybe even release to user - Grow the system through evolution

What are the advantages of agile?

- Change is embraced: with shorter planning cycles, it is easier to accommodate changes at any time during the project - End-goal can be unknown: agile is very beneficial for projects where the end-goal is not clearly defined. - Faster, high-quality delivery: breaking down the project into iterations (manageable units) allows the team to focus on high=quality development. Can be delivered with faster with consistent, successive iterations. - Continuous improvement: projects encourage feedback from users and team members throughout the whole project.

What does a DFD allow you to do?

- Check your thinking (does it really work like that?) - Use thinking to check your DFD e.g. - Gaps in understanding (what happens at that end?) - Differences (the data receiver contradicts the sender) - Confusion (to clear them up if there are any e.g. this process doesn't work)

Methodology

- Chosen way - Basis of 6 criteria - Overall concept/design - Philosophy of how to do work

First three parts of a physical data flow diagram

- Clarify which processes are performed by humans and which are automated - Describe processes in detail - Sequence processes in the order they must be executed

Types of Questions

- Closed-ended -- more specific answer - Open-ended question -- valuable information

What does contemporary elicitation consist of?

- Continuous user involvement - Prototyping - Agile Planning Game - Joint Application Design - User-Centred Design - Business process reengineering

Data dictionaries are used for

- Create reports - Generate Computer program and source code - Analyze the sytem design for completion -Create XML document structures

What are the disadvantages of formal organisation?

- Delay in action - Ignores social needs of employees - Emphasis only on work

Businesses in the 21st century

- E-commerce or I-commerce - B2C (Business-to-Consumer) - B2B (Business-to-Business)

What are the advantages of information organisations?

- Fast communication - Fulfils social needs - Correct feedback

What are the features of formal organisation?

- Formal organisational structure is created intentionally by the process of organising - Purpose of formal organisation structure is achievement of organisational goal - In formal organisational structure each individual is assigned a specific job - Every individual is assigned a fixed authority or decision-making power - Results in creation of superior-subordinate relations - Creates a scalar chain of communication in the organisation

Use Case Diagram

- Graphically shows the relationship between a use case and an actor - Names always start with an action - 1 Use case = 1 narrative

What are sprints?

- Heart of scrum activity - 4 weeks or less - Some allow up to 6 but emphasise limit - Results in creation of 'done', usable, releasable product increment - Next sprint starts immediately after one ends During a sprint - No changes are made that would affect the sprint goal - DT composition constant - Quality goals do not change - Scope may be renegotiated with PO and DT as more is learned

Examples of Application Software

- Horizontal system - Vertical system - Legacy systems

Systems Development Life Cycle (SDLC)

- Idea - Planning - Analysis - Design - Implementation

6 Core Processes (IPDDBComplete)

- Identify the problem/obtain approval - plan and monitor the project - discover/understand details (Systems Analysis) - design system components - Build, test, and integrate system components - Compete system tests and deploy the solution

What is the method for interviews?

- Identify what you need to know (if you can, might not know it) - Find out who you can get that from - Work out interview objectives - Plan the interview (prepare question and identify amount of time you need)

What are the 5 benefits to scrum?

- Improves communications - Eliminate other meetings - Identify and remove obstacles - Promote quick decision-making - Improve each DT member's knowledge of overall project.

What is the agile method?

- Incremental / iterative approach - Instead of in-depth planning at the beginning of the project, agile methodologies are open to changing requirements over time - Encourages constant feedback from end users

What are the features of informal organisation?

- Informal organisational structure gets created automatically without any intended efforts of managers. - Formed by the employees to get psychological satisfaction - Does not follow any fixed path of flow of authority or communication - Source of information cannot be known under informal structure as any person can communicate with anyone in organisation

What is the prototyping model?

- Instad of freezing requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. - Prototype is based on currently known requirements - By using the prototype, users can get an 'actual feel' of the system

What does traditional elicitation consist of?

- Interviewing (Individual users, Nominal Group technique (process where a group identify problems, generates solutions and makes decisions) - Analysing procedures - Analysing documents - Observing people

What is scrum?

- It's an iterative, incremental system creation - Scrum Teams (ST) - Scrum Events - Scrum Artefacts - Pillars (transparency, inspection, adaption) - Development Team - Product Owner - DT work is done in sprints - Short time boxes with clear goals that complete certain 'user-stories' - Sprint goal is stated in business terms - 1 sprint delivers 1 increment of product

What is the definition / concept of done in scrum?

- It's defined and agreed by product owner and development team - e.g. All code checked in, all code delivered to tester(s), all code ready to deploy, etc...

What is throwaway in prototyping?

- It's used to explore ideas - Build an interface - Either with functionality or not - Walk the users through it - To make your conversations with the user much more about their reality / possibilities - Maybe more than once - explore alternatives - It does not become part of the final system

What is the agile methodology?

- Learning happens in all stages - Ergo: - Iterate - Change what has been created already - Re-factor program code (improve it) - DELIVER ON TIME - Time is top priority (time over features) - Modern - Industry accepted - More effective - Scrum (user stories)

Interview Methods

- Listen very carefully - Ask for meanings of company jargon - Take notes - May be only interview with person (avoid needing clarification)

What are the disadvantages of the waterfall method?

- Major downside to waterfall's rigidity is the inability to handle change. Testing occurs late In the life cycle, and if you find that user's do not like the product then it can be too late to pivot. - Slow delivery times: As many as four phases need to be completed before coding begins. Which means that stakeholders / customers won't see a working product until late in the life cycle. - Customers/Stakeholders often don't know what they want until they have a chance to play with a working prototype. Since al;l requirement gathering is done at the start, there is a large chance of missing the mark and not delivering a product which is wanted

What are potential risks for an outcome of a project?

- Nature of a project: too large/complicated - Client characteristics: client has 5 employees/ 500 - Developer Characteristics: Skills? Familiar with technology? - Project Management: Scope creep, too optimistic

What is good project management?

- No micromanaging - Good organization

What is product backlog?

- Order list, everything for product, single source of requirements. - Product Owner is responsible for backlog (Content, availability, order) - PB evolves, continually, dynamic (never complete, 'groomed' by PO and DT during sprint). - PB comprises all: features, functions, requirements, enhancements, fixes. - Layout consists of description, order and estimate. - Higher order items are clearer and more detailed with a more precise estimation. (ESSENTIALLY A COLLECTION OF USER STORIES)

Hardware

- Physical layer of the information system - Moore's Law

What does a Systems Analyst do?

- Plan, develop, and maintain information systems - Also manages IT projects, including tasks, resources, schedules, and costs - Conducts meetings, delivers presentations, and writes memos, reports, and documentation

What are the disadvantages of the prototype model

- Practically, the methodology may increase the complexity of the system as scope of system may expand beyond original plans - Incomplete application may cause application not to be used - Incomplete or inadequate problem analysis

What are the contemporary elicitation techniques?

- Prototyping - Agile Planning Game - Continuous User involvement - Joint Application Design - User-Centred Design

Prototyping

- Respect engineering concept Elicitation cycle: - Conduct initial analysis - Build a small part of the system - Check it with the user - Powerful with IT literate users - Can use evolutionary or throwaway in project (can also use both in same project) - Regularly involves users - Feedback, criticism: - Identification of incorrect thinking - Opportunity to correct software built so far

What is the development team?

- Self organising, no one tells DT how to work - Cross functional (have all skills needed). - Everyone is a developer

What are scrum teams?

- Self-organising and multi-functional - Members do not have fixed roles - Scrum Master (SM), Product Owner (PO), Development Team (DT)

What is sprint backlog?

- Set of product backlog items selected for a sprint (along with plan for delivering the increment and realising the sprint goal). - When new work is required to complete sprint then add to SB.

Disadvantages of information organisations

- Spread rumors - No systematic working - May bring negative results - More emphasis on individual interest

Software

- System software - Application software

What are the advantages of formal organisation?

- Systematic Working - Achievement of organisation objectives - No overlapping work - Co-ordination - Creation of chain command - More emphasis on work

What is the process of the Agile Planning Game?

- Team goes through all items and chooses the one which has the lowest effort. Write number '2' on the card. - Team looks at the item with highest value - Each team member thinks about how much effort the team will expend to fully complete all work. - If all team members choose the same value, they write the value on the item and go back to step three for the next item (if no more items then process is complete). - Person with the highest and lowest value cards both explain why the voted the way they did.

What are the disadvantages of agile?

- Team must be knowledgeable: Agile teams are usually small, so team members must be highly skilled in a variety of areas - Time commitment from developers: Agile is most successful when development team is completely dedicated to the project. Active involvement and collaboration is required throughout the agile process. - Documentation can be neglected: Agile prefers working software over comprehensive documentation. Agile teams should find the right balance between documentation and discussion.

Last three parts of a physical data flow diagram

- Temporary data stores and transaction files - Specify actual document and file names - Controls to ensure accuracy and completeness

What are user stories?

- They provide slim, high-level requirements - They are 'reminders to have a talk with stake-holders' Each Story: - Stakeholder writes it - Use simplest tools you can - e.g. index cards - Remember non functional requirements - Indicate estimated size (hours to program) - Indicate priority - Give it an ID so you can refer to it. Collect Stories Formalise them, analyse them and identify roles and requirements - They describe a user and the reason why they need to use the service you're building - THEY ARE ESSENTIAL IN BUILDING A SERVICE TO MEET USER NEEDS Every member must use user stories to: - Track everything they need to do - Think about their work from a user's perspective - discuss their work with colleagues

What are the stages for planning an interview?

- Think through what they might do (or what you can assess) - Design questions around that (and for possible alternatives) - Use open and closed questions (can elicit previously unknown info) Closed question example - has the ordering system ever failed? - Used to find out facts and stop interviewee wandering - Risk of missing unknown info - Need to complete interviews on schedule - Always have a sponsor high up in the organisation (get key interviewees to cooperate)

What are Scrum Events?

- Time-boxed - Sprint: planning meetings, daily scrums, development work, review and retrospective

What is the purpose of a DFD?

- To act as the starting point for redesigning a system - Show the scope and boundaries of a system - To show how the data flows in a system - May be used as a communications tool between a systems analyst and any person who plays a part in the system.

What is the waterfall method?

- Traditional approach to software development where the project is broken up into distinct stages that must be completed in sequence. - Must complete one phase before moving onto the next. - Once that phase is completed, you cannot go back. (can only travel downstream) - Must complete full development cycle before returning to the top.

What do you get from listening in an interview?

- Truth (and Accidental / Deliberate non-truth) - Opinions - Speculation

What is included in a use case narrative?

- Use Case Name - ID - Priority - Actor - Description - Trigger/Type - Preconditions - Normal Course - Postconditions - Exceptions

What are decision tables?

- Used for conditional logic - Does not have the ambiguity of English - Simpler than psuedo-code flowcharts and structured English for complex logic.

What are the advantages of the prototype model?

- Users are actively involved in development - Users get a better understanding of the system being developed - Errors can be detected much earlier - Quicker user feedback is available

Standards

- Very important - Formal rules for naming files - Forms indicating goals reached - Programming guidelines

Characteristics of a jelled team

- Very low turnover rate -Strong sense of identity -A feeling of eliteness

What are the main methodologies of system creation?

- Waterfall (linear) - Structured (linear) - Prototyping (iterative) - Agile (iterative) ITERATION HAS BECOME TO BE GENERALLY ACCEPTED AS DELIVERING BENEFIT

What are the common questions to ask when interviewing?

- What do users do? - What information do they need to do that? - What information do they pass to others (to whom and why?) - What information would enable them to work better?

How do we construct a decision table?

- Work out all conditions and name them - Work out all possible actions and name them - Create all possible rules - Define actions for each rule - Sometimes there is no action possible

Soft System Methodology

- approach for encouraging communication in a group about a problem - set of techniques that create a consensus

Economic Feasibility

- based on hard facts - 1 time costs, reoccurring costs, benefits (savings)

Coupling

- how models of a system is interconnected - has to be just right to have good productivity - highly coupled = expensive & lower productivity

Rapid Application Development (RAD)

-Address both weaknesses of structure design methodologies (Complete specification and time lapses) by adjusting the SDLC phases to get some part of the system developed quickly and into the hands of the users -As a user better understands the information technology (IT), the systems requirements tend to expand

Good Questionnaire Design

-Begin with non-threatening and interesting questions -Group items into logically coherent sections -Do not crowd a page with to many items -Avoid abbreviations -Pretest to identify confusing questions -Provide anonymity to respondents

Advantages of logical data flow diagram

-Better communication with users -More stable system -Increased understanding of the business -Elimination of redundancy - Increased flexibility and easier to maintain

How to create a requirements definition

-Determine the types of functional and non functional requirements applicable to the project -Requirements that meet a need but are not within the current scope can be added to a list of future enhancements

What does the SDLC require?

-Establishes systems goals -Setting up the project -Determining requirements -Business knowledge and management skill

Agile Development

-Few rules and practices that focus on the working conditions of the developers -Accommodate changing requirements -Based on short cycles and sprints - eliminates modeling and documentation overhead and time -Require co location of the development team -can evolve into a prototyping approach "programmers gone wild" -Lack of audibility -Hard to deliver large mission critical systems

Two steps to drawing the decision tree

-First identify all conditions and actions and the timing -Second begin building the tree from left to right while making sure you are complete in listing

Architecture centric

-Function (external) view: focuses on the users perspective -Static (structural) view: focuses on attributes methods, classes and relationships -Dynamic (behavioral) view: focuses on messages passes among objects and state changes within an object

What does a data repository contain

-Information about system data -Procedural Logic and use cases -Screen and report design -Relationship between entities -Project requirements -Project management information

Techniques used for requirements gathering

-Interviews (most popular technique) -Joint Application (JAD) -Questionnaires -Document analysis -Observation

Strategies for problem analysis

-Root cause analysis -Duration analysis -Activity-based costing Same as duration analysis but applied to costs -Informal bench marking Analyzes similar processes in other successful organizations -Outcome analysis What does the customer want in the end? -Technology analysis Apply new technologies to business processes and identify benefits -Activity elimination Eliminate each activity in a business process in a "force-fit" exercise

Primary Drivers of Systems Development

-Scope -Time -Cost

Skills Needed for an Analyst

-Technical -business -Analytical -Communications -Interpersonal -Ethics

Three advantages of a decision tree over a decision table

-The order of checking conditions -Conditions and actions are found on the same branches but not on others -Trees are more readily understood.

When is SCRUM good

-Unclear user requirements -Unfamiliar technology -Complexity -Need for reliability -Short time schedule

Iterative and Incremental

-Undergoes testing and refinement -The analyst understands the system better over time

Characteristics of OOAD

-Use case driven -Architecture Centric -Iterative and incremental

Observation Technique

-Users/managers often don't remember everything they do -Checks validity of information gathered in other ways -Behaviors may change when people are watched -Be careful not to ignore periodic activities

Dot-com

.com Internet-dependent firm Company that bases its primary business on the Internet, rather than using traditional business channels

Elements of Use Case Diagrams

1. Actors -External entities that interact with your system (persons, systems, or other organizations) 2.Associations -lines to connect actors and use-cases (interactions, inclusions, extensions, or generalizations) 3. Use case -A major process in the system that gives a benefit to the users 4.Subject boundary -A named box that depicts the scope of the system 5. Include Relationship -Represents the inclusion of the functionality of one use case within another (mandatory) 6.Extend Relationship -Represents the extension of the use case to include optional behavior

Problems in Requirements determination

1. Analyst may not have access to the correct users 2.Requirements specifications may be inadequate 3.Some requirements may not be known in the beginning 4.Verifying and validating requirements can be difficult

Problems in determining requirements: Problem analysis

1. Ask users to identify problems with the current system 2.Ask users how they would solve these problems 3.Good for improving efficiency or ease of use

Requirements of Analysis Phase

1. Business - What it needs 2. User - what they need to do 3. Functional - what software should do 4. Non-functional - characteristics software should have 5. System - how it should be built

order of processes

1. Customer Inquiry 2. Create a Quotation 3.Customer purchase order 4. Sales Order 5. prepare the shipment 6. send 7. customer invoice 8. receive payment

Activity Diagrams

1. Develop these from the use-cases -These model the business processes or how a business operates -Used to illustrate the movement of objects (data) between activities

Agile Development Methodologies

1. Extreme Programming -Founded on four core values: communication, simplicity, feedback, and courage (quality first and personal development mentality -Not suitable for large projects or non jelled teams -Difficult to include outsiders -Lack of analysis and design documentation raises issues in complex projects 2.Scrum -Teams are self organized and self directed -No designated team leader -Once a spring has begun, they do not consider any additional requirements

What are the criteria for determining correct development methodology?

1. How familiar you are 2. Clarity of user requirements 3. System complexity 4. System reliability 5. Short time schedules 6. Schedule visibility

What are the risks that could effect the output of a project?

1. Nature of a project - how big/complicated 2. Client characteristics - how familiar is client w/tech and developer 3. Developer characteristics - confident in project domain/how familiar with the technology/turnover 4. Project Management - proper documentation/good relationship with the client

RAD Methodologies

1. Phased -Breaks an overall system into a series of versions that are developed sequentially. The most important and fundamental requirements are bundled into the first version of the system. -Have the advantage of quickly getting a useful system into the hands of the users -Major drawback is that users begin to work with systems that are intentionally incomplete 2.Prototyping -Performs the analysis, design, and implementation phases concurrently -Quick and dirty system with minimal features that users can interact with -Fundamental issues and problems are not recognized until well into the development process

What is BP and Functional Modeling

1. Process of turning the requirements into functional models -Model is a representation of reality -Functional Models are logical (independent of how they are implemented manual or computerized) -Develop use cases from the requirements -Includes a diagram and a description to depict the discrete activities that the users perform -A use care represents a function or an action within the system -The subject (of a use care) is the system under analysis or design to which a set of use cases apply (business or company, software system, physical system or device, or a smaller subsystem having some behavior)

Guidelines for Activity Diagrams

1. Set the scope of the activity being modeled 2. Identify the activities; connect them with flows 3.Identify any decisions that must be made 4.Identify potential parallelism in the process 5.Draw the activity diagram

The SDLC Process

1. The process consists of four phases 2.Each phase consists of a series of steps 3.Each phase is documented (deliverables) 4.Phases are executed sequentially, incrementally, iteratively, or in some other pattern

3 steps of Analysis Phase

1. Understand current situation (as-is system) 2. Identify improvements 3. Define requirements for new system (to-be system)

What are the secondary goals of a Systems Analyst?

1. Understand user requirements 2. Communicate the current understanding of the proposed system 3. Prevent expensive mistakes 4. State a design problem 5. State conditions for system acceptance

First three structured english steps

1. express all logic in terms of sequential structures, decision structures, case structures, or iteration 2. use and capitalize accepted keywords such as IF, THEN, ELSE, DO 3. Indent blocks of statements to show their hierarchy.

Data flow approach has four main advantages over the narrative

1. freedom from committing to the tech implementation too early 2. further understanding of interrelationships 3. communicating current system knowledge 4. analysis of the proposed system have been defined

5 Key Components of an Information System

1. hardware 2. software 3. data 4. processes 5. people

First three steps to create a use case model

1. review the business specifications 2. identify the actors within the problem 3. identify high level events and develop the primary use cases that describe the events

Implementation Phase Steps

1.Construct the system -Build it (write the programming code) -Test it 2.Install system -Train the users 3.Support the system (maintenance)

Design Phase Steps

1.Develop a design strategy 2.Design architecture and interfaces 3.Develop databases and file specifications 4.Develop the program design to specify: -What programs to write -What each program will do

Four Phases of SDLC

1.Planning -Why should we build this system -What value does it provide? -How long will this take? 2.Analysis -Who will use it? -What should the system do for us? -Where and when will it be used? 3.Design -How should we build it? 4.Implementation

Planning Phase Steps

1.Project Initiation -Develop/receive a system request -Conduct a feasibility analysis 2.Project Management -Develop the work plan -Staff the project -Monitor and control project

Identifying Major Use-Cases

1.Review the requirements definition 2.Identify the subjects boundaries 3.Identify the primary actors and their goals 4.Identify the business processes and major use cases

Major components of feasibility

1.Technical (can we build it?) 2.Economic (should we build it?) 3.Organizational (will they use it?)

Structured Development

1.Waterfall -Identifies system requirements long before programming begins -Minimizes changes to the requirements as the project proceed -Design must be completely specified before programming begins 2.Parallel -Attempts to address the problem of long delays between the analysis phase and the delivery of the system -Divides the project int a series of distinct sub projects that can be designed and implemented in parallel -It can reduce the time to deliver a system -Sometimes the sub projects are not completely independent

Last two structured english steps

4. Underline words or phrases that have been defined in the data dictionary 5. be careful when using and or operations

Implementation

4th phase in which info system is coded, tested installed, and supported in the organization

Last two steps to create a use case model

5. review each primary use case to determine variations 6. Develop the use case documents for all primary use cases

probability of a project coming in on the critical path time is

50%

Which of the following is a core practice of the agile approach?

A 40-hour work week

Horizontal system

A basic system, such as an inventory or payroll package that is commonly used by a variety of companies

Help desk

A centralized resource staffed by IT professionals that provides users with the support they need to to their jobs Three main objectives: To show people how to use systems resources more effectively To provide answers to technical or operational questions To make users more productive by teaching them how to meet their own information needs

Pareto Chart

A chart drawn as vertical bar graph, in which the bars represent various causes of a problem, arranged in descending order, so the team can focus on the most important causes

A set of classes involved in a use case

A collaboration consists of ...........

Groupware

A collaborative software, designed to help people involved in a common task to achieve their goals.

Relationships

A concept map is essentially a node-and-arc representation, where the nodes represent the individual requirements and the arcs represents the ........... among the requirements

Certification

A credential an individual earns by demonstrating a certain level of knowledge and skill on a standardized test

repository

A database that serves as a central storage location for all information about a system being developed

Scalable

A design that can expand to meet new business requirements and volumes

Mission statement

A document or statement that describes the company for its stakeholders and briefly states the company's overall purpose, products, services, and values

Request For Proposal

A document provided to vendors that asks them to propose hardware and system software that will meet the requirements of a new system.

Request for proposal (RFP)

A document provided to vendors that asks them to propose hardware and system software that will meet the requirements of a new system.

System Requet

A document that describes the reasons for and the value added from building a new system contains: 1.Project Sponsor 2.Business Need 3.Business requirements 4.Business value 5.Special issues

What-if

A feature of business support systems that allows analysis to define and account for a wide variety of issues (including issues not completely defined)

system flowchart

A flowchart that shows the flow of input data to processing and finally to output, or distribution of information.

Systems request

A formal request to the IT department that describes problems or desired changes in an information system or business process

Systems request

A formal request to the IT department that describes problems or desired changes in an information system or business process Might propose enhancements for an existing system, the correction of problems, or the development of an entirely new system

Use Case

A formal way of representing the way a business system interacts with its environment. A high-level overview of the business processes in a business information system.

Whats a methodology and categories of it

A formalized approach to implementing the SDLC -Process oriented -Data Centered -Object-oriented (Balance between process and data) -Structured -Rapid Action Development (RAD) -Agile Development

System Development Life Cycle SDLC

A framework that identifies all the activities required to research, build, deploy, and often maintain an information system.

Graphical User Interface (GUI)

A huge improvement because it used icons, graphical objects and pointing devices.

User Sciences & Experience Research (USER)

A lab that focuses on improving ease of use and exploring new ways of using computers.

Case for action

A part of the preliminary investigation report to management that summarizes project requests and makes specific recommendations

Systems analyst

A person who plans, analyzes, and implements information systems

project

A planned undertaking that has a beginning and an end and produces some end result.

Deliverable

A polished, deliverable product, suitable for its intended use

End product

A polished, deliverable product, suitable for its intended use

fishbone diagram

A popular technique for investigating causes and effects

reverse engineering

A process that lets the analyst examine an existing application and break it down into a series of diagrams, structure charts, and, in some cases, source code.

Modeling

A process that produces a graphical representation of a concept or process that systems developers can analyze, test, and modify

Business Process Modeling

A process used to represent company operations and information needs

Encryption

A process where data is coded (converted into unreadable characters) so that only those with the required authorization can access the data (usually via decoding software)

procedural programming language

A programming language that requires a programmer to create code statements for each processing step.

False

A requirement is a statement of what the system must do and how it will be implemented

Path through a use case

A scenario is the same as a(n)

Information Systen

A set of interrelated components that collect, process, store, and provide as output the information needed to complete business tasks.

System

A set of related components that produces specific results.

System

A set of related components that produces specific results

System

A set of related components that produces specific results.

Questionnaires

A set of written questions used to obtain information from individuals, typically a low response rate. Less than 50% for paper and 30% for web.

Storyboard

A sketch that shows the general screen layout and design. Can be created with software or even drawn freehand.

Project scope

A specific determination of a project's boundaries or extent

Systems development methodology

A standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems

application life cycle management (ALM)

A start-to-finish approach to planning, designing, developing, deploying, managing, and maintaining an information system, using specialized software tools

SAD

A step-by-step process for developing high-quality information systems.

Object

A structure that encapsulates (or packages) attributes and methods that operate on those attributes. It is an abstraction of a real-world thing in which data and processes are placed together to model the structure and behavior of the real-world object

Vertical system

A system designed to meet the unique requirements of a specific business or industry, such as a Web-based retailer or video rental chain

product life cycle management (PLM)

A system that integrates all aspects of a product, its data, and its users across the SDLC in a large enterprise setting.

Enterprise resource planning (ERP) systems

A system that integrates individual traditional business functions into a series of modules so that a single transaction occurs seamlessly within a single information system rather than several separate systems

Enterprise Resource Planning (ERP) Systems

A system that integrates individual traditional business functions into a series of modules so that a single transaction occurs seamlessly within a single information system rather than several separate systems.

Operational feasibility

A system that will be used effectively after it has developed

object-oriented analysis and design (OOAD)

A technique used to create objects called actors, which represent the human users who will interact with the system.

Class

A term used in object-oriented modeling to indicate a collection of similar objects

fourth-generation environment

A term used to describe an efficient software development environment that is created through the use of powerful CASE tools, application generators, report generators, screen generators, and fourth-generation languages (4GLs) during prototyping.

Application generator

A tool that supports the rapid development of computer programs by translating a logical model directly into code. Also called a code generator.

Empowerment

A trend that places more responsibility and accountability throughout all levels of an organization

Waterfall model

A type of graph that depicts the result of each SDLC phase flowing down into the next phase

computer-aided software engineering (CASE) tools

A type of software development tool that helps provide some automation and assistance in program design, coding, and testing. Software package that evaluates hardware and software alternatives according to requirements given by the systems analyst. Also called automated design tools.

True

A use case that describes functionality that is complex and risky would be given a high importance level

Contract

A(n) ........ formalizes the interactions between a client and server object

Overview

A(n) ......... use case is typically created early in the process of understanding the system requirements as a way of documenting basic information about the use case

Use Case

A(n) ........... is a formal way of representing how a business system interacts with its environment

True

Agile development methodology aims at eliminating the modeling and documentation overhead in IS projects, while emphasizing simple, iterative application development

Adaptive Methods

Agile methods Method of information systems development that typically uses a spiral development model, which builds on a series of iterations

Process logic may be represented as:

All of the above (structured english, a decision table, a decision tree)

conversion

Also known as systems implementation; four direct approaches are: direct, parallel, pilot, and phased.

Attribute

An ....... of an analysis represents a piece of information that is relevant to the description of the class

IBM

An I.T. company that has been successful for over 100 years.

Network administration

An IT function that includes hardware and software maintenance, support, and security In addition to controlling user access, network administrators are also responsible for installation, configuration, management, monitoring, and maintenance of network applications

Agile Development

An Information System development process that emphasizes flexibility and rapid response to anticipate new changing requirements during development

Iterative

An adaptive method of development that typically uses a spiral development model, which builds on a series of iterations

False

An analyst that focuses on the technical issues of the organization (hardware, software, databases, and networks) is commonly called a change management analyst.

Process-centered

An analytic approach that describes processes that transform data into useful information

Service-Oriented Architecture (SOA)

An approach to systems development based on building complete systems through assembling software components, each of which model generic business functions

Fuzzy logic

An approach used in knowledge management systems that allows logical inferences to be drawn from imprecise relationships

Systems evaluation

An assessment conducted during the systems implementation phase to determine whether the system operates properly and if costs and benefits are within expectations

Prototype

An early, rapidly constructed working version of a proposed information system

False

An essential use case describes the specific set of steps to be followed.

Facebook Zero

An example of an application that took advantage of the constraint of limited multimedia but the affordance of Always on data connection

screen generator

An interactive tool that helps you design a custom interface, create screen forms, and handle data entry format and procedures. Also called a form painter.

System

An interrelated set of components which are viewed as a whole

Message

An object-oriented command that tells an object to perform a certain method

Rational Unified Process (RUP)

An object-oriented systems development methodology. This methodology establishes four phases of development: inception, elaboration, construction, and transition. Each phase is organized into a number of separate iterations

Event

An occurrence which takes place at a specific time and triggers a predetermined response from a system

eXtreme Programming

Another Agile Development involving short, incremental development cycles, automated test, two-person programming teams and lots of coding, testing, listening, and designing

Stakeholder

Anyone who is affected by the company's performance, such as customers, suppliers, stockholders, and members of the community

Technology Analysis

Apply new technologies to business processes and identify benefits

direct approach

Approach for systems implementation whereby the old system is simply abandoned for the new system.

Scope Management

Avoid scope greed as a result of new requests from the client for new features

Business-to-Consumer

B2C A commercial exchange (e.g. products or services) between businesses and consumers conducted over the Internet

Business Process Model

BPM A graphical representation of one or more business processes

Business Process Modeling Notation

BPMN A standard set of shapes and symbols used to represent events, processes, and workflows in computer-based modeling tools

Business Process Reegineering

BPR An attempt by companies to simplify operations or reduce costs

Business Support Systems

BSS Provide job-related information support to users at all levels of a company

Systems planning phase

Begins with a request to the IT department that describes problems or desired changes in an information system or a business process

Intangible benefits

Benefits that are difficult to measure in dollars

Tangible benefits

Benefits that can be measured in dollars Result from a decrease in expenses, an increase in revenues, or both

Which of these is not an advantage of prototyping

Buffers users against computer malfunctioning

Which of these is not a guideline for developing a prototype

Build the system slowly and carefully

System Acquisition Strategies

Build, Buy or Outsource

prototyping

Building a model or prototype that can be modified before the actual system is installed.

Acquisition Strategy Influences

Business Need, Experience, Skills, Project Management & Time

Business Rules

Business logic Determinate of how a system handles data and produces useful information Reflects the operational requirements of the business

Mobile Commerce

Buying and selling of goods and services through wireless handheld devices such as cellular telephone and personal digital assistants (PDAs).

eCommerce

Buying and selling of goods and services, or the transmitting of funds or data, over an electronic network, primarily the internet.

Computer-Aided Systems Engineering

CASE Computer-aided software engineering A technique that uses powerful programs called CASE tools to provide an overall framework for systems development and support a wide variety of design methodologies, including structured analysis and object-oriented analysis

Computer-Aided Software Engineering

CASE Computer-aided systems engineering A technique that uses powerful programs called CASE tools to provide an overall framework for systems development and support a wide variety of design methodologies, including structured analysis and object-oriented analysis

___________ software, such as microsoft product or Peoplesoft may be used for prototyping?

COTS

Class

CRC cards are used to document the responsibilities and collaborations of a(n) ..........

Customer relationship management

CRM Systems that integrate all customer-related events and transactions including marketing, sales, and customer service activities

Tangible Business Value

Can be quantified and measured directly. ex) 2% reduction in operating costs

SWOT Analysis

Can focus on a specific product or project, an operating division, the entire company, or the mission statement itself.

CPO

Chief procurement officer

What are the advantages of the waterfall method?

Clear deadlines: The static nature and predictable workflow make it easy to estimate costs, create timelines and stick to deadlines - Each phase has a clear start point and a requirement review gate at the end, so the team is forced to complete all tasks before the project can proceed - Requires documentation and a clear paper trail for each phase of development. - Predictable timelines and well-documented projects make it easy to give status updates

Client-Server architecture

Client handles presentation logic and server handles data access logic and data storage. Application logic is either on server or split between server and client.

Three types of computing architecture

Client, Server, Client-Server

Which of the following can be used to communicate ideas that would otherwise remain fuzzy or unshaped?

Coding

Information

Collection of facts organized in such a way that they have additional value beyond the value of the facts themselves.

Information Technology

Combination of hardware and software products and services that companies use to manage, access, communicate, and share information

Information Technology

Combination of hardware and software products and services that companies use to manage, access, communicate, and share information.

Decision Support System (DSS)

Combines databases, mathematical or graphical models, and interactive user interfaces or dialogues allowing users to manipulate data and models.

Supply Chain Management (SCM)

Companies who provide materials, services and functions. The management of the flow of goods and services, involves the movement and storage of raw materials, of work-in-process inventory, and of finished goods from point of origin to point of consumption.

Enterprise Applications

Company-wide applications, including order processing systems, payroll systems, and company communications networks

systems audit

Compares the performance of a new system to the original design specifications to determine if the new procedures are actually improving productivity.

economic feasibility

Comparing the costs of a new system to the benefits it promises.

What is the most important thing in the SDLC process

Completing the user requirements.

Systems review committee

Computer Resources Committee A group of key managers and users responsible for evaluating systems requests

Application Software

Computer software designed to support organizational functions or processes

CASE

Computer-Aided Systems Engineering

Functional and nonfunctional requirements

Concept maps allow the relationships among the .............. to be explicitly represented

What are the typical stages in the waterfall method?

Conception - First phase of the system development life cycle starts with an idea. Ends with a rough estimate of the scope of the project. Initiation - Second phase involves hiring the team and expanding upon project scope with objectives, purpose and deliverables Analysis - A feasibility analysis is conducted by looking at the scope and gathering all requirements into a requirement specification document. Design - Mockups, wireframes and storyboards. Designers put a face to the project. Requirements are reviewed and evaluated. Team goals are set and a plan of action is developed. Coding - Developers start building the actual app based on flowcharts, mockups and designs created in the previous phase. Testing - completed product undergoes testing. This stage may involve extra coding to resolve any issues. Also user acceptance testing. Production - Product is launched into market Maintenance - Users will inevitably run into bugs. Development team need to stand ready to resolve any issues.

framework

Conceptual structure that organizes and documents system development tasks.

Components of a Decision Table

Condition stub, action stub, condition entry, action entry.

Build

Custom in-house development

Events - Motel

Customer makes reservation Customer provides payer details Customer checks in Customer checks out Motel generates bill Customer pays bill Manager generates reports

Electronic Data Interchange (EDI)

Data sharing arrangement between computer- to-computer replacing snail mail, fax and email.

Open Rectangle

Data store

Information

Data that has been changed into a useful form of output

Business Profile

Definition of a company's overall functions, processes, organization, products, services, customers, suppliers, competitors,constraints, and future direction

Process

Describe the tasks and business functions that users, managers, and IT staff members perform to achieve specific results

Product-oriented

Describes IT companies that manufacture computers, routers, or the microchips

Interface

Describes an interaction or connection between a system and its environment, or between subsystems.

Ergonomics

Describes how people work, learn, and interact with computers. Study of people's efficiency in their working environment.

User Interface (UI)

Describes how users interact with a computer system. Consists of all the hardware, software, screens, menus, functions, output, and features that affect two-way communications between the user and the computer.

Human-Computer Interaction (HCI)

Describes the relationship between computers and people who use them.

Requirements model

Description of business functions that an information system must support

Data Model

Description of data structures and design

Business Process

Description of specific events, tasks, and desired results

Process model

Description of system logic and processes that programmers use to develop necessary code modules

Web Support

Design and construct Web pages, monitor traffic, manage hardware and software, and link Web-based applications to the company's information systems.

Web support

Design and construction of Web pages, monitoring traffic, managing hardware and software, and linking Web-based applications to the company's existing information systems

In order to build decision tables, what does the analyst not need to do?

Determine the minimum size of the table

Conversion Styles

Direct or Parallel

User-selected Help

Displays information when the user requests it.

Electronic data interchange

EDI A process that involves the computer-to-computer transfer of data between companies

Electronic product code

EPC Technology that uses RFID tags to identify and monitor the movement of each individual product, from the factory floor to the retail checkout counter

Electronic proof of delivery

EPOD Use of RFID tags on each crate, case or shipping unit to create a digital shipping list

Enterprise resource planning

ERP A process that establishes an enterprise-wide strategy for IT resources Defines a specific architecture,including standards for data, processing, network, and user interface design

User Experience

Easy to learn, shortcuts for experts, training

False

Economic feasibility focuses on whether the system can be built by examining the risks associated with the users' and analysts' familiarity with the application, familiarity with the technology, and project size

In describing the value format of a data element, the symbol X(8) represents:

Eight alphanumeric characters

Components

Either an irreducible part or an aggregate of parts of the system (called a sub-system)

In describing data structure, what do brackets [] represent?

Either/or alternative

E-commerce

Electronic commerce I-commerce Transactions (e.g. buying and selling of goods and information) that occur on the Internet

Activity Elimination

Eliminate each activity in a business process in a "force-fit" exercise

End users

Employees, customers, vendors, and others who interact with an information system

Users

End users Employees, customers, vendors, and others who interact with an information system

Project Manager

Ensures that the project is completed on time and within budget.

Project Manager

Ensures the project is completed on time and within budget

ERP

Enterprise Resource Planning. implementation broke silos

Preliminary investigation

Feasibility Study An initial investigation to clearly identify the nature and scope of the business opportunity or problem

Ishikawa diagram

Fishbone Diagram An analysis tool that represents the possible causes of a problem as a graphical outline

Root Cause Analysis

Focus on the cause of a problem not its solution, try to determine the causes.

Requirements Analyst

Focuses on eliciting the requirements from the stakeholders

Aesthetics

Focuses on how an interface can be made attractive and easy to use.

Change Management Analyst

Focuses on people and management issues

Business Analyst

Focuses on the business issues

Business Analyst

Focuses on the business issues surrounding the sytem

Change Management Analyst

Focuses on the people and management issues

Infrastructure Analyst

Focuses on the technical issues

Infrastructure Analyst

Focuses on the ways the system will interact with the current infrastructure

What are the two ways of drawing a DFD?

Formal (normally) - Many DFD's - Conform to standard practice - Necessary for teams (especially larger teams) Informal - One (large) DFD - Non-standard - Typically, you are the sole DFD writer and reader (small team of 2 or 3)

Aesthetics

Functional & Inviting, White space, no more than 2 font sizes

FURPS

Functional, Usability, Reliability, Performance, and Security Requirements. - a widely used framework

Which of the following is not contained in the data repository?

Generated computer code

Obscelesence

Getting rid of system when no longer needed

Business Process Model (BPM )

Graphically displays one or more business processes.

Technical support

Group that supports the wide variety of IT systems and users Includes six main functions: Application development Systems support User support Database administration Network administration Web support

Aggregation

Has a

Brick-and-mortar firms

Have physical stores where customers can see and touch the products.

Elicitation Strategy

How to extract the info from the client (interviews, observation, sometimes JAD sessions)

Network Administration

Includes hardware and software maintenance, support, and security.

Subject, Verb, Direct Object, Preposition, Indirect Object

Individual steps in a use case should be written in the form ........

A patched up prototype is likely to be

Inefficient

In-house applications

Information systems developed for a company, by itself

Enterprise computing

Information systems that support company-wide data management requirements, such as airline reservation, or credit card billing systems

Enterprise Computing

Information systems that support company-wide operations and data management requirements.

4 Major Types of relatioships

Inheritance Aggregation -Collection -Composition Associations

True

Inheritance is supported in use cases through the generalization relationship

Project Plan

Initiation - opening Planning Execution - analysis/design Control - throughout SDLC Enclosure - decide to stop or not

event-driven programming language

Instead of writing a series of sequential instructions, a programmer defines the actions that the program must perform when certain events occur. Also called nonprocedural programming language.

rapid applications development (RAD)

Involves the use of powerful development software and specialized teams as an alternative to the systems development life cycle approach. Time for development is shorter and quality of the completed systems development is better, although cost is greater.

Inheritance

Is a

Functional Decomposition Diagram

Is a graphical representation of business functions that starts with major functions, and then breaks them down into several levels of detail.

User Interface

Is a vital element in the systems design phase.

User Interface Design

Is the first task in the systems design phase.

Hardware

Is the physical layer of the information system.

Strategic Planning

Is the process of identifying long-term organizational goals, strategies, and resources.

Fishbone diagram

Ishikawa Diagram An analysis tool that represents the possible causes of a problem as a graphical outline

Physical DFD

It depicts how the current system operates and how a system will be implemented

Decision Tables

It is a matrix containing row or columns for defining a problem and the actions.

Structured Analysis

It is a systematic approach, which uses graphical tools that analyze and refine the objectives of an existing system and develop a new system specification which can be easily understandable by user.

Data Flow Diagram

It is a technique develop by Larry Constantine to express the requirements of system in a graphical form.

Data Flow Diagram

It is an initial stage of design phase that functionally divides the requirement specification down to the lowest level of detail.

False

It is easier to ask an interviewee what is used to perform a task than it is to show the interviewee a form an ask what information on the form is used.

Physical DFD

It is implementation dependent. It shows which functions are performed.

Logical DFD

It is implementation independent. It focuses only on the flow of data between processes

Action Stub

It is in the lower left quadrant which outlines all the action to be carried out to meet such condition

Condition Stub

It is in the upper left quadrant which lists all the condition to be checked

Condition Entry

It is in upper right quadrant which provides answers to questions asked in condition stub quadrant.

Project Effort Estimation

It is the process of assigning projected values for time and effort, involves trade-offs between functionality, time and cost.

Pseudocode

It may specify physical programming logic without actual coding during and after the physical design.

Logical DFD

It shows how business operates; now how the system can be implemented

Data Flow Diagram

It shows the flow of data between various functions of system and specifies how the current systems is implemented

In describing data structure, braces { } are used to indicate:

Iteration

Real

Jim has documented a use case that describes the functionality of a system as "To compute gross pay, multiply the hours worked that are recorded on the time card from the time clock by the hourly rate that is recorded in the employee master file from the MS SQL server database." This is an example of a(n) .......... use case

Schedule feasibilty

Knowledge that a project can be implemented in an acceptable time frame

Agile/Adaptive Methods

Latest trend in software development. Team-based effort broken down into cycles.

False

Lauren, a systems analyst, has excellent interpersonal skills. To take advantage of her skills, the functional lead of the project should assign her to program in Java or C++

Principles of User Interface Design

Layout, Content Awareness, Aesthetics, User Experience, Consistency, Minimize Effort

What are Nielsen's 101?

Learnability - how easy for 1st time users to perform a task Efficiency - Once learned, how quickly can users perform tasks Memorability - how easy to re-establish proficiency (after time gap) Errors - How many errors does a user make, how severe, how can they recover Satisfaction - how pleasant it is to use the design

Strategic plans

Long-range plans that define the corporate mission and goals Typically defined by top management, with input from all levels

Running a section of code over and over again until some conditions is met is an example of a:

Loop

Management information systems

MIS 16

Microsoft Solutions Framework

MSF A Microsoft approach to systems development Objective: To define and analyze business requirements and provide IT solutions

False

Michelle has been assigned the task of completing the project in a timely manner and within budget. Her project team role is infrastructure analysts

Interface Design Prototyping

Mockup

Requirements modeling

Modeling that is used in the systems planning phase of SDLC Involves fact-finding to describe the current system and identify the requirements for the new system, using fact-finding techniques such as interviews, surveys, observation, and sampling

Which is not one of three main advantages of a decision tree over a decision table?

More correct as a communication tool

Object-Oriented Analysis

More recent method for developing systems. Objects represent actual people, things, or events.

Object-oriented analysis

O-O analysis System description based on identification of things called objects [which represent real people, places, events, or transactions

Rectangles

Object nodes model these objects in an activity diagram. Object nodes are portrayed in an activity diagram as ..........

Where are objects and classes in a sequence diagram

Object on the left and classes along the top

Scope Creep

Occurs when new requirements are added to the project after the original project scope was defined and "frozen"

Legacy systems

Older systems that are typically less technologically advanced than currently available systems

the fraud triangle

Opportunity, Rationalization, pressure

Actors

Participating - those that are involved within the event but do not start the action Initiating/Primary - those that trigger the event

Which kind of prototyping is most similar to what engineers call "bread boarding"?

Patched up prototype

Steps in Project Management

Project Identification, System Request, Feasibility Analysis, Project Selection

5 Elements of System Request

Project Sponsor: Primary point of contact for the project Business Need: The reason prompting the project Business Requirements: What will the system do Business Value: How will the business benefit from the project Special Issues: Anything else that should be considered

Nondiscretionary project

Project where no choice exists

Project Selection

Projects are approved, declined or delayed based on value added vs. risks.

Discretionary projects

Projects where management has a choice in implementing them

discretionary projects

Projects where management has a choice in implementing them.

nondiscretionary projects

Projects where no choice exists

Computer-Aided Systems Engineering (CASE) Tools

Provide an overall framework for systems development and support a wide variety of design methodologies.

Business Support System

Provide job-related information support to users at all levels of a company.

Middle Managers and Knowledge Workers

Provides direction, necessary resources, and performance feedback to supervisors and team leaders and needs more detailed information than top managers.

System requirements document

Software requirements specification Contains the requirements for the new system, describes the alternatives that were considered, and makes a specific recommendation to management

System software

Software that controls the computer and includes the operating system, device drivers that communicate with hardware, and utilities

Method

Specific tasks that an object must perform What and how an object does something

Systems analysis phase

Specifications of the present system

Systems design phase

Specifications of the proposed system

Problem Definition (Problem Statement)

Step 1

Total cost of ownership

TCO A number used in assessing costs, which includes ongoing support and maintenance costs, as well as acquisition costs

Transaction processing systems

TP Systems Operating systems used to process day-to-day recurring business transactions, such as customer billing

How do you shorten project time?

Take away resources from non-critical paths during slack time and apply them to the critical path

Quality Assurance

Team that reviews and tests all applications and systems changes to verify specifications and software quality standards.

Components of Project Feasibility

Technical Feasibility, Economic Feasibility, Organizational Feasibility (Will they use it?)

Which of the following is not one of the four values of agile modeling?

Technical Skill

System design specification

Technical design specification Detailed design specification A document that presents the complete design for the new information system, along with detailed costs, staffing, and scheduling for completing the next SDLC phase, systems implementation

Input Masks

Templates or patterns that make it easier for users to enter data.

Service-oriented

Term used to describe a company that primarily offers information or services, or sells goods produced by others

Technical feasibility

Term used to describe a project or request for an organization that has the resources to develop or purchase, install, and operate the system

Economic feasibility

Term used to describe a situation in which the projected benefits of a proposed system outweigh the estimated costs involved in acquiring, installing, and operating it

cycle time

The average successive time between completions of successive units

flow time

The average time that it takes a unit to move through an entire process or system. Includes time being worked on ans wel as time spent waiting in queue

Implementation

The fourth phase of the SDLC in which the information system is coded, tested, installed, and supported in the organization

Productivity Paradox

The observation that productivity increases at a rate that is lower than expected when new technologies are introduced

False

The organizational management of a business is involved in hands-on activities related to the project

Systems analyst

The organizational role most responsible for the analysis and design of information systems

throughput rate (flow rate)

The output rate that the process is expected to produce over a period of time

Logical design

The part of the design phase of the SDLC in which all functional features of the system chosen for development are described independently of any computer platform

Project Sponsor

The person who identifies the business values that can be gained from using information technology is called the .........

Hardware

The physical layer of the information system, to include computers, networks, communications equipment, and other technology-based infrastructure

Outsourcing

The practice of turning over responsibility for some or all of an organization's information systems applications and operations to an outside firm

Outsourcing

The practice of turning over responsibility fro some to all of an organization's information systems applications and operations to an outside firm.

1. A long time elapses between completion of the system proposal and the delivery of the system 2. If the team misses important requirements, expensive post-implementation programming may be needed 3. The design must be completely specified on paper before programming begins

The principal disadvantages(s) with the waterfall development methodology is (are)..........

Project creep

The process by which projects with very general scope definitions expand gradually, without specific authorization

What is elicitation?

The process of collecting requirements of a system from multiple sources (users, customers and other stakeholders)

Application Development

The process of constructing the programs and code modules that are the building blocks of an information system

System conversion

The process of decommissioning the current system and installing a new system into the organization

Systems Analysis and Design

The process of developing and maintaining an information system

Systems analysis and design

The process of developing information systems that effectively use hardware, software, data, processes, and people to support he company's business objectives

Strategic planning

The process of identifying long-term organizational goals, strategies, and resources

Project management

The process of planning, scheduling, monitoring, controlling, and reporting upon the development of an information system

Analysis phase of the Systems Development Life Cycle (SDLC)

The process of understanding how an information system can support business needs, design the system, build it, and deliver it to users is the......

Inheritance

The property that occurs when entity types or object classes are arranged in a hierarchy and each entity type or object class assumes the attributes and methods of its ancestors; that is, those higher up in the hierarchy. The property allows new but related classes to be derived from existing classes

Cloud computing

The provision of computing resources, including applications, over the Internet, so customers do not have to invest in the computing infrastructure needed to run and maintain the resources

Reuse

The use of previously written software resources, especially objects and components, in new applications

Control

The user has the right to be in control of the system and be able to get the system to respond to a request for attention.

Dependencies

The user has the right to be informed clearly all the systems requirements for successfully using software or hardware.

Assistance

The user has the right to communicate with the technology provider and receive a thoughtful and helpful response when raising concerns.

Instruction

The user has the right to easy-to-use instructions (user guides, online or contextual help, and error messages) for understanding and utilizing a system to achieve desired goals and recover efficiently and gracefully from problem situations.

Usability

The user should be the master of software and hardware technology, not vice versa. Products should be natural and intuitive to use.

Web 2.0

This describes a second generation of the web that will enable people to collaborate, interact, and share information much more effectively.

Physical Design

This is a plan for the actual implementation of the system.

Managed Hosting

This is another name for internet business services (IBS).

Triple Constraint

Time, Cost and Scope

Content Awareness

Titles, Menus, Clear information

True

To better understand the As-Is system the project team members can perform document analysis on existing forms, reports, and business process models

What is a data dictionary?

We need a breakdown of what is in a data flow and data store. It's similar to a database and data store, it stores records, fields, values, etc... We add a Data Dictionary for each data flow and each data store.

When should you use a decision tree.

When the sequence of conditions and actions is critical or when not every condition is relevant to every action

False

When you begin an interview the first goal is to establish control and let the interviewee know that you have a mastery of the subject

o-I---<

Which of the following diagramming symbols represents an actor in a use case diagram?

Operations

Which of the following will be converted to methods in later phases of the SDLC?

CRC cards

a brainstorming technique for designing interactions in use cases by assigning responsibilities and collaborations for classes

Use cases

a case or situation where the system is used. (verb: Look up supplier)

class

a category or classification of a set of objects or things

domain model class diagram

a class diagram that only includes classes from the problem domain

concrete class

a class that allows individual objects or instances to exist

concrete class

a class that can be instantiated (objects can be created of this type)

abstract class

a class that can never be instantiated (no objects can be created of this type)

free-standing Internet application

a client/server application that is self-contained and doesn't require the use of a Web browser

three-layer architecture

a client/server architecture that divides an application into view layer, business logic layer, and data layer

Virtual Private Networks (VPNs)

a closed network with security and closed access built on top of a public network, such as the Internet

encryption algorithm

a complex mathematical transformation that encrypts or decrypts binary data

device-top application

a computer application that is built to execute on a local computer (such as a desktop) without requiring a client/server connection

client-server architecture

a computer network configuration with user's computers and central computers that provide common services

local area network (LAN)

a computer network in which the cabling and hardware are confined to a single location

computer application (app)

a computer software program that executes on a computing device to carry out a specific function or set of related functions

Computer application

a computer software program that executes on a computing device to carry out a specific function or set of related functions.

state

a condition during an object's life when it satisfies some criterion, performs some action, or waits for an event

precondition

a condition that must be true before a use case begins

referential integrity

a consistent state among foreign key and primary key values

referential integrity constraint

a constraint, stored in the schema, that the DBMS uses to automatically enforce referential integrity

value limit control

a control that checks numeric data input to ensure that the value is reasonable

completeness control

a control that ensures that all required data values describing an object or transaction are present

data validation control

a control that ensures that numeric fields that contain codes or identifiers are correct

output control

a control that ensures that output arrives at the proper destination and is accurate, current, and complete

complex update control

a control that prevents errors that can occur when multiple programs try to update the same data at the same time or when recording a single transaction requires multiple related database updates

input control

a control that prevents invalid or erroneous data from entering the system

object responsibility

a design principle in which objects are responsible for carrying out system processing

navigation visibility

a design principle in which one object has a reference to another object and thus can interact with it

Network Diagram

a diagram that depicts project tasks and interrelationship

Project Scope Statement

a document prepared that describes what the project will deliver and outlines the high level of work

System Vision Document

a document to help define the scope of a new system

public key encryption

a form of asymmetric key encryption that uses a public key for encryption and a private key for decryption

test case

a formal description of a starting state, one or more events to which the software must respond, and the expected response or ending state

normalization

a formal technique for evaluating and improving the quality of a relational database schema

structure chart

a graphical diagram showing the hierarchical organization of modules

radio buttons

a group of choices from which the user selects only one; the system then automatically turns off all other buttons in the group

agile development

a guiding philosophy and set of guidelines for developing information systems in an unknown, rapidly changing environment

agile modeling (AM)

a guiding philosophy in which only models that are necessary, with a valid need and at the right level of detail, are created

unauthorized user

a person who isn't allowed access to any part or functions of the system

DFD

a picture of the movement of data between external entities and the process and data stores within the system

project

a planned undertaking that has a beginning and an end, and that produces some definite result

product backlog

a prioritized list of user requirements used to choose work to be done in a Scrum project

Technical feasibility

a process of assessing the development organizations ability to construct a proposed system

structured programming

a programming approach where each module has one start point and one end point and uses sequence, decision, and repetition constructs only

dependency relationship

a relationship between packages, classes, or use cases in which a change in the independent item requires a change in the dependent item

activation lifeline

a representation of the period during which a method of an object is alive and executing

FURPS

a requirements classification framework (acronym stands for functionality, usability, reliability, performance, and security)

path

a sequential set of connected states and transitions

test data

a set of starting states and events used to test a module, group of modules, or entire system

integrated development environments (IDEs)

a set of tools that work together to provide a comprehensive development and programming environment for software developers

serial flow process

a single path for all stages of production

tool

a software application that assists developers in creating models or other components required for a project

Web mini-app

a software application that provides a complete set of functions but that must be executed within the confines of another application

plug-ins

a software component that adds specific capabilities to a larger software application

software as a service (SAAS)

a software delivery model similar to a utility, in which the application and its associated data are accessed via the Internet without locally installed programs

Secure Sockets Layer (SSL)

a standard set of methods and protocols that address authentication, authorization, privacy, and integrity

composite state

a state containing other states and transitions (that is, a path)

data flow diagram (DFD)

a structured analysis model showing inputs, processes, storage, and outputs of a system

Feasibility

a study that determines if the proposed info system makes sense for the organization from economic and operational standpoint

user acceptance test

a system test performed to determine whether the system fulfills user requirements

build and smoke test

a system test that is performed daily or several times a week

enterprise-level system

a system that has shared resources among multiple people or groups in an organization

noun technique

a technique to identify problem domain objects by finding and classifying the nouns in a dialog or description setting

brainstorming technique

a technique to identify problem domain objects in which developers work with users in an open group

event decomposition technique

a technique to identify use cases by determining the external business events to which the system must respond

user goal technique

a technique to identify use cases by determining what specific goals or objectives must be completed by a user

relationship

a term that describes a naturally occurring association between specific things, sometimes called an association

chaordic

a term used to describe adaptive projects that are chaotic and ordered

association

a term, in UML, that describes a naturally occurring relationship between specific things, sometimes called a relationship

theme

a type of add-on to an application that allows the look and feel, such as colors and layout, to be changed

toolbar

a type of add-on usually comprised of iconic menu items that access the capabilities of the application or plug-ins in a userfriendly fashion

generalization/specialization relationship

a type of hierarchical relationship in which subordinate classes are subsets of objects of the superior classes; an inheritance hierarchy

component diagram

a type of implementation diagram that shows the overall system architecture and the logical components within it

widget

a type of plug-in that focuses on enhancing the user interface with additional capability

aggregation

a type of whole-part relationship in which the component parts also exist as individual objects apart from the aggregate

composition

a type of whole-part relationship in which the component parts cannot exist as individual objects apart from the total composition

stereotype

a way of categorizing a model element by its characteristics, indicated by guillemets (<< >>)

certifying authority

a widely accepted issuer of digital certificates

swimlane heading

activity diagram column containing all activities for a single agent or organizational unit

spiral model

an adaptive SDLC approach that cycles over and over again through development activities until completion

n-ary association

an association between n distinct types of things

unary association

an association between two instances of the same type of thing

source code control system (SCCS)

an automated tool for tracking source code files and controlling changes to those files

Hypertext Transfer Protocol Secure (HTTPS)

an encrypted form of information transfer on the Internet that combines HTTP and TLS

digital certificate

an institution's name and public key (plus other information, such as address, Web site URL, and validity date of the certificate) encrypted and certified by a third party

database (DB)

an integrated collection of stored data that is centrally managed and controlled

performance test or stress test

an integration and usability test that determines whether a system or subsystem can meet time-based performance criteria

system test

an integration test of an entire system or independent subsystem

Sequenced data dictionary entries

become simple structured english statements

Invoice

bill for product

architectural design

broad design of the overall system structure; also called general design or conceptual design

BPR

business process re engineering, drove processes that brought new systems. databases were created.

physical requirements

characteristics of hardware such as size, weight, power consumption, and operating conditions

system controls

checks or safety procedures to protect the integrity of the system and the data

domain classes

classes that describe objects from the problem domain

oversight committee

clients and key managers who review the progress and direct the project

complex data type

combinations of or extensions to primitive data types that are supported by programming languages, operating systems, and DBMSs

why start a systems development project?

competitive advantage.

which of the following is not one of the four basic structures used to code

computation

implementation requirements

constraints such as required programming languages and tools, documentation method and level of detail, and a specific communication protocol for distributed components

steps for the iterative approach using prototypes

investigate, analyze, & define the problem. build the initial version or prototype of the system. put the prototype into operation. refine & modify the prototype.

Structured Analysis

is a development method that allows the analyst to understand the system and its activities in a logical way

Decision Trees

is a diagram that shows alternative actions and conditions within horizontal tree framework. It is a method for defining complex relationships by describing decisions and avoiding the problems in communication

opt frame

notation on a sequence diagram showing optional messages

loop frame

notation on a sequence diagram showing repeating messages

external outputs

reports or other outputs produced for use by people outside the organization

reliability requirements

requirements that describe system dependability

second normal form (2NF)

restriction that a table is in 1NF and that each non-key attribute is functionally dependent on the entire primary key

third normal form (3NF)

restriction that a table is in 2NF and that no non-key attribute is functionally dependent on any other non-key attribute

Balancing

the conservation of inputs and outputs to a DFD process when that process is decomposed to a lower level

Recurring costs

the cost resulting from the ongoing evolution

prototyping

the creation of a preliminary model or version of a major subsystem.

last mile

the final leg that delivers connectivity from the Internet network to the customer

In sequence diagrams how do you show timing

the first activities shown at the top of the diagram

Transmission Control Protocol/ Internet Protocol (TCP/IP)

the foundation protocol of the Internet; used to provide reliable delivery of messages between networked computers

primary key

the key chosen by a database designer to represent relationships among rows in different tables

use case realization

the process of elaborating the detailed design with interaction diagrams for a particular use case

object-oriented analysis (OOA)

the process of identifying and defining the use cases and the sets of objects (classes) in the new system

authentication

the process of identifying users who request access to sensitive resources

What is project manageement

the process of planning and controlling system development within a specified time at a minimum cost with the right functionality

hosting

the process of providing physical servers at a secure location and selling those services to other businesses that wish to deploy Web sites

When doing pair programming, which person(s) chooses a partner programmer?

the programmers

system capabilities

the required capabilities of a new system; part of a System Vision Document

detailed work schedule

the schedule that lists, organizes, and describes the dependencies of the detailed work tasks

application program interface (API)

the set of public methods that are available to the outside world

problem domain

the specific area (or domain) of the user's business need (or problem) that is within the scope of the new system

pseudostate

the starting point of a state machine diagram, indicated by a black dot

data type

the storage format and allowable content of a program variable, class attribute, or relational database attribute or column

payback period

the time period after which the dollar benefits have offset the dollar costs

process flowcharting

the use of a diagram to present the major elements of a process. Basic elements = tasks or operations, flows of materials or customers, decision points, and storage areas or queues.

production system

the version of the system used from day to day

lifeline or object lifeline

the vertical line under an object on a sequence diagram to show the passage of time for the object

3 tier architecture

top is client (GUI, Presentation layer middle is business logic (application) bottom is Information (Data)

communication diagrams

type of interaction diagram that emphasizes the objects that send and receive messages for a specific use case

sequence diagrams

type of interaction diagram that emphasizes the sequence of messages sent between objects for a specific use case

systems development lifecycle (SDLC)

understand the business problem or opportunity. develop an information system solution. implement the information system solution.

scenarios or use case instances

unique sets of internal activities within use cases

Which is structured English not based on?

unstructured logic

database synchronization

updating one database copy with changes made to other database copies

information is created when

we add context to data

visibility

when a control is visible so that users know it is available, the control providing immediate feedback to indicate that it is responding to the user

silo

when you focus so narrowly on the specific task that you lose sight of the big picture or the larger process.

vertical enrichment

worker is involved in planning, organizing, and inspecting work

horizontal enrichment

worker performs a greater number of variety of tasks

Three Major Trends

◦ Rapidly increasing globalization ◦ Technology integration for seamless information access ◦ Rapid growth of cloud-based computing and services

Work Plan

- How tasks are structured - Depends on methodology

What are the two types of elicitation?

- Traditional - Contemporary

Rule of Thumb

1 unit of work = 2 weeks of time

Moore's Law

Accurately predicted that computer processing power would double every 18 to 24 months

Agile Methods

Adaptive methods Systems development methods that attempt to develop a system incrementally, by building a series of prototypes and constantly adjusting them to user requirements

Present Value

Amount / (1 + interest rate)^n

Problem Analysis

Ask users to identify problems with current system, ask users how they would solve these problems. G

Transaction Processing System (TPS)

Automates the handling of data for business activities or transactions.

True

Benchmarking refers to studying how other organizations perform a business process so you can learn how your organization can do it better

Top-Down Approach

Breaking the bigger picture into smaller pieces/tasks

Analysis Phase

Breaking whole into parts to understand parts' nature, function, and interrelationships

the fraud diamond

Capability, Opportunity, Rationalization, pressure

Properties

Characteristics that objects inherit from their class or possess on their own

organization chart

Chart showing the levels of management and formal lines of authority in an organization.

grid chart

Chart that shows the relationship between input and output documents.

which of the following is included in a physical data structure?

Codes that identify the status of a master record

system

Collection of activities and elements designed to accomplish a goal.

System Proposal

Combines all materials created in planning and analysis

IS

Combines technology, people, and data to provide support for business functions.

True

Control flows in an activity diagram are shown using solid-lines with arrows while object flows are shown using dashed lines with arrows

False

Creating a work plan requires three steps: 1. Identify the tasks that need to be accomplished 2. Estimate the time that it will take to complete the tasks 3. Record the task completion time in a Gantt Chart

Object model

Description of objects, which combines data and processes

Duration Analysis

Determine the time required to complete each step in a business process. Compare to total time required for the entire process

Top Managers

Develop long-range strategic plans, which define the company's overall mission and goals.

Biometric device

Device that identifies a person by a retina scan or by mapping a facial pattern

data flow diagram

Diagram showing data or information flow within an information system.

Internet-dependent

Dot-com firm .com firm Company that bases its primary business on a commercial Web site, rather than using traditional business channels

Prototyping

Early working version of an information system.

Project Effort Estimation

Estimation involves trade-offs between functionality, time, and cost

Scrum estimation

Everyone in DT: - Has a deck of cards - Chooses their estimate - Reveals their card at same moment - If approx same, agree - If discrepancies, discuss and repeat until approx the same.

SWOT analysis

Examination of a company's Strengths, Weaknesses, Opportunities, and Threats

Feasibility study

Feasibility report

Preliminary investigation

Feasibility study An initial investigation to clearly identify the nature and scope of a business opportunity or problem

Natural Language

Feature that allows users to type commands or requests in normal English phrases.

preliminary investigation

First phase of the systems life cycle. It involves defining the problem, suggesting alternative systems, and preparing a short report.

Time Boxing

Fixed deadline, even if functionality needs to be reduced

Information center

IC Help desk Supports users by training them on application software User support specialists answer questions, troubleshoot problems, and serve as a clearinghouse for user problems and solutions

Information technology

IT A combination of hardware, software, and telecommunications systems that support business operations, improve productivity, and help managers make decisions

Event analysis

Identifies the events to which the system is expected to respond, names the inputs and outputs, and ID's those who interact with the system by providing inputs and receiving outputs

Decomposed into a set of use cases

If a use case becomes too complex, it should be .......

Sprint

In SCRUM, teams organize themselves in a symbiotic manner and set their own goals for each.........:

The high level functionality of the system

In order to approve a system request, the approval committee must know

True

In the UML, the Activity Diagram illustrates all the interactions between the system and its environment

False

In the UML, the Use Case Diagram illustrates all the interactions between the system and its environment

Business Information Systems

Integrated in one product and can be delivered by the same software package.

Interface Standards Design

Interface metaphor, interface templates, interface objects, interface actions, interface icons,

I-commerce

Internet commerce E-commerce Transactions (e.g. buying and selling of goods and information) that occur on the Internet

Systems

Interrelated (collaborative or cooperative) set of business procedures (or components) within a business unit (environment or domain), working together for one purpose (mission) around a agreed-upon set of guidelines (business rules)

Joint application development

JAD A popular systems development technique that uses a cross-matrixed task group of users, managers and IT professionals that work together to gather information, discuss business needs, and define the new system requirements

Just-in-time

JIT The exchange or delivery of information when and where it is needed

False

Joint Application Design (JAD) is always the better requirements-gathering technique than others. In practice, every project should only JAD

Inference Rules

Logical rules that identify data patterns and relationships.

Corrective maintenance

Making changes in a system to repair flaws in its design, coding or implementation

technical feasibility

Making sure hardware, software, and training will be available to facilitate the design of a new system.

operational feasibility

Making sure the design of a new system will be able to function within the existing framework of an organization.

MRP

Material Requirements Planning. subset of ERP

International Business Machine

Meaning of the acronym IBM.

Operational Feasibility

Means that a proposed system will be used effectively after it has been developed.

Progress Monitoring

Measuring progress: - In 'story points' - Usually ideal person-days or hours - Burndown charts - Burnup charts

top-down analysis model

Method used to identify top-level components of a system, then break these components down into smaller parts for analysis.

MCSD

Microsoft Certified Solutions Developer

Process specifications are sometimes called __________ , because they are a small portion of the total project specifications

Minispecs

CASE environment

More than just a set of CASE tools. A CASE environment includes any use of computer-based support in the software development process.

Systems Integration

Most large companies require systems that combine transaction processing, business support, knowledge management, and user productivity features.

Interviews

Most popular requirement gathering technique

object-oriented programming languages (OOPL)

Non-procedural programming languages that are especially valuable in implementing an object-oriented system design.

Context-sensitive Help

Offers assistance for the task in progress.

Unlike the decision tree used in management science, what doesn't the analyst's tree contain

Outcomes

Outsource

Outsource development to a third party

Unified Modeling Language (UML)

Overall, the consistent notation, integration among the diagramming techniques, and application of the diagrams across the entire development process makes...........a powerful and flexible tool set for analysts and developers

Supervisors and Team Leaders

Oversee operational employees and carry out day-to-day functions and needs decision support information, knowledge management systems, and user productivity systems.

Business Profiles

Overview of a company's mission, functions, organization, products, services, customers, suppliers, competitors, constraints, and future direction.

Calculating the number of people needed

Person-months/time wanted to complete by in months

Systems support and security phase

Phase during which the IT staff maintains, enhances, and protects the system

systems development

Phase four of the systems life cycle, consisting of developing software, acquiring hardware, and testing the new system.

systems maintenance

Phase six of the systems life cycle consisting of a systems audit and periodic evaluation.

systems design

Phase three of the systems life cycle, consisting of designing alternative systems, selecting the best system, and writing a systems design report.

Locations

Pilot, Phased or Simultaneous

What are the six stages of the Systems Development Lifecycle?

Planning - Defining problems, objects and the resources (such as personnel and costs). Studying ability of proposing alternative solutions. Analysis - What the user requirements are, what are their expectations Design - Good understanding of customers requirements, defines the architecture of the system Implementation and deployment - After complete understanding of the system and specifications - coding happens here, hardware is ready and system is ready to be deployed. Testing and Integration - Testing ensures customer satisfaction, can be performed by real users Maintenance - Making sure system won't go obsolete

Project Phases

Planning, Analysis, Design, Implementation

Manager

Planning, Organizing, Directing, Monitoring. Primary role is to increase the efficiency of the team, making the group more effective.

Break-Even Point

Point in time which the costs of the project equals the value it has delivered (Yearly NPV - Cumulative NPV)/Yearly NPV

Network model

Portrayal of the design and protocols of telecommunications links

CASE Tools

Powerful software used to in computer-aided systems engineering to help systems analysts develop and maintain information systems

Predictive

Predictive approach Structured analysis based on a detailed plan, similar to a blueprint for constructing a building

Feasibility study

Preliminary investigation An initial invetsigation to clearly identify the nature and scope of a business opportunity or problem

Four Software Functions

Presentation Logic, Application Logic, Data Access Logic & Data Storage

Predefined Values

Prevents spelling errors, avoid inappropriate data in a field, and make the user's job easier.

Internet-dependent Firms

Primary business depends on the Internet rather than a traditional business channel

Internet-dependent firms

Primary business depends on the Internet rather than a traditional business channel.

Transaction processing system (TPS)

Process data generated by day-to-day business operations. An organized collection of People, Procedures, Software, Databases, and devices used to record completed business transactions.

What is the Systems Development Life Cycle?

Process of creating and maintaining information systems

Circle

Process transforming data flow

Primitive Processes

Processes that do not create a child diagram

Modeling

Produces a graphical representation of a concept or process that systems developers can analyze, test, and modify.

Knowledge workers

Professional staff members such as systems analysts, programmers, accountants, researchers, trainers, and human resource specialists

Unit testing should include

Program ID, Tester, Date Designed & Conducted, Results, Requirement Addressed checkbox, Interface ID, Data Field& Value Entered. Also The expected results and actual results

Document Analysis

Provides information about the system as it is.

User Support

Provides users with technical information, training, and productivity support.

Systems support and security

Provides vital protection and maintenance services for system hardware and software, including enterprise computing systems, networks, transaction processing systems, and corporate IT infrastructure

Systems Support and Security

Provides vital protection and maintenance services.

Which of these is not a way users can be expected to help in prototyping?

Providing the necessary technical expertise for interfacing with the database

Quality assurance

QA A process or procedure for minimizing errors and ensuring quality in products

Rapid application development

RAD A team-based technique that speeds up information systems development and produces a functioning information system

Radio frequency identification

RFID Technology that uses high-frequency radio waves to track physical objects

Selecting Acquisition Strategy

RFP, RFI & RFQ

Rational unified process

RUP According to IBM, offers a flexible, iterative process for managing software development projects that can minimize risk, and ensure predictable results

RFID

Radio frequency identification

Data

Raw facts, can be alphanumeric, image, audio, and video.

False

Rectangles are used to represent association relationships in use case diagrams

Consistency

Reduce learning curve, terminology, predictability

Information Technology

Refers to the combination of hardware, software, & services that people use to manage, communicate, & share information.

Business Case

Refers to the reasons, or Justification, for a proposal.

Business case

Refers to the reasons, or justification, for a proposal

Functional Requirement

Relates to a process or data

Operational Employees

Relies on TP systems to enter and receive data they need to perform their jobs and needs information to handle tasks and make decisions previously made by supervisors.

systems design report

Report prepared for higher management describing alternative designs, presenting costs versus benefits, and outlining the effects of alternative designs on the organization.

systems analysis report

Report prepared for higher management describing the current information system, the requirements for a new system, and a possible development schedule.

Object

Representation of a real person, place, event, or transaction

Spiral model

Representation of a series of iterations, or revisions, based on user feedback

RFP

Request for Proposal; lists the company details and requested system and stipulates a deliverable date

RFQ

Request for Quote; only pricing is needed

Constraint

Requirement A condition that the system must satisfy or an outcome that the system must achieve

What is the best way to validate a Use Case?

Role play in front of the client so they can tell you what you missed, what was incorrect, and what was right on target

In a decision table, contradictions occur when:

Rules suggest different actions but satisfy the same conditions

Inference rules

Rules that identify data patterns and relationships within a knowledge management system

Supply chain management

SCM The coordination, integration, and management of materials, information, and finances as they move from suppliers to customers, both within and between companies

Systems development life cycle

SDLC Activities and functions that systems developers typically perform, regardless of how those activities and functions fit into a particular methodology The SDLC model includes the following steps: 1. Systems planning 2. Systems analysis 3. Systems design 4. Systems implementation 5. Systems support and security

Supplier relationship management

SRM Allows online B2B interaction where buyers and sellers, distributors, and manufacturers can offer products, submit specifications, and transact business

XY chart

Scatter Diagram A tool used by system analysts to graphically show the correlation between two variables

In the agile approach, ______________ is determined by listening to customers and getting them to write down their stories

Scope

Layout

Screen divided into 2 areas (status, work & nav) minimize movement, similar areas grouped together.

Process-control

Screens that allowed the user to send commands to the system.

Online Documentation

Searchable and easier to update

Which prototype include only some, but not all, of the components of the final system?

Selected Features Prototype

Use Case

Sequence of actions that occur when an actor uses a system to complete a process

True

Sergei, the project manager, is worried about completing the project on time. To increase the productivity of his 15-person team he should create subteams with no more than 10 people on a subteam

Which of these is a potential disadvantage of prototyping?

Shapes systems before problem is thoroughly understood

When do you use the prototype model?

Should be used when the desired system needs to have a lot of interaction with the end users

Infrastructure Design

Similar to DFD; Site map

Agile Methodologies

Similar to RAD (actually an offshoot). This methodology shares three key principles: (1)Adaptive rather than predictive (2) Emphasize people rather than roles (3) Self-adaptive processes

Consumer Products

Simple aqnd natual for the general population.

systems analysis and design

Six phases of problem-solving procedures for examining information systems and improving them.

automated design tools

Software package that evaluates hardware and software alternatives according to requirements given by the systems analyst. Also called computer-aided software engineering (CASE) tools.

Software package

Software that is purchased or leased from another firm; a commercially produced software product, or family of products

Computer-aided software

Software tools that provide automated support for some portion of the systems development process

Human-Computer Interface

Started in the 1980s with users typing complex commands in green text on a black screen.

Feasibility Study (Feasibility Report)

Step 2

Systems analysis phase (Specifications of the present system)

Step 3

Systems design phase (Specifications of the proposed system)

Step 4

Systems construction (Programs, their documentation, and user manuals)

Step 5

System testing & evaluation (Test and evaluation results, and the system ready to be delivered to the user/client)

Step 6

Systems Analysis and Design

Step-by-step process for developing high-quality information systems

In agile development ___________ are derived by spoken interaction between developers and users, not on written communication

Stories

Strong Business Case

Suggests that the company should pursue the alternative, above other options, because it would be in the firm's best interest to do so.

Interactive model

System model in which model planning, analysis, and design tasks interact continuously to produce prototypes that can be tested and implemented

Computer resources committee

Systems Review Committee A group of key managers and users responsible for evaluating systems requests

Application Development

Systems are developed by teams consisting of users, managers, and IT staff members.

Object-oriented analysis and design (OOAD)

Systems development methodologies and techniques based on objects rather than data or processes

Rapid Application Development (RAD)

Systems development methodology created to radically decrease the time needed to design and implement information systems. This methodology relies on extensive user involvement, prototyping, integrated CASE tools, and code generators

True

Technical feasibility focuses on whether the system can be built by examining the risks associated with the application

Brick-and-Mortar

Term used to describe traditional companies whose business model predated electronic commerce

Client Based architecture

Terminals or Microcomputers & ATMs. Performs all logic functions while server handles data storage.

System testing and evaluation

Test and evaluation results, and the system ready to be delivered

Systems construction

Testing, verification, and validation of the system just built

System proposal

The ........... brings together into a single comprehensive document the material created during planning and analysis

True

The SVDPI form of sentences in use cases aids in the identification of classes

Critical Thinking Skills

The ability to compare, classify, evaluate, recognize patterns, analyze cause and effect, and apply logic

Information systems analysis and design

The complex organizational process whereby computer-based information systems are developed and maintained

Identify the major use cases, expand the major use cases, confirm the major use cases, create the use-case diagram

The correct sequence of the major steps in creating use case diagrams is ......

User-centered Sytem

The distinction blurs between input, output and the interface itself.

Maintenance

The final phase of the SDLC, in which an information system is systematically repaired and improved

Planning

The first phase of the SDLC in which an organization's total information system needs are identified, analyzed, prioritized, and arranged.

False

The include relationship represents the optional inclusion of another use case

process capacity

The maximum rate with which the process can generate outputs

development environment

The mix of software tools, methods, and physical resources that an IT team uses to create an information system.

Interviewing

The most commonly used information-gathering technique is ...........

System Proposal

The most comprehensive and complete deliverable of the analysis phase is ..........

Moore's Law

The observation that the number of transistors in a dense integrated circuit doubles approximately every two years.

Physical design

The part of the design phase of the SDLC in which the logical specifications of the system from logical design are transformed into technology-specific details from which all programming and system construction can be accomplished

Systems Analyst

The person that identifies opportunities for improvements and designs an information system to implement them is called a(n).....

Net present Value (NPV)

The present value of benefit less the present value of costs (PV Benefits - PV Costs)

cloud computing

The provision of computing resources, including applications, over the internet, so customers do not have to invest in the computing infrastructure need to run and maintain the resources.

utilization

The ratio of the time that a resource is actually activated relative to the time that it is available for use

Data

The raw material or basic facts used by information systems

Systems analysis phase

The second SDLC phase The building of a logical model of the new system

Analysis

The second phase of the SDLC where system requirements are studied and structured

systems analysis

The second phase of the systems life cycle determines the requirements for a new system.

Application Architecture

The set of information systems the organizations needs to support its strategic plan

Requirements Determination

The single most critical step of the entire SDLC, changes can be easily made in this stage, more than 50% system failures are due to problems with this.

systems life cycle

The six phases of systems analysis and design are called the systems life cycle. The phases are preliminary investigation, systems analysis, systems design, systems development, systems implementation, and systems maintenance.

False

The standar approach to select who should complete a questionnaire during information gathering is to sample only those departments that do not have direct contact with the As-Is system

Processes

The tasks and business functions that users, managers, and IT staff members perform to achieve specific results

Systems design phase

The third SDLC phase Creation of a blueprint for the new system that will satisfy all documented requirements, whether the system is being developed in-house or purchased as a package

Design

The third phase of the SDLC in which the description of the recommended solution is converted into logical and then physical system specifications

1. Creating the work plan 2. Staffing the project 3. Controlling and directing the project

The three steps of project management are ..........

False

The top-down approach is an appropriate strategy for most interviews because it enables the interviewee to become accustomed to the topic before he or she needs to provide specifics and it enables the interviewer to understand the issues before moving to the details.

Systems development life cycle (SDLC)

The traditional methodology used to develop, maintain, and replace information systems

Systems Development Lifecycle

The traditional model describing the life of an information system from conception to retirement

Reuse

The use of previously written software resources, especially objects and components, in new applications.

Compliance

The user has the right to a system that performs exactly as promised.

1990s to 2000s

This decade consisted of more focus on system integration, GUI applications more application service providers, client/ server platforms, more use of the world wide web and internet, more web application development.

1970s to 1980s

This decade consisted of systems analysis and design becoming more of engineering discipline,personal computers, mainframes, people began to write more off the shelf software and there was an introduction to 4 generation languages, PC explosion (IBM and HP at the lead) and breakthrough of case tools and object oriented tools.

From the 2000s and beyond

This decade consisted of the infusion of wireless technology, PDAs, smart phones, introduction to other forms of software including cloud based applications, component based applications, and an increase in mobile web applications development.

.NET

This is an example of a web-based development environment

Internet Business Services

This is attractive to customers because it offers online data center support, mainframe computing power for mission-critical functions, and universal access via the Internet.

False

To complete a 20 person-month project in 10 months, a team should have 4 full-time staff members assigned to the project

Requirements Determination Purpose

To convert high-level business requirements (from the system request) into detailed requirements that can be used as inputs for creating models.

Structured Analysis

Traditional method for developing systems (SDLC). Uses graphical diagrams to develop and portray system specifications that are easily understood by users. Organized into phases.

forward engineering

Translating business processes and functions into applications.

Requirements gathering techniques process is used to

Uncover all requirements (those uncovered late int eh process are more difficult to incorporate). Also, to build support and trust among users.

In order to use structured english, which convention is not advisable?

Use a blank line to separate sets of statements with different purposes

Use Case Driven

Use cases define the behavior of a system: How the user interacts with the system to perform some activity -Each use case focuses on one business process

How do we write a user story?

User stories should include enough info for your product manager to decide how important the story is. They should always include: - Person using the service (the actor) - What the user needs the service for (the narrative) - Why the user needs it (the goal) Usually written in this format: As a... [Who is the user?] I need/want/expect to... [what does the user want to do?] So that... [why does the user want to do this?]

Knowledge Management System

Uses a large database called a knowledge base and allows users to find information by entering keywords. A discipline that promotes an integrated approach to identifying, capturing, evaluating, retrieving, and sharing all of enterprise's information assets.

Management Information System (MIS)

Uses raw data from TPS systems, and converts them into meaningful aggregate form, resulting in summary reports.

Usability Metrics

Using software that can record and measure user interaction with the system.

business analytics

Using software to measure past performance to help managers understand business trends and monitor current operations.

Server based architecture

Usually a mainframe, performs all four software functions. Simple works well but hard to upgrade a little at a time.

Critical success factors

Vital objectives that must be achieved for the enterprise to fulfill its mission

Collection

Weaker

cascading style sheets (CSS)

Web page encoding standard that enables a Web site designer to specify parts of a page that will always look the same and parts that will vary by task or audience

Feasibility Analysis

What are the risks? Can these risks be overcome

When should you use decision tables

When complex combinations of conditions actions and rules are found. Or you require a method that effectively avoids impossible situations, redundancy, and contradictions.

False

When drawing use case diagrams, higher level use cases are drawn below lower level use cases

Large project size

Which of the following factors would tend to increase the technical risk of a project?

Pareto Chart

Widely used tool for visualizing issues that need attention.

Groupware

Workgroup software Programs that run on a company intranet that enable users to share data, collaborate on projects, and work in teams

Extensible markup language

XML Flexible data description language that allows Web-based communication between different hardware and software environments

pair programming

XP practice in which two programmers work together on designing, coding, and testing software

Scatter diagram

XY chart A tool used by system analysts to graphically show the correlation between two variables

relational database management system (RDBMS)

a DBMS that organizes data in tables or relations

Gantt chart

a bar chart that portrays the schedule by the length of horizontal bars superimposed on a calendar

intangible benefit

a benefit that accrues to an organization but that can't be measured quantitatively or estimated accurately

Tangible benefit

a benefit that can be measured in dollars

tangible benefit

a benefit that can be measured or estimated in terms of dollars

intangible benefit

a benefit that cannot be easily measured in dollars or with certainty

encryption key

a binary input to the encryption algorithm—typically a long string of bits

abstract class

a class that describes a category or set of objects but that never includes individual objects or instances

boundary class, or view class

a class that exists on a system's automation boundary, such as an input window

data access class

a class that is used to retrieve data from and send data to a database

control class

a class that mediates between boundary classes and entity classes, acting as a switchboard between the view layer and domain layer

browser-based application

a client/server application that executes locally within the control of a Web browser

security control

a control that protects the assets of an organization from all threats, with a primary focus on external threats

integrity control

a control that rejects invalid data inputs, prevents unauthorized data outputs, and protects data and programs against accidental or malicious tampering

access control

a control that restricts which persons or programs can add, modify, or view information resources

field combination control

a control that reviews combinations of data inputs to ensure that the correct data are entered

project management

a controlled process of initiating, planning, executing, and closing down a project

Tangible cost

a cost associated with an information system that can be measured in dollars and with certainty

one time cost

a cost associated with project start up and development

intangible cost

a cost that can not be measured in dollars

primitive data type

a data type supported directly by computer hardware or a programming language

phased deployment

a deployment method that installs a new system and makes it operational in a series of steps or phases

direct deployment or immediate cutover

a deployment method that installs a new system, quickly makes it operational, and immediately turns off any overlapping systems

parallel deployment

a deployment method that operates the old and the new systems for an extended time period

action-expression

a description of the activities performed as part of a transition

entity class

a design identifier for a problem domain class

indirection

a design principle in which an intermediate class is placed between two classes to decouple them but still link them

protection from variations

a design principle in which parts of a system that are unlikely to change are segregated from those that will

separation of responsibilities

a design principle that recommends segregating classes into separate components based on the primary focus of the classes

walking skeleton

a development approach in which the complete system structure is built but with bare-bones functionality

input, process, output (IPO) development order

a development order that implements input modules first, process modules next, and output modules last

bottom-up development

a development order that implements low-level detailed modules first

top-down development

a development order that implements top-level modules first

class diagram

a diagram consisting of classes (i.e., sets of objects) and associations among the classes

entity-relationship diagram (ERD)

a diagram consisting of data entities (i.e., sets of things) and their relationships

state machine diagram

a diagram showing the life of an object in states and transitions

system sequence diagram (SSD)

a diagram showing the sequence of messages between an external actor and the system during a use case or scenario

colocation

a hosting service with a secure location but in which the computers are usually owned by the client businesses

Data repository

a large collection of project information

access control list

a list attached or linked to a specific resource that describes users or user groups and the nature of permitted access

Web 2.0

a loosely defined, nonstandard term used to refer to Web sites that permit user-generated content and user interaction, such as social networking sites

cardinality

a measure of the number of links between one object and another object in a relationship

multiplicity

a measure, in UML, of the number of links between one object and another object in an association

retrospective

a meeting held by the team at the end of an iteration to determine what was successful and what can be improved

open-source software

a method of developing, delivering, and licensing software that makes the application source code freely available to any interested developer or client

stub

a method or class developed for unit testing that simulates the behavior of a method that hasn't yet been written

driver

a method or class developed for unit testing that simulates the behavior of a method that sends a message to the method being tested

class-level method

a method that is associated with a class instead of with objects of the class

virtual server

a method to partition the services of a physical Web server so it appears as multiple, independent Internet servers

network diagram

a model that shows how the application is deployed across networks and computers

visibility

a notation that indicates (by plus or minus sign) whether an attribute can be directly accessed by another object

method signature

a notation that shows all the information needed to invoke, or call, the method

functional dependency

a one-to-one association between the values of two attributes

privileged user

a person who has access to the source code, executable program, and database structure of the system

registered user

a person who is authorized to access the system

project management body of knowledge (PMBOK)

a project management guide and standard of fundamental project management principles

coupling

a qualitative measure of how closely the classes in a design class diagram are linked

cohesion

a qualitative measure of the focus or unity of purpose within a single class

text box

a rectangular box that accepts text typed on a keyboard or recognized from speech input

whole-part relationship

a relationship between classes in which one class is a part or a component portion of another class

<> relationship

a relationship between use cases in which one use case is stereotypically included within the other use case

critical path

a sequence of tasks that can't be delayed without causing the entire project to be delayed

Systems development process or Methodology

a set of comprehensive guidelines for carrying out all of the activities of each core process of the SDLC

system development methodology

a set of comprehensive guidelines for the SDLC that includes specific models, tools, and techniques

Technology Architecture

a set of computing hardware, network hardware and topology, and system software employed by an organization

technology architecture

a set of computing hardware, network hardware and topology, and system software employed by an organization

UP discipline

a set of functionally related activities that combine to enable the development process in a UP project

information system

a set of interrelated computer components that collects, processes, stores, and provides as output the information needed to complete business tasks

content delivery network (CDN)

a set of server computers, separate from the hosting computers, used to deliver such static content as images or videos

buffer

a storage area between stages where the output of a stage is placed prior to being used in a downstream stage

maintenance release

a system update that provides bug fixes and small changes to existing features

production release, release version, or production release

a system version that is formally distributed to users or made operational for long-term use

transaction logging

a technique by which any update to the database is logged with such audit information as user ID, date, time, input data, and type of update

digital signature

a technique in which a document is encrypted by using a private key to verify who wrote the document

structured analysis

a technique to determine what processing is required and to organize those requirements by using structured analysis models

usability test

a test to determine whether a method, class, subsystem, or system meets user requirements

alpha version

a test version that is incomplete but ready for some level of rigorous integration or usability testing

beta version

a test version that is stable enough to be tested by end users over an extended period of time

list box

a text box that contains a list of predefined data values

combo box

a text box that contains a predefined list of acceptable entries but permits the user to enter a new value when the list doesn't contain the desired value

use case description

a textual model that lists and describes the processing details for a use case

object

a thing in an information system that responds to messages by executing functions or methods

guard-condition

a true/false test to see whether a transition can fire

table

a two-dimensional data structure of columns and rows

mashup

a type of Web site that combines the functionality of several other Web sites through the use of predefined APIs

Rich Internet Applications (RIAs)

a type of Web site that provides active user interaction as well as delivers rich multimedia

Engineering Drawing

a visual representation of the product and it's components.

synchronization bar

activity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent paths

Data stores are used to store:

all base elements and some derived elements

In designing a GUI screen, a default value of a data element can be displayed on:

all of the above (drop down lists, radio buttons, check boxes)

When drawing the decision tree, systems analysts do not have to identify:

all outcomes

Income Statement

also known as a profit and loss statement. it is a record of revenue and expenses for a specific period of time.

Transport Layer Security (TLS)

an Internet standard equivalent to SSL

IP Security (IPSec)

an Internet standard for secure transmission of low-level network pack

Secure Hypertext Transport Protocol (HTTPS)

an Internet standard for securely transmitting Web pages

waterfall model

an SDLC approach that assumes the phases can be completed sequentially with no overlap

incremental development

an SDLC approach that completes portions of the system in small increments across iterations, with each increment being integrated into the whole as it is completed

CRUD technique

an acronym for Create, Read/Report, Update, and Delete; a technique to validate or refine use cases

use case

an activity that the system performs, usually in response to a request by a user

Transport Layer Security (TLS)

an advanced version of Secure Sockets Layer (SSL) protocol used to transmit information over the Internet securely

Purchase Order (PO)

an agreement to purchase the stated material, for the stated price, under the stated terms.

predictive approach to the SDLC

an approach that assumes the project can be planned in advance and that the new information system can be developed according to the plan

adaptive approach to the SDLC

an approach that assumes the project must be more flexible and adapt to changing needs as the project progresses

iterative development

an approach to system development in which the system is "grown" piece by piece through multiple iterations

Iterative Development

an approach to system development in which the system is "grown" piece by piece through multiple mini-projects called iterations

ternary association

an association between exactly three distinct types of things

association class

an association that is also treated as a class; often required in order to capture attributes for the association

key

an attribute or set of attributes, the values of which occur only once in all the rows of the table

compound attribute

an attribute that consists of multiple pieces of information but is best treated in the aggregate

class-level attribute

an attribute that contains the same value for all objects in the system

foreign key

an attribute that duplicates the primary key of a different (or foreign) table

identifier or key

an attribute the value of which uniquely identifies an individual thing or object

persistent class

an entity class whose objects exist after a system is shut down

temporal event

an event that occurs as a result of reaching a point in time

external event

an event that occurs outside the system, usually initiated by an external agent

state event

an event that occurs when something happens inside the system that triggers some process

FURPS+

an extension of FURPS that includes design consrtaints as well as implementation, system interface, physical, and support ability requirements

FURPS

an extension of FURPS that includes design constraints as well as implementation, interface, physical, and supportability requirements

cloud computing

an extension of virtual servers in which the resources available include computing, storage, and Internet access and appear to have unlimited availability

actor

an external agent; a person or group that interacts with the system by supplying or receiving data

Subsystem

an identifiable and fully functional part of a complete system

subsystem

an identifiable and partitioned portion of an overall system

Agile Development

an information systems development process that emphasizes flexibility to anticipate new requirements during development

brief use case description

an often one-sentence description that provides a quick overview of a use case

Context Diagram

an overview of an organizational system that

metaphors

analogies between features of the user interface and aspects of physical reality that users are familiar with

on-demand software

another term for SAAS

gadget

another term for a widget—often used for widgets that reside on a desktop

Process specifications

are created for primitive processes and some higher level processes on a DFD. They are also called minispecs.

Physical Design

aspect of Design in SDLC in which logical specification of the system from logical design is transformed into technology-specific details

binary associations

associations between exactly two distinct types of things

CASE tools

automate many systems development tasks. allow more than one person to work on the same system at the same time via a multiuser interface.

Election data dictionary entries

become if then else structured english statements

Tangible Benefits

benefits that can be measured in dollars

XML tags

character sequences (such as and ) that define the beginning, end, and meaning of the text that appears between them

replicated database server architecture

complete database copies are hosted by cooperating DBMSs running on multiple servers

Baseline Project Plan

contains estimates of a projects scope, benefits, costs, risks, and resource requirements

Requirements determination purpose

convert high level business requirements (from the system request) into detailed requirements that can be used as inputs for creating models

make to stock

creating an inventory stock to be used when customer orders come in.

instantiation

creation of an object based on the template provided by the class definition

schema

database component that contains descriptive information about the data stored in the physical data store

physical data store

database component that stores the raw bits and bytes of data

hawthorn effect

decreasing light to see if it affected workers

object-oriented design (OOD)

defining all of the types of objects necessary to communicate with people and devices in the system, showing how objects interact to complete tasks, and refining the definition of each type of object so it can be implemented with a specific language or environment

usability

degree to which a system is easy to learn and use

activity diagram

describes user (or system) activities, the person who does each activity, and the sequential flow of these activities

user documentation

descriptions of how to interact with and use the system, as used by end users and system operators

system documentation

descriptions of system requirements, architecture, and construction details, as used by maintenance personnel and future developers

Each data flow diagram should be defined with

descriptive information and its composite structure elements

attributes

descriptive pieces of information about things or objects

user-centered design

design techniques that embody the view that theuser interface is the entire system

Intangible Benefits

difficult to measure in dollars but are important to the company.

system development challenges

difficulty of requirements determination. changes in requirements. scheduling & budgeting difficulties. changing technology. diseconomies of scale: brooke's law = adding more people to a late project makes the project later.

work measurement techniques

direct and indirect

Which of the following is not a basic activity of agile development?

documenting

interaction diagram

either a communication diagram or a sequence diagram that shows the interactions between objects

Intangible Costs

employee morale

software engineering

employs computer-aided software engineering (CASE).

asymmetric key encryption

encryption method that uses different keys to encrypt and decrypt the data

symmetric key encryption

encryption method that uses the same key to encrypt and decrypt the data

Extensible Markup Language (XML)

extension of HTML that embeds self-defining data structures within textual Messages

turnaround documents

external outputs that includes one or more parts intended to be returned with new data or information

human-computer interaction (HCI)

field of study concerned with the efficiency and effectiveness of user interfaces vis-à-vis computer systems, human-oriented input and output technology, and psychological aspects of user interfaces

Maintenance

final phase of the SDLC in which an info system is systematically repaired and improved

origin state

for a particular transition, the original state of an object from which the transition occurs

destination state

for a particular transition, the state to which an object moves after the completion of a transition

Gantt Chart

graphical representation of a project that shows each task as a horizontal bar whose length is proportional to its time for completion

technique

guidelines to specify a method for how to carry out a development activity or task

supportability requirements

how a system is installed, configured, monitored, and updated

Bill of Materials (BOM)

identifies all the materials of parts needed to make one unit of a finished product. It is based on the design of the product.

economic feasibility

identifying the financial benefits and costs

A veritcal line in a sequence diagram

indicates when the class or object is busy doing things

system interfaces

inputs or outputs that require minimal human intervention

constraint

is a requirement or a condition that a system must satisfy or an outcome that the system must achieve.

Data Dictionary

is a structured repository of data elements in the system. It stores the descriptions of all DFD data elements that is, details and definitions of data flows, data stores, data stored in data stores, and the processes

XY Chart or scatter Diagram

is another problem-solving tool.

a derived data element is one that:

is created by processes as a result of calculations or a series of decision-making statements

Structured English

is derived from structured programming language which gives more understandable and precise description of a process

System Vision Document

is developed to identify the benefits to the company and the functional capabilities that will be included in the system.

Which of the following is not an example of a keyword for structured english

is like

In describing the data type of the value of a data element, a VARCHAR data type:

is used for data that can contain any number of characters (up to the database limit)

Context Diagram

it helps in understanding the entire system by one DFD which gives the overview of a system.

Action Entry

it is in lower right quadrant which indicates the appropriate action resulting from the answers to the conditions in the condition entry quadrant.

systems investigation & analysis

looks at the existing system & determines if it can & should be improved - feasibility. -operational. -economic (tangible v. intangible). -technical. -human factors. -legal/political.

detail design

low-level design that includes the design of the specific program details

specialization of labor

made high speed, low cost production possible; enhanced standard of living; adverse effects on workers (econmies of scale)

job enrichment

make job more interesting to worker; horizontal or vertical

maintenance & review

makes sure that the new or modified system is operating as intended.

direct manipulation metaphor

metaphor in which objects on a display are manipulated to look like physical objects (pictures) or graphic symbols that represent them (icons)

desktop metaphor

metaphor in which the visual display is organized into distinct regions, with a large empty workspace in the middle and a collection of tool icons around the perimeter

dialog metaphor

metaphor in which user and computer accomplish a task by engaging in a conversation or dialog via text, voice, or tools such as labeled buttons

SDLC

methodology used to develop, maintain and replace info system

Systems that require constant updating and technical design are prone to which kind of error?

miscommunication

fraud triangle

model of fraud that states that opportunity, motivation, and rationalization must all exist for a fraud to occur

systems design & implementation

modifying an existing system or developing a new one.

TVM

money available today is worth more than the same amount tomorrow

accounts payable (AP)

money owed by a company to its creditors.

accounts receivable (AR)

money owed to a company by its debtors.

partitioned database server architecture

multiple distributed database servers are used and the database schema is partitioned, with some content on only one server and some content copied on all servers

blocking

occurs when the activities in a stage must stop because there is no place to deposit the item

starving

occurs when the activities in a stage must stop because there is no work

row

one horizontal group of data attribute values in a table

single database server architecture

one or more databases are hosted by a single DBMS running on a single server

attribute

one vertical group of data attribute values in a table

performance requirements

operational characteristics related to measures of workload, such as throughput and response time

usability requirements

operational characteristics related to users, such as the user interface, related work procedures, online help, and documentation

project management

organizing and directing other people to achieve a planned result within a predetermined schedule and budget

true/false condition

part of a message between objects that is evaluated prior to transmission to determine whether the message can be sent

Service Level Agreement (SLA)

part of the contract between a business and a hosting company that guarantees a specific level of system availability

the Panama Papers

people committing tax fraud by moving money to panama. (newspapers worked together to catch it)

ways to reduce processing time

perform activities in parallel, change the sequence of activities, or reduce interruptions or bottlenecks

client

person or group that provides the funding for a system development project

Stakeholders

person who have an interest in the successful implementation of the system.

external stakeholders

persons outside the organization's control and influence who interact with the system or have a significant interest in its operation or success

executive stakeholders

persons who don't interact directly with the system but who either use information produced by the system or have a significant financial or other interest in its operation and success

stakeholders

persons who have an interest in the successful implementation of the system

operational stakeholders

persons who regularly interact with a system in the course of their jobs or lives

internal stakeholders

persons within the organization who interact with the system or have a significant interest in its operation or success

indirect

predetermined motion-time data system, elemental data

How do we prevent fraud in a system

prevent opportunity, separation of duty

what is the purpose of separation (segregation) of duty?

primary purpose is to prevent fraud and promptly detect errors and irregularities

persistent classes

problem domain classes that must be remembered between program executions (i.e., require storage in a database)

work measurement

process of analyzing jobs fro the purpose of setting time standards to: schedule work and allocate capacity, motivate and measure work performance, evaluate performance, and provide benchmarks

cost/benefit analysis

process of comparing costs and benefits to see whether investing in a new system will be beneficial

Physical data flow diagrams include

processes for adding, reading, changing, and deleting records.

internal outputs

reports or other outputs produced for use within the organization

detailed reports

reports that contain specific information on business transactions

exception reports

reports that provide details or summary information about transactions or operating results that fall outside a predefined normal range of values

summary reports

reports that summarize detail or recap periodic activity

executive reports

reports used by highlevel managers to assess overall organizational health and performance

model

representation of some aspect of a system

interface requirements

required interactions among systems

security requirements

requirements that describe how access to the application will be controlled and how data will be protected during storage and transmission

first normal form (1NF)

restriction that all rows of a table must contain the same number of columns

design constraints

restrictions to which the hardware and software must adhere

refactoring

revising, reorganizing, and rebuilding part of a system so it is of higher quality

workflow

sequence of processing steps that completely handles one business transaction or customer request

storyboarding

sequence of sketches of the display screen during a dialog

Physical data flow diagrams

show how the system operates or how the new system will be implemented.

a horizontal arrow in a sequence diagram

shows messages and optional parameters that are sent between classes

gantt chart

shows progress through systems development activities by putting a bar through appropriate cells.

Business case

shows tangible and intangible economic benefits and costs and then feasibility

A horizontal bar in a sequence diagram

shows when the class or object is busy doing things

check boxes

similar to radio buttons, but the user can select multiple items within the group

assistive technologies

software (such as text-to-speech and voice-recognition utilities) that adapts user interfaces to the special needs of persons with disabilities

parallel process

some of production has alternative paths where two or more machines are used to increase capacity

event

something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system event.

bottleneck

stage that limits the capacity or throughput of the process

design patterns

standard design techniques and templates that are widely recognized as good practice

Unified Modeling Language (UML)

standard set of model constructs and notations defined by the Object Management Group

nonfunctional requirements

system characteristics other than the activities it must perform or support

object-oriented approach

system development based on the view that a system is a set of interacting objects that work together

mathematical models

system models that describes requirements numerically or as mathematical expressions

graphical models

system models that use pictures and other graphical elements

unit testing

test of an individual method, class, or component before it is integrated with other software

integration test

test of the behavior of a group of methods, classes, or components

textual models

text-based system models such as memos, reports, narratives, and lists

use case diagram

the UML model used to graphically show use cases and their relationships to actors

system requirements

the activities a system must perform or support and the constraints that the system must meet

support activities

the activities in the support phase whose objective is to maintain and enhance the system after it is installed and in use

functional requirements

the activities that the system must perform

information systems development process

the actual approach used to develop a particular information system

multiplicity constraints

the actual numeric count of the constraints on objects allowed in an association

slack time

the amount of time that an activity can be delayed without delaying the whole project

perfect technology assumption

the assumption that a system runs under perfect operating and technological conditions

help desk

the availability of support staff to assist users with technical or processing problems of the information system

business benefits

the benefits that accrue to the organization; usually measured in dollars

automation boundary

the boundary between the computerized portion of the application and the users who operate the application but are part of the total system

server computer

the central computer that provides services (such as database access) to the client computers over a network

product owner

the client stakeholder for whom the system is being built

client computers

the computers at which the users work to perform their computational tasks

top-down programming

the concept of dividing a complex program into a hierarchy of program modules

inheritance

the concept that specialization classes inherit the attributes of the generalization class

concurrency or concurrent state

the condition of being in more than one state at a time

structured design

the design process of organizing a program into a set of modules and organizing those modules into a hierarchical structure

response time

the desired or maximum allowable time limit for software response to a query or update

throughput

the desired or minimum number of queries and transactions that must be processed per minute or hour

Systems Development Life Cycle (SDLC)

the entire process consisting of all the activities required to build, launch, and maintain an information system

DFD completeness

the extent to which all necessary components of a DFD have been included and fully described

DFD consistency

the extent to which information contained on one level of a set of nest DFDs is also included in other levels

ceremony

the level of formality of a project; the rigor of holding meetings and producing documentation

project iteration schedule

the list of iterations and use cases or user stories assigned to each iteration

work breakdown structure (WBS)

the list or hierarchy of activities and tasks of a project; used to estimate the work to be done and to create a detailed work schedule

primitive DFD

the lowest level of decomposition

elementary business processes (EBPs)

the most fundamental tasks in a business process, which leaves the system and data in a quiescent state; usually performed by one person in response to a business event

transition

the movement of an object from one state to another state

logistics processes

the movement of things such as materials, people, or finished goods

HTML5

the new HTML specification that standardizes RIA specifications for built-in browser delivery

Object Classes

the nouns that describe categories of things

application architecture

the organization and construction of software resources to implement an organization's information systems

Systems analyst

the organizational role most responsible for the analysis and design of info system

business logic layer or domain layer

the part of a three-layer architecture that contains the programs that implement the business rules and processes

data layer

the part of a three-layer architecture that interacts with the data

view layer

the part of the three-layer architecture that contains the user interface

Scrum master

the person in charge of a Scrum project—similar to a project manager

users

the person or group of people who will use the new system

client

the person or group that funds the project

break-even point

the point in time at which dollar benefits offset dollar costs

Hypertext Markup Language (HTML)

the predominant language for constructing Web pages and which consists of tags and rules about how to display pages

net present value (NPV)

the present value of dollar benefits and dollar costs of a particular investment

Internet backbone

the primary data routes between large, strategically interconnected networks and routers on the Internet

Planning

the priorities, detailed steps, work plan for project

authorization

the process of allowing or restricting a specific authenticated user's access to a specific resource based on an access control list

encryption

the process of altering data so unauthorized users can't view them

decryption

the process of converting encrypted data back to their original state

Work breakdown structure

the process of dividing the project into manageable tasks and logically ordering them to ensure a smooth evolution between tasks

Critical path

the shortest time in which a project can be completed

subclass

the subordinate or more specialized class in a generalization/specialization relationship

superclass

the superior or more general class in a generalization/specialization relationship

data entities

the term used in an ER diagram to describe sets of things or individual things

Design

the third phase of the SDLC in which the description of the recommended solution is converted into logical and then physical specfications

Balance Sheet

this shows what the company owns (assets), what it owes to others (liabilities), and how much many shareholders have invested in the company (equity)

systems design

those activities that enable a person to define and describe in detail the system that solves the need

systems analysis

those activities that enable a person to understand and specify what the new system should accomplish

Systems Design

those system development activities that enable a person to describe in detail how the resulting information system will actually be implemented.

Systems Analysis

those system development activities that enable a person to understand and specify what the new system should accomplish

direct

time study, work sampling

visual modeling tools

tools that help analysts create and verify graphical models and may also generate program code

systems delevopment process

typically called a systems development life cycle (SDLC).

Systems Development

typically starts with a systems request, followed by a preliminary investigation, which includes feasibility study

which is the correct choice?

use decision trees when the sequence of conditions and actions is critical

cloud-based database server architecture

use of a cloud computing service provider to provide some or all database services

drill down

user-interface design technique that enables a user to select summary information and view supporting detail

multifactor authentication

using multiple authentication methods for increased reliability

Tangible Costs

usually can be measured in dollars

A goal of producing process specifications is to

validate the system design, including data flow diagrams and the data dictionary

packing list

what goes in the box and leave with the product

postcondition

what must be true upon the successful completion of a use case

picking list

what the warehouse has in stock

Sales Order (SO)

when a company receives the customer's Purchase Order (PO), it creates an internal document called a sales order.

logical design

when all functional features of the system chosen for development in analysis are described independently of any computer platform

peer-to-peer connection

when independent computers communicate and share resources without the need of a centralized server computer

affordance

when the appearance of a specific control suggests its function

When should you use structured english

when there are many repetitious actions or when communication to end users is important

camelback notation or camelcase notation

when words are concatenated to form a single word and the first letter of each embedded word is capitalized

1st thing to do when setting up an ERP system

you must have a general ledger so START with a charter of accounts

Corporate Culture

À set of beliefs, rules, traditions, values, and attitudes that define a company and influence its way of doing business

People

◦ Stakeholders ◦ Users or end users

Data

◦ Tables store data ◦ Linked tables work together to supply data


Kaugnay na mga set ng pag-aaral

6.7 Area and Circumference of Circles

View Set

Chapter 32:Birth-Related Stressors

View Set

Understanding Architecture Midterm

View Set

Psychology Exam 3 Practice Questions

View Set

Ch 2. Chemical Level of Organization - Dr. Deva Joseph

View Set

Chapter 15: Absolutism and Constitutionalism Study Guide

View Set