ANALISIS KEBUTUHAN DAN PERANCANGAN SISTEM INFORMASI (REQUIREMENT ANALYSIS AND DESIGN OF INFORMATION SYSTEMS)

 

 

Concepts, Techniques, Methods and Applications

 

 

 

 

 

 

Course Syllabus

 

 

 

 

 

 

 

 

 

 

 

 

Academic Staff

Faculty of Computer Science

University of Indonesia

UNIVERSITY OF INDONESIA

FACULTY OF COMPUTER SCIENCE

COURSE SYLLABUS

REQUIREMENTS ANALYSIS AND DESIGN OFINFORMATION SYSTEMS

 


Instructor  :Wahyu Catur Wibowo & Farisya Setiadi                Office   : MTI, Salemba UI

Class hours : Tue: 19:00-21:30                                           Fasilkom R. 3201, Depok       

                        Thu: 19:00-21:30                         Office hours :Tue, 17:00-18:00             

E-mail          : wibowo@cs.ui.ac.id         

Course Website: http://wcw.cs.ui.ac.id/teaching/akps_2018_2019_2       

                       

 

Description

This course focuses on the System Requirements Analysis, Design, and Implementation of Information Systems (SRADIIS). SRADIIS involves understanding the nature of user’s and organization’s information needs and how to capture those needs and use them for the Design and Implementation of Information System in order to achieve organization’s objectives.  The SRADIIS should be an integrated approach of human-computer interaction which may result in adaptable Information Systems.  It is cannot be considered as a one-sided or single component. It is an interrelated process as it evolves to respond to growth and changes in technologies advancement, organization’s environment, organization’s mission and objectives, organization’s management and users’ information needs.

 

The course will to a large extent deal with concept of SRADIIS, methodologies of how to conduct SRADIIS so that organization’s performances can be improved.  Various approaches used in the methodology will be discussed including the use of various methods, techniques, processes, procedures, and tools. Beside that, this course will explore the role of SRADIIS that have moved from having a peripheral stand alone function in an organization (just a support systems) e.g. like catering, to having a core function (enabler) in driving profitability and competitiveness in many ways - producing quality of information, improve decision making and improve resource sharing. The Analysis, Design and Implementation of Information Systems should be able to improve competitiveness and sustain strategic position of an organization.

 

Evaluation will be based on participation, individual assignments, group project, quizzes, presentations, and exams.

 

Course Objectives

 

The objectives of the course are 1) to understand the basic concept of SRADIIS, 2) to understand various approaches in SRADIIS and, 3) to exercise a full cycle of SDLC in the SRADIIS in the real world.        

 

Required Reading

 

Dennis, et. al., “Systems Analysis & Design: An Object Oriented Approach with UML 5th ed”, John Wiley & Sons, 2015.

Additional Reading

 

·         Satzinger, John W., Robert B. Jackson, and Stephen D. Burd. Systems analysis and design in a changing world. Cengage learning, 2011.

·         Bentley, Lonnie D., and Jeffrey L. Whitten. Systems analysis and design for the global enterprise. Vol. 417. New York: McGraw-Hill, 2007.

·         Knapp, Jake, John Zeratsky, and Braden Kowitz. Sprint: How to solve big problems and test new ideas in just five days. Simon and Schuster, 2016.

·         Other reading materials will be assigned in class.

 

Method of Teaching Delivery

 

The lecture will be delivered using dual-mode (combination of face-to-face and online through SCELE). All the class materials will be available on SCELE.

 

Assignments

 

Readings. Readings are an essential part of your effort to understand the materials. I suggest that you read ahead and use class time to ask questions that weren’t clear in the readings or to share your thoughts with the class.

 

Participation. Your present in the class, in SCELE, and involve in subject matter discussion are count toward your class participation.  You are invited to respond to the course materials. Please share your comment, question, experience, etc., and be the first to invoke discussion—in class as well in discussion forum in SCELE.

 

IS Project Initiation. IS project initiation is one-page responses to a particular need of IS in an organization. The assignment will be handed one week prior to when they are due. The purpose of this exercise is to hone your critical thinking skills to initiate IS project in an organization.

 

Quizzes. There will be quizzes delivered in class as well as through SCELE. It may no notification being made in advance to deliver quiz. Quizzes provide immediate feedback on previous materials and will be administered at the end of each topic. You have to be ready anytime for a short time quiz as a medium for immediate feedback. Quizzes account for a portion of your participation grade, which constitutes 10 percent of your grade.

 

Final Project and Class Presentation. Each group of students will develop a new project. The project shall address a particular problems and a particular methodology in the SRADIIS: actions proposed to address the problem, steps involved, methods and techniques used, a description of how the project meets the technical and business needs of the requirements, and the implementation. The project shall include a working prototyping system, report and contain approximately 20-25 pages (1.5 spaced, plus bibliography and appendices).

 

Exam. The mid-term exam will cover the topics discussed in the class of the semester.

 

Assessment

 

Your final grade will not rest on one or two assignments but will be based on how many points you accumulate throughout the semester. My view is that this would better reflect your learning process and would minimize anxiety associated with exam. The weights assigned to each component are as follows:

 

Participation

7.5%

Quiz 1

5%

Quiz 2

5%

Mid-term examination

15%

Project Initiation

7.5%

Project Plan & Feasibility Analysis (Group)

10%

System Proposal (Group)

20%

System Design & Implementation (Group)

20%

Group presentation

10%

Total

100%

 

Class Policies and Teaching Delivery

 

Attendance  Students are expected to attend class regularly. There are 75% minimum attendance requirements (UI’s policy!), and attendance sheets will be passed out and will be factored into your participation grade. In the case of absence, students are responsible to stay current on information regarding materials covered in class and any changes in schedule.

 

Late Assignments. For each day an assignment is turned late, the total grade will be deducted 5 (five) points. If you have a justified reason for not turning the assignment on time (e.g., due to extenuating circumstances), please let me know prior to the due date. I want to be flexible, yet fair to other students in the class. All late assignments are to be turned in to the secretary or to special different digital box.

 

Academic dishonesty and Incompletes. Each student should be familiar with the guidelines set in the “Code of Student Ethics” for issues pertaining to academic dishonesty. No incompletes (I) will be assigned. There will be no makeup exams unless prior notice is given and documentation of emergency is given.

 

Dual-mode teaching delivery is adopted, face-to-face teaching and through SCELE.There will be an intensive class and electronic discussions on the course’s topics.         

 

Grades (rounded to the nearest number):

           

A

>90

A-

>85 – 90 

B+

>80 – 85

B

> 75 – 80

B-

> 70 – 75

C

65 – 70

D

<65

Lesson Plan (16 weeks)

 

Week

Topic

Learning Outcomes

Assessment

Readings

1

Course Overview

·         Course syllabus

 

Introduction

·         System, information systems (IS), and types of IS

·         The systems development life cycle

·         Evolution of systems development methodologies

·         System analyst roles and skills

·         The traditional method vs. object-oriented method

 

IS Project Planning & Management

·         Project identification

·         Feasibility analysis

·         Project selection

·         Creating and managing workplan

·         Staffing the project

·         To understand the basic concept of IS

·         To understand the evolution of system development methodologies

·         Understand the fundamental systems development life cycle

·         Define the roles and skills of a system analyst

·         Describe and explain the differences between two overall approaches to IS development

·         Understand the importance of linking the information systems to business needs

·         Be able to create a system request

·         Understand how to assess technical, economic, and organizational feasibility.

·         Be able to perform a feasibility analysis.

·         Understand how projects are selected in some organizations.

·         Become familiar with estimation.

·         Be able to create a project workplan (WBS, Gantt Chart, Pert chart).

·         Become familiar with how to staff a project.

·         Understand how computer-aided software engineering, standards, and documentation improve the efficiency of a project.

·         Understand how to reduce risk on a project.

Assignment #1 (Announced)

Satzinger ch. 1,

 

Bentley ch. 1,

 

Dennis

ch. 1-2

 

 

2

Requirements Analysis

·         Requirements definition

·         Requirements analysis strategies

·         Requirements gathering techniques

·         The system proposal

·         Understand how to create a requirements definition.

·         Become familiar with requirements analysis techniques.

·         Understand when to use each requirements analysis technique.

·         Understand how to gather requirements using interviews, JAD sessions, questionnaires, document analysis, and observation.

·         Understand when to use each requirements-gathering technique.

Assignment #1 (Due)

 

 

Assignment #2 (Announced)

 

 

 

Quiz #1

Dennis

ch. 3

3

Functional Modeling

·         Use-case diagram

·         Use-case description

·         Activity diagram

·         Verifying and validating functional models

·         Understand the rules and style guidelines for activity diagrams.

·         Understand the rules and style guidelines for use cases and use-case diagrams.

·         Understand the process used to create use cases and use-case diagrams

·         Be able to create functional models using activity diagrams, use cases, and use-case diagrams.

·         Be able to verify and validate functional requirements

 

Dennis

ch. 4

4

Structural Modeling

·         CRC cards

·         Class diagram

·         Object diagrams

·         Understand the rules and style guidelines for creating CRC cards, class diagrams, and object diagrams.

·         Understand the processes used to create CRC cards, class diagrams, and object diagrams.

·         Be able to create CRC cards, class diagrams, and object diagrams.

·         Understand the relationship between the structural and use case models.

Assignment #2 (Due date)

 

 

Assignment #3 (Announced)

Dennis

ch. 5

5

Behavioral Modeling

·         Crude analysis

·         Interaction diagram

·         Behavioral state machines

·         Understand the rules and style guidelines for sequence and communication diagrams and behavioral state machines.

·         Understand the processes used to create sequence and communication diagrams and behavioral state machines.

·         Be able to create sequence and communication diagrams and behavioral state machines.

·         Understand the relationship between the behavioral models and the structural and functional models.

 

Dennis

ch. 6

6.

Moving on to Design

·         Verifying and validation the analysis models

·         Design strategies

Selecting an acquisition strategy

·         Understand the verification and validation of the analysis models.

·         Understand the transition from analysis to design.

·         Be familiar with the custom, packaged, and outsource design alternatives.

·         Be able to create an alternative matrix.

Assignment #3 (Due date)

 

Assignment #4 (Announced)

Dennis

ch. 7

7.

User Experience Design & Human-Computer Interaction

·         Principles for user interface design

·         User interface design process

·         Navigation design

·         Input design

·         Output design

·         Mobile computing and social media user interface design

·         International and cultural issues

Non-functional requirements in user interface design

·         Understand several fundamental user interface (UI) design principles.

·         Understand the process of UI design.

·         Understand how to design the UI structure.

·         Understand how to design the UI standards.

·         Understand commonly used principles and techniques for navigation design

·         Understand commonly used principles and techniques for input design.

·         Understand commonly used principles and techniques for output design.

·         Be able to design a user interface.

Understand the effect of nonfunctional requirements on the human-computer interaction layer.

-

Dennis

ch. 9

8.

Mid semester test

·         -

Midterm test

-

9

Physical Architecture Design

·         Elements of the physical architecture

·         Cloud computing

·         Ubiquitous computing and the Internet of Things (IOT)

·         Greet IT

·         Infrastructure design

·         Nonfunctional requirements in physical architecture design

·         Understand the different physical architecture components.

·         Understand server-based, client-based, and client–server physical architectures.

·         Be familiar with distributed objects computing.

·         Be able to create a network model using a deployment diagram.

·         Understand how operational, performance, security, cultural, and political requirements affect the design of the physical architecture layer.

·         Be familiar with how to create a hardware and software specification.

 

Dennis

ch. 10

10

Construction, Testing, Installation and Operations

 

·         Managing programming

·         Developing documentation

·         Designing tests

·         Cultural issues and information systems adoption

·         System conversion plan

·         Change management

·         System support and maintenance

·         Be familiar with the system construction process.

·         Understand different types of tests and when to use them.

·         Understand how to develop documentation.

·         To be familiar with system installation process

·         To understand different types of conversion strategies and when to use them

·         Understanding techniques for managing change

·         Be familiar with post-installation processes such as system support and system maintenance.

Quiz #2

Dennis

ch. 12, 13

11

 

 

-

Dennis

ch. 13

12

Agile (Scrum)

·         Be familiar with contemporary agile technique, Scrum

·         Understanding when to use Scrum compared to other methodologies

 

Sutherland

13

Design Sprint

·         Two-hour workshop

·         30-minute prototype demonstration

 

Knapp

13

Course Review and Summary

-

Assignment #4 (Due)

 

14

Assignment Presentation

-

-

 

15

Assignment Presentation

-

-

 

16

Assignment Presentation

-

-

 

 

 

Document Revision History

 

No.

Version

Date

Description

Author

1.

2.0

20th August 2017

-

Zainal A. Hasibuan

2

3.0.

24th August 2017

New lesson plan with learning outcomes and additional reading.

Panca Hadi Putra

3.

3.1.

25th August 2017

Assessment component.

Panca Hadi Putra

3.

3.2.

29th August 2017

Assessment schedule.

Panca Hadi Putra

4.

3.3.

4th September 2017

Assessment component (removed final exam) and assessment schedule.

Panca Hadi Putra

5.

3.4.

2nd October 2017

Assessment component.

Panca Hadi Putra

6.

3.5.

26th January 2018

Week 1 and 2 combined. New material for week 12.

Panca Hadi Putra

7.

3.6

1st September 2018

Added agile (scrum) in week 12.

Panca Hadi Putra

 

 

 

 

[END OF DOCUMENT]