Search in the document preview
Learning outcomes of the course
On the completion of this course, the student should be able to:
• Understand the concepts of information systems • Use System Development Life Cycle (SDLC) in real‐world cases • Analyze the current information system in the organization • Design and implement proper information systems in the organization • Use Data Flow Diagram, Data Dictionary and other analysis and design tools in proper
On the completion of this course, the student should be able to develop the following practical skills
• To apply some of the analysis and design techniques in a systems development situation
• To communicate requirements for business functionality of an information system in terms of data required, data storage and processing
• To participate effectively in an information systems development project conducted within the context of the classroom situation
CIS 306: Information Systems Analysis & Design
Semester:Office Hours: To be announced Category: TA for the Course:
Bachelor in Computer and Information Sciences
Course Code (Credit hrs)
(CIS 306) Information Systems Analysis and Design (3 Credit hrs) 1 Contact Hour is equivalent to 60 minutes. 1 Lab credit is equivalent to 3 contact hours.
Description The aim of this course is to provide students with an opportunity to learn the
basic knowledge (knowing) and skills (doing) to specify and to develop computer information systems. The course will focus on the front‐end of the system development life cycle (SDLC), by examining in some details the techniques, methods, tools, procedures, and methodologies employed by systems analysts in the analysis, design and implementation of organizational information systems. This course introduces established and evolving methodologies for the analysis, design, and development of an information system. Emphasis is placed on system characteristics, managing projects, prototyping, CASE/OOM tools, and systems development life cycle phases. Upon completion, students should be able to analyze a problem and design an appropriate solution using a combination of tools and techniques.
Objectives The students are expected to be able to:
1. Develop the needed communication and analytical skills to solicit, identify, analyze and refine loosely structured user requirements to produce a meaningful system design specification. Describe the key concepts, major objectives, task set, and tools used in each phase of the SDLC.
2. Distinguish between the different software process models (waterfall, iterative, prototyping, spiral), and describe their characteristics.
3. Describe the major systems development methodologies (SADT, RAD, JAD, participatory, OOAD etc.) of systems development and the criteria for their selection.
4. Communicate with potential systems users effectively and professionally, to elicit, clarify, define and refine user requirements.
5. Conduct an analysis of the information requirements of an organization to model its information processing needs.
6. Produce appropriate system specifications and documentation at each phase of the system development life cycle. This will include but not limited to input and output screens, forms, queries, reports and user dialogues.
7. Demonstrate the ability to use the different systems analysis & design diagramming techniques including: data flow diagrams (DFD), entity relationship diagrams (ERD), structure charts, pseudo‐code, decision tress and tables, use‐case diagrams, class diagrams etc.
8. Demonstrate the ability to use project management tools, such as PERT, CPM, and Gantt chart to manage a project.
9. Produce a project plan that is both feasible and conformance to systems requirements, including the conduct of a formal feasibility or break‐even analysis.
10. Conduct a real‐life systems project in a team environment. 11. Demonstrate the ability to communicate effectively in both written and oral
forms during systems development progress report sessions.
Pre-requisites Object‐oriented Analysis and Design
Textbooks/Co urse URL
Course Text: 1. Hoffer, J.A., George, J.R. and Valacich, J.S. 2005, Modern Systems Analysis
& Design, 4th Ed., Prentice Hall; Upper Saddle river, NJ. Recommended Books:
1. Kendall, K.E. & Kendall, J.E. 2002, Systems Analysis and Design, 5th Ed., Prentice Hall: Upper Saddle River, NJ.
2. Whitten, J.L., Bentley, L.D., & Dittman, K.C. 2004, Systems Analysis and Design Methods, 6th Ed., McGraw‐Hill Irwin: New York, NY.
3. Satzinger, J.W., Jackson, R.B., & Burd, S.D. 2002, Systems Analysis and Design in a Changing World, 2nd Ed., Course Technology: Cambridge, MA.
4. Shelly, G.B., Cashman, T.J., & Rosenblatt, H.J. 2001, Systems Analysis and Design, 4th Ed., Course Technology: Cambridge, MA.
Resource Material: Drawing or diagramming software tools may be found at:
(a) SmartDraw site: http://www.smartdraw.com (Free software download available) (b) Microsoft Visio site: http://www.microsoft.com/office/visio/, (This software is available in Lab SSS 203. Alternatively, you may purchase a copy under the UW academic license agreement with Microsoft)
Course URL: http://www.pieas.edu.pk/umarfaiz
Semester Project: This semester project is the group work only. So, the individual work is not allowed. Form the team of three (3) members to design the new computerized information system to replace the existing one. All team members will receive the same mark for that project, but there will be opportunity for team members to submit a confidential report to the instructor if they feel that another member(s) is not putting in the appropriate amount of effort. The instructor reserves the right to scale the marks for individual student if deemed necessary, naturally after verifying the alleged situation. Start by preparing the proposal of your project to identify the reason and need of designing the new system. Content in the proposal: Your proposal must contain following topics: Introduction of project • General Information • Overview of problems in current system • Objectives • Expected result • Project scope • Current system analysis • New system development plan
The deadline for different phases will be announced in the class.
Lectures, Tutorials & Attendance
Teaching Method(s): Lecturing Teaching Media:
Policy Slides, handouts There will be 48 sessions of 60 minutes each 80% attendance is mandatory
Grading/ Grading Policy
Quizzes 15% Sessional I/Sessional II 35% Final Exam 50% (Grades will be given as per PIEAS’ Policy (see prospectus for further details) There will be absolutely no makeup quizzes. Makeup midterm will only be allowed in case of extreme emergency. Contact the instructor as soon as the emergency permits to discuss possible course of action depending on the extremity of the emergency. For credit all assignments must be turned in time. Late assignments will not earn any credit but to get a passing grade all assignments must be eventually turned in.
Regulations In addendum to Institute’s policy following rules will be strictly adhered to:
1. Attendance: Students are expected to attend course sessions. In case of any absence, students are responsible to make up for the course covered in the missed session. Attendance profile is consistently compiled and updated at the department and it is mandatory to meet the minimum requirements of 80% to qualify for appearance in the final examination.
2. Class Behaviour: Cell phones must be turned off when the student enters the classroom. Disruption of class by a cell phone may lead to expulsion from the class.
3. Academic Honesty: Academic integrity is the foundation of the academic community. Each student has the primary responsibility for being academically honest, students are advised to read and understand all sections of this policy relating to standards of conduct and academic life.
4. Plagiarism: Plagiarism involves the use of quotations without quotation marks, the use of quotations without indication of the source, the use of another's idea without acknowledging the source, the submission of a paper, laboratory report, project, or class assignment (any portion of such) prepared by another person, or incorrect paraphrasing.
Plagiarism and cheating are regarded as very serious offences. In cases where cheating has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level.
Enclosures: • Attendance Record: • Table of Specifications: • Question Papers (Sessional I + Sessional II + Final):
• Marking Scheme (Model Answers + Checking Hints): • Assignment Topics: • Quizzes: • Case Studies/Class Participation: • Evaluation Sheet:
CIS 306: Information Systems Analysis & Design
1-5 Part One The Context of Systems Development Projects Chapter 1 The Context of Systems Analysis and Design Methods Chapter 2 Information Systems Development Chapter 3 Project Management
6-24 Part Two Systems Analysis Methods Chapter 4 Systems Analysis Chapter 5 Fact‐Finding Techniques for Requirements Discovery Chapter 6 Modeling System Requirements with Use Cases Chapter 7 Data Modeling and Analysis Chapter 8 Process Modeling Chapter 9 Object‐Oriented Analysis and Modeling Using the UML Chapter 10 Feasibility Analysis and the System Proposal
24-42 Part Three Systems Design Methods Chapter 11 Systems Design Chapter 12 Application Architecture and Modeling Chapter 13 Database Design Chapter 14 Output Design and Prototyping Chapter 15 Input Design and Prototyping Chapter 16 User Interface Design Chapter 17 Object‐Oriented Design and Modeling Using the UML
43-48 Part Four Beyond Systems Analysis and Design Chapter 18 Systems Construction and Implementation
Weekly Course Plan (Table of Specifications) Week# Lecture# Reading Topics Homework Week1 Lecture 1 Hoffer et al.
Chs 1-3, Appendix 1 Introduction The Systems Development Environment
Lecture 2 The Systems Development Environment (cont’d)
Lecture 3 The Systems Development Environment (cont’d)
Week2 Lecture 4 Hoffer et al. Chs 3, 4 & 5
Succeeding as a Systems Analyst
Lecture 5 Succeeding as a Systems Analyst
Lecture 6 Succeeding as a Systems Analyst
Week3 Lecture 7 Hoffer et al. Chs 6 & 7
Systems Analysis 1: Analysis phase, data gathering and use of models
Lecture 8 Lecture 9 Week4 Lecture 10 Hoffer et al. Chs 7 &
Appendix 2 Systems Analysis 2: Process modelling/ DFDs, Automated tools, MS Visio
Lecture 11 Lecture 12 Week5 Lecture 13 Hoffer et al. Chs 7 &
8 Systems Analysis 3: Process modelling/ DFDs; Logic modelling
Lecture 14 Lecture 15 Week6 Lecture 16 Hoffer et al. Ch 9 Systems Analysis 4: Data
modelling/ E-R models
Lecture 17 Lecture 18 Week7 Lecture 19 Hoffer et al. Ch 9 Systems Analysis 5: Data
modelling/ E-R models
Lecture 20 Lecture 21
Week8 Lecture 22 Hoffer et al. Appendix
3 Systems Analysis 6: Overview of Object-Oriented Approaches
Lecture 23 Lecture 24 Week9 Lecture 25 Hoffer et al. Ch 10 Systems Design 1: Overview
of design phase, design alternative, database design
Lecture 26 Lecture 27 Week10 Lecture 28 Hoffer et al. Chs 11 &
12 and an interface design text
Systems Design 2: Designing forms & reports; user interface design
Lecture 29 Lecture 30 Week 11 Lecture 31 Hoffer et al. Chs 13 Systems Design 3: Designing
system architecture; finalising design specifications
Lecture 32 Lecture 33 Week 12 Lecture 34 Hoffer et al. Chs 14
and interface design text
Systems Design 3: Designing system architecture; finalising design specifications
Lecture 35 Lecture 36
Week 13 Lecture 37 Hoffer et al. Chs 15 Systems Implementation &
Lecture 38 Lecture 39 Week 14 Lecture 40 Hoffer et al. Chs 6 Systems Implementation &
Lecture 41 Lecture 42 Week 15 Lecture 43 Review of issues and
trends in systems analysis and design; Revision; Unit evaluation
Implementation phase activities and documentation
Lecture 44 Lecture 45 Week 16 Lecture 46 Lecture 47 Lecture 48
Term Paper Topics
Risk Analysis Business Process Reengineering Testing Concepts Change Control Object Oriented Concepts as they apply to Software Engineering Rapid Application Design Project Management Software Team Taxonomy Measuring Quality Quality Assurance Data Modeling Structured Analysis Validation Testing Component Based Development