SAD | PAPER
1. SDLC Stands for .
--> System Development Life Cycle (or Software Development Life Cycle).
--> System Development Life Cycle (or Software Development Life Cycle).
2. What is Information System?
--> An Information System is a collection of hardware, software, data, people, and procedures that work together to collect, process, store, and distribute information to support decision-making in an organization.
--> An Information System is a collection of hardware, software, data, people, and procedures that work together to collect, process, store, and distribute information to support decision-making in an organization.
3. What is Software Engineering?
--> Software Engineering is the systematic, disciplined, and quantifiable approach to the design, development, operation, and maintenance of software.
--> Software Engineering is the systematic, disciplined, and quantifiable approach to the design, development, operation, and maintenance of software.
1. Give Difference Between Quality Assurance (QA) and Quality Control (QC).
Quality Assurance (QA):
- It is a process-oriented approach focused on preventing defects.
- It ensures that the right processes are defined and followed during development.
Quality Control (QC):
- It is a product-oriented approach focused on identifying and fixing defects.
- It involves executing the software (testing) to ensure the final product meets the required standards.
Quality Assurance (QA):
- It is a process-oriented approach focused on preventing defects.
- It ensures that the right processes are defined and followed during development.
Quality Control (QC):
- It is a product-oriented approach focused on identifying and fixing defects.
- It involves executing the software (testing) to ensure the final product meets the required standards.
1. Write short note on SDLC.
System Development Life Cycle (SDLC) is a structured, step-by-step process used by software industries to design, develop, and test high-quality software. It provides a standard framework to build a system that meets customer expectations and completes within time and cost estimates.
Phases of SDLC:
1. Requirement Gathering and Analysis: The most important phase where business requirements are gathered from the client. Feasibility studies are conducted to check if the software is viable.
2. System Design: Based on the requirements, the system and software design is prepared. This phase defines the overall system architecture (Logical design and Physical design).
3. Coding / Implementation: The actual development starts here. Programmers write the source code using programming languages based on the design documents.
4. Testing: The developed software is tested thoroughly against the requirements to ensure there are no bugs and it works exactly as expected.
5. Deployment: Once tested and approved, the software is deployed into the production environment for the end-users to use.
6. Maintenance: After deployment, the system is maintained by updating it, fixing any newly discovered issues, and enhancing it to handle new requirements over time.
System Development Life Cycle (SDLC) is a structured, step-by-step process used by software industries to design, develop, and test high-quality software. It provides a standard framework to build a system that meets customer expectations and completes within time and cost estimates.
Phases of SDLC:
1. Requirement Gathering and Analysis: The most important phase where business requirements are gathered from the client. Feasibility studies are conducted to check if the software is viable.
2. System Design: Based on the requirements, the system and software design is prepared. This phase defines the overall system architecture (Logical design and Physical design).
3. Coding / Implementation: The actual development starts here. Programmers write the source code using programming languages based on the design documents.
4. Testing: The developed software is tested thoroughly against the requirements to ensure there are no bugs and it works exactly as expected.
5. Deployment: Once tested and approved, the software is deployed into the production environment for the end-users to use.
6. Maintenance: After deployment, the system is maintained by updating it, fixing any newly discovered issues, and enhancing it to handle new requirements over time.
--- OR ---
1. DFD Stands for .
--> Data Flow Diagram.
--> Data Flow Diagram.
2. What is System?
--> A System is an organized, interacting, or interdependent group of elements forming a complex whole, designed to achieve a specific goal or set of goals.
--> A System is an organized, interacting, or interdependent group of elements forming a complex whole, designed to achieve a specific goal or set of goals.
3. In a ___ Activity are represented by a ___.
--> In an Activity Diagram, activities are represented by a rounded rectangle.
--> In an Activity Diagram, activities are represented by a rounded rectangle.
1. Explain Fact Finding Techniques in detail.
(Note: Since this is 2 marks, providing a brief overview of the main techniques is appropriate.)
Fact-finding techniques are methods used by system analysts to collect information about the existing system and user requirements. The primary techniques include:
1. Interviewing: Directly talking to users and managers to get detailed, qualitative feedback.
2. Questionnaires: Distributing structured forms to a large group of people to gather quantitative data quickly.
3. Observation: Directly watching employees perform their daily tasks to see exactly how the current system works.
4. Record / Document Review: Studying existing manuals, forms, and reports to understand data flow and business rules.
(Note: Since this is 2 marks, providing a brief overview of the main techniques is appropriate.)
Fact-finding techniques are methods used by system analysts to collect information about the existing system and user requirements. The primary techniques include:
1. Interviewing: Directly talking to users and managers to get detailed, qualitative feedback.
2. Questionnaires: Distributing structured forms to a large group of people to gather quantitative data quickly.
3. Observation: Directly watching employees perform their daily tasks to see exactly how the current system works.
4. Record / Document Review: Studying existing manuals, forms, and reports to understand data flow and business rules.
1. Explain Decision Table in detail.
Definition:
A Decision Table is a tabular representation of complex logical rules. It is a fact-finding and system modeling tool used to map out various conditions and the corresponding actions that should be taken. It is highly useful when business rules involve multiple combinations of "If-Then" logic.
Structure of a Decision Table:
It is divided into four main quadrants:
1. Condition Stub (Upper Left): Lists all the possible conditions or variables that affect the decision.
2. Condition Entry (Upper Right): Contains the actual values for the conditions (usually represented as Y for Yes, N for No, or dashes '-' for irrelevant).
3. Action Stub (Lower Left): Lists all the possible actions that can be taken based on the conditions.
4. Action Entry (Lower Right): Indicates which specific actions are to be executed for each specific combination of conditions (usually marked with an 'X').
Advantages:
- Simplifies complex business logic that would be confusing in paragraph form.
- Ensures all possible combinations of conditions are considered, preventing missing logic.
- Easy for both programmers to code from and non-technical stakeholders to verify.
Definition:
A Decision Table is a tabular representation of complex logical rules. It is a fact-finding and system modeling tool used to map out various conditions and the corresponding actions that should be taken. It is highly useful when business rules involve multiple combinations of "If-Then" logic.
Structure of a Decision Table:
It is divided into four main quadrants:
1. Condition Stub (Upper Left): Lists all the possible conditions or variables that affect the decision.
2. Condition Entry (Upper Right): Contains the actual values for the conditions (usually represented as Y for Yes, N for No, or dashes '-' for irrelevant).
3. Action Stub (Lower Left): Lists all the possible actions that can be taken based on the conditions.
4. Action Entry (Lower Right): Indicates which specific actions are to be executed for each specific combination of conditions (usually marked with an 'X').
Advantages:
- Simplifies complex business logic that would be confusing in paragraph form.
- Ensures all possible combinations of conditions are considered, preventing missing logic.
- Easy for both programmers to code from and non-technical stakeholders to verify.
1. White Box testing is also known as .
--> Clear Box Testing, Glass Box Testing, Transparent Box Testing, or Structural Testing.
--> Clear Box Testing, Glass Box Testing, Transparent Box Testing, or Structural Testing.
2. What is Bug?
--> A bug is an error, flaw, mistake, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
--> A bug is an error, flaw, mistake, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
3. What is the full form of SRS?
--> Software Requirements Specification.
--> Software Requirements Specification.
1. Explain Non-Functional Testing.
Non-Functional Testing is a software testing type that checks the non-functional attributes of a software application. Rather than checking "what" the software does (which is functional testing), it checks "how well" the software operates.
It focuses on parameters such as:
1. Performance: How fast the system responds.
2. Usability: How user-friendly the interface is.
3. Scalability: How well the system handles an increasing amount of work.
4. Security: How safe the system is from cyber threats.
Non-Functional Testing is a software testing type that checks the non-functional attributes of a software application. Rather than checking "what" the software does (which is functional testing), it checks "how well" the software operates.
It focuses on parameters such as:
1. Performance: How fast the system responds.
2. Usability: How user-friendly the interface is.
3. Scalability: How well the system handles an increasing amount of work.
4. Security: How safe the system is from cyber threats.
1. Write a note on Software Test Level in detail.
Software testing is grouped into different levels to identify missing areas and prevent overlap between development lifecycle phases. The four main levels of software testing are:
1. Unit Testing:
- It is the first level of testing, usually performed by the developers.
- It involves testing individual components or modules of the software in isolation to ensure each piece of code works correctly on its own.
2. Integration Testing:
- Performed after unit testing.
- Individual units are combined and tested as a group.
- The purpose is to expose faults in the interaction between integrated units (e.g., checking if the database connects properly with the user interface).
3. System Testing:
- The fully integrated software is tested as a complete system.
- It verifies that the software meets the overall business and technical requirements.
- It is a black-box testing technique performed by a dedicated testing team.
4. Acceptance Testing:
- The final level of testing, often performed by the end-users or clients (User Acceptance Testing - UAT).
- It determines whether the software is ready for release to the market based on whether it solves the user's business needs.
Software testing is grouped into different levels to identify missing areas and prevent overlap between development lifecycle phases. The four main levels of software testing are:
1. Unit Testing:
- It is the first level of testing, usually performed by the developers.
- It involves testing individual components or modules of the software in isolation to ensure each piece of code works correctly on its own.
2. Integration Testing:
- Performed after unit testing.
- Individual units are combined and tested as a group.
- The purpose is to expose faults in the interaction between integrated units (e.g., checking if the database connects properly with the user interface).
3. System Testing:
- The fully integrated software is tested as a complete system.
- It verifies that the software meets the overall business and technical requirements.
- It is a black-box testing technique performed by a dedicated testing team.
4. Acceptance Testing:
- The final level of testing, often performed by the end-users or clients (User Acceptance Testing - UAT).
- It determines whether the software is ready for release to the market based on whether it solves the user's business needs.
--- OR ---
1. What is informal Review?
--> An informal review is a type of static testing that does not follow a documented process or formal rules. It is typically a "buddy check" or peer review where a colleague quickly looks over code or documents to find obvious defects.
--> An informal review is a type of static testing that does not follow a documented process or formal rules. It is typically a "buddy check" or peer review where a colleague quickly looks over code or documents to find obvious defects.
2. What is fault?
--> A fault is the physical manifestation of an error or mistake within the software code or logic. If a fault is executed during runtime, it leads to a software failure.
--> A fault is the physical manifestation of an error or mistake within the software code or logic. If a fault is executed during runtime, it leads to a software failure.
3. What is Load testing?
--> Load testing is a type of performance testing that determines how a software application behaves while being accessed by multiple users simultaneously under expected and peak load conditions.
--> Load testing is a type of performance testing that determines how a software application behaves while being accessed by multiple users simultaneously under expected and peak load conditions.
1. Explain White Box Testing.
White Box Testing (also known as Clear Box, Glass Box, or Structural Testing) is a testing technique that examines the internal structures, workings, and code of an application.
- Requirement: The tester must have knowledge of programming and the internal logic of the code.
- Goal: To verify the flow of inputs and outputs through the application, improve design and usability, and strengthen security.
- Types: Statement coverage, Branch coverage, Path coverage, and Loop testing are common white-box techniques.
White Box Testing (also known as Clear Box, Glass Box, or Structural Testing) is a testing technique that examines the internal structures, workings, and code of an application.
- Requirement: The tester must have knowledge of programming and the internal logic of the code.
- Goal: To verify the flow of inputs and outputs through the application, improve design and usability, and strengthen security.
- Types: Statement coverage, Branch coverage, Path coverage, and Loop testing are common white-box techniques.
1. Explain Testing Artifacts.
Testing Artifacts are the documents, models, and deliverables created and maintained during the Software Testing Life Cycle (STLC). They help in organizing the testing process, tracking progress, and providing documentation for future reference.
Key Testing Artifacts Include:
1. Test Plan: A comprehensive document detailing the scope, approach, resources, schedule, and objectives of the testing activities. It acts as the blueprint for the entire testing phase.
2. Test Cases: A set of conditions, inputs, execution steps, and expected results designed to test a specific software feature. Good test cases are repeatable and traceable.
3. Test Data: The actual data inputs created or selected to be used while executing the test cases (e.g., valid/invalid usernames, boundary value numbers).
4. Requirements Traceability Matrix (RTM): A document that maps and traces business requirements to the corresponding test cases. It ensures that every requirement has at least one test case covering it (100% test coverage).
5. Defect / Bug Report: A document logged by a tester when a test case fails. It contains details like the bug description, steps to reproduce, severity, priority, and screenshots.
6. Test Summary Report: A final document created at the end of the testing phase that summarizes all testing activities, the number of bugs found/fixed, and the final quality sign-off of the software.
Testing Artifacts are the documents, models, and deliverables created and maintained during the Software Testing Life Cycle (STLC). They help in organizing the testing process, tracking progress, and providing documentation for future reference.
Key Testing Artifacts Include:
1. Test Plan: A comprehensive document detailing the scope, approach, resources, schedule, and objectives of the testing activities. It acts as the blueprint for the entire testing phase.
2. Test Cases: A set of conditions, inputs, execution steps, and expected results designed to test a specific software feature. Good test cases are repeatable and traceable.
3. Test Data: The actual data inputs created or selected to be used while executing the test cases (e.g., valid/invalid usernames, boundary value numbers).
4. Requirements Traceability Matrix (RTM): A document that maps and traces business requirements to the corresponding test cases. It ensures that every requirement has at least one test case covering it (100% test coverage).
5. Defect / Bug Report: A document logged by a tester when a test case fails. It contains details like the bug description, steps to reproduce, severity, priority, and screenshots.
6. Test Summary Report: A final document created at the end of the testing phase that summarizes all testing activities, the number of bugs found/fixed, and the final quality sign-off of the software.
1. What is Unit testing?
--> Unit testing is a software testing method where individual units or components of a software (like a specific function or method) are tested in isolation to verify they work exactly as intended.
--> Unit testing is a software testing method where individual units or components of a software (like a specific function or method) are tested in isolation to verify they work exactly as intended.
2. V-Model is an extension of .
--> The Waterfall Model.
--> The Waterfall Model.
3. Explain Components of Neoload.
--> NeoLoad consists of three main components:
1. Controller: Used to design the test, manage the load generators, and analyze the results.
2. Load Generators: Simulate the behavior of virtual users attacking the application.
3. Monitoring Agents: Extract performance metrics (CPU, Memory, etc.) from the servers during the test.
--> NeoLoad consists of three main components:
1. Controller: Used to design the test, manage the load generators, and analyze the results.
2. Load Generators: Simulate the behavior of virtual users attacking the application.
3. Monitoring Agents: Extract performance metrics (CPU, Memory, etc.) from the servers during the test.
1. Explain ZAP tool with pros and cons.
OWASP ZAP (Zed Attack Proxy) is a free, open-source security tool used for penetration testing and finding vulnerabilities in web applications. It sits as a "man-in-the-middle" proxy between the tester's browser and the web application.
Pros:
- Completely free and open-source.
- Excellent for automated security scanning and manual testing.
- Actively maintained by a strong community.
Cons:
- Steeper learning curve for beginners.
- Can generate "false positives" (flagging things as vulnerabilities when they aren't), requiring manual verification.
OWASP ZAP (Zed Attack Proxy) is a free, open-source security tool used for penetration testing and finding vulnerabilities in web applications. It sits as a "man-in-the-middle" proxy between the tester's browser and the web application.
Pros:
- Completely free and open-source.
- Excellent for automated security scanning and manual testing.
- Actively maintained by a strong community.
Cons:
- Steeper learning curve for beginners.
- Can generate "false positives" (flagging things as vulnerabilities when they aren't), requiring manual verification.
1. Explain Spiral Model in detail.
Definition:
The Spiral Model is a highly risk-driven software development process model. It combines the iterative nature of prototyping with the controlled, systematic aspects of the Waterfall model. It is designed for large, expensive, and complex projects.
Phases of the Spiral Model (The 4 Quadrants):
Each loop (or spiral) represents a phase in the software process, divided into four quadrants:
1. Objective Determination & Identify Alternatives:
Requirements are gathered from the customer. Objectives, constraints, and alternative solutions for the current phase are identified.
2. Risk Analysis & Resolution (The core feature):
All alternatives are evaluated based on objectives and constraints. Potential risks are identified and resolved (often by building a prototype). If risks cannot be resolved, the project may be terminated here.
3. Development & Execution:
The actual development and testing of the software occur in this phase. The model chosen for development depends on the risks identified (e.g., if UI risks are high, prototyping is used).
4. Planning the Next Iteration:
The customer evaluates the current output. Based on their feedback, the project is reviewed, and planning for the next phase (the next loop of the spiral) begins.
Advantages: Strong risk management; good for large, critical projects; accommodates changes easily.
Disadvantages: Highly dependent on risk-analysis expertise; expensive; not suitable for small projects.
Definition:
The Spiral Model is a highly risk-driven software development process model. It combines the iterative nature of prototyping with the controlled, systematic aspects of the Waterfall model. It is designed for large, expensive, and complex projects.
Phases of the Spiral Model (The 4 Quadrants):
Each loop (or spiral) represents a phase in the software process, divided into four quadrants:
1. Objective Determination & Identify Alternatives:
Requirements are gathered from the customer. Objectives, constraints, and alternative solutions for the current phase are identified.
2. Risk Analysis & Resolution (The core feature):
All alternatives are evaluated based on objectives and constraints. Potential risks are identified and resolved (often by building a prototype). If risks cannot be resolved, the project may be terminated here.
3. Development & Execution:
The actual development and testing of the software occur in this phase. The model chosen for development depends on the risks identified (e.g., if UI risks are high, prototyping is used).
4. Planning the Next Iteration:
The customer evaluates the current output. Based on their feedback, the project is reviewed, and planning for the next phase (the next loop of the spiral) begins.
Advantages: Strong risk management; good for large, critical projects; accommodates changes easily.
Disadvantages: Highly dependent on risk-analysis expertise; expensive; not suitable for small projects.
--- OR ---
1. Iterative model is also known as .
--> Cyclic Model or Iterative Enhancement Model.
--> Cyclic Model or Iterative Enhancement Model.
2. V-Model is also known as .
--> Verification and Validation Model.
--> Verification and Validation Model.
3. Spiral model is focus on .
--> Risk Analysis (or Risk Management / Risk Assessment).
--> Risk Analysis (or Risk Management / Risk Assessment).
1. Define the Term the Freeware and Shareware.
Freeware:
Software that is completely free to download, install, and use indefinitely. However, the source code is kept proprietary (hidden) by the creator, and the user cannot modify it. (Examples: Adobe Reader, Skype).
Shareware:
Commercial software distributed for free but on a limited trial basis (e.g., a 30-day trial or with limited features). Once the trial expires, the user must pay a license fee to continue using it or to unlock the full features. (Examples: WinRAR, IDM).
Freeware:
Software that is completely free to download, install, and use indefinitely. However, the source code is kept proprietary (hidden) by the creator, and the user cannot modify it. (Examples: Adobe Reader, Skype).
Shareware:
Commercial software distributed for free but on a limited trial basis (e.g., a 30-day trial or with limited features). Once the trial expires, the user must pay a license fee to continue using it or to unlock the full features. (Examples: WinRAR, IDM).
1. Explain NeoLoad testing tool.
Definition:
NeoLoad is a premier, enterprise-level performance testing platform developed by Tricentis. It is designed specifically to automate the load and performance testing of Web applications, APIs, and microservices.
Key Features & Workflow:
1. Simulating Traffic: It evaluates the performance of an application by generating thousands of virtual users, simulating real-world network traffic conditions.
2. Component Architecture: It uses a Controller to design test scripts, Load Generators to simulate the heavy user traffic, and Monitoring Agents to track the health of the servers (CPU, RAM, Database queries) under pressure.
3. Protocol Support: It supports a wide array of modern protocols including HTTP/2, WebSockets, SOAP, and REST, making it highly adaptable for modern architectures.
4. CI/CD Integration: It integrates seamlessly with Continuous Integration/Continuous Deployment (CI/CD) pipelines like Jenkins or Bamboo, allowing teams to test performance automatically every time new code is deployed (Shift-Left testing).
Advantages:
- Fast Script Creation: Features a graphical interface that allows testers to create complex scripts without heavy coding.
- Scalability: Easily scales out tests to millions of users using cloud load generation.
- Real-time Analytics: Provides highly detailed, real-time dashboards and reports to quickly identify performance bottlenecks before an application goes live.
Definition:
NeoLoad is a premier, enterprise-level performance testing platform developed by Tricentis. It is designed specifically to automate the load and performance testing of Web applications, APIs, and microservices.
Key Features & Workflow:
1. Simulating Traffic: It evaluates the performance of an application by generating thousands of virtual users, simulating real-world network traffic conditions.
2. Component Architecture: It uses a Controller to design test scripts, Load Generators to simulate the heavy user traffic, and Monitoring Agents to track the health of the servers (CPU, RAM, Database queries) under pressure.
3. Protocol Support: It supports a wide array of modern protocols including HTTP/2, WebSockets, SOAP, and REST, making it highly adaptable for modern architectures.
4. CI/CD Integration: It integrates seamlessly with Continuous Integration/Continuous Deployment (CI/CD) pipelines like Jenkins or Bamboo, allowing teams to test performance automatically every time new code is deployed (Shift-Left testing).
Advantages:
- Fast Script Creation: Features a graphical interface that allows testers to create complex scripts without heavy coding.
- Scalability: Easily scales out tests to millions of users using cloud load generation.
- Real-time Analytics: Provides highly detailed, real-time dashboards and reports to quickly identify performance bottlenecks before an application goes live.
1. List out three level of COCOMO model.
--> 1. Basic COCOMO
--> 2. Intermediate COCOMO
--> 3. Detailed COCOMO
--> 1. Basic COCOMO
--> 2. Intermediate COCOMO
--> 3. Detailed COCOMO
2. PERT stands for .
--> Program Evaluation and Review Technique (or Project Evaluation and Review Technique).
--> Program Evaluation and Review Technique (or Project Evaluation and Review Technique).
3. Timeline Chart also known as .
--> Gantt Chart.
--> Gantt Chart.
1. Explain Project costing based on Metrics.
Project costing based on metrics involves estimating the financial cost and effort required for a software project using historical data and quantitative measures (metrics).
Common size metrics include Lines of Code (LOC) or Function Points (FP). By calculating the estimated size of the project and multiplying it by the historical cost-per-unit (e.g., cost per FP or cost per LOC from past similar projects), project managers can generate a realistic estimate of the total budget and human effort required.
Project costing based on metrics involves estimating the financial cost and effort required for a software project using historical data and quantitative measures (metrics).
Common size metrics include Lines of Code (LOC) or Function Points (FP). By calculating the estimated size of the project and multiplying it by the historical cost-per-unit (e.g., cost per FP or cost per LOC from past similar projects), project managers can generate a realistic estimate of the total budget and human effort required.
1. Explain COCOMO Model.
Definition:
The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry Boehm. It uses a regression formula with parameters derived from historical project data to estimate the effort, cost, and schedule of a software project based on its size (usually measured in KLOC - Kilo Lines of Code).
Three Levels of COCOMO:
1. Basic COCOMO: Provides a quick, rough estimate of software development effort and cost based solely on the estimated lines of code.
2. Intermediate COCOMO: Calculates effort as a function of program size and a set of "cost drivers" (like hardware constraints, personnel experience, and use of modern tools) to give a more accurate estimate.
3. Detailed COCOMO: Incorporates all characteristics of the intermediate version with an assessment of the cost drivers' impact on each specific step of the software engineering process (analysis, design, etc.).
Three Modes of Software Projects:
1. Organic: Small, simple software projects handled by a small team with good prior experience and flexible requirements.
2. Semi-detached: Intermediate size and complexity. The team has mixed experience, and the requirements are somewhat rigid.
3. Embedded: Complex software with tight constraints, high hardware/software coupling, and strict operational requirements (e.g., flight control software).
Definition:
The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry Boehm. It uses a regression formula with parameters derived from historical project data to estimate the effort, cost, and schedule of a software project based on its size (usually measured in KLOC - Kilo Lines of Code).
Three Levels of COCOMO:
1. Basic COCOMO: Provides a quick, rough estimate of software development effort and cost based solely on the estimated lines of code.
2. Intermediate COCOMO: Calculates effort as a function of program size and a set of "cost drivers" (like hardware constraints, personnel experience, and use of modern tools) to give a more accurate estimate.
3. Detailed COCOMO: Incorporates all characteristics of the intermediate version with an assessment of the cost drivers' impact on each specific step of the software engineering process (analysis, design, etc.).
Three Modes of Software Projects:
1. Organic: Small, simple software projects handled by a small team with good prior experience and flexible requirements.
2. Semi-detached: Intermediate size and complexity. The team has mixed experience, and the requirements are somewhat rigid.
3. Embedded: Complex software with tight constraints, high hardware/software coupling, and strict operational requirements (e.g., flight control software).
--- OR ---
1. GANTT Stands for .
--> "Gantt" is not an acronym. It is named after its inventor, Henry Gantt, who designed the chart around the years 1910–1915.
--> "Gantt" is not an acronym. It is named after its inventor, Henry Gantt, who designed the chart around the years 1910–1915.
2. LOC Stands for .
--> Lines of Code.
--> Lines of Code.
3. FP Stands for .
--> Function Point.
--> Function Point.
1. Explain Project Estimation technique.
Project Estimation Techniques are methods used by project managers to predict the amount of time, human effort, and financial budget required to successfully build a software system.
They are generally categorized into two main types:
1. Empirical Estimation: Based on expert experience, educated guesses, and historical data from past projects (e.g., Expert Judgment, Delphi technique).
2. Heuristic/Algorithmic Estimation: Uses mathematical models and formulas based on project characteristics and size (e.g., COCOMO model, Function Point Analysis).
Project Estimation Techniques are methods used by project managers to predict the amount of time, human effort, and financial budget required to successfully build a software system.
They are generally categorized into two main types:
1. Empirical Estimation: Based on expert experience, educated guesses, and historical data from past projects (e.g., Expert Judgment, Delphi technique).
2. Heuristic/Algorithmic Estimation: Uses mathematical models and formulas based on project characteristics and size (e.g., COCOMO model, Function Point Analysis).
1. Write a note on TIME-LINE chart.
Definition:
A timeline chart, most commonly known as a Gantt Chart, is a highly effective visual representation of a project schedule. It is widely used in software project management to plan, coordinate, and track specific tasks over time.
Structure of the Chart:
- Vertical Axis: Lists all the specific tasks, activities, or milestones that make up the software project.
- Horizontal Axis: Represents the time span of the project, broken down into days, weeks, or months.
- Horizontal Bars: Placed across the chart to represent the duration of each task. The left end of the bar marks the start date, and the right end marks the completion date.
Key Advantages & Uses:
1. Visual Tracking: Project managers can instantly see what tasks are currently in progress, what is falling behind, and what has been completed.
2. Dependencies: It clearly shows overlapping activities and task dependencies (e.g., "Coding" cannot start until "System Design" is finished).
3. Resource Allocation: Helps in assigning team members to specific tasks at specific times, ensuring nobody is overworked or sitting idle.
4. Milestones: Special markers (like diamonds) can be placed on the timeline to indicate major project milestones (like the release of a Beta version).
Definition:
A timeline chart, most commonly known as a Gantt Chart, is a highly effective visual representation of a project schedule. It is widely used in software project management to plan, coordinate, and track specific tasks over time.
Structure of the Chart:
- Vertical Axis: Lists all the specific tasks, activities, or milestones that make up the software project.
- Horizontal Axis: Represents the time span of the project, broken down into days, weeks, or months.
- Horizontal Bars: Placed across the chart to represent the duration of each task. The left end of the bar marks the start date, and the right end marks the completion date.
Key Advantages & Uses:
1. Visual Tracking: Project managers can instantly see what tasks are currently in progress, what is falling behind, and what has been completed.
2. Dependencies: It clearly shows overlapping activities and task dependencies (e.g., "Coding" cannot start until "System Design" is finished).
3. Resource Allocation: Helps in assigning team members to specific tasks at specific times, ensuring nobody is overworked or sitting idle.
4. Milestones: Special markers (like diamonds) can be placed on the timeline to indicate major project milestones (like the release of a Beta version).
1. VDW stand for .
--> Visio Web Drawing.
--> Visio Web Drawing.
2. What is the extension of Visio Drawing file?
--> .vsdx (for modern Visio versions 2013 and later) or .vsd (for older versions).
--> .vsdx (for modern Visio versions 2013 and later) or .vsd (for older versions).
3. CADD Stand for .
--> Computer-Aided Design and Drafting.
--> Computer-Aided Design and Drafting.
1. What is UML? Explain it.
UML (Unified Modeling Language) is a standardized, general-purpose visual modeling language used in the field of software engineering.
- It provides a standard way to visualize the design of a system, including its architectural blueprints, structures, and behaviors.
- It is not a programming language but a pictorial language used to specify, construct, and document the artifacts of a software system using standard diagrams like Use Case diagrams, Class diagrams, and Sequence diagrams.
UML (Unified Modeling Language) is a standardized, general-purpose visual modeling language used in the field of software engineering.
- It provides a standard way to visualize the design of a system, including its architectural blueprints, structures, and behaviors.
- It is not a programming language but a pictorial language used to specify, construct, and document the artifacts of a software system using standard diagrams like Use Case diagrams, Class diagrams, and Sequence diagrams.
1. What is MS Visio? How it is used in designing and documentation of project with example?
What is MS Visio:
Microsoft Visio is a powerful diagramming and vector graphics application. It is widely used by business analysts, system architects, and software engineers to create professional diagrams that simplify complex information.
How it is used in Designing and Documentation:
Visio provides built-in stencils and templates tailored for software development. During the SDLC, teams use Visio to create visual documentation that is much easier for stakeholders and developers to understand than plain text.
- Requirement Phase: Used to draw Use Case diagrams to show system boundaries and user interactions.
- Design Phase: Used to create Data Flow Diagrams (DFDs), Entity-Relationship (ER) diagrams for databases, and UML Class diagrams for Object-Oriented programming.
Example:
Imagine a team building an "Online E-commerce Store". A business analyst can open MS Visio, select the "UML" template, and drag-and-drop shapes to quickly build a Use Case Diagram. They draw stick figures representing the "Customer" and "Admin", and connect them to ovals representing actions like "Search Product", "Add to Cart", and "Process Payment". This single visual document clearly communicates the system's functional requirements to the programmers who will write the code.
What is MS Visio:
Microsoft Visio is a powerful diagramming and vector graphics application. It is widely used by business analysts, system architects, and software engineers to create professional diagrams that simplify complex information.
How it is used in Designing and Documentation:
Visio provides built-in stencils and templates tailored for software development. During the SDLC, teams use Visio to create visual documentation that is much easier for stakeholders and developers to understand than plain text.
- Requirement Phase: Used to draw Use Case diagrams to show system boundaries and user interactions.
- Design Phase: Used to create Data Flow Diagrams (DFDs), Entity-Relationship (ER) diagrams for databases, and UML Class diagrams for Object-Oriented programming.
Example:
Imagine a team building an "Online E-commerce Store". A business analyst can open MS Visio, select the "UML" template, and drag-and-drop shapes to quickly build a Use Case Diagram. They draw stick figures representing the "Customer" and "Admin", and connect them to ovals representing actions like "Search Product", "Add to Cart", and "Process Payment". This single visual document clearly communicates the system's functional requirements to the programmers who will write the code.
--- OR ---
1. Class diagram is used to represent______.
--> The static structure of a system (including classes, attributes, operations, and their relationships).
--> The static structure of a system (including classes, attributes, operations, and their relationships).
2. What is the extension of Visio template file?
--> .vstx (for newer versions) or .vst (for older versions).
--> .vstx (for newer versions) or .vst (for older versions).
3. UML Stand for .
--> Unified Modeling Language.
--> Unified Modeling Language.
1. Explain Class diagram.
A Class Diagram is a core structural UML diagram that describes the structure of an object-oriented system. It acts as a blueprint for the system.
It consists of:
1. Classes: Represented as rectangles divided into three compartments (Class Name, Attributes, and Operations/Methods).
2. Relationships: Lines connecting the classes to show how they interact, such as Association, Inheritance (Generalization), Aggregation, and Composition.
A Class Diagram is a core structural UML diagram that describes the structure of an object-oriented system. It acts as a blueprint for the system.
It consists of:
1. Classes: Represented as rectangles divided into three compartments (Class Name, Attributes, and Operations/Methods).
2. Relationships: Lines connecting the classes to show how they interact, such as Association, Inheritance (Generalization), Aggregation, and Composition.
1. Draw a class diagram for Customer order.
Explanation of Relationships:
1. Customer to Order: A Customer can place zero or multiple (0..*) Orders. An Order belongs to exactly one (1) Customer. (One-to-Many Association).
2. Order to OrderDetails: An Order contains one or more (1..*) OrderDetails. (Composition/Aggregation).
3. OrderDetails to Item: Each OrderDetail line refers to exactly one (1) specific Item/Product. (Association).
Customer
- customerId: int
- name: String
- address: String
- name: String
- address: String
+ register()
+ login()
+ placeOrder()
+ login()
+ placeOrder()
1 ─ places → 0..*
1 (places) 0..*
↓
↓
Order
- orderId: int
- orderDate: Date
- status: String
- orderDate: Date
- status: String
+ calcTotal()
+ cancelOrder()
+ confirm()
+ cancelOrder()
+ confirm()
1..* (contains)
↓
↓
OrderDetails
- quantity: int
- subTotal: float
- subTotal: float
+ calcWeight()
0..* ← refers to ─ 1
0..* (refers to) 1
↓
↓
Item
- itemId: int
- price: float
- description: String
- price: float
- description: String
+ getPrice()
+ updateStock()
+ updateStock()
Explanation of Relationships:
1. Customer to Order: A Customer can place zero or multiple (0..*) Orders. An Order belongs to exactly one (1) Customer. (One-to-Many Association).
2. Order to OrderDetails: An Order contains one or more (1..*) OrderDetails. (Composition/Aggregation).
3. OrderDetails to Item: Each OrderDetail line refers to exactly one (1) specific Item/Product. (Association).
No comments:
Post a Comment