BT 1005 Managing Information Lecture 1 Introduction to Information Systems: Information Systems Concepts.

Slides:



Advertisements
Similar presentations
Project Analysis Course ( ) Final Project Report Overview.
Advertisements

Database Systems: Design, Implementation, and Management Tenth Edition
CASE Afternoon Primer Session Topics of Discussion July 22, 2013 FINAL DRAFT.
July 11 th, 2005 Software Engineering with Reusable Components RiSE’s Seminars Sametinger’s book :: Chapters 16, 17 and 18 Fred Durão.
Feb. 13, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #9 Tuesday, Feb. 13, 2001.
The Architecture Design Process
Project title Your Names Plan on 8 minutes (no more than 6 slides)
SOFTWARE ENGINEERING for REAL-TIME SYSTEMS (© J.E.Cooling 2003) Software design - core concepts - slide 1 Software engineering for real-time systems Section.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
01-1 Physics I Class 01 1D Motion Definitions.
02-1 Physics I Class 02 One-Dimensional Motion Definitions.
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
Object Oriented Software Development Systems and Models Seminar: Week 1 Brian Farrimond.
PVK-061 Contents Introduction Requirements Engineering Project Management Software Design Detailed Design and Coding Quality Assurance Maintenance.
1 Software Requirements Specification Lecture 14.
Development through partnership Infrastructure Delivery Management Toolkit: 2010 Edition Delivery Process 3: Operations & Maintenance 1.
AD description template definition Marián Mlynarovič FIIT Lectures 2006.
Use Case Analysis – continued
An introduction to enterprise systems a birds-eye view of the course.
RFIX Concept note Introduction Outline of the purpose & content of the draft Concept note. Astana 22 September.
Introduction to Programming and Software Development CMPCD1017 Session 2:Requirements Analysis and Specification.
1. Computer Integrated Manufacturing (CIM) has received much attention in the last decade. A company that adopts CIM practices is supposed to operate.
June 6, 2001By: Respickius Casmir1 Doctoral Thesis Title and Author A Systemic-Holistic Approach to Academic Programmes In IT Security Presented By Louise.
Lesson 7 Guide for Software Design Description (SDD)
CE0825 Object-Oriented Programming 2 © Allan C. Milne Abertay University v
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa USE CASES In this lecture: Use cases - What are use.
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
Engineering System Design
OBJECTIVES, JOB TITLES, WRITING JD, FORMATS & PROFILING Job Description By: Arthur Gonzaga &Lane Joan Baay.
Qualitative and Quantitative Research Quantitative Deductive: transforms general theory into hypothesis suitable for testing Deductive: transforms general.
SYSTEM ANALYSIS AND DESIGN 1. Topics to include.. WHAT IS SAD? NEED FOR SAD ROLE OF THE SYSTEM ANALYST QUALITIES OF SYSTEM CHARACTERISTICS FEASIBILITY.
Lecture 7: Requirements Engineering
Lecture # 3 & 4 Chapter # 2 Database System Concepts and Architecture Muhammad Emran Database Systems 1.
Sept. 18, 2003CS WPI1 CS 509 Design of Software Systems Lecture #3 Thursday, Sept. 18, 2003.
1 | 2010 Lecture 1: Systems – what and why?. Covered in this lecture Systems and systems thinking Why we use Systems Engineering Systems from “cradle.
1 CS Tutorial 5 Frid. Oct 23, 2009 Design Document Tutorial.
Lecture 8: 9/19/2002CS149D Fall CS149D Elements of Computer Science Ayman Abdel-Hamid Department of Computer Science Old Dominion University Lecture.
C o n f i d e n t i a l 1 Course: BCA Semester: III Subject Code : BC 0042 Subject Name: Operating Systems Unit number : 1 Unit Title: Overview of Operating.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
Project Deliverables CEN Engineering of Software 2.
Chapter 1: Introduction to Systems Engineering April 2012.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 31. Review Creational Design Patterns – Singleton Pattern – Builder Pattern.
20CC Ltd Independent Consultants © 20CC Ltd Systems Thinking Overview Sources from The Open University acknowledged.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Computer Based Systems Stage 2 Information Technology Studies Computer & Communication Systems.
Copyright (c) 2014 Pearson Education, Inc. Introduction to DBMS.
MIS.
Math 1411 Chapter 1: Limits and Their Properties 1.5 Infinite Limits.
Lecture 11 Lecture 5 Report Writing I (Problem definition to concept selection)
Advanced Higher Computing Science The Project. Introduction Worth 60% of the total marks for the course Must include: An appropriate interface using input.
 System Requirement Specification and System Planning.
Chapter 4 : Network models. Lecture 8. Layered Tasks - We use the concept of layers in our daily life. As an example, let us consider 2 friends who communicate.
Logical Architecture and UML Package Diagrams. The logical architecture is the large-scale organization of the software classes into packages, subsystems,
A framework for Web science didactics michalis vafopoulos
HEADING OF PRESENTATION. HEADING OF PRESENTATION.
<<Project Name>> <<Team Members>>
Infrastructure Delivery Management Toolkit:
The Object Oriented Approach to Design
Lecture Software Process Definition and Management Chapter 3: Descriptive Process Models Dr. Jürgen Münch Fall
تكملة الوحدة الاولى الفصل الثاني بالكتاب للاطلاع ثم الفصل الثالث التخطيط لبناء الاختبارات التحصيلية الفصل الثالث من الكتاب (87-164)
Software Engineering Lecture #14.
Planning Theory Theory is a way of understanding the world, a framework for our interpretation of facts and experience. Theory has to be applied Praxis:
Tentative Title: XXXXXX
Requirements Document
<Project Title>
Week1 software - Lecture outline & Assignments
Requirements Engineering Lecture 6
Meta-Data: the key to accessing Data and Information
Designing Scalable Architectures
Presentation transcript:

BT 1005 Managing Information Lecture 1 Introduction to Information Systems: Information Systems Concepts

Contents Systems Approach Systems Boundaries Opened and Closed systems Systems Properties

Systems Approach Definition –usually along the lines of: “a series of parts, interconnected for the purpose of reaching a specific aim.”

Systems InputProcessingOutput

Systems InputProcessingOutput Feedback Control Storage

Systems Approach (cont’d) Systems are made of component parts A hierarchy can exist in the description of the system A change in one part could effect the whole system

Systems Boundaries Defines the scope of the system Can have problems when: –responsibilities overlap or –there are ambiguities of function

Opened and Closed systems Open – interact with external environment –Not to be confused with open architecture (any software on any machine) Closed – self contained

Hard and Soft properties Hard properties –Technical –Specific –Clearly defined Soft –Qualitative –Vague (fuzzy)

Summary Systems Approach – looks at whole system and its effects Boundaries should be defined Can be Open or Closed Can have Hard and/or Soft properties

Here endeth the first lesson Any Questions?