0% found this document useful (0 votes)
31 views5 pages

Software Engineering Imp

Most important
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
31 views5 pages

Software Engineering Imp

Most important
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

SOFTWARE ENGINEERING (SE)

1 MARKS
Q.1 List the benefits of prototyping model.
Ans.1) Improved Requirements Gathering
2)Enhanced User Involvement
3)Early Detection of Defects
4)Reduced Risk
5)Improved Quality
6)Increased User Satisfaction

Q.2 List the primary goal of software engineering.


Ans. 1. Quality: Develop software that meets requirements, is reliable, efficient, scalable, and
maintainable.
2. Functionality: Create software that fulfills its intended purpose and meets user needs.
3. Reliability: Ensure software operates consistently and accurately in various environments.
4. Efficiency: Optimize software performance, minimizing resource utilization.
5. Maintainability: Design software for easy modification, updates, and troubleshooting.
6. Scalability: Develop software that adapts to growing demands and changing requirements.
7. Usability: Create user-friendly software with intuitive interfaces.

Q.3 Define Agility.


Ans. In software development the term ‘agile’ is adapted to mean ‘the ability to
respond to changes – changes from Requirements, technology and People.
Q.4 State any two human factors considered agile software
development.
Ans. 1)Competence: Competence in the agile development context, encompasses natural talent
and specific software related skills with overall technical knowledge.
2) Decision Making Ability: The project team must be allowed the freedom to control its own
destiny, so they can take individual decisions on various issues.

Q.5List the problem faced during requirement elicitation.


Ans.1)changing requirement
2)stakeholder involvement
3)communication issue
4)hidden requirement
5)lack of domain knowledge
6)time constraints
7)cultural and organizational barriers
Q.6 What is negotiation?
Ans. When multiple stakeholders are involved, requirements will conflict. This concerned with
prioritizing requirements and finding and resolving requirements conflicts through negotiation.

Q.7 What is meant by structured analysis.


Ans. Structured Analysis is a development method that allows the analyst to
understand the system and its activities in a logical way.

Q.8List the components of structured analysis.


Ans.1)Data flow
2)Modularity
3)Control flow
4)Decision Table
5)Module
6)Context diagram
7)Abstraction
Q.9 What is meant by deployment?
Ans. The software is delivered to the customer who evaluates the delivered product and provides
feedback based on the evaluation. In short, the delivery of a working system for evaluation and
feedback is called deployment.

Q.10 What is software architecture?


Ans. The complete structure of the software, which is composed of various components
of a system, the attributes of those components and the relationship amongst them is
called software architecture.
2 marks question…..
Q.1 What are software quality guidelines for good design?
Ans. 1)A design should lead to interface that reduce the complexity of connections
between components and with the external environment.
2)A design should lead to components that exhibit independent functional
characteristics.
3)A design should lead to data structure that are appropriate for the classes to be
implemented and are drawn from recognizable data patterns.
4)A design should be represented using a notation that effectively communicates its
meaning.
Q.2 Explain use case model.
Ans. 1)A use case model use to interact with the system to solve a problem. A use case model
consists of a different of model elements. 2)The most important model elements are use cases,
actors and the relationships between them.
3)A use case model is represented by using use case diagram is just a special kind of diagram and
shares the same common properties as do all other diagrams a name and graphical contents that
are a projection into a model.
4)Use case diagrams present an outside view of the manner the elements in a system behave and
how they can be used in the context.

Q.3 State the importance of generalization in class diagram.


Ans. 1)A generalization is a relationship between a general thing i.e. super class or parent class
and a specific thing i.e. sub-class or child class.
2)It is similar to the concept of inheritance in OOP's. Generalization can be defined as "a
relationship which connects a specialized element with a generalized element."
3)It basically describes inheritance relationship in the world of objects. It is known as an "is a"
relationship since the child class is a type of the parent class.
4)Generalization is the ideal type of relationship that is used to showcase reusable elements in the
class diagram.

Q.4 What is software requirement specification?


Ans. The software requirements document (sometimes called the Software
Requirements Specification or SRS) is an official statement of what the system
developers should implement.
Q.5 State the difference between structured and unstructured
interviews
Ans.
Structured interviews Unstructured interviews
1)applicants are asked the same questions in the 1)applicants may be asked different questions.
same order.
2)structured interview is one in which a particular set 2)Unstructured interview refers to an interview in
of predetermined questions are prepared by the which the questions to be asked to the respondents
interviewer in advance. are not set in advance.
3)Aim to maintain consistency 3)Aims at spontaneous and open ended discussions
4)Application are evaluated using a common rating 4)A standardized rating scale is not required.
scale.

Q.6 Explain agile process model.


Ans. 1)Agile is a development process that emphasizes customer satisfaction through the continuous provision
of working software.
2)Agile SDLC model is a combination of iterative and incremental process models with focus on process
adaptability and customer satisfaction by rapid delivery of working software products.
3)Agile methods break the product into small incremental builds. These builds are provided in iterations. Each
iteration typically lasts from about one to three weeks.
4)Every iteration involves cross functional teams working simultaneously on various areas like Planning,
Requirements Analysis, Design, Coding, Unit Testing and Acceptance Testing.
5)At the end of the iteration, a working product is displayed to the customer and important stakeholders.
6)Agile models believe that every project needs to be handled differently and the existing methods need to be
tailored to best suit the project requirements.

Q.7Define agile? State its advantages and disadvantages.


Ans. An agile software process must adapt incrementally. To accomplish
incremental adaptation, an agile team requires customer feedback.
Advantages of Agile:
1. Change is Embraced: With shorter planning cycles, it is easy and to accommodate and accept
changes at any time during the software project.
2. End-goal can be Unknown: Agile is very beneficial for projects where the end-goal is not clearly
defined. As the project progresses, the goals will come to light and development can easily and
simply adapt to these evolving requirements.
3. Faster and High-quality Delivery: Breaking down the project into iterations (manageable units)
allows the software team to focus on high-quality development, with faster delivery.
4. Strong Team Interaction: Agile highlights the importance of frequent communication and face-
to-face interactions.

Disadvantages of Agile:
1. Planning can be Less Concrete: Agile is based on time-boxed delivery and project managers are often
reprioritizing tasks, it is possible that some items originally scheduled for delivery may not be complete in time.
2. Team must be Knowledgeable: Agile teams are usually small, so team members must be highly skilled in a
variety of areas.
3. Time Commitment from Developers: Active involvement and collaboration is required throughout the Agile
process, which is more time consuming than a traditional approach.

4. Final Product can be very Different: Agile is so flexible, new iterations may be added based on evolving
customer feedback, which can lead to a very different

Q.8 Explain the phases of waterfall model.


Ans. 1)Communication: In the communication phase the major task performed is requirement gathering which
helps in finding out the exact need of the customer. Once, all the needs of the customer are gathered the next
step is planning.
2)Planning: In planning major activities like planning for schedule, keeping track of on the processes and the
estimation related to the project are done. Planning is even used to find the types of risks involved throughout the
projects. Planning describes how technical tasks are going to take place and what resources are needed and how
to use them.
3)Modelling: This is one the important phases as the architecture of the system is designed in this phase. Analysis
is carried out and depending on the analysis a software model is designed. Different models for developing
software are created depending on the requirements gathered in the first phase and the planning done in the
second phase.
4)Construction: The actual coding of the software is done in this phase. This coding is done on the basis of the
model designed in the modelling phase. So in this phase software is actually developed and tested.
5)Deployment: In this last phase the product is actually rolled out or delivered and installed at customer's end and
support is given if required. A feedback is taken from the customer to ensure the quality of the product.

Q.9 Explain concurrent development model.


Ans. 1)The concurrent models deployment model is also called concurrent engineering. This
model allows developer to represent iterative and parallel elements of any of the process model.
2)The activity modeling in this model may be in any one of the states noted at any given time.
Similarly, other activities, actions, or tasks (e.g., communication or construction)can be represented
in an analogous manner.
3)All software engineering activities exist concurrently but reside in different states, (for example,
early in a project the communication activity has completed its first iteration and exists in the
awaiting changes state).
4)The modeling activity in this model which existed in the inactive state while initial communication
was completed, now makes a transition into the under development state.
5)If however, the customer indicates that changes in requirements must be made, the modeling
activity moves from the under development state into the awaiting changes state.
6)Concurrent modeling defines a series of events that will trigger transitions from state to state for
each of the software engineering activities, actions, or tasks, (for example, during early stages of
design, an inconsistency in the requirements model is uncovered).

Q.10 Explain spiral model.


Ans.1) Inner spirals focus on identifying software requirements and project risks; may also
incorporate prototyping.
2)Outer spirals take on a classical waterfall approach after requirements have been defined, but
permit iterative growth of the software.
3)Risk analysis is the most important criteria considered in this model. The spiral model has five
phases Communication, Planning, Risk Analysis, Modeling, Construction and Deployment.
4)A software project repeatedly passes through these phases in iterations (called spirals in this
model).
5)The baseline spiral, starting in the communication phase, the planning phase, requirements are
gathered and risk is assessed, modeling, construction and deployment. Each subsequent spiral
builds on the baseline spiral.
6)IEEE defines the spiral model as, "a model of the software development process in which the
constituent activities, typical requirements analysis, preliminary and detailed design, coding,
integration and testing are performed iteratively until the software is complete".

You might also like