1. Software Maintenance? 8. What is duty of project management ?

Def: it is the process of modifying the software It is the duty of software project management
after it has delivered to customer. to keep this under constraints . Software
project management keep the software project
2. But Way we will modify after the delivery? under all define constraints.
Ans: there can be different reason we can Software project management is well –
modify the software for the improvements, we disciplined filed and an art using which we plan,
can modify the software to correct the faults manage and supervise the software project
captured by customer/end user
9. What is project management?
3. Need Of Maintenance? Software project management field mainly deal
We may perform software maintenance for the with three thing
following requirement Time
1. interface with faults Const
2. Improve the design Quality
3. Implement enhancement
4. Inject security patches 10. What is project management
1. Software project management is a
4. Categories of software maintenance? complete domain and the project manager
1. Preventive Maintenance : in this categories is the person responsible to keep the whole
we always try to predict the problems that project under the domain according to the
can crate issue for us in future and we try to constraints.
over come those problems in advance 2. He is the person who keep the project on
2. Corrective maintenance: it is the track and management
maintenance in which we found a bug a try 3. Project manage is the drive of the software
to remove and fix the issue instantly it is an project management
essential type of maintenance which we
must perform instantly , or the software will 11. Responsibilities of project manager?
stop its regular working. 1. Project Planning
3. Perfective maintenance : new feature keep 2. Scope Management
coming in the field of the it and software . 3. Project estimation
You must keep your software compatible 4. Software size
with the new features to do that you 5. Effort
perform perfective maintenance. 6. Time
4. Adaptive maintenance: may be user was 7. Cost Estimation
using windows now he is planning to move 8. Resources management
on MAC OS . He may ask you wo perform 9. Resources management
some adaptive changes in the software 10.Risk Management
that’s’ the adaptive Maintenance
5. 12. Responsibilities of project manager?
6. What is project management He is the fully responsibilities to keep the
Project management is a way to lead the team project on track
and use all the resources in a manage way to He monitor the flow of team activities , their
achieve the required results which we want at planning and put them in a sequence and under
the end of the project the constraints of the project
The focus the project management is to achieve Project manager also make important changes
all of the project goals under the given if needed some here in between the project
constraints. according to the situation and take some bold
7. What is a project ? decisions
A project is a group of tasks that we perform to
achieve the required result not in the software
domain project in every domain is a group of
task.
13. Software Quality Assurance(SQA)?
Software quality assurance is simply a way to 19. Configuration Management activities?
assure quality in the software 1 ) configuration management is a whole
14. Where to use SQA? system which comprise on 4 activities
Software quality assurance is a process which 1) change management
works parallel to development of Software 2) version management
3) system building
15. How SQA is beneficial? 4) Release management
1. SQA produce high quality software and
those are beneficial. 20. Configuration in Management in S. E?
2. High quality application means shot Configuration in Management
development time
3. High quality application save the time and 1) configuration management is the set of policies ,
cost process and tool which we use to manage the changes
4. Better reliability and no maintenance for in software
long time 2) why we need a special system to manage the
5. High quality commercial software increase changes in software
market share of company.
Because when software is changing with time it can slip
16. Regression Testing in S. E? from its track.
Regression Testing
20. Version Management?
1 ) this is also a type of software testing.
1. It keep track of the version numbers of the
2) in this type of software testing we just retest
software system it name is already defining
any code or program after adding some future
it
or line of codes to it.
2. The version management system video
30 this testing helps us to make it sure the new
about how version system work is already
addition to the already working code is not
available channel kindly watch that.
making any problem is the functionality of code.
21. System Building?
17. Need Of Regression Testing in S. E?
1. This is the process of assembling and linking
1. Change in requirement on some demand
2. New feature is added to the software all the program components and libraries to
3. After defect fixing make the executable system
2. It is a complex process , this phase also
4. After performance issue fixing
communicate with the version control
Note: if you performed all these fixing by adding
system to check the previous build and to
something new then you will perform
decide what should be the next build .
regression testing.
22. Release management?
18. Difference between regression and re-
1. release management keep track of the
testing?
release of the software to the customers.
There is a minor difference between these two
2. It also keep track of the all other kind of
put sometime people use them for representing
releases.
some thing.
3. There are two kind of release major release
1. Regression is when you test after adding
and minor release .
some nee code.
4. Like if the releases number or let say
2. Re-rest is when you do not add some code
version number is 8.4.1 it means minor
fix the issue without addition and check it
release number is 1 and major release is 4
the error is still there .
and the main software is 8

23. Why organization ignore it?

1. They think it is time consuming process
2. They think it increase the cost of the
project.
 24. What is a Software?
Software is more than just a program code. A 29. Context And Process Models
program is an executable code, which serves Represent all external entities that may interact
with a system.
some computational purpose.
▪ 1. Program: The program or code itself is System all the center , with no details of its
interior structure
definitely included in the software.
▪ 2. Data: The data on which the program The objective is to focus attention on external
operates is also considered as part of the softw factors and events that should be considered in
▪ 3. Documentation: Another very important developing a complete set of systems
thing that most of us forget is documentation. requirement and constraints
All the documents related to the software are
also considered as part of the software. 30. Process Models?
Software is not just the code Process models reveal how the system being
developed is used in broader business process.
25. Software Engineering?
Software Engineering is the set of processes and 31. Interaction Models?
Types Of interactions that can be represented in
tools to develop software. Software Engineering
is the combination of all the tools, techniques, a model:
1. Modeling user interaction is important as it
and processes that used in software production.
helps to identify user requirement .
26. System Modeling?
System Modeling: is the process of developing 2. Modeling system – to –system interaction
abstract models of a system. highlight the communication problems that
Each model presenting a different view or may arise.
perspective of that system. 3. Modeling components interaction helps us
Representing a system using some kind of understand if a proposed system structure
is likely to deliver the required system
graphical notation.
performance and dependability
27. Why We need system modeling?
System modeling helps us to get different 32. System Boundaries ?
perspective 1. System boundaries are established to
Behavioral perspective define what is inside and what is outside
External perspective the system.
Structural perspective 2. They show other system that are used or
depend on the system being developing
28. Types Of UML Models? 3. The process of the system Boundaries has a
1. Activity diagrams : which show the activities profound effect in the system requirements
involved in a process or in data processing.
2. Use Case Diagrams: which show the 33. Legacy Software
activities involved in a process or in data a legacy system is an old method, technology,
processing . computer system, or application program, "of,
3. Sequence diagrams: which show relating to, or being a previous or outdated
interactions between actors and the system computer system.
and between actors and the system and
between system components. 34. PROCESS MODELS
4. Class Diagrams: which show the object create a timely, high-quality result. The road
map that you follow is called a “software
classes in the system and association
between these classes process.”
5. state diagrams : which show how the 35. GENERIC PROCESS MODEL
system reacts to internal and external A generic process framework for software
events. engineering defines five framework activities
communication, planning, modeling,
construction, and deployment.
36. Linear process flow
45. WHAT IS AN AGILE PROCESS ?
Any agile software process is characterized in a
37. Iterative process flow manner that addresses a number of key
assumptions about the majority of software
projects:

46. Extreme programming (XP) is a software

38. Waterfall Model development methodology which is
The waterfall model, sometimes called the intended to improve software quality and
classic life cycle, suggests a systematic, responsiveness to changing customer
sequential approach to software development requirements.
that begins with customer specification of
requirements and progresses through planning, 47. AGILE PROCESS MODELS
modeling, construction, and deployment. 1. Adaptive Software Development (ASD)
2. Scrum
39. Incremental Process Models
3. Dynamic Systems Development Method
The incremental model combines elements of
(DSDM)
linear and parallel process flows discussed
4. Crystal
Earlier. the incremental model applies linear
sequences in a staggered fashion as calendar 5. Feature Drive Development (FDD)
time progresses. 6. Lean Software Development (LSD)
7. Agile Modeling (AM)
40. Prototyping Model 8. Agile Unified Process (AUP)
In software development using Evolutionary
Prototyping model, the developers build a 48. UNDERSTANDIN REQUIREMENTS
prototype during the requirements phase. Understanding the requirements of a problem
The end users then evaluate the prototype and is among the most difficult tasks that face a
give feedback. software engineer.
49. Software Requirements
41. Spiral Model The software requirements are description of
The spiral model is an evolutionary software features and functionalities of the target
process model that couples the iterative nature system.
of prototyping with the controlled and 50. Requirement Engineering
systematic aspects of the waterfall model. The process to gather the software
requirements from client, analyze and
42. What is Agile? document them is known as requirement
The ability to create and respond to change in engineering.
order to succeed in an uncertain and unsettled
environment. 51. Requirement Engineering Process
It is a four step process, which includes –
43. What is Agile Software Development? 1. Feasibility Study
Agile software engineering combines a 2. Requirement Gathering
philosophy and a set of development 3. Software Requirement Specification
guidelines. 4. Software Requirement Validation

52. Feasibility study

When the client approaches the organization
44. WHAT IS AGILITY ? for getting the desired product developed, it
Agility has become today’s buzzword when comes up with rough idea about what all
describing a modern software process. functions the software must perform and which
Every-one is agile. An agile team is a nimble all features are expected from the software.
team able to appropriately respond to changes.
53. Requirement Gathering
If the feasibility report is positive towards 61. Brainstorming
undertaking the project, next phase starts with An informal debate is held among various
gathering requirements from the user. stakeholders and all their inputs are recorded
for further requirements analysis.
54. Software Requirement Specification
SRS is a document created by system analyst 62. Non-Functional Requirements
after the requirements are collected from Requirements, which are not related to
Performance functional aspect of software, fall into this
Cost category.
Interoperability Non-functional requirements include –
Flexibility Security
Disaster recovery Logging
Accessibility Storage
various stakeholders. Configuration
Performance
55. Software Requirement Validation Cost
After requirement specifications are developed, Interoperability
the requirements mentioned in this document Flexibility
are validated. Disaster recovery
Accessibility
56. Validation Requirements can be checked
against following 63. Requirements are categorized logically as
If they can be practically implemented 1. Must Have : Software cannot be said
If they are valid and as per functionality and operational without them.
domain of software 2. Should have : Enhancing the functionality of
If there are any ambiguities software.
If they are complete 3. Could have : Software can still properly
function with these requirements.
57. Surveys 4. Wish list : These requirements do not map
Organization may conduct surveys among to any objectives of software.
various stakeholders by querying about their
expectation and requirements from the
upcoming system.

58. Questionnaires
A document with pre-defined set of objective
questions and respective options is handed over
to all stakeholders to answer, which are
collected and compiled.

59. Task analysis

Team of engineers and developers may analyze
the operation for which the new system is
required. If the client already has some
software to perform certain operation, it is
studied and requirements of proposed system
are collected.
60. Domain Analysis
Every software falls into some domain category.
The expert people in the domain can be a great
help to analyze general and specific
requirements.