Lecture 01
Lecture 01
Lecture One
COURSE INFO.
Instructors
Dr. Mustafa Mohsini
Ms. Christina Muro
Ms. Cecilia Mambile
Information Technology
Combination of hardware and software
products and services that companies use to
manage, access, communicate, and share
information
The Future of IT
IT has created a new economy, where
advances in hardware, software, networks
provide huge benefits to businesses
worldwide.
SA&D
1
HARDWARE COMPONENT
Hardware consists of everything in the
physical layer of the information system.
For example, hardware can include
servers, workstations, networks,
telecommunications equipment, fiber-
optic cables, mobile devices, scanners,
digital capture devices, and other
technology-based infrastructure.
Hardware purchasers today face a wide
array of technology choices and
decisions. In 1965, Gordon Moore, a
cofounder of Intel, predicted that the
number of transistors on an integrated
circuit would double about every 24
months. His concept, called Moore’s Law,
has remained valid for more than 50
years. Fortunately, as hardware
became more powerful, it also became
much less expensive.
Why is it important?
Success of information systems depends on good SAD
Structured Analysis
Object-oriented (O-O) analysis
Joint Application Development (JAD) and
Rapid Application Development (RAD)
Prototyping model
The waterfall model
Rational Unified Process Model
Pros Cons
Speeds up the development process
significantly Important decisions might be made
too early, before business or IT
Users interact with Prototype issues are thoroughly understood
very quickly
Initial Design decisions may be
Users can identify needed changes poor
and refine real requirements
The waterfall model is consistent with other engineering process models and
documentation is produced at each phase. This makes the process visible so
managers can monitor progress against the development plan.
System Analysis and Design Introduction to SAD 34
METHODOLOGIES IN THE DEVELOPMENT OF
INFORMATION SYSTEMS
Phases of RUP:
1. Inception : Establish the business case for the system.
2. Elaboration : Develop an understanding of the problem domain and the
system architecture.
3. Construction : System design, programming and testing.
4. Transition: Deploy the system in its operating environment.
Investigating projects