Anda di halaman 1dari 8

Course Title: Systems Analysis & Design Course Code: ITDR3101

Year: Credit Hours: 3 hours


Coordinator:

Sem.:
Contact Hours: 4 hours
Class lecturer: Office:

COURSE DESCRIPTION

Two key phases in any System Development Life Cycle (SDLC) are:

(1) The accurate discovery and analysis of user requirements and;


(2) The design of a system that satisfies these requirements.
This course addresses both. It is essential to understand the problem and associated context. This
helps ensure development of the best computing solution. Techniques such as identifying
stakeholders and their interests, discovering and documenting information needs, and clarifying
associated processes, all help to define the problem domain more accurately. ITDR3101 discusses
methods for capturing, documenting and analyzing these requirements.
Recently, object- oriented design has gained momentum because of the wide acceptance of object
modeling using the Unified Modeling Language (UML). ITDR3101 covers object-oriented analysis
and design, user and system interface design, and database design. The course emphasizes iterative
development with three-layer architecture, information gathering and management reporting in detail.

COURSE PREREQUISITE (S): ITDR2106

List of needed Materials

Provided by the Provided by the


No. Materials Description
College Students
MS PowerPoint
Lectures Yes
slides
Student Lab
PDF Yes
Book
Tutorials PDF Yes

Graduate Attribute:

A3, A4, A5, A6, A9

Course objectives:
To understand the principles of and motivation behind systems analysis and design and where
they fit in the context of systems development.
To understand how to successfully gather, analyze, and manage user requirements in
preparation for system design.
Acquire skills in Object-Oriented (OO) concepts and techniques.
To be conversant with the use of Computer Assisted Software Engineering (CASE) tools such
as Sybase Power Designer (15.5) that supports a particular design paradigm.

Learning Outcomes:

On successful completion of course ITDR3101, students will be able to:


1. Identify stakeholders and describe their roles in system development.
2. Identify problem/opportunity, cause/effect and business requirements for a given problem
scenario.
3. Perform systems analysis traditional tasks:
a. Problem analysis
b. Requirements analysis
4. Describe the principles, terminology and techniques associated with the OO paradigm.
5. Know the syntax and semantics of the Unified Modeling Language with respect to modeling
use case diagrams, class diagrams, activity diagrams, interaction diagrams, state machine
diagrams, package diagrams and deployment diagrams.
6. Understand object-oriented concepts such as: association, aggregation and composition;
polymorphism and generalization; messaging and object interaction, state and lifespan of
objects.
7. Be able to perform a systems analysis & design activity on a small-scale system using the
UML.
8. Distinguish logical versus physical models and translate logical process and data models into
physical design models using design software.
9. Be able to explain what is involved in implementing, testing, installing, deploying a system in
its final operating environment.
10. Communicate both orally and in writing as an individual and as a member of a team
Course working plan:

Lecture Lab

Introduction to Course
Outline,
Case Study- A larger
Ridgeline Mountain
An Overview of System
Outfitters (RMO) project is
Development, Objectives
introduced that will be used
of Analysis and Design,
throughout the course to
System Development Life
Lecture1 and Lab1

illustrate analysis and


Cycle,
design.

Introduction
Characteristics of iterative
Tutorial 1: An Overview of
system development
Week 1

System Development.

Systems Analysis
Activities, Tutorial 2: Requirements
Investigating Requirements

Analysis.
What Are Requirements?
Introduction to Project and
Lecture2 and Lab2

Models and Modelling, Team Building and discuss


the ideas.
Stakeholders,
Additional Reading: The
Week 2

Information-Gathering Role of the Systems Analyst.


Techniques

Tutorial 3: Use Cases in the


Use Cases and User Goals.
Ridgeline Mountain
Outfitters Case
Lecture3 and Lab3

Use Cases and Event


Decomposition,
Lab1: Introduction to CASE
Tool,
Use Cases

Use Cases and CRUD,


Week 3

Lab 2: Drawing Use Case


User Case Diagrams,
Diagrams

Domain Modelling,
Tutorial 4: Domain model
Class diagrams for RMO
Identify and analyze
Consolidated Sales and
Domain Entities and
Lecture4 and Lab4

Domain Modeling

Marketing System.
Domain Classes,
Lab3: Drawing Class
Create an entity-
Diagrams and Entity
relationship diagram,
Week 4

Relationship Diagrams using


Create a domain model
CASE tool.
class diagram
Requirements Models Requirements Models
Activity Diagrams for Use

Lecture5 and Lab5


Tutorial 5: Activity diagrams
Cases, Basic concepts

Extending the
/notations,
Lab4: Developing activity
diagram using CASE tool
Steps and guidelines
Week 5

Use Case Descriptions, Tutorial 6: System Sequence


Lecture6 and Lab6

Diagrams and Documenting

Extending the
The System Sequence Use Cases
DiagramIdentifying
Inputs and Outputs Lab5: Drawing System
Week 6

Sequence Diagrams using


CASE tool

Extending the Requirements


Mid-Semester Exam

The State Machine Tutorial 7: State Machine


DiagramIdentifying diagrams
Lecture7 and Lab7

Object Behaviour,
Lab 6: Developing State
Integrating Requirements Machine diagram using
Models CASE tool
Week 7

Models

The Essentials of Design,


Essentials of Design and

Inputs and Outputs for Assignment Submission


Lecture8 and Lab8

Design Activities

Systems Design, (10 marks)

Design Activities, Tutorial 8: The Elements of


Design
Week 8

Design the Systems


Environment

User-Interface Design
Concepts,

The Transition from Project Deliverable-1/in


User and System Interfaces

Analysis to User-Interface
Design, Tutorial 9: User Interface
Design
Lecture9 and Lab9

Identifying System
Interfaces, Lab 8: User Interface
Design/Prototype creation
Designing System Inputs,
Week 9

Designing System Outputs


Approaches to System Development
Approaches to the SDLC,

The Support Phase of the


SDLC, Tutorial 10: Approaches to
SDLC and Agile
Lecture10 and Lab10 Methodologies, Models, Development.
Tools and Techniques,
Project Progress Discussion
Two Approaches to (Object Oriented Case Study
Software Construction and 2)
Week 10

Modeling,

Agile Development

Object Oriented Design:

Object Oriented Design:


Principles,
Lecture11 and Lab11

Tutorial 11: Object Oriented


Bridging from Analysis to Design Principles
Implementation,
Principles Lab 8: Design Classes and
Week 11

Fundamental Principles of the Design Class Diagram


Object Oriented Detail
Design

Object Oriented Design:


Use Case realizations,
Object Oriented Design:
Use Case realizations

Tutorial 12: Object Oriented


Lecture12 and Lab12

Detailed Design of Design: User Case


Multilayer Systems, realizations.

Use Case Realization with Lab 9: Use Case Realization


Week 12

Sequence Diagram with Sequence Diagrams.

Testing,
Lecture13 and Lab13

Making the System

Deployment Activities, Tutorial 13: Making the


System Operational
Planning and Managing
Operational

Implementation, Testing, In-Class Assessment


Week 13

and Deployment, (10 marks)


Trends in System
Development
Methodologies,

Current Trends in System


Trends in Technology Tutorial 14: Current Trends

Lecture15 and Lab15 Lecture14 and Lab14


Infrastructure, in System Development

Trends in Application Project Submission

Development
Software Availability, (10 marks)
Week 14

The Web as an Application


Platform

Revision
Project Presentations
Project Presentations (5 marks)
Week 15

(5 marks)

Teaching Methods

The course will be delivered through a combination of: lectures/laboratories/tutorials/group work.


One lecture of 2 hours duration is given each week for 14 weeks. In addition there will be two hours
supervised lab session each week. Projects are carried out as a group of three. The course is
continuously assessed, the credit being based on all the project; written and practical assignments.
Each assessment task is linked to specific learning outcomes listed (although in many cases there is
overlap with associated learning outcomes).

A reasonable degree of independence is expected of students. Emphasis is placed on students learning


material by themselves, rather than being spoon-fed everything in classes. Supplementary reading is
encouraged, and students who intend to become information systems professionals should be building
a personal library of reference books.

Effective teaching environment for this course: PCs running Windows 7 or higher operating
system with Sybase Power Designer (or any other CASE Tool) installed. Blackboard and online
database resources for reference.

Assessment Methods

ASSESSMENT MEASURES Learning Outcomes


Assignment 3,4,5
In-class Assessment 5,6,7
Mid-Term Exam 1,3,4,5,6
Project 1,2,3,4,5,6,7,8, 10
Final Exam All
Assessment and mark distribution

Marks are distributed as follows:

Assessment Mid term Assignment Practical Exam Project Final Exam Total

weight 15 10 10 15 50 100

Assignment: 10%
Assignment is based on a mini-case discussion of a business problem. This requires students to
analyze the business problem and design a solution. Assignment will require the application of object
oriented concepts and the Unified Modeling Language (UML) for requirements analysis. Further
details, including assessment criteria, will be provided in a separate document. For assignment,
students work in groups (maximum group size allowed is two members).

Practical Exam: 10%

This component tests individual students knowledge and is a written assignment that consists of
exam style questions based around topics presented in the course. The questions will be of an open-
ended nature and will put you in good stead for the examination at the end of the course.

Project Marks: 15%

Project Deliverable 1: System Proposal (Introduction to Project and Requirements


Specification)

Project Deliverable 2: Final SRS Document (with Analysis & Design) 10 Marks

Project Deliverable 3: Project Presentation 5 Marks

TEXT BOOK (S):

Title Edition Author Publisher


Introduction to Systems 6th John Satzinger, THOMSON Course
Analysis and Design, An Robert Jackson, and Technology, 2012
Agile, Iterative Approach Stephen Burd,
ISBN 978-1.111-
97226-4

References

Title Edition Author Publisher


Object-Oriented Simon Bennet, Steve McGraw-Hill 2010
Systems Analysis and 4th Revised McRobb, and Ray ISBN-13: 978-
Design Using UML Farmer 0077125363
Introduction to Alan Dennis and Wiley 2014
Systems Analysis and 6th Barbara Haley ISBN: 1118897846
Design Wixom
Pearson- 2013
Systems Analysis and th ISBN-13: 978-
9 Kendall and Kendall 0133023442
Design
ISBN-10: 0133023443

Anda mungkin juga menyukai