System
Analysis and Design
EG
2212 CT
Year:
II Total:
5 hours/week
Semester:
IV Lecture:
3 hrs/week
Practical: 2 hrs/week
Course Description:
Systems are created to solve
problems. One can imagine or think systems approach as an organized way of
dealing with specific problem. So, in this real or active world, the System
Analysis and design, mainly deals with the software development activities. The
students can able to know about the system and design and can provide the full
knowledge about the system analysis and design and use of model.
Course Objectives:
After completing this course the student will able to:
1. Define
a system
2. Explain
the different phase of SDLC and their uses
3. Describe
the components of System Analysis and Design
4. Analyze
and specify the requirements of a system.
5. Design
system components and environments.
6. Build
general and detailed models that assist programmers in implementing a system
7. Design
a database for storing data and a user interface for data input and output, as
well as controls to protect the system and its data.
Course Contents:
Unit
|
Topics
|
Contents
|
Hours
|
Methods /Media
|
Marks
|
1
|
Introduction
to
System
Analysis &
Design
|
1.1 Introduction
1.2 Objectives
1.3 Defining System
1.4 System Life Cycle
1.5 Phase of System Development Life Cycle
1.6 Planning, Analysis, Design, Implementation and Maintenance
|
6
hours
|
||
2
|
Development,
Management
&
Supporting
Processes
|
2.1 Development Process
2.1.1 Emergent
System Properties
2.1.2 System Engineering
2.2 Management Process
2.3 Supporting Process
2.4 System Structure
2.5 Type of Information System
|
6
hours
|
Unit
|
Topics
|
Contents
|
Hours
|
Methods /Media
|
Marks
|
2.5.1 Transaction Processing System
2.5.2 Management Information System
2.5.3 Decision Support System
|
|||||
3
|
Approaches
to
System
Development
and
Importance
of
Metrics
Measurement
in
SDLC
in SAD
|
3.1 Finding the Problems
3.2 Methodology and Models, tools &
Techniques
3.3 Software Measurement Process and
Examples
3.4 Size Oriented Metrics and Example
3.5 Function Oriented Metrics
3.6 Defect Removal Efficiency (DRE)
3.7 Measurements
3.8 Types of Metrics
3.9 Factors
or Indicator Affecting Software Quality
|
7
hours
|
||
4
|
Requirement
Analysis
|
4.1 Introduction
4.2 The Important of Communication
4.3 Identifying the Requirement
4.4 Information Collection Methods
4.5 Gathering Information by asking questions
4.5.1 Questionnaires
4.5.2 Electronic Data Gathering
4.6 Gathering Information by Observation
4.7 Gathering Information by Prototyping
4.8 Interviewing and Software
Requirement Document
|
6
hours
|
||
5
|
Data & System Flow Diagram
|
5.1 Introduction
5.2 DFD and SFD symbols
5.3 Describing System by DFD
5.4 Logical and Physical DFDS
5.5 Processing Description Method
5.6 Structure English
5.7 Decision Tables
|
6
hours
|
||
6
|
Object
Modeling and Designing
|
6.1 Data Dictionary
6.2 E-R Model
6.3 Transforming E-R Diagram into
Relations
6.4 Normalizations (1st , 2nd
and 3rd Normal Form)
|
6
hours
|
||
Unit
|
Topics
|
Contents
|
Hours
|
Methods
/Media
|
Marks
|
6.5 Object Modeling
6.5.1 Object Environment
6.5.2 Object Structures
6.6 Modeling behavior in object modeling
6.6.1 Class Object Diagram
6.6.2 Use Case Diagram/sequence Diagram
|
|||||
7
|
Quality
Assurance
|
7.1 Introduction
7.2 Implementing Quality Assurance
7.3 Inspections
|
4
hours
|
||
8
|
Introduction
to
Software
Engineering
|
8.1 Introduction
8.2 Software
Development Process
8.2.1 Waterfall Model
8.2.2 Evolutionary Model
8.2.3 Spiral Model
|
4
hours
|
||
9
|
Practical:
Teacher/Instructor should provide at least 3 case study about system.
|
30hrs
|
|||
1.
System Analysis and Design by Igor
Hawryszkiewycz
2.
Modern System Analysis and Design by Jeffery A.
Hoffer, Joey F. George, Joseph S. Valacich
3.
Web sites of System Analysis and Design
No comments:
Post a Comment