Q.1 What is System? Explain System Types.

What is a System?

A system is a set of connected components or elements that work together to achieve a common
goal or purpose. It takes inputs, processes them, and produces outputs. Systems can be found in
various fields such as engineering, biology, computer science, and management.

System Types

1. Based on Functionality

 a. Physical Systems
Systems made of physical components.
Example: Computer hardware, car engine, electric circuits.

 b. Abstract Systems
Conceptual or non-physical systems, often involving ideas or models.
Example: Mathematical models, software algorithms, financial systems.

2. Based on Interaction

 a. Open Systems
Systems that interact with their environment by exchanging energy, matter, or information.
Example: Human body, business organization, computer networks.

 b. Closed Systems
Systems that do not interact with the environment; isolated from external influences.
Example: Thermos flask (ideal closed system).

3. Based on Structure

 a. Deterministic Systems
Systems that operate in a predictable and well-defined manner.
Example: Calculator, clockwork mechanism.

 b. Stochastic (Probabilistic) Systems

Systems that involve randomness or uncertainty in their behaviour.
Example: Stock market, weather systems.

4. Based on Time Behaviour

 a. Static Systems
Systems that do not change over time.
Example: Bridge structure, map.

 b. Dynamic Systems
Systems that change over time and respond to inputs or environmental changes.
Example: Traffic control system, economy.
5. Based on Purpose

 a. Man-Made Systems
Systems designed and created by humans to fulfil specific purposes.
Example: Computers, satellites.

 b. Natural Systems
Systems that occur naturally in the environment without human intervention.
Example: Solar system, ecosystem.

6. Based on Integration

 a. Simple Systems
Systems with few components and straightforward interactions, easy to understand.
Example: Light switch.

 b. Complex Systems
Systems with many interrelated components and intricate interactions.
Example: Human brain, internet.

Q.2 What is software system? Explain Types

What is a Software System?

A software system is a collection of programs, procedures, and data that perform specific tasks on a
computer or other digital devices. It provides the necessary instructions to hardware to perform
useful functions and enables users to accomplish various activities.

Types of Software Systems

1. System Software

Software that provides a platform to run application software and manages hardware resources.

 Operating Systems (OS): Windows, Linux, macOS, Android

 Utility Programs: Antivirus, Disk Cleaners

 Device Drivers: Printer driver, graphics card driver

 Firmware: Embedded OS in routers, washing machines

2. Application Software

Software designed for end users to perform specific tasks.

 Productivity Software: MS Office, Google Docs, Excel

 Media Players: Windows Media Player

  Browsers: Chrome, Firefox, Edge

 Graphics Software: Photoshop, CorelDraw

3. Programming Software

Tools used by developers to write, test, and maintain software.

 Compilers: GCC, Turbo C++

 Text Editors: VS Code, Sublime Text

 Debuggers: GDB, WinDbg

 IDEs (Integrated Development Environments): IntelliJ, Eclipse, NetBeans

4. Middleware

Acts as a bridge between system software and applications, facilitating communication and data
management.

 Database Middleware: ODBC, JDBC

 Message Oriented Middleware (MOM): RabbitMQ, Kafka

 Object Request Brokers: CORBA

 Web Middleware: API Gateways, web servers

5. Embedded Software

Software embedded in hardware systems to perform specific control functions.

 Examples: Software in microwave ovens, smart TVs, ATM machines, automotive systems
(ABS, ECU)

6. Enterprise Software

Software designed to support business operations and processes.

 Enterprise Resource Planning (ERP): SAP, Oracle

 Customer Relationship Management (CRM): Salesforce, Zoho

 Supply Chain Management: SAP SCM, Oracle SCM

7. Web-Based Software

Software that runs within a web browser and does not require installation on the local machine.

 Examples: Gmail, Google Drive, Canva, Trello

  Technologies: HTML, CSS, JavaScript, backend frameworks ([Link], Django)

8. Artificial Intelligence Software

Software that mimics human intelligence and makes decisions based on data.

 Machine Learning Systems: TensorFlow, Scikit-learn

 Natural Language Processing (NLP): ChatGPT, Google Translate

 Robotic Process Automation (RPA): UiPath, Blue Prism

9. Real-Time Software

Systems that respond to inputs instantly, often used in control and monitoring systems.

 Examples: Air Traffic Control, Pacemakers, Industrial Robotics

 Types:

 Hard real-time: Systems with strict timing constraints (e.g., Air Traffic Control,
Medical Systems)

 Soft real-time: Systems with more flexible timing (e.g., Multimedia Transmission,
Computer Games, Voice over IP)

Q.3 Detailed Explanation of SDLC (Software Development Life Cycle)

Phases of SDLC

1. Preliminary Investigation

 Understand the problem or opportunity.

 Request clarification about the system request.

 Conduct a feasibility study considering:

 Technical feasibility: Can the system be built with current technology and
expertise?

 Economic feasibility: Are the costs justified by the benefits?

 Operational feasibility: Will the system solve the problem and be accepted
by users?

 Obtain management approval to proceed.

2. Determination of System Requirements

  Business analysts and stakeholders gather and analyse requirements.
 Goal: Understand what the user needs.
 Output: Software Requirements Specification (SRS) document.
3. Design of System
 Design technical architecture and UI/UX (user research, wireframes,
visual design, interaction patterns).
 Goal: Plan how the software will work and look.
 Output: Design documents, wireframes, database schemas.
 Example: Decide how the login page will look and how the database
will store orders.
4. Development of Software
 Developers write code based on the design.
 Goal: Build the software using programming languages and tools.
 Output: Functional software modules.
 Example: Frontend in React Native, backend in [Link], database in
MongoDB.
5. System Testing
 Testers check the software for bugs, errors, and performance issues.
 Goal: Ensure the software is reliable and meets requirements.
 Types of Testing: Unit, Integration, System, Acceptance.
 Example: Test if payment gateway works properly or if app crashes on
Android 12.
6. Implementation and Evaluation
 The final product is released to users.
 Goal: Make the software live and available.
 Environment: May include staging → production deployment.
 Example: Upload the app to Google Play Store and App Store.
7. Maintenance
 Fix bugs, update features, support users.
 Goal: Keep the software working well over time.
 Types: Corrective, Adaptive, Perfective maintenance.
 Example: Add a new payment method or fix a login bug.
Goal of SDLC

 To develop software that is cost-effective, reliable, maintainable, and meets user

expectations.

Popular SDLC Models

Model Description Suitable For

Waterfall Linear, phase-by-phase Small, well-defined projects

Agile Iterative, flexible Changing requirements, startups

Spiral Design + prototyping in iterations Risk-heavy, large projects

V-Model Testing at each stage Critical systems (e.g., medical)

DevOps Combines development and operations Fast delivery, automation-focused

Q.4 Roles of a System Analyst

A System Analyst plays an important role in the development and maintenance of

information systems by bridging the gap between business needs and technology solutions. Their
responsibilities include:

1. Requirement Gathering

 Meet with stakeholders to understand their business needs.

 Document both functional and non-functional requirements.

2. Feasibility Study

 Evaluate the technical, economic, and operational feasibility of the project.

 Help decision-makers determine if the project is worth pursuing.

3. System Design

 Translate gathered requirements into detailed system specifications.

 Design system architecture including data flow, interfaces, and processes.

4. Communication Bridge

 Act as a liaison between business users and developers.

 Ensure clear understanding of expectations and constraints on both sides.

5. Documentation
  Prepare and maintain important documents such as system requirements, data
models, and process flows.

6. System Evaluation & Selection

 Assist in choosing appropriate hardware, software, or third-party services.

 Evaluate system performance and recommend improvements.

7. Support Development & Testing

 Collaborate with developers to ensure they understand the design.

 Assist in developing test cases and conducting user acceptance testing (UAT).

8. Training & Support

 Help train end-users on the new system.

 Provide post-deployment support and gather user feedback.

Tools Used by System Analysts

 UML Tools: Lucidchart, [Link]

 Project Management: Jira, Trello

 Requirement Gathering: MS Word, Confluence

 Modelling Tools: ERD (Entity Relationship Diagram), DFD (Data Flow Diagram)

Q.5 Explain Requirement Gathering Techniques

Requirement Elicitation is the process of gathering information from stakeholders about what they
need from the system. It involves various fact-finding techniques to ensure a comprehensive
understanding of the system requirements.

Common Requirement Gathering Techniques:

1. Interviews

 One-on-one or group discussions with stakeholders to understand their needs and

expectations.

 Two types of interviews:

 Structured Interview: Uses standardized questions with open or closed

response formats.

 Advantages: Uniform questions, easy to administer and evaluate,

objective, shorter interviews.

 Disadvantages: High preparation cost, may limit respondent

freedom, less flexibility.
  Unstructured Interview: Uses a flexible question-answer format encouraging
respondents to share feelings, ideas, and beliefs.

 Advantages: Greater flexibility, can explore spontaneous topics, may

uncover overlooked areas.

 Disadvantages: Time-consuming, potential interviewer bias, may

gather irrelevant information.

2. Questionnaires/Surveys

 Distribute structured or semi-structured forms to collect information from a large

group.

 Can be open-ended (to explore feelings and opinions) or closed (to control
responses).

 Advantages: Can reach many respondents, standardized format yields reliable data.

 Disadvantages: No observation of reactions, may have low response rate, costly to

develop and distribute.

3. Record Review

 Examining existing system documentation, manuals, reports, policies, and

procedures.

 Helps understand current processes and organizational operations.

 Useful at the start or during the study to compare actual operations with
documented procedures.

4. Observation

 Watching users perform tasks in their actual work environment.

 Helps discover hidden or unstated needs and obtain first-hand information on how
activities are carried out.

 Useful for understanding document handling, process flows, and real-world

operations.

5. Workshops

 Group sessions with users and stakeholders to brainstorm and gather requirements
collaboratively.

6. Brainstorming

 Generating a wide range of ideas or requirements from stakeholders in a short time.

7. Focus Groups

 Interactive group discussions with selected users to explore needs, opinions, and
preferences.

Q.6 Categories of information systems.

1. Transaction Processing Systems (TPS):

- Fundamental computer-based systems that process business transactions.

- Aim to improve routine business activities.

- Transactions are events or activities affecting the organization, such as placing orders,
billing customers, hiring employees, depositing cheques, calculating salary, making payments
to suppliers, and managing materials.

- Transaction processing activities include calculation, classification, sorting, storage and

retrieval, and summarizing.

- Operate at the operational level (lowest level).

- Characteristics:

1. High volume of transactions.

2. Each transaction is similar.

3. Procedures for processing transactions are well understood and detailed.

4. Few exceptions to normal procedures.

5. Provide speed and accuracy.

2. Management Information Systems (MIS):

- Assist managers in decision making and problem solving.

- Used at middle and top management levels.

- Utilize data from transaction processing and other sources.

- Support routine, structured decisions made at regular intervals (daily, weekly,

monthly).

- Provide predefined reports and queries to help managers make recurring decisions.

- Decisions supported are structured because the information needed and decision
processes are known.

3. Decision Support Systems (DSS):

- Assist managers in making decisions that are unstructured or semi-structured,

often occurring once or infrequently.

- Unstructured decisions lack clear procedures and may have unknown factors.

- Key aspect is determining what information is needed.

- Provide flexibility for users to define report contents and formats since predefined
reports are not feasible.
 - Generally used by top management.

- Support managerial judgment but do not replace it.

Q.7 Use of Decision Tree with Example

Decision Tree is a diagrammatic method used to represent conditions and actions sequentially. It
helps in deciding which conditions to consider first, second, and so on, showing the relationship
between each condition and its permissible actions. The diagram looks like branches of a tree, hence
the name.

Key Features of a Decision Tree:

 The root (left side) is the starting point of the decision process.

 Nodes represent conditions that must be evaluated.

 Branches represent possible outcomes of each condition.

 The right side lists the actions to be taken based on the sequence of conditions followed.

 Progression from left to right along branches corresponds to making a series of decisions.

Advantages of Using Decision Trees:

1. Clearly identifies the actual decisions to be made and the sequence of operations.

2. Easy to understand and interpret.

3. Does not require assumptions about data before preparation.

4. Suitable for solving real-world problems.

Example: Decision Tree for Discount Authorization

Q.8 Explain use and types of decision table with example

Decision Table

A Decision Table is a tabular method for representing and analysing decision rules. It helps in
specifying which actions to take under various conditions. It is a matrix consisting of:

 Condition Statements: Identify relevant conditions.

 Condition Entries: Specify the values or states of each condition.

 Action Statements: List possible actions to be taken.

 Action Entries: Indicate which actions to perform for each combination of conditions.

Purpose:

 To clearly define complex decision logic.

 To avoid ambiguity in decision-making.

 To provide a systematic way to represent all possible scenarios.

Components of a Decision Table

Component Description

Condition Statement Identifies the relevant conditions to consider.

Condition Entry Specifies the value or state of each condition.

Action Statement Lists the possible actions to take.

Action Entry Indicates which actions apply for each condition combination.

Types of Decision Table Entries

 1. Extended-Entry Form:
Every condition and action entry are explicitly stated (no blanks).

2. Mixed-Entry Form:
Some entries may be left blank or marked with a symbol (e.g., 'X') to indicate "don't care" or
irrelevant conditions.

3. ELSE Form:
Uses an ELSE clause to cover all other unspecified conditions, simplifying the table.

Q.9 There are three types of accounts in a bank. Assume that the accounts are current account,
saving account and fixed deposit account. In current account bank do not give any interest, in saving
account bank gives 5% of interest, and in fixed deposit account bank gives interest depend on time at
following:

Duration Interest

6 months 8%

1 year 10%

5 years 12%

Draw the data flow diagram, decision table, decision tree and structured English

1. Data Flow Diagram (DFD)

Context:

 Input: Account Type, Duration (only for Fixed Deposit)

 Process: Calculate Interest Rate

 Output: Interest Rate

 Level 0 DFD (High-level)

 Level 1 DFD (Detailed)

2. Decision Table

Condition / Decision Rules 1 2 3

Account Type Current Account Saving Account Fixed Deposit

Duration N/A N/A 6 months

Interest Rate (%) 0 5 8

3. Decision Tree
4. Structured English

IF Account_Type = "Current Account" THEN

Interest_Rate = 0

ELSE IF Account_Type = "Saving Account" THEN

Interest_Rate = 5

ELSE IF Account_Type = "Fixed Deposit" THEN

IF Duration = "6 months" THEN

Interest_Rate = 8

ELSE IF Duration = "1 year" THEN

Interest_Rate = 10

ELSE IF Duration = "5 years" THEN

Interest_Rate = 12

ELSE

Interest_Rate = 0 // No interest for other durations

END IF

ELSE

Interest_Rate = 0 // Default case if account type is unknown

END IF

Q.10 Write down IEEE definition for Software engineering

The application of a systematic, disciplined, quantifiable approach to the development, operation,

and maintenance of software; that is, the application of engineering to software

Q.11 Explain with figure s/w engineering layers

Software Engineering Layers

Software engineering is structured in layers that build upon each other to ensure quality software
development. These layers are:

1. Process Layer

 Purpose:
The process layer manages and controls software projects.

 Focus:
It ensures the delivery of quality work products by defining a structured approach to
software development activities.

 Role:
It provides a framework for planning, monitoring, and controlling the software lifecycle.

2. Methods Layer

 Purpose:
The methods layer provides the technical "how-to" for software engineering tasks.

 Focus:
It includes techniques and guidelines for:

 Communication among stakeholders

 Requirements analysis

 Design modelling

 Program construction
  Testing and validation

 Role:
It guides engineers on applying best practices and technical procedures to produce quality
software.

3. Tools Layer

 Purpose:
The tools layer offers automated or semi-automated support for the process and methods.

 Focus:
It includes software tools that assist in:

 Project management

 Requirements capture

 Design and modelling

 Code generation

 Testing and debugging

 Role:
Tools improve productivity, consistency, and quality by supporting engineers in their tasks.

Q.12 Define s/w process and explain process framework activities

Definition of Software Process

A Software Process is a collection of activities, actions, and tasks that are performed to create a
software work product.

 Activities:
Broad efforts aimed at achieving a major objective in software development.

 Actions:
A set of tasks grouped together to produce a significant work product.

 Tasks:
Small, well-defined objectives focused on producing specific outcomes.

Software Process Framework

A Process Framework establishes the foundation for a complete software engineering process by
identifying a small number of framework activities. These activities are applicable to all software
projects, regardless of their size or complexity.

Process Framework Activities

1. Communication
  Engage with stakeholders and customers.

 Understand the objectives of the system and gather software requirements.

2. Planning

 Develop a detailed software project plan.

 Include resources needed, tasks to be performed, risk factors, and schedule.

3. Modelling

 Create architectural and design models.

 Helps in understanding the problem better and working towards the best solution.

4. Construction

 Generate code and perform testing.

 Identify and fix errors, ensuring all specified requirements are met.

5. Deployment

 Deliver the complete or partial software product to the customer.

 Obtain evaluation and feedback for further improvement.

Q.13 Explain in brief general steps in carrying out in s/w engineering

1. Understand the Problem through Communication

Engage with stakeholders, users, and customers to gather and clarify the
requirements. Effective communication ensures a clear understanding of the
problem to be solved.

2. Plan a Solution by Modelling and Software Design

Develop models and design the software architecture that addresses the
requirements. This step involves creating blueprints that guide the construction of
the software.

3. Carry Out the Plan for Code Generation

Implement the design by writing code. This step translates the planned solution into
a working software product.

4. Examine the Result for Accuracy by Testing and Quality Assurance

Test the software to identify and fix defects. Quality assurance activities ensure the
software meets the specified requirements and is reliable.

Q.14 Explain principle of best practice / or Hooker’s general

Principles of Best Practice in Software Engineering

 1. Software Should Provide Value to Users
The primary goal of software is to deliver real value to its users. Every feature or function
should contribute meaningfully to user needs.

2. Keep the Software Design Simple

Simplicity in design makes software easier to understand, maintain, and less prone to errors.

3. Maintain the Vision of the Project Throughout

The overall vision or goal of the project should guide all development activities to ensure
conceptual integrity.

4. Keep Work Products Understandable

Documentation, code, and other work products should be clear and organized so others can
easily understand and work with them.

5. Design for Future Changes

Software should be designed flexibly to accommodate future modifications without major
rework.

6. Build Reusable Components

Developing reusable modules or components saves time and effort in current and future
projects.

7. Think Before Acting (Learn Before Starting)

Careful planning and understanding before implementation lead to better outcomes.

Hooker’s General Principles for Software Engineering Practice

1. The Reason It All Exists

Software systems must provide value to users. Before starting any project or task, ask:
“Does this add real value to the system?”
If the answer is no, do not proceed.

2. KISS (Keep It Simple, Stupid!)

Simple designs are easier to maintain and less error-prone.

3. Maintain the Vision

Without a clear, consistent vision, the system becomes a patchwork of incompatible designs.

4. What You Produce, Others Will Consume

Always produce work products (code, documentation) that others can understand and use.

5. Be Open to the Future

Design software to be adaptable to future changes and requirements.

6. Plan Ahead for Reuse

Anticipate reuse opportunities and design components accordingly.

7. Think!
Thoughtful, deliberate planning before action leads to better results.
Q.15 What is Agility? Explain in brief the manifesto for Agile software development nt.

What is Agility?

Agility refers to the ability of a software development team to respond effectively, rapidly, and
adaptively to change. It emphasizes flexibility, continuous communication, and collaboration to
deliver high-quality software that meets evolving customer needs.

Manifesto for Agile Software Development (Brief Explanation)

The Agile Manifesto promotes principles that guide agile teams to work efficiently and
collaboratively:

 Effective (rapid and adaptive) response to change: Agile teams embrace change even late
in development, adapting quickly to new requirements or market conditions.

 Effective communication among all stakeholders: Continuous and open communication

between developers, customers, and other stakeholders ensures alignment and quick
resolution of issues.

 Drawing the customer onto the team: Customers are actively involved throughout the
development process, providing feedback and clarifying requirements.

 Organizing a team so that it is in control of the work performed: Agile teams are self-
organizing and empowered to make decisions about how to accomplish their work.

 Yielding rapid, incremental delivery of software: Software is developed and delivered in

small, functional increments, allowing for frequent releases and early value to customers.

Q.16 Explain the Agile process and key quality of the people in an agile team in brief.

Agile Process

The Agile process is an iterative and adaptive approach to software development characterized by:

 Customer-driven requirements: Development is guided by customer descriptions of what is

needed, often expressed as scenarios.

 Short-lived plans: Agile recognizes that plans are temporary and must be frequently updated
to reflect changes.

 Iterative development: Software is developed in repeated cycles with a strong focus on

construction activities.

 Multiple software increments: The product is delivered in small, functional pieces rather
than a single final release.

 Adaptability: The process adjusts continuously as changes occur in requirements or

environment.

Key Qualities of People in an Agile Team

Agile teams rely heavily on the human factors that enable flexibility and collaboration. Key qualities
include:

 Competence: Team members must have the necessary skills and capabilities to perform their
tasks effectively.

 Common Focus: Everyone on the team shares the same goals and priorities.

 Collaboration: Open and continuous communication and cooperation among team members
and stakeholders.

 Decision-Making Ability: The team should be empowered to make decisions quickly and
effectively.

 Fuzzy Problem-Solving Ability: Ability to handle uncertain or ambiguous problems creatively.

 Mutual Trust and Respect: Team members trust each other and respect diverse opinions and
contributions.

 Self-Organization: The team organizes its own work and processes without heavy external
control.

Q.17 Explain Extreme Programming with figure.

Extreme Programming (XP)

Extreme Programming (XP) is an Agile software development methodology that emphasizes

customer satisfaction, simplicity, and frequent delivery of functional software through iterative
cycles.
XP Planning

 User Stories: The process begins with creating user stories, which are short descriptions of
features from the customer's perspective.

 Cost Assessment: The Agile team evaluates each story and assigns a cost (effort estimate).

 Grouping Stories: Stories are grouped into increments that can be delivered as functional
software.

 Commitment: The team commits to a delivery date for each increment.

 Project Velocity: After delivering the first increment, the team measures project
velocity (rate of progress) to help plan and schedule subsequent increments.

XP Design

 Keep It Simple Principle: Designs are kept as simple as possible to meet current
requirements.

 CRC Cards: Use of Class-Responsibility-Collaborator cards to define classes and their

responsibilities collaboratively.

 Spike Solutions: For complex design problems, small prototype solutions called spikes are
created to explore approaches.

 Refactoring: Continuous improvement of the internal design through iterative refinement

without changing external behaviour.

XP Coding

 Test-Driven Development: Unit tests are written before coding a feature (test-first
approach).

 Pair Programming: Two programmers work together at one workstation, improving code
quality and knowledge sharing.

XP Testing

 Daily Unit Tests: All unit tests are run daily to ensure code correctness.

 Acceptance Tests: Defined by the customer to verify that the software meets customer-
visible requirements.

Q.18 Explain Adaptive Software Development.

Adaptive Software Development (ASD)

Adaptive Software Development (ASD) is an iterative and flexible approach to software development
originally proposed by Jim Highsmith. It is designed to handle complex and uncertain projects by
emphasizing adaptability and continuous learning.

Distinguishing Features of ASD:

 Mission-Driven Planning: Planning is focused on achieving a clear mission or goal rather

than detailed upfront specifications. This allows the team to adapt plans as the project
evolves.

 Component-Based Focus: Development is organized around components or modules,

enabling incremental delivery and easier management of changes.

 Time-Boxing: Work is divided into fixed-length periods called time boxes (short iterations),
within which specific tasks or features are developed and delivered.

 Explicit Consideration of Risks: Risks are identified and managed proactively throughout the
development process to reduce uncertainties.

 Emphasis on Collaboration: Close collaboration among stakeholders is encouraged to gather

requirements and ensure alignment with business needs.

 Emphasis on Learning: Continuous learning and adaptation are integral, with teams
reflecting on progress and adjusting processes and goals accordingly.

Q.19 Explain Scrum process flow with figure.

Scrum Process Flow

Scrum is an Agile software development framework originally proposed by Ken Schwaber and Jeff
Sutherland (and later popularized by Schwaber and Beedle). It focuses on iterative development,
collaboration, and delivering working software in fixed time periods called sprints.

Distinguishing Features of Scrum:

 Work Partitioned into Packets: Development tasks are divided into manageable units or
"packets" derived from a prioritized list of requirements called the product backlog.

 Ongoing Testing and Documentation: Testing and documentation happen continuously as

the product is developed.

 Sprints: Work is organized into fixed-length iterations called sprints (usually 2-4 weeks). Each
sprint aims to complete a set of backlog items. No changes are allowed during a sprint to
maintain focus.

 Daily Scrum Meetings: Short daily meetings (~15 minutes), led by the Scrum Master, where
team members discuss progress, plans, and impediments. These meetings are often held
standing up to keep them brief.
  Sprint Demos: At the end of each sprint, a demo of the working product increment is
delivered to the customer for feedback.

What is a Data Dictionary?

A Data Dictionary is a catalog -a repository-of the elements in a system. As a name

suggests these elements center around data and the way they are structured to meet user

requirements and organization need. The data dictionary stores details and descriptions

of data element.

Q.20 all process model

 SDLC

A. Preliminary Investigation

B. Determination of System Requirements

C. Design of System

D. Development of Software

E. System Testing

F. Implementation and Evaluation

G. Maintenance
 Waterfall
A. Communication
B. Planning
C. Modelling
D. Construction
E. Deployment
 V-Model
1) Verification
A. Requirement Gathering
B. Architectural Design
C. Component Design
D. Code Generation
2) Validation
A. Unit Testing
B. Integration Testing
C. System Testing
D. Acceptance Testing
 Agility
o XP (Extreme Programming)
A. Planning
B. Design
C. Coding
a) Refactoring
D. Testing
a) Release
o Scrum
o Adaptive Software Development
 Evolutionary
o Prototyping
A. Communication
B. Quick Planning
C. Modelling Design
D. Construction of Prototype
E. Deployment, Delivery & Feedback
o Spiral
A. Identifying Objectives
B. Risk Analysis
C. Product development & Testing
D. Evaluation
 Incremental
A. Requirement Analysis
B. Design & Developing
C. Testing
D. Implementation
 Iterative
A. Communication
 B. Planning
C. Modelling
D. Construction
E. Deployment

Q.21 All diagram

 Data Dictionary
 Decision Tree
 Decision Table
o Extended-Entry Form
o Mixed-Entry Form
o ELSE Form
 DFD
 ER Diagram
 UML
o Use Case
o Activity
o Class
o Sequence
o State
o Deployment