Teaching Systems Analysis and Design in a Practical Way: A Collaborative Effort Between Computer Science and Business School by Ken Surendran-CS Chellappa.

Slides:



Advertisements
Similar presentations
Systems Investigation and Analysis
Advertisements

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
NET Section, CDI. Grammar and e-learning for Communication (GEL.com) This project: was launched initially with a view to encouraging participating schools.
The System Development Life Cycle
Sept-Dec w1d21 Third-Generation Information Architecture CMPT 455/826 - Week 1, Day 2 (based on R. Evernden & E. Evernden)
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
IS6112 Application Modelling and Design Introduction.
System Analysis and Design (SAD )
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Lecture 13 Revision IMS Systems Analysis and Design.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
12 C H A P T E R Systems Investigation and Analysis and Analysis.
Requirements Analysis Concepts & Principles
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
Analysis Concepts and Principles
Lab 1 Introduction Project Definition. Introduction and Project definition 2 Objective To give the Student an overview of the Lab Environment and tools.
Systems Development Life Cycle
System Development Life Cycle (SDLC)
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
IMS Information Systems Development Practices
CORE 1: PROJECT MANAGEMENT Overview TECHNIQUES FOR MANAGING A PROJECT Communication Skills Active Listening Mirroring Paraphrasing Summarizing Clarifying.
Software Development Process
Issues in Teaching Software Engineering Virendra C. Bhavsar Professor and Director, Advanced Computational Research Laboratory Faculty of Computer Science.
1 Introduction Chapter 1. 2 Key Ideas Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Managing the development and purchase of information systems (Part 1)
Introduction to SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2009.
Requirements Analysis
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Simplicity First: Use of Tools in Undergraduate CS and IS Teaching By David Naugler and Ken Surendran Southeast Missouri State University Computer Science.
ITEC224 Database Programming
Chapter 14 Information System Development
Systems Analysis and Design
CS206 System Analysis and Design Note 1 By ChangYu 1 Course Information Lecturer NameCHANG YU Web sitewww.chuhai.edu.hk/changyu/
2 Information Systems Chapter 12 Systems Development: Investigation and Analysis.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 1: Introduction to Systems Analysis and Design Alan.
A DESIGN AND IMPLEMENTATION COURSE FRAMEWORK: A CURRICULUM PROPOSAL FOR AN EXPERIENTIAL APPROACH TO THE SYSTEMS ANALYSIS AND DESIGN AND THE PROJECTS IN.
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Department of Industrial Engineering Sharif University of Technology Session #8.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Engr. Fawad Riasat Raja (UET Taxila) 1 LAB # 01 Introduction to SE-308 Labs Software Engineering-II.
IS2210: Systems Analysis and Systems Design and Change Twitter:
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
The Level-2 Projects for Course Clusters Haojun Sun College of Engineering Shantou University.
SYSTEM ANALYSIS AND DESIGN LAB NARZU TARANNUM(NAT)
Systems Analysis & Design David Walkiewicz March 31, 2012.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
MANAGEMENT INFORMATION SYSTEM
The System Development Life Cycle
Systems Development Life Cycle
Software Engineering cosc 4359 Spring 2017.
Information Systems Development
Fundamentals of Information Systems, Sixth Edition
Systems Analysis & Design N106
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
Concepts used for Analysis and Design
System Development Life Cycle (SDLC)
Overview of System Engineering
The System Development Life Cycle
Chapter 1 (pages 4-9); Overview of SDLC
System Development Life Cycle (SDLC)
CS 8532: Advanced Software Engineering
Chapter 12 Systems Development: Investigation and Analysis
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Systems Development Life Cycle
Information Systems Development (ISD) Systems Development Life Cycle
Presentation transcript:

Teaching Systems Analysis and Design in a Practical Way: A Collaborative Effort Between Computer Science and Business School by Ken Surendran-CS Chellappa Somarajan – MIS, SEMO Ike Ehie – MG, KSU

Cross -listed SA&D Facilitation: Agenda MIS & CS Curricula and SA&D Courses Course objectives and Syllabi Project-based assessment Managing Composite team Student feedback and analysis Problem avoidance Suggestions for future consideration

MIS & CS Curricula MIS Curriculum- IS2002 Model Courses 1Analysis & Logical Design 2. Physical Design & Implementation with DBMS 3. Physical Design & Implementation with in Emerging Environ. In MIS–SA&D (MG445) System Implementation & Practice (follow on) CS Curriculum-CC2001 Under CSBOK Areas 1.Human-Computer Interaction 2. Information Management 3. Software Engineering In Applied CS – ISA&D (IS445), Software Engineering (follow on)

Cross-listing MG445 and IS445 MG445 (SA&D) Pre-requisite: Business Database systems and a programming course Business focus Procedure paradigm and some introduction to Object-Orientation IS445 (ISA&D) Pre-requisite: A second level IS course (with database emphasis) IT-solution implementation focus ISA&D – procedure SE – object paradigm

Cross -listed SA&D Overview Principles and techniques used in Analysis and design aspects of system development. Uses techniques tools of procedure-centric structured methodology Some elements of OO to use Rational Rose Text: Dennis & Wixom SA&D: An Applied Approach Four areas: System planning, Requirements spec., Design spec., Implementation (GUI and prototypes)

Topics Overview: SDLC, Development paradigms, Roles and skills in SDLC activities Planning: Proposal, Feasibility (cost-benefit, operational, technical), Project Plan Analysis: Strategies, Info gathering, context, process and data models (DFD – levels of DFD & EFD) Design: Architectural design, design strategies, physical models, program design, database design, I/O deign (User Interface), Test case designs

Topics - Continued Implementation: Testing, implementation issues OO paradigm: UML, use-case, finding analysis classes, Interaction diagrams, class design, relationships and operations

Business plus IT-Solution Focus Plan Analysis & Design Implementation. Business FocusIT-Solution Focus

Assessment 50% tests and exams 50% group project Composite team (at least one CS and one MIS) of four / five. Instructor simulates a real-life case study (Transport company; educational software unit within University; Conference Registration system)

Project Four phases: 1.Proposal plus feasibility (10%) 2.Requirements Spec (15%) 3.Design Spec. (15%) 4.Implementation – prototype (10%) Interview, questions used for info gathering List of deliverables for each phase (e.g. for Phase-1: current situation, system objectives, solution description, resources needed, cost-benefit – NPV, technical and operational feasibility, schedule, conclusion- risks,if any)

Team Management Team leader for each phase Overall workload balance Plan - Who does what Project meetings (outside class) Project review (in class) Collaboration (Business & technical aspects) Integration of all outputs Work on mini cases – in class Tests and exams – have questions relating to project

Course Facilitation Evaluation Instruments Questionnaire – Primary Exit interview - Secondary Individual reflection – Secondary (part of last phase delivery) MIS exit interview: Very positive; compete in national A&D competition; experience actual implementation Individual: work as a team; tasks best suited, learned time management, active involvement ‘I know I want to be business analyst’

Questionnaire Twelve questions: project phasing, team composition, roles played, workload balance, skill balance, functioning of team, learning aspects, real-world experience, overall experience. 80% liked the idea of working in teams and 90% considered a positive experience, overall. 75% considered it offered real-world experience (real requirements, stress and strain of working with people of different personalities, background) All liked the idea of working on a single project with phased delivery. Several roles: each played at least 3 of the 8 roles

Problem avoidance (Role of the instructor) Provide realistic cases in stages Give feedback after each phase Alter requirements / situations slightly in the second and third phase Bring all the teams to same level at the start of each phase Liaise with team leader Observe and take corrective action. Direct team for conflict resolution.

Suggestions Let the teams learn through experience Provide additional examples (from past class work) Provide customized review for each team and also discuss common problems in class Insist on quality & meeting deadlines Ensure deadlines are met Encourage innovative solution Plan for in-class team meetings