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 FALL	2013
PROGRAM	MBADS – (SEM 3/SEM 5) / MBAFLEX / MBAN2 – (SEM 3)/ PGDISMN - (SEM 1)
SUBJECT CODE & NAME	MI0033- SOFTWARE ENGINEERING
SEMESTER	3
BK ID	B1483
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 Highlight the reasons for measuring a software product. Also discuss the classification of process metrics measurement.

Ans : Reasons for measuring a software product :

The very nature of software engineering makes measurement a necessity, because more rigorous methods for production planning, monitoring, and control are needed, otherwise the amount of risk of software projects may become excessive, and software production may easily get out of industrial control. This would produce obvious damages to both software producers (e.g., higher costs, schedule slippage) and users (e.g., poor quality products, late product delivery, high prices). To be effective and make good use of the resources devoted to it, software measurement should address important development issues, i.e., it should be carried out within a precise goal of industrial interest. In this context, software measurement may serve several purposes, depending on the level of knowledge about a process of product.

Q.2 The Elite info systems has gone through three phases of application change management. They are informal, production promotion and software configuration management. In earlier informal phase the software engineer who developed the code has to place it into production. Due to poor documentation, there was difficulty in understanding and differentiating between the new code and existing code. Then elite info systems adopted change management process. The first ERP was implemented in the company. The company also segregated the duties of the software professional in the company based on the area of specialization and domain knowledge. According to this phase the developer who develops the code could not be held responsible for placing into production. Rather if the developer who wants to change the code has to submit the request through web based application where the changes are tracked and updated simultaneously. Automated workflow was established so that requests could be routed to the right channel for approval. The SCM was introduced into their development life cycle and this brought about a change in the software production life cycle. The SCM process gave segregation of duties which diminished the damage that could be caused by incompetence. Therefore in software configuration management phase, segregation of duties ensured security and reduced the risk. The various responsibilities of configuration migration, enhancement of quality control and analysis and coordination with the change management group. The tools used in the systems is application- change tracking and development tool. They used this software to govern and archive the various software versions. It stores all the code in the archiving version manager, which enhance quality and simplifies troubleshooting. The process adopted helps to improve the quality by managing change and predicting its effect. Consistent governing rules were enforced throughout the deployment process. It provide clear accountability which automated audits trails identified the required approvals at each phase. Early intervention results in more repeatable, faster deployments with fewer errors. Due to the deployment of this process, the three main goals of change management were achieved which are; development of quality, reduction by risk by helping ensure that processes are repeatable and predictable, and reduction of development costs. The following are the benefits of the process Increased developer productivity Improved IT service to internal clients Enhanced scalability Employee acceptance Therefore Elite Info Systems concludes that SCM is to be made as an integral part of their production process. The company regarded SCM not as a luxury, but as necessity.

a. Which process did Elite Info Systems deployed to improve the quality of change? Why?

Ans : Elite info system deployed Software configuration management process (SCM). This system was deployed because due to the deployment of this process, the three main goals of change management were achieved which are;

1. development of quality,

2. reduction by risk by helping ensure that processes are repeatable and predictable, 

3. reduction of development costs.

In software engineering, software configuration management (SCM) is the task of tracking and controlling changes in the software, part of the larger cross-discipline field of configuration management." SCM practices include revision control and the establishment of baselines. If something goes wrong, SCM can determine what was changed and who changed it. If a configuration is working well, SCM can determine

b. What is predictive reliability? How SCM will help in prediction?

Ans :  Predictive reliability :

Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment. Software Reliability is also an important factor affecting system reliability. It differs from hardware reliability in that it reflects the design perfection, rather than manufacturing perfection. The high complexity of software is the major contributing factor of Software Reliability problems. Software Reliability is not a function of time - although researchers have come up with models relating the two. The modelling technique for Software Reliability is reaching its prosperity, but before using the technique, we must carefully select the appropriate model that can best suit our case. Measurement in software is still in its infancy. No good quantitative methods have been developed to

Q. 3 With the program module diagram explain bottom-up integration. Give example

Ans :  Integration testing is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing phase and before system testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. A component, in this sense, refers to an integrated aggregate of more than one unit.

Bottom Up is an approach to Integration Testing where bottom level units are tested first and upper level units step by step after that. This approach is taken when bottom up development approach is followed. Test Drivers are needed to simulate higher

Q.4 Mr. Shyam Kumar is the Assistant project manager in a software company. The company has bagged a contract for developing software for the credit card division of a private bank. Mr. Shyam Kumar and his team have decided to take up the requirement analysis phase of software engineering. What are the tasks or operations that Mr. Shyam Kumar and his team have to take up in order to complete the software requirement analysis phase?

Ans : software requirement analysis phase:

1. The members of a software development team must have a clear understanding of what the software product must do.

2. The first step is to perform a thorough analysis of the client’s current situation, careful to define the situation as precisely as possible.

Q.5 Consider your friend has opened a small IT hub or internet café in your city. List the steps that you implement the key practices that explain the infrastructure and performances of his hub.

Ans :  Steps explaining the infrastructure and performances of cafe / hub :

1. Formulate an idea of how you want to run your Internet café and write it down, the different amenities and services you want to offer and the audience you wish to cater to.

2. Research the feasibility of your plan in the area you wish to open your Internet café. Look specifically at the demand for an Internet café and competitors in the area and estimate how much money you will require as an initial investment.

Q.6 Write Short notes on

a. Prototyping

Ans : Software prototyping, refers to the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed. It is an activity that can occur in software development and is comparable to prototyping as known from other fields, such as mechanical engineering or manufacturing.

A prototype typically simulates only a few aspects of, and may be completely different from, the final product.

Benefits of software prototype :

There are many advantages to using prototyping in software development – some tangible, some abstract.

b. Quality Control (QC)

Ans : Quality Control:

"Variation control may be equated to quality control. But how do we achieve quality control# Quality control involves the series of inspections, reviews, and tests used throughout the software process to ensure each work product meets the requirements placed upon it. Quality control includes a feedback loop to the process that created the work product. The combination of measurement and feedback allows us to tune the process when the work products created fail to meet their specifications. This approach views quality control as part of the manufacturing process. Quality control activities may be fully automated,

Dear students get fully solved assignments

Send your semester & Specialization name to our mail id :

  help.mbaassignments@gmail.com

or

call us at : 08263069601