Maneesh $apkota

B.C.A. 3rd $em

$ystem Analysis
and Design
($AD)

Assignment Notes
 1

Unit-1
System Development Fundamentals

Q1) What do you mean by system? Explain the characteristics id a

system.
 System is a collection of interrelated computers that perform a specific task.
Example: College System, Economics System, Marketing, Sales, Accounting etc.

Characteristics of a System are:

 Organization:
It implies structure and order. It’s an arrangement of the components
that helps to achieve objectives.
 Integration:
It refers to the completeness of the system. It is more than sharing a
physical part of the location, i.e. part of a system work together within the
system even though each part performs a unique function.
 Central Objective:
A stated Objective may be the real objective it is not uncommon for an
organization to state one objective and operate to achieve another.
 Interaction:
The Manner in which each component functions with other components
of the system. For example: purchasing must interact with production,
advertising with sales, etc.
 Interdependence:
The part of the organization or the computer system depends on one
another. They are coordinated and linked together according to the plan.
 Boundaries and interface:
A system should be defined by its boundaries the limits that identify its
components, process and then interrelationship when it interfaces with
another system.
The fundamental across numerous disciplines, representing a set of interacting or
independent components forming a complex, unified whole. Understanding a

System Analysis and Design (SAD)

 2

system requires analyzing not just its individual parts, but also the dynamic
interaction that governs its overall stability, performance, and evolution.

Q2) Define Information System? Explain the components of

information system.
 The interrelated components working together to collect, process, store and
determine information to support decision making, coordination, control, analysis
and visualisation in an organisation.
Information system produces information by using data about significant people,
places and things from within the organisation or from the external environment to
make decision, control operation, analyse problem and create new product or
service.
The components of information systems are:
1. Hardware
Physical devices used for input, processing, storage, and output. Examples:
computers, servers, networking equipment, printers, and mobile devices. Hardware
provides the infrastructure that enables information systems to function.
2. Software
Programs and applications that run on hardware to process and manage data.
Includes system software (like operating systems) and application software (like ERP
systems, databases, or productivity tools). Software defines how tasks are executed
and how users interact with the system.
3. Data
Raw facts and figures that are processed into meaningful information. Data is
the core resource of an information system. Examples: customer records, financial
transactions, sensor readings. Without accurate and relevant data, the system
cannot provide useful insights.
4. People
Users who interact with the system, including IT professionals, managers, and
end-users. People design, operate, and maintain the system, and interpret the
information it produces. Human input and decision-making are critical for the
system’s success.
5. Procedure
Rules, policies, and workflows that govern how data is collected, processed,
and used. Examples: business processes, security protocols, and reporting
standards. Processes ensure consistency, efficiency, and compliance in how
information is handled.

System Analysis and Design (SAD)

 3

Fig: Basic Information System Model

Q3) Explain the types of information system?

The major types of information systems include Transaction Processing
Systems (TPS), Management Information Systems (MIS), Decision
Support Systems (DSS), Executive Information Systems (EIS),
Knowledge Management Systems (KMS), and Office Automation
Systems (OAS). Each serves a different organizational need.

1. Transaction Processing System (TPS)

 Purpose: Handles day-to-day business transactions.
 Examples: Point-of-sale systems, payroll processing,
online booking systems.
 Key Role: Ensures accuracy, speed, and reliability
in routine operations.
2. Management Information System (MIS)
 Purpose: Provides summarized reports for
managers to monitor performance.
 Examples: Sales reports, inventory summaries,
financial dashboards.
 Key Role: Converts raw data into structured information for decision-
making.
3. Decision Support System (DSS)
 Purpose: Helps managers make non-routine, complex decisions.
 Examples: Forecasting tools, risk analysis models, “what-if” simulations.
 Key Role: Combines data, models, and analytical tools to support problem-
solving.
4. Executive Information System (EIS)
 Purpose: Provides top executives with easy access to critical information.
 Examples: Strategic dashboards, trend analysis, competitor insights.
 Key Role: Focuses on long-term planning and strategic decision-making.
5. Knowledge Management System (KMS)
 Purpose: Captures, stores, and shares organizational knowledge.
 Examples: Company intranets, document repositories, expert systems.
 Key Role: Promotes learning, innovation, and collaboration across the
organization.
6. Office Automation System (OAS)
 Purpose: Supports daily office activities and communication.
 Examples: Email systems, word processors, scheduling tools, video
conferencing.

System Analysis and Design (SAD)

 4

 Key Role: Improves productivity and streamlines routine office tasks.

Put together, these systems form the backbone of modern organizations,

ensuring information flows seamlessly from operational levels right up to
strategic decision-making.

Q4) What are information systems analysis and design?

 Information systems analysis and design is the organized process of studying
an organization’s needs, identifying problems, and creating or improving
information systems to meet those needs. It ensures that technological solutions
fit business goals and work efficiently.
Systems Analysis
 Definition: The process of examining a business problem, gathering
requirements, and breaking down the system into parts.
 Purpose: To determine what the system should do.
 Activities include:
• Collecting and interpreting facts about current processes.
• Identifying problems, inefficiencies, or opportunities.
• Modeling requirements using tools like data flow diagrams (DFDs),
decision tables, or use cases.
• Making sure all objectives are clear before moving to design.
 Outcome: A detailed specification of system requirements.

Systems Design
 Definition: The process of planning and specifying the structure, components,
and interfaces of the new or improved system.
 Purpose: To determine how the system will meet the requirements identified
in analysis.
 Activities include:
• Designing databases, user interfaces, and workflows.
• Defining hardware and software needs.
• Creating prototypes or models.
• Planning integration with existing systems.
 Outcome: A blueprint for building or modifying the system.

Relationship with System Development Life Cycle (SDLC)

Analysis and design are key phases of the SDLC, which typically include:
1. Planning – defining scope and objectives.
2. Analysis – identifying requirements.
3. Design – creating system specifications.
4. Implementation – building and testing.

System Analysis and Design (SAD)

 5

5. Deployment and Maintenance – rolling out and supporting the system.

Systems analysis specifies what the system should do, while systems design
specifies how it will do it. Together, they create the foundation for building
effective information systems that solve organizational problems and support
decision-making.

Q5) Who is system Analyst? Discuss the role of system Analyst.

A system analyst is a professional who bridges the gap between the needs of
businesses and technological solutions. He/She does this through analyzing,
designing, and continuously making improvements in information systems to
make organization operations more efficient and effective.
Who is a System Analyst?
The Systems Analyst examines and evaluates IT systems to understand how
they work and how they could be improved. He acts as a liaison between the
stakeholders-management, users, clients and the technical team-developers
and engineers. His key objective is to ensure technology solutions meet
business objectives.
Key Roles and Responsibilities of a System Analyst
 Requirement Gathering & Analysis
• Identify business needs through interaction with stakeholders.
• Translate these needs into technical specifications.
 System Design & Development Support
• Design system architecture in collaboration with developers.
• Verify that the system meets all functional and non-functional
requirements.
 Problem Solving & Optimization
• Analyze existing systems to identify inefficiencies.
• Recommend improvements or new solutions.
 Testing & Validation
• Participate in system testing to ensure accuracy and reliability.
• Validate that the system meets the expectations of the users.
 Documentation & Communication
• Prepare detailed reports, diagrams, and documentation.
• Simplify technical details so that stakeholders without a technical
background can understand.
 Training & Support
•Train end-users on new systems.
• Ongoing support and troubleshooting.

System Analysis and Design (SAD)

 6

System analysts ensure that technology investments are cost-effective, user-

friendly, and aligned with organizational strategy. Without them, businesses risk
building systems that don’t meet real needs or fail to integrate properly with
existing processes. In short, system analysts are the designers of efficiency
within IT systems who ensure technology serves further, not complicate,
business goals.

Q6) How has system analysis and design changed over the past two
decades.
SAD has undergone dramatic changes over the last two decades; it has moved
from rigid, document-heavy methods to agile, user-centered, and technology-
driven approaches.

Key Changes in System Analysis and Design: The 2000s–2020s

 From Waterfall to Agile & Iterative Models
• Early 2000s: Traditional Waterfall SDLC dominated. It contained
sequential phases, starting from requirements to design, then
implementation, and finally testing.
• Today: Agile, Scrum, and DevOps are focused on iterative development,
continuous feedback, and faster delivery.

 User-Centered Design
• Past: The focus was on technical efficiency.
• Now: Systems are designed with consideration for user experience,
accessibility, and personalization.

 Integration of Emerging Technologies

• Past: Systems were largely desktop-based with limited integration with
the internet.
• Now: Cloud computing, mobile platforms, AI, IoT, and big data analytics
are integral to system design.

 Shift to Automation & Tools

• Previously: Manual documentation and modeling, such as flowcharts, ER
diagrams.
• Now: This involves automated CASE tools, UML modeling, and design
assisted by AI, which will provide quick ways of carrying out analysis and
documentation.

 Security & Compliance Focus

System Analysis and Design (SAD)

 7

• Past: Security used to be an afterthought.

• Present: Cybersecurity, data privacy laws such as GDPR and HIPAA, and
compliance are integrated into the design from inception.

 Collaboration & Globalization

• Earlier: Teams used to work locally with limited collaboration tools.
• Now: Distributed teams use platforms like Jira, GitHub, and cloud-based
collaboration to develop the system in real time.

System analysis and design have progressed from structured technical

processes to a flexible, user-centered, technology-based practice, which is
faster, more secure, and adaptable.

Q7) Define CASE tools? Explain the types of CASE tools along with
Pros and Cons.
 CASE (Computer-Aided Software Engineering) tools are software applications
designed to automate and support various stages of the software development life
cycle (SDLC), such as analysis, design, coding, testing, and maintenance. They help
improve productivity, accuracy, and consistency in software engineering.
Types of CASE Tools
1. Upper CASE Tools
These tools are used in the early stages of the software development life
cycle (SDLC), such as planning, requirement analysis, and system design. They help
analysts and designers create models, diagrams, and documentation.
• Pros: They improve requirement gathering, system modeling, and documentation
quality.
• Cons: They can be expensive and require significant training to use effectively.

2. Lower CASE Tools

These tools support the later stages of SDLC, including coding, testing, and
maintenance. They are often used by developers and testers to automate tasks like
code generation, debugging, and test execution.
• Pros: They reduce coding errors, speed up testing, and make debugging easier.
• Cons: They are limited to specific phases and may not integrate smoothly with
other tools.

3. Integrated CASE Tools (I-CASE)

These tools provide end-to-end support across the entire SDLC, combining
both upper- and lower-case functionalities. They allow teams to manage
requirements, design, coding, testing, and documentation in one environment.

System Analysis and Design (SAD)

 8

• Pros: They ensure consistency, improve collaboration, and cover the full lifecycle.
• Cons: They are complex, require significant training, and can be resource
intensive.

4. Cross-life Cycle CASE Tools (Middle CASE)

These tools work across multiple phases of SDLC, bridging the gap between
analysis, design, and implementation. They are often used for modeling (like UML
diagrams) and communication between teams.
• Pros: They provide flexibility, enhance communication, and connect design with
coding.
• Cons: They may lack depth in specialized tasks and can consume more resources.

CASE tools provide a framework and set of utilities that assist developers, analysts,
and testers in building high-quality software. They automate repetitive tasks, ensure
proper documentation, and help maintain standards across projects. Examples
include Rational Rose, Enterprise Architect, and Visual Paradigm.

Q8) Define Project.? Explain the project triangle.

 A project is a temporary endeavor undertaken
to create a unique product, service, or result.
• It has a defined start and end date.
• It is unique (not routine operations).
• It requires resources such as people, time, and COS SCOP
money.
• It is aimed at achieving specific objectives T E
within constraints.
Examples: Developing a mobile app,
constructing a bridge, or launching a marketing TIME
campaign.
Fig: A project
Triangle
In short: A project is a temporary effort with defined goals, and the project
triangle shows how scope, time, and cost must be balanced to achieve success.
The Project Triangle, also called the Triple Constraint, is a model that shows the
three primary factors that determine project success:
1. Scope (Quality/Features)
• Defines what the project will deliver.
• Includes requirements, functionalities, and specifications.
• If scope increases (more features), it usually requires more time and cost.
2. Time (Schedule)

System Analysis and Design (SAD)

 9

• Refers to the project deadline.

• Faster delivery may require more resources or reduced scope.
3. Cost (Budget)
• The financial resources allocated.
• Lower budget may mean fewer features or longer timelines.

A project is a temporary and one-of-a-kind effort to create something unique, which

has a specific objective and operates within defined time, cost, and scope
constraints. Unlike on-going operations, a project has a distinct start and end date,
and it aims to deliver a unique product, service, or result. The project triangle, also
known as the triple constraint, shows the balance between three critical factors:
scope-the features and quality of the delivery, time-the schedule or deadline, and
cost-the budget and resources. These three aspects are interrelated, and changing
any one of them has an inevitable effect on the other two. For example, expanding
the scope may require more time and higher costs, while reducing the budget might
limit the features or extend the timeline. Successful project management involves
maintaining the equilibrium among these variables to assure quality outcomes.

Q9) List and describe the common skills and activities of project
Manager?
A Project Manager (PM) is the person responsible for planning, executing, and
closing projects successfully. To do this, they need a blend of skills and perform a
set of activities that ensure the project meets its objectives within scope, time,
and budget.
 Common Skills of a Project Manager
 Leadership
Ability to inspire, guide, and motivate the team toward achieving project goals.
 Communication
Clear and effective communication with stakeholders, team members, and clients to
avoid misunderstandings.
 Time Management
Prioritizing tasks, setting realistic deadlines, and ensuring timely delivery.
 Risk Management
Identifying potential risks early and developing mitigation strategies.
 Problem-Solving
Quickly analyzing issues and finding practical solutions to keep the project on track.
 Negotiation
Balancing stakeholder demands, resolving conflicts, and securing resources.
 Technical Knowledge
Understanding the tools, processes, and technologies relevant to the project
domain.

System Analysis and Design (SAD)

 10

 Common Activities of a Project Manager

 Project Planning
Defining scope, objectives, deliverables, timelines, and resources.
 Team Coordination
Assigning tasks, monitoring progress, and ensuring collaboration among team
members.
 Budget Management
Estimating costs, allocating funds, and controlling expenses.
 Monitoring & Controlling
Tracking project performance using KPIs, dashboards, and reports.
 Stakeholder Management
Engaging with stakeholders, managing expectations, and providing updates.
 Risk Assessment
Identifying risks, analyzing their impact, and implementing contingency plans.
 Quality Assurance
Ensuring deliverables meet required standards and client expectations.
 Project Closure
Completing final deliverables, obtaining approvals, and documenting lessons
learned.

A project manager is both a strategist and a facilitator. Their skills ranging from
leadership to risk management enable them to handle complex challenges, while
their activities like planning, monitoring, and closing ensure projects are delivered
successfully.

Q10) Explain the Phase of Project Management?

Project management is typically divided into five key phases, often referred to as
the Project Management Life Cycle. Each phase has its own purpose, activities, and
deliverables, and together they ensure that a project is completed successfully.

Phases of Project Management

1. Initiation Phase
• This is where the project begins.
• The main goal is to define the project’s purpose, objectives, and feasibility.
• Activities include identifying stakeholders, preparing a business case, and
securing approval.
• Deliverable: Project Charter (formal authorization of the project).
2. Planning Phase
• Detailed planning ensures the project runs smoothly.
• Activities include defining scope, setting goals, creating schedules,
estimating costs, and identifying risks.
• Tools like Gantt charts, Work Breakdown Structures (WBS), and risk registers
are often used.
• Deliverable: Project Management Plan (roadmap for execution).
3. Execution Phase

System Analysis and Design (SAD)

 11

• This is where the actual work happens.

• Resources are allocated, tasks are assigned, and deliverables are produced.
• The project manager coordinates the team, manages communication, and
ensures quality standards are met.
• Deliverable: Project Deliverables (products, services, or results).
4. Monitoring and Controlling Phase
• Runs parallel to execution to track progress and performance.
• Activities include monitoring KPIs, managing risks, controlling changes, and
ensuring the project stays on scope, time, and budget.
• Deliverable: Performance Reports and updated project documents.
5. Closure Phase
• Marks the formal end of the project.
• Activities include delivering the final product, obtaining stakeholder
approval, releasing resources, and documenting lessons learned.
• Deliverable: Final Project Report and Lessons Learned Document.

In short, the five phases Initiation, Planning, Execution, Monitoring & Controlling,
and Closure form the backbone of project management. They ensure that projects
are well-defined, properly planned, executed efficiently, monitored for success, and
closed with valuable insights into the future.

Q11) What is Outsourcing? Explain its pros and cons.

Outsourcing is a business activity in which an organization outsources some of its
tasks, services, or processes to third-party vendors or companies instead of
performing them in-house. This is generally done to cut costs, utilize special
expertise, and free the company to focus on its core activities.
Outsourcing: a company might outsource one of its functions, such as IT services,
customer support, manufacturing, or payroll. It can be domestic, meaning within the
same country, or international, which is offshoring. Example: A company in Nepal
outsourcing software development to a firm in India.
Pros of Outsourcing
 Cost Savings: Saves costs by using cheaper labor markets or specialized
vendors.
 Core Business Focus: Lets companies focus on strategic goals while
outsourcing routine tasks.
 Access to Expertise: Provides specialized skills and advanced technology
that may not be available in-house.
 Scalability & Flexibility: Operations can be easily scaled up or down
depending upon demand.
 Improved Efficiency: With better processes and experience, vendors are
often able to deliver faster results.

System Analysis and Design (SAD)

 12

Cons of Outsourcing
 Loss of Control: Less direct oversight of outsourced tasks may affect
quality.
 Communication Barriers: Different time zones, languages, and cultures
can lead to misunderstandings.
 Security Risks: The sensitive data being shared with external parties
increases the chance of breach.
 Dependency on Vendors: Over-relying on outsourcing partners makes the
company also vulnerable with the event of a vendor failure.
 Hidden Costs: Outsourcing reduces direct costs but may involve other costs
in managing contracts and quality control.

Outsourcing helps an organization reduce costs while gaining skills, but it also
involves challenges such as loss of control and other attendant risks. The secret to
successful outsourcing depends on the right selection of vendors, clear
communication, and proper balancing of costs versus quality.

Q12) What are the different sources of software? List them.

Software can come from a variety of sources depending on how it is developed,
distributed, and acquired. Here’s a clear list of the different sources of software:

Sources of Software
1. In-house Development
 An organization’s own IT team develops software internally.
 Tailored to meet specific business needs.
2. Contracted/Custom Development
 Software is built by external vendors or consultants specifically for a client.
 Often used when specialized expertise is required.
3. Commercial Off-the-Shelf (COTS) Software
 Ready-made software products are available for purchase.
 Examples: Microsoft Office, Adobe Photoshop.
4. Open-Source Software
 Software whose source code is freely available to the public.
 Examples: Linux, Apache, MySQL.
5. Shareware

System Analysis and Design (SAD)

 13

 Software distributed freely for trial use but requires payment for full
functionality.
 Example: WinRAR.
6. Freeware
 Software available at no cost, often with limited support.
 Examples: VLC Media Player, Google Chrome.
7. Embedded Software
 Software is built into hardware devices to control their functions.
 Examples: software in washing machines, routers, or smartphones.
8. Web-based/Cloud Software
 Applications delivered via the internet, often subscription based.
 Examples: Google Workspace, Salesforce.

Software can originate from several different sources, each serving unique needs
depending on cost, flexibility, and usage. Organizations may build applications
through in-house development, where their own IT teams design solutions
tailored to specific requirements, or they may rely on contracted/custom
development, outsourcing projects to external vendors for specialized expertise.
Many businesses adopt commercial off-the-shelf (COTS) software, which is
ready-made and widely available, while others prefer open-source software,
where the source code is freely accessible for modification. Additionally, there are
shareware programs that allow trial use before purchase, and freeware, which is
completely free but often comes with limited support. In certain cases, embedded
software is built directly into hardware devices, and web-based/cloud software
is delivered online through subscription models. Some organizations also continue
to use legacy systems, older software maintained for compatibility. Together,
these sources provide a wide range of options, allowing businesses and individuals
to choose solutions that best fit their goals and resources.

System Analysis and Design (SAD)