0% found this document useful (0 votes)
9 views37 pages

MAC 251 Lecture Slides Module 2

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views37 pages

MAC 251 Lecture Slides Module 2

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 37

Department of Computer Science

Faculty of Communication & Information Sciences


University of Ilorin, Ilorin, Nigeria

MAC 251:
Fundamentals of Communication and
Information Sciences

Amos O. BAJEH, PhD


Room 29, Ground Floor/ Sub Dean’s Office
FCIS Building
Lecture Etiquette/Principles

❖ No cell phones
❖ No random coming in and going out
❖ No noise making
❖ If you are sleepy, go home
❖ If you want to read email or surf the Web,
please do it elsewhere
Module 2 Content
◼Module 2: Information System Planning and
Development

 Introduction to Systems
 Information Systems
 System Development Life Cycle Models
 Information System Professionals
1. Introduction to Systems
Learning Outcomes

At the end of this unit, you should be able to:


I. Define a system
II. State the properties of a system
III. Identify the elements of a system
IV. Highlight the types of system
1. Introduction to Systems
What is a System?

◼ The word System is derived from Greek word Systema


meaning an organized relationship between any set of
components to achieve some common cause or objective.

◼ It is “an orderly grouping of interdependent components linked


together according to a plan to achieve a specific goal.”
1. Introduction to Systems
Properties of A System
◼ Organization
◼ Interaction
◼ Interdependence
◼ Integration
◼ Central Objective
1. Introduction to Systems
Elements of A System
1. Introduction to Systems
Types of System
◼ Physical or Abstract Systems
◼ Open or Closed Systems
◼ Adaptive and Non-Adaptive System
◼ Permanent or Temporary System
◼ Natural and Manufactured System
◼ Deterministic or Probabilistic System
◼ Social, Human-Machine, Machine System
◼ Man–Made Information Systems
1. Introduction to Systems
Types of System
◼ Man–Made Information Systems
1. Formal Information System − It is based on the flow of information
in the form of memos, instructions, etc., from top level to lower levels
of management.

2. Informal Information System − This is employee-based system


which solves the day to day work related problems.

3. Computer-Based System − This system is directly dependent on the


computer for managing business applications. For example, automatic
library system, railway reservation system, banking system, etc.
2. Information Systems
What is Information System?
◼ It is a system that performs a set of information processes
requiring users, data/information and information technology.
◼ Information processes includes collecting, organizing,
analyzing, storing/retrieving, processing, transmitting/receiving
and displaying information.
◼ Structure of Information System:
2. Information Systems
Structure of Information Systems
◼ Purpose: The reason the IS is needed or developed
◼ Environment
◼ Information Technologies
◼ Participants
◼ Information processing: data collection, data organization, data
analysis, storage and retrieval, processing, transmitting
2. Information Systems
Structure of Information Systems
◼ Purpose: The reason the IS is needed or developed
◼ Environment
◼ Information Technologies
◼ Participants
◼ Information processing: data collection, data organization, data
analysis, storage and retrieval, processing, transmitting
2. Information Systems
 Information System Modeling
Information System Modeling involves the use of virtual representations
(called models) to conceptualize and construct system for managing processes
in an organization.

◼ There exist several system models, including:


1. Schematic Models
• A schematic model is a 2-D chart that shows system elements and their

linkages.
• Different arrows are used to show information flow, material flow, and

information feedback.
2. Information Systems
 Information System Modeling (cont’d)
2. Flow System Models
• A flow system model shows the orderly flow of the material, energy,

and information that hold the system together.


• Program Evaluation and Review Technique (PERT), for example, is

used to abstract a real-world system in model form.

3. Static System Models


• They represent one pair of relationships such as activity–time or cost–

quantity.
• The Gantt chart, for example, gives a static picture of an activity-time

relationship..
2. Information Systems
 Information System Modeling (cont’d)

4. Dynamic System Models


• It shows an ongoing, constantly changing status of the system. It

consists of −
a. Inputs that enter the system
b. The processor through which transformation takes place
c. The program(s) required for processing
d. The output(s) that result from processing.
2. Information Systems
System Development Life Cycle (SDLC)
SDLC is a conceptual model which includes policies and procedures
for developing or altering systems throughout their lifetime.

Phases of System Development Life Cycle (SDLC)


◼ Feasibility study
◼ Analysis and specification
◼ Design
◼ Implementation
◼ Maintenance/Support
3. SDLC Models
Models of System Development Life Cycle (SDLC)
These are the approaches to the development of Information
Systems. There are various methods for SDLC:

◼ Waterfall Model
◼ Incremental model
◼ V model
◼ Prototyping model
◼ Spiral Life Cycle Model
◼ Rapid Application Development
◼ Agile Life cycle models
◼ Lean model
3. SDLC Models
Waterfall Model
The waterfall model is a step-by-step sequential description of the
product’s life cycle that spans the phases of SDLC: Analysis,
Design, Implementation, Testing and Maintenance
3. SDLC Models
Waterfall Model
 Attributes of the model:
• Each of its stages must be entirely concluded before the next can
begin.
• Thus, analysis of requirements must be thorough and final before
design begins, and testing can only be efficiently carried out once
coding is entirely complete.
• Each stage is regarded as a static component, a rigid step in the
process.
• Subsequent changes in previous steps (e.g., awareness of new
requirements) cannot be taken into account.
3. SDLC Models
Waterfall Model
 Shortcoming of the model:
◼ Viewing each stage as a single, “frozen” step of evolution can
greatly delay the implementation stage because errors will
only be detected very late in the process, during the testing
phase, which is preceded by extensive designing and coding.

◼ The communication of objectives between developers and clients


is also greatly hindered because if the client changes the
requirements of the system, the development process needs to
completely restart for those changes to be taken into account.
3. SDLC Models
Incremental Model
In this approach:
◼ instead of dividing the SDLC into static, isolated steps, the
whole process can, instead, be designed, tested, and
implemented, one fraction at a time, in successive stages, so that
with each stage (or increment), there can be at least some
feedback from the client.
◼ This feedback will provide valuable assistance in the next
increment of the process and so forth.
◼ With each ongoing increment, the product is extensively tested
and improved, according to objectives and expectations from the
client, which facilitates its eventual success.
3. SDLC Models
Incremental Model
3. SDLC Models
The V Model
◼ The V-Model is a variation over the waterfall model that
attempted to emphasize the existing connection between each
of the stages of the development process and its respective
stage of tests.

◼ By focusing on this relationship, it ensures that adequate


quality measurements and testing are constantly resorted to,
throughout the life cycle.
3. SDLC Models
The V Model
3. SDLC Models
The V Model
The model has the following attributes:
◼ The V-Model starts off with a very similar premise to the classic
waterfall models. In successive steps, the project goes from analysis
of requirements and specifications, to architectural and detailed
design, to coding.

◼ However, instead of continuing this downward ladder, there is a


parallel structure that moves upward from the coding stage, giving
the model its distinct V shape.
3. SDLC Models
The V Model
The model has the following attributes (cont’d):
◼ The upward ladder describes each of the testing steps that
follows coding, starting with unit testing and ending with acceptance
testing, the final step before final release.

◼ In that sense, the V-Model describes three successive layers of


system development that can be described as requirements
(overall system), high-level design (software design), and low-
level design (Program design).
3. SDLC Models
The V Model
The model has the following attributes (cont’d):
◼ To each of these layers, there is a corresponding layer of
verification and testing.
◼ The core objective of the V life cycle model is to illustrate the
importance of the relationship between development and testing.
◼ Note: Since the V-Model addresses its errors shortly after they
are identified, it becomes less expensive to resolve them,
◼ However, this model is very rigid and there is little room for
flexible adaptation, particularly because any alteration in the
requirements will render all existing testing obsolete.
◼ V model requires a great deal of resources, it only works well
for small projects where requirements are easily understood.
3. SDLC Models
The Prototyping Model
◼ The prototyping model is based on the idea of creating the
entirety or part of a system in a pilot version, called the
prototype.
◼ The goal is ultimately to build in various versions and
consistently refine those versions until a final product is
reached.
3. SDLC Models
The Prototyping Model
A prototyping model essentially entails four different stages:
1. User’s requirements and needs are analyzed and identified.
2. The team develops a working prototype of the product, which
is then implemented.
3. The users test it and provide real-time feedback and
experience. If improvements and changes are found necessary, the
prototype is revised and refined
4. A new prototype is released and implemented for testing. This
sub-cycle will go on until the product is generally accepted by the
users and the final version is released.
3. SDLC Models
The Prototyping Model
◼ Prototyping models are weak on analysis and design planning.

◼ While requirements are assessed as the product is developed in


successive versions, there is little control over costs and
resources, which can dramatically increase the financial cost of
the project.

◼ Therefore, we can conclude that prototyping is ideal for larger


projects and particularly for user-centric ones.
3. SDLC Models
Spiral Life Cycle Model
◼ The spiral model introduces something that other models did
not take into account, which is risk analysis.

◼ It attempts to bring together key aspects of some other


prominent models (namely the waterfall, incremental, and
evolutionary prototyping).
3. SDLC Models
Spiral Life Cycle Model
3. SDLC Models
Spiral Life Cycle Model
◼ In this model, product delivery is not only faster, but it is also
easier to test and eventually correct.

◼ The downside to this approach is that it can be more costly to


develop and release multiple versions of the product.

◼ Note: The spiral model has significant advantages over


previously described models and makes it an ideal model for
large, mission-critical projects. On the downside, it is not very
efficient in smaller projects.
3. SDLC Models
Rapid Application Development (RAD)
◼ RAD focuses on quickly building a working model of the
software, getting feedback from users, and then using that
feedback to update the working model.
◼ After several iterations of development, a final version is
developed and implemented. The RAD methodology consists of
four phases:
3. SDLC Models
Rapid Application Development (RAD)
◼ It can be seen that the RAD methodology is much more
compressed than other SDLCs. Many of the SDLC steps are
combined and the focus is on user participation and iteration.

◼ Note: One of the most obvious flaws is that it removes a great


deal of emphasis on minute planning and modeling at the start of
the project, shifting the focus to the system construction. Another
prominent issue is that in faster development cycles, extensive
quality testing will become less prioritized, reflecting in poorer
quality overall.
3. SDLC Models
Agile Life Cycle Models
The waterfall model is a step-by-step sequential description of the
product’s life cycle that spans 5 key stages: Analysis, Design,
Implementation, Testing and Maintenance

◼ Waterfall Model
◼ Incremental model
◼ V model
◼ Prototyping model
◼ Spiral Life Cycle Model
◼ Rapid Application Development
◼ Agile Life cycle models
◼ Lean model
3. SDLC Models
Waterfall Model
The waterfall model is a step-by-step sequential description of the
product’s life cycle that spans 5 key stages: Analysis, Design,
Implementation, Testing and Maintenance

◼ Waterfall Model
◼ Incremental model
◼ V model
◼ Prototyping model
◼ Spiral Life Cycle Model
◼ Rapid Application Development
◼ Agile Life cycle models
◼ Lean model

You might also like