Slide-1

1. Developing Information Systems

A System Development Methodology is a standard process that helps an organization

plan, analyze, design, build, and maintain an information system.
It gives a clear framework to make sure the system is developed in an organized and
efficient way, reducing mistakes and helping to meet the users’ needs.

[Link] Development Life Cycle (SDLC)

Planning – The organization finds out what kind of information system it needs.
These needs are studied and arranged in order of importance.

Analysis – The details of what the system should do are collected and clearly
understood.

Design – The system is planned carefully before building.

Logical Design: Explains what the system will do, without choosing any
computer or technology yet.

Physical Design: Changes the plan into real technology details, showing how
the system will work on computers.

Implementation – The system is created, tested, and installed so people can start
using it.

Maintenance – The system is checked often, fixed when needed, and improved over
time.

[Link] with Waterfall Approach

Hard to change: Once a phase is finished, it’s difficult to go back and make changes.

Late testing: Testing is done at the end, so problems are found very late in the
process.

Takes more time: Each step must finish before the next begins, which makes the
project slow.

Less user involvement: Users give feedback only after the system is completed, so
the final product may not meet their needs.

Risk of failure: If any mistake happens in the early stages, it can affect the whole
project.
 Not flexible: It does not work well for projects where requirements may change over
time.

[Link] Approaches to Improving Development

CASE Tools:

Diagramming tools – Let you draw diagrams to show how the system works.

Computer displays and report generators – Help create a model to show how the
system will look and feel.

Analysis tools – Automatically check diagrams, forms, and reports for mistakes or
inconsistencies.

Central repository – A single storage place for all diagrams, reports, and project
documents.

Documentation generators – Create standard technical and user manuals easily.

Code generators – Automatically make programs and database code from designs,
diagrams, forms, and reports.
Agile Methodologies:

Agile is a way to build information systems quickly and flexibly. Instead of making
the whole system at once, it is made in small parts called iterations or sprints. Each
sprint usually takes a few weeks.

When to use Agile Methodologies:

Changing requirements: The system may need updates because needs can change.
Good developers: Developers should be responsible and motivated.
Active customers: Customers should understand the process and give feedback.

eXtreme Programming:
Short, incremental development cycles
Automated tests
Two-person programming teams
Coding, testing, listening, designing

6. Agail vs traditional methodology

[Link]-Oriented Analysis and Design (OOAD)

Object-Oriented Analysis and Design (OOAD) is a methodology used in software

engineering to analyze, design, and develop a system using object-oriented concepts.

Objects: Things in the real world that have properties (data) and actions (what they
can do).
Classes: Blueprints or plans to make objects.

Encapsulation: Keeping an object’s data and actions together and hiding the details
from others.

Inheritance: Making a new object based on an existing one so it can use the same
properties and actions.

Polymorphism: Same action can work in different ways for different objects.

6. Rational Unified Process

The Rational Unified Process (RUP) is a software development framework that helps
teams build software in a structured and organized way. It divides the development
into phases and the system is built step by step with continuous feedback. more easy
 Slide-2

1. Sources of Software
A. Information Technology (IT) :
Help companies make custom software for their own use.

Build, host, and run software for customers.

Offer other services like management, accounting, auditing, and finance.

B. Packaged Software Producers:

Serve many types of customers.

Provide software from general use (like accounting) to specialized use (like daycare
management).

Pre-packaged, ready-to-use software that works on small to large computers.

Off-the-shelf software is not customizable and usually meets only about 70% of a
company’s needs

C. Enterprise Solutions Software:

Enterprise Resource Planning (ERP) systems combine different business functions

into one system so a single process can work across departments smoothly. SAP is a
leading ERP provider.

D. Cloud Computing:

Cloud computing provides software and hardware over the Internet, so customers
don’t need to buy or manage their own computers.

Payment: Pay per use or monthly/yearly.

Examples of (Software as a Service):

Google Apps – for sharing documents, spreadsheets, presentations

Benefits of cloud computing:

No need for a large internal IT team.

Faster access to applications compared to building them in-house.

Cheaper than developing and maintaining software internally.

E. Open Source Software

Free to use, with source code available.

Made by a community of developers.

Works like commercial software.

Examples: Linux, MySQL, Firefox

How to make money:

Offer maintenance or support services

Sell a version with extra features.

F. In-House Development

If the company has enough skilled staff, it can develop some or all of the system in-
house.

In-house development usually requires more maintenance than other methods.

Often, a mix of purchased and in-house components (hybrid solution) is used.

2. Selecting Off-the-Shelf Software

Response time: How fast the software reacts to user actions.

Ease of installation: How easy it is to install and set up the software.

Vendor support: The help the vendor provides and its cost.

Viability of vendor: Whether the vendor can keep updating the software with system
and hardware changes.

Flexibility: How easily the software can be customized.

Documentation: Clear and up-to-date user guides and technical manuals.

3. Reuse applied to two different development technologies

Object-oriented development: Uses classes to group data and actions for common
entities (like employees).

Component-based development: Uses components that can be small (like objects)

or large (like software handling a whole business function).

4. Costs and Benefits of Reuse

Benefits:

Saves time and effort by reusing existing code or components.

Improves software quality since reused components are usually well-tested.

Reduces development costs.

Speeds up delivery of new software.

Costs:

Time and effort needed to find or adapt reusable components.

Learning curve for understanding reused code.

Possible dependency on external components or vendors.

May not perfectly fit the new system, requiring modifications.

5. 3 Steps of Software Reuse

Abstraction: Designing software in a way that it can be reused in different

situations.

Storage: Keeping software assets so others can access and use them.

Recontextualization: Making software easy for other developers to understand and

use.
 Slide-3

1. Phases of Project Management Process

Phase 1: Initiation
Phase 2: Planning
Phase 3: Execution
Phase 4: Closedown

PM Phase 1: Project Initiation

Assess size, scope and complexity, and establish procedures.
Establish:
Initiation team
Relationship with customer
Project initiation plan
Management procedures
Project management environment and workbook
Project charter

PM Phase 2: Project Planning

 Project Scope & Feasibility: What the project will do and if it’s possible.

 Divide Tasks: Break project into small tasks.

 Resource Plan: List people, tools, and materials needed.

 Preliminary Schedule: Plan task order and timing.

 Communication Plan: How to share information.

 Standards & Procedures: Set rules for work quality.

 Risk Assessment: Find problems and plan solutions.

 Preliminary Budget: Estimate costs.

 Scope Statement: Clear project goals and limits.

 Baseline Plan: Official plan to track progress.

PM Phase 3: Project Execution
Execute baseline project plan.
Monitor progress against baseline plan.
Manage changes in baseline plan.
Maintain project workbook.
Communicate project status.

PM Phase 4: Project Closedown

Bring the project to an end.
Natural Termination – Completed Successfully
Unnatural Termination – Due to time and money
Actions
Close down the project.
Conduct post-project reviews.
Close the customer contract.

2. Representing and Scheduling Project Plans

Gantt Charts
Network Diagrams
PERT Calculations
Critical Path Scheduling
Project Management Software
3. Gantt Charts vs. Network Diagrams

4. Project Management Software

Many powerful software tools help in project management.

Example: Microsoft Project can be used to:

Set project start or end dates

Create tasks and link their dependencies

View project details as Gantt charts or Network diagrams

5. Managing the Information Systems Project

 Project: A planned set of activities to reach a goal, with a clear start and end.

 Project Management: The process of starting, planning, doing, and finishing a

project in a controlled way.

 Project Manager: A systems analyst with management, leadership, technical, and

customer skills who leads the project from start to finish.

 Deliverable: The final product or output of a phase in the software development

life cycle (SDLC).

Estimating Resources
6. Constructive Cost Model (COCOMO)
A software tool that estimates project costs using past project data and current/future
project details.
 Slide-4
[Link] and Information Systems Planning

Corporate and Information Systems Planning means planning how a company’s

overall business goals and its information systems (IS) work together.

Corporate Planning: Focuses on the company’s mission, goals, and strategies for
growth and success.

Information Systems (IS) Planning: Focuses on using technology and systems to

support those business goals.

2. Information Systems (IS) Planning

IS is the process of deciding how an organization will use information technology (IT)
and systems to support its business goals and operations.
It connects business strategy with technology strategy to make the organization more
efficient and competitive.

3. Affinity Clustering

Affinity Clustering is a method used to group similar ideas or items together based on
their natural relationships.

In Information Systems Planning, it helps organize many ideas or needs collected

from users or departments into clear categories.
For example, similar system requirements can be grouped under headings like “data
management,” “security,” or “user interface.”

4. IS planing 7 phases(Component)

 Organizational Mission:
Describes the main purpose and goals of the organization.

 Informational Inventory:
Lists current information systems, data, and technology used.

 Mission and Objectives of IS:

Defines what the information system should achieve to support the organization’s
mission.

 Constraints:
Identifies limits such as budget, time, staff, or technology.
 Long-Range IS Strategies:
Plans for future system development and technology direction.

 Short-Term Plan:
Focuses on immediate projects and actions to be done soon.

 Conclusions:
Summarizes key findings, decisions, and next steps.

5. Electronic Commerce Applications and Internet Basics (Cont.)

 Business-to-Consumer (B2C): Online trade between businesses and customers.

 Business-to-Business (B2B): Online trade between companies or business partners.

 Business-to-Employee (B2E): Online services and communication between a

company and its employees.

 Internet: A global network that connects computers using common communication

rules.

 Electronic Commerce (EC): Using the Internet for business activities and
transactions.

 Electronic Data Interchange (EDI): Using telecom technology to exchange

business documents directly between organizations.

Slide-5

1. Economic feasibility

Economic feasibility is the process of checking if a project is worth the money by

comparing its costs (what you spend) with its benefits (what you gain).

Costs: Money needed to build and run the project.

Benefits: Money or value the project will bring.

If benefits are more than costs, the project is economically feasible.

[Link] Project Costs

Tangible costs: Costs you can measure in money, like hardware, labor, operations,
training, or building upgrades.

Intangible costs: Costs that are hard to measure in money, like loss of customer trust,
low employee morale, or inefficiency.

[Link] of Project Planning:

Determine standards and procedures – Decide how the project will be done.

Identify and assess risks – Find possible problems and plan for them.

Create preliminary budget – Estimate project costs.

Develop statement of work – Describe what the project will deliver.

Set baseline project plan – Finalize the initial plan to guide the project.

4. Economic feasibility:

The process of checking if a project’s benefits are greater than its costs.

Example:
A company wants to develop a mobile app.

Costs:

$10,000 for development

$2,000 for marketing

$3,000 for staff training

Benefits:

Expected $20,000 increase in sales

Improved customer satisfaction

Since the benefits ($20,000) are more than the costs ($15,000), the project is
economically feasible.