ITC211

A collection of interrelated components that function together to achieve some outcome

The process of understanding and specifying in detail what the information system should accomplish

The process of specifying in detail how the many components of the information system should be physically implemented

A business professional who uses analysis and design techniques to solve business problems using information technology

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

A system that is part of a larger system

Dividing a system into components based on subsystems that are further divided into smaller subsystems

The separation between a system and its environment that inputs and outputs must cross

The separation between the automated part of a system and the manual part of a system

• Customer Relationship Management System:
• A system that supports marketing, sales, and service operations involving direct and indirect customer interaction

• Supply chain management system:
• A system that seamlessly integrates product development, product aquisition, manufacturing, and inventory management

• Accounting and Financial Management System:
• A system that records accounting information needed to produce financial statements and other reports used by investors and creditors

• Human Resourse Management System:
• A system that supports employee-related tasks such as payroll, benefits, hiring and training.

• Knowledge Management System:
• A system that supports the storage of and access to documents from all parts of the organisation

• Collaboration Support System:
• A system that enables geographically distributed personnel to collaborate on projects and tasks

• Enterprise Resource Planning:
• A process in which an organisation commits to using an integrated set of software packages for key information systems

A centrally managed collection of data that is accessable to many users and systems at the same time

• Systems Development Life Cycle:
• The entire process of building, deploying, using and updating an information system

An SDLC approach that assumes the development project can be planned and organised in advance and that the new information system can be developed according to the plan

An SDLC approach that is more flexible, assuming that the project cannot be planned out completely in advance but must be modified as it progresses

• Project Planning
• Analysis
• Design
• Implementation
• Support

An SDLC approach that assumes the various phases of a project can be completed sequentially - one phases leaders (falls) into the next phase

• To identify the scope of the new system 'define the problem'
• ensure that the project is feasible
• develop a project schedule
• resource plan 'staff the project'
• budget for the remainder of the project
• launch the project

To understand in detail the business needs and the processing requirements of the new system

• Gather information
• Define system requirements
• Build prototypes for discovery of requirements
• Priorities requirements
• Generate and evaluate alternatives
• Review recommendations with management

To design the solution system based on the requirements defined and decisions made during analysis

• Design and integrate the network
• Design the application architecture
• Design the user interfaces
• Design the system interfaces
• Design and integrate the database
• Prototype for design details
• Design and integrate the system controls

To build, test, and install a reliable information system with trained users ready to benefit as expected from use of the system

• Construct software components
• Verify and test
• Convert data
• Train users and document the system
• Install the system

To keep the system running productively, both intially and during the many years of the system's lifetime

• Maintain the system
• Enhance the system
• Support the users

An adaptive SDLC approach that cycles over and over again through development activities until a project is complete

A preliminary working model showing some aspect of a larger system

System development processes in which work activities - analysis, design, implementation - are done once, then again, and yet again on different system components; they are repeated until the system is closer to what is ultimately needed

A representation of an important aspect of the real world

Software support that helps create models or other components required in the project

A collection of guidelines that help an analyst complete a system development activity or task

• Context Diagram
• Top level data flow diagram
• Data dictionary listings for 5 data elements
• Entity Relationship Diagram

• Use Case Diagram
• Detailed Use Case Description
• Activity Diagram
• Class Diagram

• Information Engineering
• A traditional system development methodology thought to be more rigourous and complete than the structure approach, because of its focus on strategic planning, data modeling, and automated tools

An approach to system development that views an information system as a collection of interacting objects that work together to accomplish tasks

An object orientated system development methodology (IBM's Rational Software).

UML for system modeling

Four life cycle phases - Inception, elaboration, construction and transition

Example of SDLC that is in the middle of predictive vs adaptive scale

Designed to reinforce 6 best practices for system development:

• Develop iteratively
• Define and manage system requirements
• Use component architectures
• Create visual models
• Verify quality
• Control changes

Lightweight system development approach.

Highly adaptive approach to SDLC.

User stories described. Iterative, incremental

Continuous testing, continuous integration, heavy user involvment, programming done by teams.

A collection of techniques, tools and models.

Computer Aided System Engineering

Some generate program code based on created models

Some help to automate the whole system development process

How dependant functions on other functions

Should be low

When you have to change something you do not have to change everything

How defined and close are the relationships between functions

Different from dependancy

• A set of procedures that interact with data to achieve some functionality
• - Data passed between functions
• - System as a collection of functions
• - Functional decomposition
• - Waterfall framework
• - DFD's
• - Sequence of intructions, if/else statements and loops

A set of objects that interact together through messages to achieve some objective

Set of objects that exchange data via messages to achieve some functionality

• - Processes vs System a a collection of objects
• - Object decomposition
• - Data passed between objects
• - Iterative processes
• - Class diagrams
• - Message passing and events triggering