MI0033 – SOFTWARE ENGINEERING

Dear students get fully solved assignments

Send your semester & Specialization name to our mail id :

  help.mbaassignments@gmail.com

or

call us at : 08263069601

ASSIGNMENT

DRIVE	SUMMER 2015
PROGRAM	MBADS (SEM 3/SEM 5)MBAFLEX/ MBA (SEM 3)PGDISMN (SEM 1)
SUBJECT CODE & NAME	MI0033 – SOFTWARE ENGINEERING
BK ID	B1965
CREDITS	4
MARKS	60

Note: Answer all questions. Kindly note that answers for 10 marks questions should be approximately of 400 words. Each question is followed by evaluation scheme.

Q. 1. Explain the overall agile process in detail

Answer:Agile development is billed as an iterative, incremental process that can cut down the time it takes build and deliver IT systems to business users. So what makes an agile project successful?  How do development teams avoid pitfalls that could sink a project? Various experts from government and industry involved in agile development offer a few tips.

1. Establish strong relationships between IT and business customers. In order for agile to work there has to be a strong relationship between the IT department and contractors with the agency’s business customer. The business customer, in turn, has to be able to work where there aren’t clearly defined processes,  according to Jeff Newlin, vice president and general manager of OutSystems, a provider of agile technology.

b. Explain COCOMO in a nutshell

Answer:The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry W. Boehm. The model uses a basic regression formula with parameters that are derived from historical project data and current as well as future project characteristics.

References to this model typically call it COCOMO 81. In 1995 COCOMO II was developed and finally published in 2000 in the book Software Cost Estimation with COCOMO II.[2] COCOMO II is the successor of COCOMO 81 and is better suited for estimating modern software development projects. It provides more support for

Q. 3. a. Explain function oriented metrics

Answer: Function-oriented software metrics use a measure of the functionality delivered by the application as a normalization value. Since ‘functionality’ cannot be measured directly, it must be derived indirectly using other direct measures. Function-oriented metrics were first proposed by Albrecht , who suggested a measure called the function point. Function points are derived using an empirical relationship based on countable (direct) measures of software's information domain and assessments of software complexity.

b. How do you calculate function points?

Answer: To compute function points (FP), the following relationship is used:

                              FP = count total [0.65 + 0.01 Σ(Fi)] where count total is the sum of all FP entries .

The Fi (i = 1 to 14) are "complexity adjustment values" based on responses to the following questions :

1. Does the system require reliable backup and recovery?

2. Are data communications required?

3. Are there distributed processing functions?

4. Is performance critical?

5. Will the system run in an existing, heavily utilized operational environment?

6. Does the system

Q. 4. a. Explain the system architecture specification

Answer:  Architecture should provide guidance to developers in such a way to avoid integration and maintenance issues. More specifically, architecture should identify things such as approved operating systems, approved development languages, approved data storage systems, approved communication protocols, coding practices,

b. Explain System specification review

Answer: A System Requirements Review (SRR) is a formal review conducted to ensure that system requirements have been completely and properly identified and that a mutual understanding between the government and contractor exists. It ensure that the system under review can proceed into initial systems development and that all system and performance requirements derived from the Initial Capabilities Document (ICD

Q.5. Explain the 12-step program design process of software engineering that is followed to get the organizations back on track.

Answer: The life cycle most of us probably are most familiar with is the system development life cycle (SDLC), which is closely allied with the project management life cycle. The diagram below shows both together.

Q. 6. a. Elaborate on Capability Maturity Model components.

Answer: Capability Maturity Model Integration (CMMI) is a process improvement approach that provides organizations with the essential elements of effective processes. There are three different types of appraisals, type A, B and C. In Appraisal Requirements for CMMI (ARC) the requirements for CMMI appraisal methods are described. The Standard CMMI Assessment Method for Process Improvement (SCAMPI) is the only appraisal method

b. Define Quality control and Cost of quality with the types of cost.

                                                               

Answer:Quality control, or QC for short, is a process by which entities review the quality of all factors involved in production. ISO 9000 defines quality control as "A part of quality management focused on fulfilling quality requirements".

This approach places an emphasis on three aspects:

Dear students get fully solved assignments

Send your semester & Specialization name to our mail id :

  help.mbaassignments@gmail.com

or

call us at : 08263069601