Scribd
Upload
11 views

Lab 01

The document outlines the concepts of System Analysis and Design, emphasizing the importance of identifying business problems, gathering requirements, and designing optimal solutions. It details the phases of the System Development Life Cycle (SDLC), including Planning, Analysis, Design, and Implementation, along with key topics and benefits associated with each phase. Additionally, it provides a framework for creating a System Request Plan and includes multiple-choice questions to assess understanding of the material.

Uploaded by

Mariam Nasr
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
11 views

Lab 01

The document outlines the concepts of System Analysis and Design, emphasizing the importance of identifying business problems, gathering requirements, and designing optimal solutions. It details the phases of the System Development Life Cycle (SDLC), including Planning, Analysis, Design, and Implementation, along with key topics and benefits associated with each phase. Additionally, it provides a framework for creating a System Request Plan and includes multiple-choice questions to assess understanding of the material.

Uploaded by

Mariam Nasr
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/ 12

System Analysis & Design

Lab 01
Instructor: Dr.Nesreen El saber
TA : Eng.Saja Saadoun , Eng.Pansy Youssef
2

What Is System Analysis ?


Examine a business problem, identify its objectives and requirements, and
then design the most optimal solution to fulfill those needs.
It is the very first step in any system development and the critical phase
where developers come together to understand the problem, needs, and
objectives of the project.
-​ Analysis specifies what the system should do.

Key Aspects :
1.​ Problem Identification : it involves identifying the issues that the
system is aiming to address.

2.​ Requirements Gathering : gather and write down the requirements.


This involves communicating with the customer and developer to
gather information about how the system is to be designed.

3.​ Feasibility study: this includes the evaluation of technical, operational,


and financial aspects to determine the feasibility of the proposed
solution.

4.​ Analysis and modeling : develop various models, such as Data Flow
Diagrams(DFD) , Use Cases, and Entity-Relationship(ER) diagrams.
These models help the customer to visualize the system and its
interactions.

5.​ Scope Definition : it’s important to prevent adding excessive features to


the system and ensure that the project stays within its limits.
3

What Is System Design?


Involves the process in which an organization develops a newer system or
strategy to complement or replace an existing one.
It is a process of planning a new business system or replacing an existing
system by defining its components or modules to satisfy the specific
requirements.
-​ Design focuses on how to accomplish the objective of the system.

Benefits of system analysis and design :


1.​ Improves System Quality and Efficiency

2.​ Reduces Development Costs and Risks

3.​ Enhances Decision Making

4.​ Increases User Satisfaction

5.​ Ensures Scalability and Flexibility


4

Four Phases of System Development Life Cycle (SDLC) :

1.​Planning Phase
Identifies the problem, defines project scope and develops a project plan to
ensure successful execution.

2.​ Analysis Phase

Gathers and documents user requirements, studies the current system , and
identifies improvements to ensure the new system meets business needs.

3.​ Design Phase

Creates system architecture, user interfaces, database structures, and


technical specifications to guide system development.

4.​ Implementation Phase

Develops, tests, deploys, and maintains the system, ensuring it functions


correctly while providing training and support for users.
5

Key topics that will be covered:


●​ Planning Phase :
○​ System Request Plan : A formal document that defines the system’s
purpose, goals, and justification.
○​ System Plan : Outlines the project scope, timeline, and resources
needed for development.
○​ Feasibility Study : Evaluates technical, economic, legal, operational,
and scheduling feasibility to determine if the project is viable.

●​ Analysis Phase :
○​ System Requirements: Documents functional and non-functional
requirements based on user needs.
○​ Use Case Diagram: Represents user interactions with the system to
define system behavior.
○​ Data Flow Diagram (DFD): Illustrates how data flows within the system.
○​ Entity-Relationship Diagram (ERD): Defines the database structure and
relationships between data entities.

●​ Design Phase :
○​ Architecture Diagram: Represents the system’s overall structure,
including components, databases, and communication flows.
○​ User Interface (UI) Design : Defines the visual layout and interactions
users will have with the system.

●​ Implementation Phase :
○​ Test Cases : Define the scenarios to be tested, ensuring the system
meets requirements and functions correctly before deployment.
6

System Request Plan :


A formal document used to initiate a new system development project. It
provides key information about the project’s purpose, objectives, and
justification.

Consists of :
1.​ Project Title : A clear, concise name for the proposed system .

2.​ Requestor Information : Details of the person or department


requesting the system (name, department, contact details).

3.​ Business Need / Problem Statement : Describes the current issue or


business problem that the new system aims to solve.

4.​ Proposed Solution : A brief description of how the new system will
address the business need.

5.​ Expected Benefits : Lists the benefits the system will provide, such as
improved efficiency, cost savings, accuracy, and user experience.

6.​ Project Scope : Defines what the system will and will not include.

7.​ Stakeholders : Identifies key people involved in the project, such as


system users, IT teams, and management.

8.​ Constraints and Assumptions : Constraints: Time, budget, technology


limitations. Assumptions: Availability of required data, third-party API
access, regulatory compliance.
7

9.​ Estimated Timeline : A rough estimate of how long the system will
take to develop and implement.

10.​ Approval Section : A signature or approval section for management


to authorize the project.
8

Multiple Choice Questions :

1.​ What is the main objective of System Analysis and Design?


a) To create complex systems
b) To ensure that the system meets business requirements
c) To eliminate the need for testing
d) To reduce employee workload

2.​ Which of the following best describes a system?


a) A random collection of unrelated components
b) A software program
c) A set of interrelated components working towards a common goal
d) A collection of hardware devices

3.​ What does SDLC stand for?


a) System Data Lifecycle Control
b) System Development Life Cycle
c) System Design and Lifecycle Control
d) Systematic Development of Large Computers

4.​ Who is responsible for gathering system requirements during the analysis
phase?
a) System Analyst
b) Database Administrator
c) Network Engineer
d) Graphic Designer
9

5.​ What is the first phase of the System Development Life Cycle (SDLC)?
a) Analysis
b) Design
c) Planning
d) Implementation

6.​ What is a system request?


a) A document that defines system architecture
b) A network access request
c) A software installation request
d) A request from end-users to start a new system project

7.​ What is the purpose of a feasibility study?


a) To determine if a project is legally and technically viable
b) To build the system prototype
c) To implement the system
d) To write the system documentation

8.​ What is the main purpose of the Analysis Phase?


a) To create the final system
b) To install the system in the organization
c) To test the system for errors
d) To gather user requirements and study the existing system

9.​ A Use Case Diagram is used to:


a) Show how data flows through a system
b) Show interactions between users and the system
c) Represent the physical design of the system
d) Describe the test cases for a system
10

10.​What does a Data Flow Diagram (DFD) represent?


a) The hardware structure of the system
b) The flow of data within the system
c) The final system design
d) The system's programming code

11.​In an Entity-Relationship Diagram (ERD), what does an entity represent?


a) A process in the system
b) A data store
c) A real-world object, such as a customer or order
d) A system error

12.​What is the primary role of a System Analyst?


a) To analyze user requirements and design the system
b) To write programming code
c) To test the system before deployment
d) To manage the company's network security

13.​The purpose of the Design Phase is to:


a) Code and test the system
b) Identify system requirements
c) Create system architecture and user interfaces
d) Deploy the system to users

14.​What does an Architecture Diagram show?


a) The interaction between users and the system
b) The company’s organizational hierarchy
c) The test cases for the system
d) The structure of hardware and software components
11

15.​A user interface (UI) design focuses on:


a) How users interact with the system
b) System security
c) The physical database structure
d) Network connectivity

16.​The purpose of the Implementation Phase is to:


a) Plan the system development process
b) Analyze business requirements
c) Deploy and test the system in the real environment
d) Design the system’s architecture

17.​What is the main purpose of test cases in the implementation phase?


a) To randomly check system performance
b) To systematically validate that the system meets requirements
c) To replace system documentation
d) To generate financial reports

18.​A good user interface design should be:


a) Complex and detailed
b) Consistent and user-friendly
c) Designed only for developers
d) Based solely on business requirements, ignoring user feedback
12

Create a system request form using any of the following case studies :

1.​ Hospital Appointment Management System : allows patients to book,


reschedule, or cancel appointments online or via a mobile app

2.​ University Course Registration System : An Automated Course Registration


System that allows students to register for courses online, view available
slots, and receive instant confirmation.

3.​ Online Food Ordering System : allows customers to browse the menu, place
orders, and make payments

4.​ Library Management System : automates book check-ins and check-outs


using a barcode or RFID system, tracks due dates, and alerts users about
overdue books.

5.​ Car Rental System : allows customers to book vehicles online, view pricing,
and track rental periods. The system should also help staff monitor car
availability and maintenance.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy