Institute of Technology
Department of Information Systems
Course Title: System Analysis and Design
Prepared and Compiled by: Ali H.
Reviewed By: Muktar A.
May, 2023
Werabe University, Ethiopia
i
,Contents
Chapter 1: System Development: ...................................................................................................................................... 1
1.1. Introduction to Information System development ............................................................................................. 1
1.2. System development methodologies, / Software life cycle and process model and phase ................................ 5
1.2.1. SDLC Model ............................................................................................................................................ 11
1.3. Problem Identification, Selection and Planning Phase: ................................................................................... 17
1.3.1. Gant and PERT Chart .............................................................................................................................. 24
Chapter 2: Object Orientation the new software paradigm.............................................................................................. 27
2.1. The potential benefits of object orientation ..................................................................................................... 27
2.2. The potential drawbacks of object orientation ................................................................................................. 28
2.3. Object standards............................................................................................................................................... 29
2.4. The object orientation software process and models ....................................................................................... 30
Chapter 3: Understanding the Basics Object oriented concepts ...................................................................................... 33
3.1. OO concepts from structured point of view ..................................................................................................... 33
3.2. Abstraction, Encapsulation and information hiding ........................................................................................ 34
3.3. Inheritance ....................................................................................................................................................... 35
3.4. Association....................................................................................................................................................... 38
3.5. Aggregation ..................................................................................................................................................... 40
3.6. Collaboration ................................................................................................................................................... 42
3.7. Persistence ....................................................................................................................................................... 43
3.8. Coupling........................................................................................................................................................... 43
3.9. Cohesion .......................................................................................................................................................... 44
3.10. Polymorphism .............................................................................................................................................. 45
3.11. Interfaces ...................................................................................................................................................... 45
3.12. Components ................................................................................................................................................. 46
3.13. Patterns......................................................................................................................................................... 46
Chapter 4: Gathering user requirements .......................................................................................................................... 48
4.1. Putting together requirements gathering team ................................................................................................. 49
4.2. Fundamental requirements gathering techniques ............................................................................................. 49
4.2.1. Essential Use Case Modeling................................................................................................................... 56
4.2.2. Essential User Interface Prototyping........................................................................................................ 65
4.2.3. Domain modeling with class responsibility collaborator (CRC) cards .................................................... 68
4.2.4. Developing a supplementary Specification.............................................................................................. 69
4.2.5. Identifying Change Cases ........................................................................................................................ 71
4.3. Ensuring Your Requirements Are correct: Requirement validation Techniques ............................................. 71
ii
, 4.3.1. Testing Early and Often ........................................................................................................................... 74
4.3.2. Use Case Scenario Testing....................................................................................................................... 74
Chapter 5: Determining What to Build: OO Analysis .................................................................................................... 75
5.1. System Use Case Modeling ............................................................................................................................. 76
5.2. Sequence Diagrams: From Use Cases to Classes ............................................................................................ 80
5.3. Conceptual Modeling: Class diagrams ............................................................................................................ 84
5.4. Activity diagramming ...................................................................................................................................... 96
5.5. User interface prototyping evolving your supplementary specification .......................................................... 98
5.6. Applying Analysis patterns effectively ............................................................................................................ 99
5.7. User Documentation ........................................................................................................................................ 99
5.8. Organizing your models with packages ......................................................................................................... 100
Chapter 6: Determining How to Build Your System: OO Design ................................................................................. 101
6.1. Layering your models: Class Type Architecture ........................................................................................... 101
6.2. State chart modeling ...................................................................................................................................... 102
6.3. Collaboration Modeling ................................................................................................................................. 105
6.4. Component Modeling .................................................................................................................................... 105
6.5. Deployment Modeling ................................................................................................................................... 106
6.6. Rational Persistence Modeling ...................................................................................................................... 109
6.7. User Interface Design .................................................................................................................................... 110
Chapter 7: Object Oriented Testing and Maintenance ................................................................................................... 112
6.1. An overview of testing ................................................................................................................................... 112
6.1.1. Testing concepts .................................................................................................................................... 113
6.1.2. Testing activities .................................................................................................................................... 113
6.1.3. Managing testing.................................................................................................................................... 117
6.1.4. Impact of object-oriented testing ........................................................................................................... 120
6.1.5. Types of Testing .................................................................................................................................... 121
6.2. Types and procedures of system maintenance; .............................................................................................. 130
iii
, Chapter 1: System Development:
1.1. Introduction to Information System development
Fundamentals of Information System
Information is very important part of any business, which helps the managers to take decisions. The data
flows throughout the organization and makes it active. There are lot of data available in the business, at every
time a transaction takes place ( Ex. a sale ), some data is recorded. It could be recorded on paper or in a
computer system.
The difference between data and information
Data are raw (unprocessed) facts about people, objects, events in an organization
(Ex. all the sales orders for the year)
Information is data that have been processed and presented in a form suitable for human
interpretation. (how many of each product were ordered in each month, may be shown on a graph)
System
A System is an interrelated set of business procedures (or components) used within one business unit,
working together for some purpose.
For Ex. an inventory system in the materials department keeps track of the raw materials supply.
The system takes input from outside, processes it, and sends the resulting output back to its environment.
A system can also defined as collections of people using information technology and processes that define
how people carry out their work. The system also includes informal interactions that take place in an
organization Ex. emails, phone calls.
Characteristics of a System
A System has nine characteristics
1. Components – A component is either an irreducible part or an aggregate of parts , also called as a
subsystem
Figure-1: Characteristics of System
2. Interrelated Components – The function of one component is tied to the functions of the others. Output
from one is input for another, the dependence of a part on one or more other parts.
3. Boundary – A system has boundary, within which all of its components are contained and which
establishes the limits of a system, separating it from other systems. Components within the boundary can
be changed whereas systems outside the boundary cannot be changed.
4. Purpose – All components work together to achieve the overall purpose of the system.
5. Environment – A system exist within an environment, everything outside the system‘s boundary that
influences and / or interacts the system.
6. Interfaces – The points at which the system meets its environment and there are also interfaces between
subsystems.
7. Input – System takes input from its environment
8. Output - System returns output to its environment as a result of its functioning to achieve the purpose.
Output from individual subsystems may be inputs to other subsystems.
1