TechnoByte, The Students Forum
Software Engineering

What is requirement engineering? Describe different steps for requirement engineering processes.

Requirements engineering is the process of defining, documenting and maintaining requirements in the software design process. Requirements engineering is the process of bringing out the stakeholder needs and desires and developing them into an agreed-upon set of detailed requirements that can serve as a basis for all subsequent development activities. The purpose of requirements engineering methodologies is to make the problem that is being stated clear and complete, and to ensure that the solution is correct, reasonable, and effective.


Write notes on SRS

A software requirements specification (SRS) is a document that describes what the software will do and how it will be expected to perform. It also describes the functionality the product needs to fulfill all stakeholders (business, users) needs.
An SRS can be divided into the following four tasks:

  • Defines the purpose of the product.
  • Describe what we are building.
  • Detail the requirements.
  • Deliver it for approval.

Usefulness of an SRS Document:
An SRS gives a complete picture of the entire project. It provides a single source of plan that every team involved in development will follow. It is the plan of action and keeps all the teams — from development to maintenance to work in unison.


Write notes on Software Engineering Approaches

Write notes on Project Management Processes.

What are the different characteristics of Software process ? Describe different software development processes with their merits and demerits.

Explain the various steps in cost estimation procedure using COCOMO.

Write notes on Quality Assurance Plans

Write notes on Project Monitoring Plans.

What is meant by project planning ? Describe different types of Project estimatio n techniques.


Write short notes on COCOMO

Before the start of any software project, various factors are taken into consideration. These factors decide how the project development phase will proceed, how the product will be deployed, and what are the risks involved.

One of these factors includes the time and cost factor. It is important to know how much time will it take before the product is ready for deployment. Cost does also plays a very important factor during the development of the product.

COCOMO model (Constructive Cost Estimation model) was proposed by Boehm in 1981. It is used to estimate the cost and effort required to complete any product based on its size.

The Cocomo model divides software projects into 3 types- Organic
Semi-detached
Embedded

ORGANIC – A software development project comes under organic type if the development team is small, the problem is not complex, and has been solved before. Also, a nominal experience of team members is considered. Some of the projects that can be organic are- small data processing systems, basic inventory management systems, business systems.

SEMIDETACHED – A software project that is in-between the organic and embedded system is a semi-detached system. Its characteristics include – a middle-sized development team, with a mix of both- experienced and inexperienced members, and the project complexity is neither too high nor too low.

The problems faced in this project are a few known and a few unknown, which have never been faced before. Few such projects are- Database Management System(DBMS), new unknown operating system, difficult inventory management system.

EMBEDDED – A project requiring a large team with experienced members, and having the highest level of complexity is an embedded system. The members need to be creative enough to be able to develop complex models. Such projects include- air traffic models, ATMs, complex banking systems etc.

Calculation
The effort and the time taken to complete both are calculated through predefined equations.
The formula used is-

Effort(E)= a*(KLOC)^b PM(Person month)
Time = c(E)d
Person Required = effort/time
Where,
KLOC = size of the product i.e. no. of lines of code.
a, b, c, d are constants and have different values for different models.
Time is the time required to develop the product and the unit is months.
And the effort is the total effort calculated that will be required to complete the work calculated in PM (Person Months).

If the constants are replaced by actual values, then the equations will be-

Organic-
E = 2.4(KLOC) 1.05 PM
T = 2.5(E) 0.38 Months
Semi-detached-
E= 3.0(KLOC) 1.12 PM
T = 2.5(E) 0.35 Months
Embedded-
E= 3.6(KLOC) 1.20 PM
T= 2.5(E) 0.32 Months
This is how the effort and time taken to complete the project are calculated.


Write short notes on Staffing.

What do you mean by structure oriented design ? Discuss in details the techniques for structural design.

Write notes on Design principles of function oriented design.

Write notes on De-Notations.

What is function oriented software design? Discuss in details about function oriented software design.

Discuss different types of Cohesion Metrics in the context of software design.

What is PDL ?

What is Cyclomatic complexity ? What is the need of it in the context of software design ? Explain in details with the help of flow graph.

Write notes on Data bindings

Write notes on Cohesion Metrics.

What is Testing ? Discuss the various approaches for structural testing.

What is Testing process reliability estimation ? Discuss the various approaches for functional testing.

What do you mean by SRS? What are the characteristics of good SRS? Give an example of bad SRS document? Who are the typical users of SRS document?

What is the importance of requirement analysis? What are the tools used for gathering the requirment?

What are the characteristics of software processes? Discuss various types of software processes.

What are the objectives of software project planning? Describe different project decomposition techniques.

Describe different empirical estimation models.

What are various types of development project? Explain the COCOMO model with example for all types of project.