A successful project is one where the development team:

- Delivers a system that meets user and organizational needs

- Does it on time and within budget

So the key idea: success isn’t just “building software”—it’s delivering the right software for the right people, with cost/time control.

2) “Critical for most systems development projects”

The slide highlights one particularly important factor:

- Getting users and stakeholders involved

Users are the people who will use the system.

Stakeholders are anyone who affects or is affected by the system (managers, customers, IT staff, compliance/security teams, etc.).

Why involvement matters: when users/stakeholders participate, the team better understands requirements, avoids building the wrong features, and reduces the chance of rework or failure after launch.

• Prepare a Request for Proposal (RFP): Create a detailed document specifying the required hardware, software, and other system resources.

• Evaluate and select a system design: Assess the proposed alternatives through:

  • Preliminary evaluation – Initial screening of options.

  • Final evaluation – Detailed comparison to choose the best system design.

Summary: The task involves creating an RFP to define system requirements, then evaluating design alternatives through preliminary and final assessments to select the most suitable system.

Data analysis is the process of understanding the requirements of a system and organizing information before developing it. It helps ensure that data is stored correctly and that business processes work efficiently.

1. Data Modeling

Data modeling is accomplished using an Entity-Relationship (ER) Diagram. An ER diagram shows the different entities in a database, such as Students, Courses, and Instructors, and the relationships between them. It helps designers understand how data is connected and how it should be stored in the database.

2. Activity Modeling

Activity modeling is accomplished using Data Flow Diagrams (DFDs). A DFD illustrates how data moves through a system, showing the input, processing, storage, and output of information. It explains the activities required to complete a business process or perform a business task.

Difference Between ER Diagram and DFD

• ER Diagram focuses on the structure of the data and the relationships between entities.

• DFD focuses on how data flows through the system and how business activities are performed.

Conclusion

Both ER diagrams and DFDs are important tools in data analysis. ER diagrams help organize and design the database, while DFDs help explain how the system processes and transfers data to complete business tasks efficiently.

Summary – Slide 16

The Systems Development Life Cycle (SDLC) continues after a system is implemented through maintenance and review. A new SDLC begins when the current system needs major improvements, becomes outdated because of new technology, or no longer meets the organization’s changing needs.

Example: A company replaces its old inventory system with a new cloud-based system because the old system cannot support online orders.

Summary:

Outsourcing and on-demand computing let businesses access external IT resources instead of owning everything in-house. The main goals are cutting expenses, keeping up with cutting-edge tech, avoiding HR headaches, and adapting quickly to changing needs.

• Reduce costs - A startup uses AWS Lambda (pay-per-use) instead of buying expensive servers, saving on hardware and electricity.

• Obtain state-of-the-art tech - A small retail firm outsources Al-driven inventory forecasting to a specialist vendor, rather than building its own ML team.

• Eliminate staffing problems - A mid-sized company hires an external helpdesk provider so it doesn't have to recruit, train, or manage 24/7 support staff.

• Increase technological flexibility - A media company uses cloud-based rendering on demand, scaling up for big projects and scaling down to zero when finished

Example:

A company creates a simple prototype of a mobile banking app. Users test it, give feedback, and the developers improve the app in the next iteration until it meets the users’ needs.

Installation is the process of physically setting up computer hardware and software at the organization’s site and making sure everything is ready for use. This includes placing the equipment, connecting cables, installing the operating system and required software, configuring network connections, testing the system, and confirming that all components work correctly.

Usually, the manufacturer or supplier is responsible for installing the equipment because they have the technical expertise. However, an Information Systems (IS) Manager or another representative from the organization should supervise the process to ensure that:

• The equipment is installed in the correct location.

• All hardware and software function properly.

• The installation meets the organization’s requirements.

• Any problems are identified and fixed before the system is used.

Example:
When a company buys new computers, the supplier installs the computers, connects them to the network, installs the necessary software, tests them, and ensures they are ready for employees to use. The IS Manager checks that everything has been installed correctly and is working as expected.

• OOSD combines the System Development Life Cycle (SDLC) with object-oriented modeling and programming.

• It focuses on developing software using objects that represent real-world entities.

Main OOSD Tasks:

1. Identify problems and opportunities for an object-oriented solution.

2. Gather and define user requirements.

3. Design the system.

4. Develop or modify software modules.

5. Test and evaluate the system with users.

6. Review and update the system regularly.

Example:
A startup uses Agile to release a new version of its app every two weeks based on user feedback.

• Managers = make decisions.
  Example: Decide what the system should do.

• Programmers = build the system.
  Example: Write the code for the application.

• Users = use the system.
  Example: Employees use the system every day.

Slide 13 : Developer = builds the system.
Example: A student creates an app.

• User = uses the system.
  Example: A teacher uses Word to write exams.

• End-user = creates a simple tool for themselves.
  Example: A manager makes an Excel file to record sales.

- You check/analyze the system at the end to confirm it will work correctly.

- The goal is to ensure the system can operate as intended.

- It can be done during the development process (not only after everything is finished).

What are these two slides about?

In short, they explain how a company's business goals get turned into actual IT projects. You can't just start building software out of nowhere — it has to actually serve the business.

The main point is that IS planning is all about taking big-picture company goals (like "we want to double our sales") and translating them into technical terms. If the IT team's goals and the management's goals don't align, the project is bound to fail.

How it works in practice is shown as a simple 3-step chain:

1. First, management creates the Strategic plan (where the business is heading).

2. Then comes IS planning (figuring out what tech is needed to hit those business goals).

3. Finally, this sparks Systems development initiatives (the actual, concrete projects to build the software).

CASE tools are software applications that automate repetitive SLCtasks (like diagramming, code generation, and testing) while enforcing structured methodologies. Upper-CASE specifically supports planning, analysis, and design-the early project phases.

Short examples:

• Automate tasks - A team uses a CASE tool to automatically generate Java boilerplate code from UML class diagrams, saving days of manual coding.

• Encourage SL adherence - The tool forces developers to complete requirements documentation and sign-offs before allowing them to move to coding, preventing skipped steps.

• Upper-CASE (early stages) - Analysts use a data-modeling tool to visually map entity relationships and automatically generate database schemas during design, before any code is written.

• Another Upper-CASE example - A requirements management tool that tracks user stories, creates traceability matrices, and validates that all business rules are covered before development begins.

Planning is an essential part of achieving success in any area of life. It helps people set clear goals, organize resources, and use time effectively. Good planning reduces confusion, minimizes risks, and prepares individuals or organizations to handle unexpected challenges. It also improves decision-making by providing a clear direction and priorities. Whether in education, business, or personal life, planning increases productivity, boosts confidence, and makes it easier to achieve desired results. In short, planning is the foundation of success because it turns ideas into practical actions and helps ensure goals are reached efficiently.

This topic is about deciding whether an organization should develop its own software (make) or purchase software from an external vendor (buy).

Make-or-Buy Decision

The make-or-buy decision is the choice between:

• Make: Develop the software internally using the organization’s own IT team.

• Buy: Purchase or obtain software from an external company or software vendor.

The decision depends on factors such as cost, time, business needs, available skills, and maintenance requirements.

Externally Acquired Software

Externally acquired software is software that is bought or licensed from another company instead of being developed in-house. It is usually faster to implement and often costs less than building custom software.

Software as a Service (SaaS)

Software as a Service (SaaS) is a cloud-based software model where businesses subscribe to software online and pay a monthly or yearly fee instead of buying and installing it on their own computers.

Advantages of SaaS:

• Lower upfront cost.

• Easy to access through the Internet.

• Automatic updates and maintenance.

• No need to install software on every computer.

Examples:

• Microsoft

• Google

• Zoom

System request form

Filled out by someone who wants is department to initate systems investigation Slide

Information included

. Problems in or opportunities for system

Objectives of systems investigation

Overview of proposed system

expected costs and benefits of proposed system

These tools help managers organize project work, follow progress, and make sure the project finishes on time.

• Project schedule: A detailed plan showing what tasks need to be done and when.

• Project milestone: An important checkpoint or date when a major part of the project should be completed.

• Project deadline: The final date when the whole project must be finished and ready to use.

• Critical path: The sequence of most important tasks. If any task on this path is delayed, the entire project will be delayed.

Planning Tools

• PERT (Program Evaluation and Review Technique): Used to estimate how long an activity may take when the exact time is uncertain. It uses:

• Shortest possible time — best-case estimate

• Most likely time — realistic estimate

• Longest possible time — worst-case estimate

• Gantt chart: A visual timeline that shows project tasks, their start and finish dates, and progress. It helps with planning, monitoring, and coordinating work.

Easy way to remember

Schedule = tasks plan

Milestone = important checkpoint

Deadline = final finish date

Critical path = tasks that cannot be delayed

PERT = three time estimates

Gantt chart = visual task timeline

Yahia Alhasan

• Systems Investigation: Identifies business problems or opportunities, evaluates feasibility, and decides whether to develop a new system.

• Systems Analysis: Examines the current system, identifies strengths and weaknesses, and gathers user requirements to determine what the new system should do.

• Systems Design: Creates the blueprint of the new system by designing the database, user interface, architecture, and security to meet the identified requirements.

Example: A hospital decides to develop an online appointment system.

Example: Users request online booking and automatic reminders.

Example: Design login page, patient database, and appointment screens.

1-Overview of Systems Development:

Now adays the businesses shulde work together so All managers and employees from all departments work together and use information systems.

The Goal: To learn how to plan and develop projects quickly to match corporate goals.

2. Participants in Systems Development To build any system we need three main elements:

Development Team: The people who define the system is goals and build it to meet those goals.

Project: A planned group of activities designed to achieve a specific goal.

Stakeholders: The people who will benefit from the project in the end.

• Unit Testing: Tests individual components or modules to ensure they work correctly.

• System Testing: Tests the complete system to verify it meets all requirements.

• Volume Testing: Checks how the system performs with a large amount of data.

• Integration Testing: Tests whether different modules work together correctly.

• Acceptance Testing: Performed by users or clients to confirm the system meets their needs before deployment.

Easy Memory Tip

• Unit = One module

• Integration = Modules together

• System = Entire system

• Volume = Large data

• Acceptance = User approval

We should also think about options and what we might have to give up if we choose one option over another. We have to think about if the new system's actually possible to build, if it is worth the money. If it is safe to use.

The main thing we want to get from all of this is a list of what the new system needs to be able to do. We need to make sure we have good reasons for each thing on the list. This list should be in order of importance. We know what to focus on first.

The outcome of all this work is a list of system requirements that we know are important. That we have good reasons, for.

Example: A university develops a new online student registration system. Before and after launching it, the development team reviews the system to ensure students can register for courses correctly, identify any errors, and improve performance if needed.

•Users:

–People who will interact with the system regularly

•Systems analyst:

–Professional who specializes in analyzing and designing business systems

•Programmer:

–Responsible for modifying or developing programs to satisfy user requirements