SE
SE
SE
Ans: 1. Functional requirements: These are statements of services the system should provide, how the system should react to
particular inputs, and how the system should behave in particular situations. In some cases, the functional requirements may also
explicitly state what the system should not do. Example of functional requirements are :- a) Descriptions of data to be entered into the
systemb) Descriptions of operations performed by each screenc) Who can enter the data into the systemd) Descriptions of system
reports or other outputs 2. Non-functional requirements: These are constraints on the services or functions offered by the system.
They include timing constraints, constraints on the development process, and constraints imposed by standards. Nonfunctional
requirements often apply to the system as a whole, rather than individual system features or services.i)Product requirements:These
requirements specify or constrain the behaviour of the Software Examples include performance requirements on how fast the system
must execute and how much memory it requires, reliability requirements that set out the acceptable failure rate, security
requirements, and usability requirements. ii) Organizational requirements:These requirements are broad system requirement derived
from policies and procedures in the customer’s and developer’s organization. Examples include operational process requirements that
define how the system will be used, development process requirements that specify the programming language, the development
environment or process standards to be used.
Q2. explain working of prototypes model.
Ans: Step 1: Requirement Gathering and Analysis: This is the initial step in designing a prototype model. In this phase, users are asked
about what they expect or what they want from the system.Step 2: Quick Design: This is the second step in the Prototyping Model.
This model covers the basic design of the requirement through which a quick overview can be easily described.Step 3: Build a
Prototype: This step helps in building an actual prototype from the knowledge gained from prototype design.Step 4: Initial User
Evaluation: This step describes the preliminary testing where the investigation of the performance model occurs, as the customer will
tell the strengths and weaknesses of the design, which was sent to the developer.Step 5: Refining Prototype: If any feedback is given
by the user, then improving the client’s response to feedback and suggestions, the final system is approved.Step 6: Implement Product
and Maintain: This is the final step in the phase of the Prototyping Model where the final system is tested and distributed to
production, here the program is run regularly to prevent failures.
Fig:- step➡1➡2➡3➡4➡5➡6.
Q3. explain level of testing in software engineering.
Ans: component Testing:1.component resting is method where testing. of each component in an application is done
separately.2.component testing is also known as module and program testing.3.it Finds the defect the module and verifies. the
functioning of Software. Component testing is done by the tester.4.component testing may be done in isolation From rest of the
system depending the development life cycle model. System testing:1. System testing is most probably the final test to identify that
the system meets the specification and criteria and it evaluates both function and non-functional needs for the testing.2. In system
testing, complete and integrated Software’s are tested i.e., all the system elements forming the system are tested as a whole to meet
the requirements of the system. Acceptance Testing:1.This is a kind of testing conducted to ensure that the requirements of the users
are fulfilled before its delivery and that the software works correctly in the user’s working environment.2. Acceptance Testing is the
last phase of software testing performed after System Testing and before making the system available for actual use.
supports organizational objectives does not just depend on the system itself. Digram:(yeh circle middle m hai) ◯Student result
management. Data entry operator➡ Subject info enterAdministratorStudents info reports generatedmarksheet generated Student
Ans: system dependability:1.Systemfailures may have widespread effects with large numbers of people affected by the failure.2.Systems that are not
dependable and are unreliable, unsafe or insecure may be rejected by their users.3.The costs of systemfailure may be very high if the
failure leads to economic losses or physical damage.4.Undependable systems may cause information loss with a high consequent
recovery cost.Principal properties1.Availability:The probability that the system will be up and running and able to deliver useful
services to users.2.Reliability:The probability that the system will correctly deliver services as expected by users.3.Safety:A judgment
of how likely it is that the system will cause damage to people or its
environment.4.Security:A judgment of how likely it is that the system can resist accidental or deliberate intrusions.
Q8.Explain risk management process.
Ans:1. Risk management is the area which tries to ensure that the impact of risks on cost, quality and schedule is minimized.2. The
main purpose of risk management is to identify and manage the risks associated with a software project and solve the problem.3.
Estimating the risks that can affect the project schedule or the quality of the software being developed and taking action to avoid the
risk is the important task of a project manager.4. Identifying and preparing plans to reduce their impact on the project is called risk
management.*The process of risk management involves several stages are as follows-1.Risk Identification: In this stage, the possible
project, product and business risks are identified.2.Risk Analysis : In this stage or process, the likelihood and consequences of these
risks assessed.3.Risk Planning: In this stage, risk avoidance in either planned to affect the plan or mitigate its effects on the
project.4.Risk Monitoring: In this stage, risk assessment is done continuously and the risk reduction plan is revised as more
information about risk is available.
Q9. Explain what UI design and explains in user interface design process.
Ans:
Use of metaphors and intuitive command names:Metaphor is just like the abstraction of items like real-existence that is used with
inside person interface. If textual content editor of the person interface makes use of the identical ideas or we will say equipment for
the modifying of textual content like reducing strains and paragraphs and additionally pasting distinctive textual content at distinctive
places, then it could be without difficulty associated through the person. Component-based interface:It may be smooth for the person
to apprehend if brand new interactive fashion of the interface turns into very just like interface of different programs which can be
already acquainted to the person. This is viable most effective if the improvement of distinctive interactive person interfaces is
through the use of a few preferred interface components.
Q10. What is project management ? Explain the role of project scheduling management.
Ans:*project management is the application of knowledge, Skills, tools and techniques to project activities to meet the project
requirements.*. project management is accomplished through the appropriate application and integration of the logically grouped
project management Process who categorized into five processes:1.Initiating.2.Planning.3.Executing.4.Monitoring and
controlling.5.closing
*Managing a project typically includes, but is not limited to:-1.dentifying requirements.2.Addressing the various needs, concerns and
expectations of the Stake Stakeholders in planning.3.Balancing the competing Project
constraints:1.Scope2.Quality3.Schedule4.Budget5.Resources6.Risks
1.Planning: Identifying project objectives, Scope, requirements and deliverables.2.Estimation: Estimating time, effort and resources
required for each task.3.Scheduling:-creating a timeline and allocating resource to each task, determining,dependencies,milestones
and deadlines. 4.Resource Management:Assigning human and material resources efficiently to task and skill sets.5.monitoring and
control: Tracking progress, Identifying deviations from the schedule and implementing corrective actions to keep the project on
track.6.Risk management:Identifying potential risks and uncertainties that may impact the Schedule.
7.communication:Facilitating communication among team members stakeholders and Clients to ensure everyone in informed about
project progress, change and Challenge.
Q11.what is WBS? Draw on example?
Ans:1. A Work Breakdown Structure includes dividing a large and complex project into simpler, manageable, and independent tasks.2.
The root of this tree (structure) is labeled by the Project name itself. For constructing a work breakdown structure, each node is
recursively decomposed into smaller sub-activities, until at the leaf level, the activities become undividable and independent. It follows
a Top-Down approach.3. Firstly, the project managers and top level management identifies the main deliverables of the project.4.After
this important step, these main deliverables are broke down into smaller higher-level tasks and this complete process is done
recursively to produce much smaller independent tasks.5.It depends on the project manager and team that up to which level of detail
they want to break down their project. Steps Work Breakdown Structure:Step 1: Identify the major activities of the project.Step 2:
Identify the sub-activities of the major activities.Step 3: Repeat till undividable, simple, and independent activities are created.
Digram:- PROJECT
TASK TASK TASK
SUB-TASK SUB-TASK
WORK PACKAGE WORK PACKAGE WORK PACKAGE
Q12. Explain CMMI.
Ans:1. capability Maturity Model Integration (CMMI) is a successor of CMM and is a more evolved model that incorporates best
components of individual disciplines of CMM like Software CMM, Systems Engineering CMM, People CMM, etc.2. Since CMM is a
reference model of matured practices in a specific discipline, so it becomes difficult to integrate these disciplines as per the
requirements.3. This is why CMMI is used as it allows the integration of multiple disciplines as and when needed.
Objectives of CMMI :1.Fulfilling customer needs and expectations.2.Value creation for investors/stockholders.3.Market growth is
increased.4.Improved quality of products and services.5.Enhanced reputation in Industry.
Q13.Explain verification and validation.
Ans: Verification:-Verification is the process of checking that software achieves its goal without any bugs. It is the process to ensure
whether the product that is developed is right or not. It verifies whether the developed product fulfills the requirements that we have
. Verification is simply known as Static Testing.
Static Testing:Verification Testing is known as Static Testing and it can be simply termed as checking whether we are developing the
right product or not and also whether our software is fulfilling the customer’s requirement or not.
1.Inspections.2.Reviews.3.Walkthroughs.4.Desk-checking.
Dynamic Testing:Validation Testing is known as Dynamic Testing in which we examine whether we have developed the product right
or not and also about the business needs of the client. Here are some of the activities that are involved in Validation.1.Black Box
Testing2.White Box Testing3.Unit Testing4.Integration Testing
Q14.Explain Big Bang approach of testing
Ans:1.Big bang integration testing is a testing approach where all components or modules are integrated and tested as a single unit.
This is done after all modules have been completed and before any system-level testing is performed.2.This is in contrast to
incremental integration testing, in which components are tested one at a time or in small groups.3.This approach is typically used
when there is a tight deadline for delivering the software product, and all development teams are working in parallel on their
respective components.4. Simulation of the complete system: Big bang integration testing involves simulating the complete system.
This means that all components and modules are integrated and tested at the same time.5.Testing all components together: Since all
components are integrated and tested at the same time, this means that all components are tested together. This is beneficial as it
allows for the testing of interactions between components.
Q15.what is software measurement.
Ans: Software Measurement: A measurement is a manifestation of the size, quantity, amount, or dimension of a particular attribute
of a product or process. Software measurement is a titrate impute of a characteristic of a software product or the software process.
Software Measurement Five Principles:1.Formulation: The derivation of software measures and metrics appropriate for the
representation of the software that is being considered.2.Collection: The mechanism used to accumulate data required to derive the
formulated metrics.3.Analysis: The computation of metrics and the application of mathematical tools.4.Interpretation: The evaluation
of metrics results in insight into the quality of the representation.5.Feedback: Recommendation derived from the interpretation of
product metrics transmitted to the software team.Classification of Software Measurement:There are 2 types of software
measurement: 1.Direct Measurement: In direct measurement, the product, process, or thing is measured directly using a standard
scale.2.Indirect Measurement: In indirect measurement, the quantity or quality to be measured is measured using related parameters
i.e. by use of reference.
Q16. Explain SLOC with an example.
Ans: A line of code (LOC) is any line of text in a code that is not a comment or blank line, and also header lines, in any case of the
number of statements or fragments of statements on the line. LOC consists of all lines containing the declaration of any variable, and
executable and non-executable statements.AD:1. Effort Estimation: LOC is occasionally used to estimate development efforts and
project deadlines at a high level. Although caution is necessary, project planning can begin with this.2. Benchmarking Tool: When
comparing various iterations of the same program, LOC can be used as a benchmarking tool. It may bring information on how
modifications affect the codebase’s total size.DIS:1. Challenges in Agile Work Environments: Focusing on initial LOC estimates may not
adequately reflect the iterative and dynamic nature of development in agile development, as requirements may change.2. Challenges
with Maintenance: Higher LOC codebases are larger codebases that typically demand more maintenance work.
EX:- void selSort(int x[], int n){
int i, j, min, temp;
for (i = 0; i < n - 1; i++) {
min = i;
for (j = i + 1; j < n; j++)
if (x[j] < x[min])
min = j;
temp = x[i];
x[i] = x[min];
x[min] = temp;}}
Q17. Write a short note on FPA.
Ans:Function Point Analysis was initially developed by Allan J. Albrecht in 1979 at IBM and has been further modified by the
International Function Point User’s Group (IFPUG). Allan J. Albrecht gave the initial definition.
There are two types of Functional Point Analysis:1.Transactional Functional Type.2. Data Functional Type
*Transactional Functional Type:1.External Input (EI): EI processes data or control information that comes from outside the
application’s boundary. The EI is an elementary process.2.External Output (EO): EO is an elementary process that generates data or
control information sent outside the application’s boundary. 3.External Inquiries (EQ): EQ is an elementary process made up of an
input-output combination that results in data retrieval.*Data Functional Type:1.Internal Logical File (ILF): A user-identifiable group of
logically related data or control information maintained within the boundary of the application.2.External Interface File (EIF): A group
of users recognizable logically related data allusion to the software but maintained within the boundary of another software.
Q18. Explain priorities of extreme programming
Ans:1. Extreme programming (XP) is one of the most important software development frameworks of Agile models. It is used to
improve software quality and responsiveness to customer requirements.2.The extreme programming model recommends taking the
best practices that have worked well in the past in program development projects to extreme levels.3.Extreme programming is
described as • An attempt to reconcile humanity and Productivity• A mechanism for social change• A path to improvement. • A style
of development.4.XP values:• communication• Simplicity• Feedback• courage• Respect.5.XP principles:1.The planning game: Scope
next release with business priorities technical estimate.2.Small Release put simply system into production quickly.3.Metaphor: side
development with simple Shared Story of how the whole system works.4.40-hour week:Never work overtime a second in a row.
Q19. Draw activity Diagram of ATM machine
Ans:
Q20. Difference between IAAS, PAAS and SAAS.