com
D.SAMEERA,Asst.Prof 2010
UNIT - 1
Conventional Software Management
2. In order to mange and control all of the intellectual freedom associated with software development one should follow
the following steps:
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
3. Since the testing phase is at the end of the development cycle in the waterfall model, it may be risky and invites
failure.
So we need to do either the requirements must be modified or a substantial design changes is warranted by
breaking the software in to different pieces.
-There are five improvements to the basic waterfall model that would eliminate most of the development
risks are as follows:
a) Complete program design before analysis and coding begin (program design comes first):-
- By this technique, the program designer give surety that the software will not fail because of storage, timing, and
data fluctuations.
- Begin the design process with program designer, not the analyst or programmers.
- Write an overview document that is understandable, informative, and current so that every worker on the project
can gain an elemental understanding of the system.
b) Maintain current and complete documentation (Document the design):-
-It is necessary to provide a lot of documentation on most software programs.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
- Due to this, helps to support later modifications by a separate test team, a separate maintenance team, and
operations personnel who are not software literate.
c) Do the job twice, if possible (Do it twice):-
- If a computer program is developed for the first time, arrange matters so that the version finally delivered
to the customer for operational deployment is actually the second version insofar as critical design/operations are
concerned.
- “Do it N times” approach is the principle of modern-day iterative development.
d) Plan, control, and monitor testing:-
- The biggest user of project resources is the test phase. This is the phase of greatest risk in terms of cost and
schedule.
- In order to carryout proper testing the following things to be done:
i) Employ a team of test specialists who were not responsible for the original design.
ii) Employ visual inspections to spot the obvious errors like dropped minus signs, missing factors of
two, jumps to wrong addresses.
iii) Test every logic phase.
iv) Employ the final checkout on the target computer.
e) Involve the customer:-
- It is important to involve the customer in a formal way so that he has committed himself at earlier points before
final delivery by conducting some reviews such as,
i) Preliminary software review during preliminary program design step.
ii) Critical software review during program design.
iii) Final software acceptance review following testing.
IN PRACTICE:-
- Whatever the advices that are given by the software developers and the theory behind the waterfall model, some
software projects still practice the conventional software management approach.
Projects intended for trouble frequently exhibit the following symptoms:
i) Protracted (delayed) integration
- In the conventional model, the entire system was designed on paper, then implemented all at once,
then integrated. Only at the end of this process was it possible to perform system testing to verify that the
fundamental architecture was sound.
- Here the testing activities consume 40% or more life-cycle resources. ACTIVITY
COST
Management 5%
Requirements 5%
Design 10%
Code and unit testing 30%
Integration and test 40%
Deployment 5%
Environment 5%
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
- It includes four distinct periods of risk exposure, where risk is defined as “the probability of missing a
cost, schedule, feature, or quality goal”.
Project Stakeholders :
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
1) Finding and fixing a software problem after delivery costs 100 times more than finding and fixing the
problem in early design phases.
2) You can compress software development schedules 25% of nominal (small), but no more.
4) Software development and maintenance costs are primarily a function of the number of source lines of
code.
5) Variations among people account for the biggest difference in software productivity.
6) The overall ratio of software to hardware costs is still growing. In 1955 it was 15:85; in 1985, 85:15.
8) Software systems and products typically cost 3 times as much per SLOC as individual software programs.
Software-system products cost 9 times as much.
- 80% of the software scrap and rework is caused by 20% of the errors.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
Part-2
Evolution of Software Economics
SOFTWAR ECONOMICS:-
The cost of the software can be estimated by considering the following things as parameters to a
function.
1)Size: Which is measured in terms of the number of Source Lines Of Code or the number of
function points required to develop the required functionality.
2)Process: Used to produce the end product, in particular the ability of the process is to avoid non-
value-adding activities (rework, bureaucratic delays, communications overhead).
3)Personnel: The capabilities of software engineering personnel, and particularly their experience
with the computer science issues and the application domain issues of the project.
4)Environment: Which is made up of the tools and techniques available to support efficient
software development and to automate the process.
The relationship among these parameters and estimated cost can be calculated by using,
- One important aspect of software economics is that the relationship between effort and size
exhibits a diseconomy of scale and is the result of the process exponent being greater than 1.0.
- Converse to most manufacturing processes, the more software you build, the more expensive it is
per unit item.
- There are three generations of basic technology advancement in tools, components, and processes
are available.
1) Conventional: 1960 and 1970, Craftsmanship. Organizations used custom tools, custom
processes, and virtually all custom components built in primitive languages. Project performance was highly
predictable.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
2) Transition: 1980 and 1990, software engineering. Organizations used more-repeatable processes
and off-the-shelf tools, and mostly (>70%) custom components built in higher level languages.
- Some of the components (<30%) were available as commercial products like, OS, DBMS,
Networking and GUI.
- 70% component-based,
- 30% custom
E n v i r o n m e n t s / t o o l s :
S i z e:
P r o c e s s :
T y p i c a l p r o j e c t P e r f o r m a n c e :
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
Return on investment is a very popular metric because of its versatility and simplicity. That
is, if an investment does not have a positive ROI, or if there are other opportunities with a higher ROI, then
the investment should be not be undertaken
Project Sizes :
The less software we write, the better it is for project management and for product quality
- The cost of software is not just in the cost of ‘coding’ alone; it is also in
Analysis of requirements
– Design
– Review of requirements, design and code
– Test Planning and preparation
– Testing
– Bug fix
– Regression testing
– ‘Coding’ takes around 15% of development cost
- Clearly, if we reduce 15 hrs of coding, we can directly reduce 100 hrs of development effort, and also
reduce the project team size appropriately !
- Size reduction is defined in terms of human-generated source code. Most often, this might still mean that
the computer-generated executable code is at least the same or even more
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
- If there is no proper well-documented case studies then it is difficult to estimate the cost of the
software. It is one of the critical problem in software cost estimation.
- But the cost model vendors claim that their tools are well suitable for estimating iterative
development projects.
- In order to estimate the cost of a project the following three topics should be considered,
- There are a lot of software cost estimation models are available such as,
- Of which COCOMO is one of the most open and well-documented cost estimation models
- Most software experts argued that the SLOC is a poor measure of size. But it has some value in the
software Industry.
- SLOC worked well in applications that were custom built why because of easy to automate and
instrument.
- Now a days there are so many automatic source code generators are available and there are so
many advanced higher-level languages are available. So SLOC is a uncertain measure.
- The main advantage of function points is that this method is independent of the technology and is
therefore a much better primitive unit for comparisons among projects and organizations.
- The main disadvantage of function points is that the primitive definitions are abstract and
measurements are not easily derived directly from the evolving artifacts.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA,Asst.Prof 2010
- Function points is more accurate estimator in the early phases of a project life cycle. In later
phases, SLOC becomes a more useful and precise measurement basis of various metrics perspectives.
- The most real-world use of cost models is bottom-up rather than top-down.
- The software project manager defines the target cost of the software, then manipulates the parameters and
sizing until the target cost can be justified.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
UNIT-II
Improving Software Economics
- It is not that much easy to improve the software economics but also difficult to measure and
validate.
- There are many aspects are there in order to improve the software economics they are, Size,
Process, Personnel, Environment and quality.
- These parameters (aspects) are not independent they are dependent. For example, tools enable
size reduction and process improvements, size-reduction approaches lead to process changes,
and process improvements drive tool requirements.
- GUI technology is a good example of tools enabling a new and different process. GUI builder
tools permitted engineering teams to construct an executable user interface faster and less cost.
- Two decades ago, teams developing a user interface would spend extensive time analyzing
factors, screen layout, and screen dynamics. All this would done on paper. Where as by using
GUI, the paper descriptions are not necessary.
- Along with these five basic parameters another important factor that has influenced software
technology improvements across the board is the ever-increasing advances in hardware
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
performance.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
Here UPFs (Universal Function Points) are useful estimators for language-independent in the
early life cycle phases. The basic units of function points are:
- External outputs
- External inquiries
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
Booch described the following three reasons for the success of the projects that are using
Object-Oriented concepts:
2) The use of continuous integration creates opportunities to recognize risk early and
make incremental corrections without weaken the entire development effort.
REUSE:
Organizations that translates reusable components into commercial products has the
following characteristics:
- They take ownership of improving product quality, adding new features and
transitioning to new technologies.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
COMMERCIAL COMPONENTS
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
1) Meta process:
2) Macro process:
3) Micro process:
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
- COCOMO model suggests that the combined effects of personnel skill and experience can
have an impact on productivity as much as a factor of four over the unskilled personnel.
- Balance and coverage are two of the most important features of excellent teams.
Whenever a team is in out of balance then it is vulnerable.
- It is the responsibility of the project manager to keep track of his teams. Since teamwork
is much more important than the sum of the individuals.
2) The principle of job matching: Fit the tasks to the skills and motivation of the people
available.
3) The principle of career progression: An organization does best in the long run by
helping its people to self-actualize.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
4) The principle of team balance: Select people who will complement and synchronize
with one another.
5) The principle of phase-out: Keeping a misfit on the team doesn’t benefit anyone.
– If people are already available with required skill set, just take them
– If people are already available but do not have the required skills, re-train them
– If you are not able to recruit skilled people, recruit and train people
- Project Manager
- Software Architect
Decision-making skill. The jillion books written about management have failed to
provide a clear definition of this attribute. We all know a good leader when we run into
one, and decision-making skill seems obvious despite its intangible definition.
Selling skill. Successful project managers must sell all stakeholders (including
themselves) on decisions and priorities, sell candidates on job positions, sell changes to
the status quo in the face of resistance, and sell achievements against objectives. In
practice, selling requires continuous negotiation, compromise, and empathy.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
Planning tools, Quality assurance and analysis tools, Test tools, and User
interfaces provide crucial automation support for evolving the software engineering
artifacts.
Round-trip engineering: is a term used to describe the key capability of
environments that support iterative development.
Forward engineering: is the automation of one engineering artifact from
another, more abstract representation. Ex: compilers and linkers
Reverse engineering: is the generation of modification of more abstract
representation from an existing artifact. Ex: creating visual design model from
a source code.
ACHIEVING REQUIRED QUALITY:
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
- This transition is was motivated by the unsatisfactory demand for the software
and reduced cost.
THE PRINCIPLES OF CONVENTIONAL SOFTWARE ENGINEERING
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
1) Make quality #1: Quality must be quantified and mechanisms put into place
to motivate its achievement.
2) High-quality software is possible: In order to improve the quality of the
product we need to involving the customer, select the prototyping, simplifying
design, conducting inspections, and hiring the best people.
3) Give products to customers early: No matter how hard you try to learn user’s
needs during the requirements phase, the most effective way to determine real
needs is to give users a product and let them play with it.
4) Determine the problem before writing the requirements: Whenever a
problem is raised most engineers provide a solution. Before we try to solve a
problem, be sure to explore all the alternatives and don’t be blinded by the
understandable solution.
5) Evaluate design alternatives: After the requirements are greed upon, we must
examine a variety of architectures and algorithms and choose the one which is not
used earlier.
6) Use an appropriate process model: For every project, there are so many
prototypes (process models). So select the best one that is exactly suitable to our
project.
7) Use different languages for different phases: Our industry’s main aim is to
provide simple solutions to complex problems. In order to accomplish this goal
choose different languages for different modules/phases if required.
8) Minimize intellectual distance: We have to design the structure of a software
is as close as possible to the real-world structure.
9) Put techniques before tools: An un disciplined software engineer with a tool
becomes a dangerous, undisciplined software engineer.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
10) Get it right before you make it faster: It is very easy to make a working
program run faster than it is to make a fast program work. Don’t worry about
optimization during initial coding.
11) Inspect the code: Examine the detailed design and code is a much better way
to find the errors than testing.
12) Good management is more important than good technology
13) People are the key to success: Highly skilled people with appropriate
experience, talent, and training are key. The right people with insufficient tools,
languages, and process will succeed.
14) Follow with care: Everybody is doing something but does not make it right
for you. It may be right, but you must carefully assess its applicability to your
environment.
15) Take responsibility: When a bridge collapses we ask “what did the engineer
do wrong?”. Similarly if the software fails, we ask the same. So the fact is in
every engineering discipline, the best methods can be used to produce poor results
and the most out of date methods to produce stylish design.
16) Understand the customer’s priorities. It is possible the customer would
tolerate 90% of the functionality delivered late if they could have 10% of it on
time.
17) The more they see, the more they need. The more functionality (or
performance) you provide a user, the more functionality (or performance) the
user wants.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
18) Plan to throw one away .One of the most important critical success factors
is whether or not a product is entirely new. Such brand-new applications,
architectures, interfaces, or algorithms rarely work the first time.
19) Design for change. The architectures, components, and specification
techniques you use must accommodate change.
20) Design without documentation is not design. I have often heard software
engineers say, “I have finished the design. All that is left is the documentation.”
21. Use tools, but be realistic. Software tools make their users more efficient.
22. Avoid tricks. Many programmers love to create programs with tricks-
constructs that perform a function correctly, but in an obscure way. Show the
world how smart you are by avoiding tricky code.
23. Encapsulate. Information-hiding is a simple, proven concept that results in
software that is easier to test and much easier to maintain.
24. Use coupling and cohesion. Coupling and cohesion are the best ways to
measure software’s inherent maintainability and adaptability.
25. Use the McCabe complexity measure. Although there are many metrics
available to report the inherent complexity of software, none is as intuitive and
easy to use as Tom McCabe’s.
26. Don’t test your own software. Software developers should never be the
primary testers of their own software.
27. Analyze causes for errors. It is far more cost-effective to reduce the effect of
an error by preventing it than it is to find and fix it. One way to do this is to
analyze the causes of errors as they are detected.
28. Realize that software’s entropy increases. Any software system that
undergoes continuous change will grow in complexity and become more and
more disorganized.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
29. People and time are not interchangeable. Measuring a project solely by
person-months makes little sense.
30) Expert excellence. Your employees will do much better if you have high
expectations for them.
Major risks must be addressed early to increase predictability and avoid expensive
downstream scrap and rework.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
5) Enhance change freedom through tools that support round-trip engineering: (The
automation element)
- Visual modeling with rigorous notations and formal machine- process able language
provides more objective measures than the traditional approach of human review and
inspection of ad hoc design representations in paper doc.
7) Instrument the process for objective quality control and progress assessment:
- Life-cycle assessment of the progress and quality of all intermediate product must be
integrated into the process.
- The best assessment mechanisms are well-defined measures derived directly from the
evolving engineering artifacts and integrated into all activities and teams.
of detail:
No single process is suitable for all software developments. The process must
ensure that there is economy of scale and ROI.
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
www.jntuworld.com
www.jntuworld.com
D.SAMEERA 2010
www.jntuworld.com
www.jntuworld.com
UNIT-III
LIFE-CYCLE PHASES
INTRODUCTION:
- If there is a well defined separation between “research and development” activities and
“production” activities then the software is said to be in successful development process.
- Most of the software’s fail due to the following characteristics ,
1) An overemphasis on research and development.
2) An overemphasis on production.
1) The engineering stage: Less predictable but smaller teams doing design and production
activities. This stage is decomposed into two distinct phases inception and elaboration.
2) The production stage: More predictable but larger teams doing construction, test, and
deployment activities. This stage is also decomposed into two distinct phases construction and
transition.
www.jntuworld.com
www.jntuworld.com
These four phases of lifecycle process are loosely mapped to the conceptual framework of the
spiral model is as shown in the following figure.
- In the above figure the size of the spiral corresponds to the inactivity of the project with respect
to the breadth and depth of the artifacts that have been developed.
- This inertia manifests itself in maintaining artifact consistency, regression testing,
documentation, quality analyses, and configuration control.
- Increased inertia may have little, or at least very straightforward, impact on changing any given
discrete component or activity.
- However, the reaction time for accommodating major architectural changes, major requirements
changes, major planning shifts, or major organizational perturbations clearly increases in
subsequent phases.
INCEPTION PAHSE:
The main goal of this phase is to achieve agreement among stakeholders on the life-cycle
objectives for the project.
PRIMARY OBJECTIVES
www.jntuworld.com
www.jntuworld.com
ESSENTIAL ACTIVITIES:
1) Formulating the scope of the project
2) Synthesizing the architecture
3) Planning and preparing a business case
ELABORATION PHASE
- It is the most critical phase among the four phases.
- Depending upon the scope, size, risk, and freshness of the project, an executable architecture
prototype is built in one or more iterations.
- At most of the time the process may accommodate changes, the elaboration phase activities
must ensure that the architecture, requirements, and plans are stable. And also the cost and
schedule for the completion of the development can be predicted within an acceptable range.
PRIMARY OBJECTIVES
1) Base lining the architecture as rapidly as practical
2) Base lining the vision
3) Base lining a high-reliability plan for the construction phase
4) Demonstrating that the baseline architecture will support the vision at a reasonable
cost in a reasonable time.
ESSENTIAL ACTIVITIES
1) Elaborating the vision
2) Elaborating the process and infrastructure
3) Elaborating the architecture and selecting components
CONSTRUCTION PHASE
During this phase all the remaining components and application features are integrated into
the application, and all features are thoroughly tested. Newly developed software is integrated
where ever required.
- If it is a big project then parallel construction increments are generated.
PRIMARY OBJECTIVES
www.jntuworld.com
www.jntuworld.com
In order to manage the development of a complete software system, we need to gather distinct
collections of information and is organized into artifact sets.
www.jntuworld.com
www.jntuworld.com
- Set represents a complete aspect of the system where as artifact represents interrelated
information that is developed and reviewed as a single entity.
- The artifacts of the process are organized into five sets:
1) Management 2) Requirements 3) Design
4) Implementation 5) Deployment
here the management artifacts capture the information that is necessary to synchronize
stakeholder expectations. Where as the remaining four artifacts are captured rigorous notations
that support automated analysis and browsing.
www.jntuworld.com
www.jntuworld.com
1) REQUIREMENT SET:
- The requirements set is the primary engineering context for evaluating the other three
engineering artifact sets and is the basis for test cases.
- Requirement artifacts are evaluated, assessed, and measured through a combination of
1) Analysis of consistency with the release specifications of the mgmt set.
2) Analysis of consistency between the vision and the requirement models.
3) Mapping against the design, implementation, and deployment sets to
evaluate the consistency and completeness and the semantic balance between
information in the different sets.
4) Analysis of changes between the current version of the artifacts and previous versions.
5) Subjective review of other dimensions of quality.
2) DESIGN SET:
- UML notations are used to engineer the design models for the solution.
- It contains various levels of abstraction and enough structural and behavioral information to
determine a bill of materials.
- Design model information can be clearly and, in many cases, automatically translated into a
subset of the implementation and deployment set artifacts.
The design set is evaluated, assessed, and measured through a combination of
1) Analysis of the internal consistency and quality of the design model.
2) Analysis of consistency with the requirements models.
3) Translation into implementation and deployment sets and notations to evaluate the
consistency and completeness and semantic balance between information in the
sets.
4) Analysis of changes between the current version of the design model and previous
versions.
5) Subjective review of other dimensions of quality.
3) IMPLEMENTATION SET:
www.jntuworld.com
www.jntuworld.com
- The implementation set include source code that represents the tangible implementations of
components and any executables necessary for stand-alone testing of components.
- Executables are the primitive parts that are needed to construct the end product, including
custom components, APIs of commercial components.
- Implementation set artifacts can also be translated into a subset of the deployment set.
Implementation sets are human-readable formats that are evaluated, assessed, and measured
through a combination of
1) Analysis of consistency with design models
2) Translation into deployment set notations to evaluate consistency and completeness
among artifact sets.
3) Execution of stand-alone component test cases that automatically compare expected
results with actual results.
4) Analysis of changes b/w the current version of the implementation set and previous
versions.
5) Subjective review of other dimensions of quality.
4) DEPLOYMENT SET:
- It includes user deliverables and machine language notations, executable software, and the
build scripts, installation scripts, and executable target-specific data necessary to use the
product in its target environment.
Deployment sets are evaluated, assessed, and measured through a combination of
1) Testing against the usage scenarios and quality attributes defined in the requirements
set to evaluate the consistency and completeness and the semantic balance between
information in the two sets.
2) Testing the partitioning, replication, and allocation strategies in mapping components
of the implementation set to physical resources of the deployment system.
3) Testing against the defined usage scenarios in the user manual such as installation,
user-oriented dynamic reconfiguration, mainstream usage, and anomaly management.
4) Analysis of changes b/w the current version of the deployment set and previous
versions.
5) Subjective review of other dimensions of quality.
Each artifact set uses different notations to capture the relevant artifact.
1) Management set notations (ad hoc text, graphics, use case notation) capture the plans,
process, objectives, and acceptance criteria.
www.jntuworld.com
www.jntuworld.com
2) Requirement notation (structured text and UML models) capture the engineering context
and the operational concept.
3) Implementation notations (software languages) capture the building blocks of the solution
in human-readable formats.
4) Deployment notations (executables and data files) capture the solution in machine-readable
formats.
- The structure of the information delivered to the user (testing people) is very different from
the structure of the source code implementation.
- Engineering decisions that have impact on the quality of the deployment set but are relatively
incomprehensible in the design and implementation sets include:
1) Dynamically reconfigurable parameters such as buffer sizes, color palettes, number of
servers, number of simultaneous clients, data files, run-time parameters.
2) Effects of compiler/link optimizations such as space optimization versus speed
optimization.
3) Performance under certain allocation strategies such as centralized versus distributed,
primary and shadow threads, dynamic load balancing.
4) Virtual machine constraints such as file descriptors, garbage collection, heap size,
maximum record size, disk file rotations.
5) Process-level concurrency issues such as deadlock and race condition.
www.jntuworld.com
www.jntuworld.com
- Each state of development represents a certain amount of precision in the final system
description.
- Early in the lifecycle, precision is low and the representation is generally high. Eventually,
the precision of representation is high and everything is specified in full detail.
- At any point in the lifecycle, the five sets will be in different states of completeness.
However, they should be at compatible levels of detail and reasonably traceable to one another.
- Performing detailed traceability and consistency analyses early in the life cycle i.e. when
precision is low and changes are frequent usually has a low ROI.
Inception phase: It mainly focuses on critical requirements, usually with a secondary focus on
an initial deployment view, little implementation and high-level focus on the design
architecture but not on design detail.
Elaboration phase: It include generation of an executable prototype, involves subsets of
development in all four sets. A portion of all four sets must be evolved to some level of
completion before an architecture baseline can be established.
Construction: Its main focus on design and implementation. In the early stages the main focus
is on the depth of the design artifacts. Later, in construction, realizing the design in source code
and individually tested components. This stage should drive the requirements, design, and
implementation sets almost to completion. Substantial work is also done on the deployment
www.jntuworld.com
www.jntuworld.com
set, at least to test one or a few instances of the programmed system through alpha or beta
releases.
Transition: The main focus is on achieving consistency and completeness of the deployment
set in the context of another set. Residual defects are resolved, and feedback from alpha, beta,
and system testing is incorporated.
TEST ARTIFACTS:
Testing refers to the explicit evaluation through execution of deployment set
components under a controlled scenario with an expected and objective outcome.
- What ever the document-driven approach that was applied to software development is also
followed by the software testing people.
- Development teams built requirements documents, top-level design documents, and detailed
design documents before constructing any source files or executable files.
- In the same way test teams built system test plan documents, unit test plan documents, and
unit test procedure documents before building any test drivers, stubs, or instrumentation.
- This document-driven approach caused the same problems for the test activities that it did for
the development activities.
- One of the truly tasteful belief of a modern process is to use exactly the same sets, notations,
and artifacts for the products of test activities as are used for product development.
- The test artifacts must be developed concurrently with the product from inception through
deployment. i.e. Testing a full-life-cycle activity, not a late life-cycle activity.
- The test artifacts are communicated, engineered, and developed within the same artifact sets
as the developed product.
- The test artifacts are implemented in programmable and repeatable formats as software
programs.
- The test artifacts are documented in the same way that the product is documented.
- Developers of the test artifacts use the same tools, techniques, and training as the software
engineers developing the product.
- Testing is only one aspect of the evaluation workflow. Other aspects include inspection,
analysis, and demonstration.
- The success of test can be determined by comparing the expected outcome to the actual
outcome with well-defined mathematical precision.
MANAGEMENT ARTIFACTS:
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
:
• Managing change is one of the fundamental primitives of an iterative development process.
• This flexibility increases the content, quality, and number of iterations that a project can
achieve within a given schedule.
• Once software is placed in a controlled baseline, all changes must be formally tracked and
managed.
• Most of the change management activities can be automated by automating data entry and
maintaining change records online.
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
UNIT-4
Model-Based Software Architectures
INTRODUCTION:
• Software architecture is the central design problem of a complex software system in the same way an
architecture is the software system design.
• The ultimate goal of the engineering stage is to converge on a stable architecture baseline.
• Architecture is not a paper document. It is a collection of information across all the engineering sets.
• Architectures are described by extracting the essential information from the design models.
• A model is a relatively independent abstraction of a system.
• A view is a subset of a model that abstracts a specific, relevant perspective.
• The most critical and technical product of a software project is its architecture
1. An architecture ( the intangible design concept) is the design of software system it includes all
engineering necessary to specify a complete bill of materials. Significant make or buy decisions
are resolved, and all custom components are elaborated so that individual component costs and
construction/assembly costs can be determined with confidence.
2. An architecture baseline (the tangible artifacts) is a slice of information across the engineering
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
artifact sets sufficient to satisfy all stakeholders that the vision (function and quality) can be
achieved within the parameters of the business case (cost, profit, time, technology, people).
3. An architectural description is an organized subset of information extracted from the design set
model's. It explains how the intangible concept is realized in the tangible artifacts.
The number of views and level of detail in each view can vary widely. For example the architecture of
the software architecture of a small development tool.
There is a close relationship between software architecture and the modern software development
process because of the following reasons:
www.jntuworld.com
www.jntuworld.com
1. A stable software architecture is nothing but a project milestone where critical make/buy decisions should have
been resolved. The life-cycle represents a transition from the engineering stage of a project to the production
stage.
2. Architecture representation provide a basis for balancing the trade-offs between the problem space
(requirements and constraints) and the solution space (the operational product).
3. The architecture and process encapsulate many of the important communications among individuals, teams,
organizations, and stakeholders.
4. Poor architecture and immature process are often given as reasons for project failure.
5. In order to proper planning, a mature process, understanding the primary requirements and demonstrable
architecture are important fundamentals.
6. Architecture development and process definition are the intellectual steps that map the problem to a solution
without violating the constraints; they require human innovation and cannot be automated.
• Software architecture include the structure of software systems, their behavior, and the patterns that
guide these elements, their collaborations, and their composition.
• An architecture framework is defined in terms of views is the abstraction of the UML models in the
design set. Where as an architecture view is an abstraction of the design model, include full breadth and
depth of information.
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
1) Design: describes architecturally significant structures and functions of the design model.
2) Process: describes concurrency and control thread relationships among the design, component,
and deployment views.
The design view is probably necessary in every system; the other three views can be added to deal
with the complexity of the system at hand.
The requirements set may include UML models describing the problem space.
www.jntuworld.com
www.jntuworld.com
The design set include all UML design models describing the solution space.
• The design, process, and use case models provide for visualization of the logical and behavioral
aspect of the design.
2. The design view describes the architecturally significant elements of the design model. It is modeled
statistically by using class and object diagrams, and dynamically using any of the UML behavioral
diagrams.
3. The process view addresses the run-time collaboration issues involved in executing the architecture on a
distributed deployment model, including logical software topology, inter process communication, and state
mgmt. it is modeled statistically using deployment diagrams, and dynamically using any of the UML
behavioral diagrams.
4. The component view describes the architecturally significant elements of the implementation set. It is
modeled statistically using component diagrams, and dynamically using any of the UML behavioral
diagrams.
The deployment view addresses the executable realization of the system, including the allocation of logical
processes in the distributed view to physical resources of the deployment network. It is modeled statistically
using deployment diagrams, and dynamically using any of UML behavioral diagrams.
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
Architecture descriptions take on different forms and styles in different organizations and domains. At any
given time, an architecture requires a subset of artifacts in engineering set.
- An architecture baseline is defined as a balanced subset of information across all sets, whereas an
architecture description is completely encapsulated within the design set.
1) Requirements 2) Design
3) Implementation 4) Deployment
www.jntuworld.com
www.jntuworld.com
• But the simplistic activity sequences are not realistic why because it include many teams, making
progress on many artifacts that must be synchronized, cross-checked, homogenized, merged and
integrated.
• In order to manage complex software’s the workflow of the software process is to be changed that is
distributed.
• Modern software process avoids the life-cycle phases like inception, elaboration, construction and
transition. It tells only the state of the project rather than a sequence of activities in each phase.
7) Deployment
• These activities are performed concurrently, with varying levels of effort and emphasis as a project
progresses through the life cycle.
The term workflow means a thread of cohesive and mostly sequential activities.
Management workflow: controlling the process and ensuring win conditions for all stakeholders.
Environment workflow: automating the process and evolving the maintenance environment.
Requirements workflow: analyzing the problem space and evolving the requirements artifacts.
Design workflow: modeling the solution and evolving the architecture and design artifacts.
Implementation workflow: programming the components and evolving the implementation and
deployment artifacts.
www.jntuworld.com
www.jntuworld.com
2. Iterative life-cycle process: From the above figure each phase describes at least two iterations
of each workflow. This default is intended to be descriptive, not prescriptive. Some projects may
require only one iteration in a phase; other may require several iterations. The point here is that
the activities and artifacts of any given workflow may require more than one pass to achieve
adequate results.
www.jntuworld.com
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
ITERATION WORKFLOWS:
An iteration consists of a set of activities in various proportions. An iteration is a set of allocated scenarios.
The components that are needed in order to implement those scenarios are developed and integrated with the
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com
Management: Planning to determine the content of the release and develop the detailed plan for the iteration
and assigning the tasks, related work to the development team.
Environment: Evolving the software change order database to reflect all new baselines and changes to
existing baseline for all product, test, and environment components.
Requirements: Analyzing the baseline plan, the baseline architecture, and the baseline requirements set
artifacts to fully elaborate the use cases to be to be demonstrated at the end of this iteration
and their evolution criteria.
Updating any requirements set artifacts to reflect changes needed by results of
this iteration’s engine activities.
Design: Evolving the baseline architecture and the baseline design set artifacts to elaborate fully the design
model and test model components necessary to demonstrate at the end of this iteration.
Updating design set artifacts to reflect changes needed by the results of this iteration’s
engine activities.
Implementation: Developing or acquiring any new components, and enhancing or modifying any existing
components, to demonstrate the evolution criteria allocated to this iteration.
Integrating and testing all new and modified components with existing baselines
(previous versions).
Assessment: Evaluating the results of the iteration; identifying any rework required and determining whether
it should be performed before development of this release or allocated to the next release and
assessing results to improve the basis of the subsequent iteration’s plan.
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
Deployment: Transitioning the release either to an external organization to internal closure by conducting a
post-mortem so that lessons learned can be captured and reflected in the next iteration.
- Iterations in the inception and elaboration phases focus on management, requirement and design activities.
- Iterations in the construction phase focus on design, implementation and assessment activities.
- Iterations in the transition phase focus on assessment and deployment
www.jntuworld.com
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
!#"$%"& '()* '+(),-.
/01"/" 23/(4
•
5 4/
$%67."$%"0-89$%: 5 /(;$
/<$%
-(/=<($%(>/?/
-;@4A-BC%DFE, 55 $%(;1
/G& H("/?-I& H$%$/'$% 5
/(J 55 ;$/(/K"JG89(/'(L
/;LL/( 5 -A
• M'N-OQP(R=STU0VWXYU[ZN-O]\Y^/ZW;X/U[Z_ZSX/`7aYTN-bQUcPJPU[Sd>ZeYSfYU.`YW OQO
UTU[X'P?d>N-PW fgS_P%WNgX/Zh
• M'N-OQP(R=STUaYTN-O
UZZWNgXYSV;Z,WX\YN'P%ePmYaYU[Z,N-ONgT+wqSXYWSPW;NYXYZ,STUd>N-PW fYSPU`\'m
c%STU[U[T.wgTN'R.Pe9tbvNY\
ZSPWZ*O
ScPWNgX'tqSXY`HPe/U0Nga/aYNgT+P^YX/W P(mHP%N@d1Sx-U.SG`YW OO~U[TU[X/cU[z
'#gF(H?#g,sHs#Y0
F#
! nqU[Z_a/NgXYZW\YWVW P(mHO
NgTJa/TNYcU[Z_Z]`/UO
WXYW PW;NYXLSX/`Ld>SWX9P%U[X/SXYcU[h%O
NgTJUSd1aYVU?PeYUGaYTNgcU[ZZYO~NYTI`/UfgU[VNgaYWX9w
.ZN-OPR=STU.W;Z`YW OO~U[TU[X9PJO
TNgdPe/U0a/TNgc%UZZ^YZU[`HPN@`YUfYUVNga m-.SaYaYVWcSPWNgX/z
#! psT+wqSX/W;SPWNgX/SV7TNgVUZd>Sml\YUO~^YV O
W;VVU[`¡\'mlS¢Z_WX9wqVU£WXY`/W fYW`Y^/SVLNgTZ_UfYU[TSV0`YW OQO
U[TU[X'PPUSd>Zvt
`/U[aYU[XY`/W;X9w:NgXHPe/U0ZcSVU.N-OgPeYU.NgT+wqSX/W_S_P%WNgX/h $ %
www.jntuworld.com
www.jntuworld.com
& ' (
§
H
6
!s
! "IeYWZPUSd!WZ@TU[ZaYNgX/ZW;\/VU1O~NgT#UceYSX'wqUN'O7WX'O
NgTd>SPWNgX)SXY`aYTNgcU[ZZKwq^YW`/SXYcU\/N-PePN)NgT<O~TNgd
aYTN-bQU[cP<a/TScPW PWNgX/UTZz
WXYUOQO
U[cPW fYU.\Y^YTU[S^Yc%TScmgz
'&(
)I**+,*¢
- ]!s
www.jntuworld.com
www.jntuworld.com
! r P W;ZkTU[ZaYNgX/Z_W\/V;UO
NgT S^'PNgd1SPW;X9w Pe/UjNgTwgSXYWSPWNgXvZkaYTNgcU[ZZvtd>SW;X9PSWXYWX'w¢PeYUjNgT+wqSX/W_S_P%WNgX*Z
ZvPSX/`YST`U[X9fgWTNgXYd>U[X9PtIPTSW;X/WX'waYTN-bvU[cPZ?PN^/ZULP%e/U U[X'fYW;TNgX/d>U[X'P(tSXY`d>SWX9P%SW;X/WX'wNgT+wqSX/W;SPWNgX i
R=W`YU.TU^/ZS\YVU.SZZ_UPZz
#! "INYNgVZ*t?P%U[ce/XYW|Y^/U[Z=SX/`PTSW;X/WX'wCcSX3\YUWd>aYVU[d>U[X'PU[`3UOQO
UcP%W fYU[V m't#NgX/V mkW O:M$##%¤¡WZ=TU[Z_a/NgXYZW\YVU O~NgT
Z^Ya/aYNgT+PW;X9w:SX/`7d>NgX/W PNgTWX'wPe/U0ZvPSXY`/ST`7U[X'fYW;TNgX/d>U[X'Pz
' $' ' ]
& %
* + *
cNgTaYNYTSPU.WX'O~NYTd>S_P%WNgXLZ*mYZvPUd1ZWX'PUwqTSPWNgXYz
#! { TN-O
U[Z_ZWNgX/SV>`YUfYU[V;NYaYd>U[X'Ph "ITSWX/W;X9w cSd>a9ta/U[TZNgX/XYU[V1TU[cT^/W P%WX9wtaYU[TZNgXYX/UV=Zx-WVV1`/SPS\YSZU
d>SWX9P%U[X/SXYcU[z
,-. /0 10 2
www.jntuworld.com
www.jntuworld.com
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
#! "IeYU `/UfgU[VNgaYd1UX9P
PUSd N-R=X/Z PeYU cNYd>aYNgX/U[X'P¡cNYXYZvPT^/cPW;NYX SXY` d>SWX'PU[XYSXYcU ScPW fYW PW;U[Zz "IeYU
SZZU[Z_Zd>U[X9PJPU[SdjWZZU[aYSTSPUFO~TNgdj`YUfYU[V;NYaYd>U[X'Pz
www.jntuworld.com
www.jntuworld.com
NYZ*PGaYTN-bvU[cPZSTU>N'fgU[TFTUZvPTW;cP%U[`/zIM'ce/U`/^YVUtcNgZvPZ*tyO
^YXYcP%WNgX/SVW Pm'tSXY`|/^YSVW P(m,Ua/U[cPSPW;NYXYZKSTU=eYW wqe/V m
WX'PU[TTU[VSPU`LSXY`7TU[|Y^/W;TU.cNgX'PWXY^/Ng^YZXYUwgN-PW;S_P%WNgXLSd>NgX9w:d>^YV PWaYVU.Z*PSx'U[eYNgV`/UTZqR1e/N@eYSfYU.`YW OQO
UTU[X'PIwqNgSV;Zz
#! M'N-OQP(R=STU7d>SX/SwqU[d>U[X9PPUSdoWZ<TU[Z_a/NgXYZW\YVUHO
NgT}aYVSX/XYWX'w#PeYULUOO~NgT+P(tIcNgX/`Y^YcP%WNgXKPe/ULaYVSX9tISXY`@S`YSa9P%WX9w
PeYU.aYVSXHPN@ce/SX'wgU[ZWXHPeYU.^YX/`YU[TZ*PSX/`YWX'w@N-OgPeYU.TU[|/^YWTU[d>U[X9P%ZNgTJ`YU[ZW wgXYz
(!2 * 0
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
! r PWZTU[ZaYNgX/Z_W\/V;U<O
NgT[Pe/U.STce/W P%U[cP^/TU#SX/`PN7ZaYU[cW OQmLScNYd>aYVUPU.\/WV;V9N-Od>SPU[TWSV
O
NgT[Pe/U.ZN-OP(R1STU#SX/`PeYU
U[X'wgW;X/U[UTWX'w X/Uc%UZZST+m£PN d>Sx'U ZW wqXYW O
W;c%SX'Pd>Sx'U-\/^'m£PTS`YU i N'OQO~ZZN PeYSPc^YZvPNgd cNYd>aYNgX/U[X'PZ STU
U[VS\YNgTSPU[`HPNKPeYU.UPU[X'PIPeYSP?cNgX/ZvP%T^YcP%WNgX-SZZ_U[d>\/V m@cNgZvPZSTU.eYW wgeYV m@a/TU[`YWcPS\/VUz
)! "Ie/WZPU[Sd W;Z SVZN TU[ZaYNgX/Z_W\/V;U¡O~NgTZ*mYZvPUd i VUfgU[V|/^YSVW P(m Z^Yce SZ TU[VW;S\YWVW P(m'tCaYU[T+O~NgTd>SX/cUtCSX/`
d>SWX9P%SW;X/S\YWVW P(mgz
www.jntuworld.com
www.jntuworld.com
& &
3 + *
!. . Z_a/U[cWSVW;ZvPZJR=W Pe§`/UP%SW;VU[`@x'XYN-R=VU[`'wqU0N-OcNgd1d>U[TcWSV-cNgd>a/NgXYU[X9P%ZcU[X'PTSV_PN:S
ZvmgZvPU[d *ZSTceYW PU[cP^YTU[z
Ng\9bvU[cPZNgX7SGXYUP(R=NgTx-z
4 !2 * 0
* 6 * % 7 6 &
* +
www.jntuworld.com
www.jntuworld.com
* * 6 6
+
-8 ' 9 /0 10 2
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
.-22 0 :0
www.jntuworld.com
www.jntuworld.com
"!
# $ %
# &' (! )*+ ,
#-+*
(. -*
/ 0
#
1 2
-' 3 45 (.
6' ' (.
7 2
-869$:
7; 6
*+*!/ 4<!
=%>
7 ' ?'6@ =>A9$B >?*+!3C
ED
GFC H (.! *.I+* J
#
KL
7
# K M 2+%>;
*
C N )+*
!3 '
O J <!
7
7; (. '* 6 2
' * ,*+3P / Q = ,' -+
D
RS. ? / ! ='
T 3 U$ (. 2/ 5 (. ?*+3P / 3V (.
+ (.
# T W0
* 'X . ,+
!* *+3P C DFCY
CZ* 2 6!/
# ; 3'7%.!
[
3 +\Z 2 (6!/
7 ;
3+ ( 3 (D
^]U! ='
# ? (. _ `+* 3 2 0*
3.
# G
# + 2 (6!3C (!
3!*+
# ? .
%
! ;+P / 4
6@ * O
7-+ 3 4C
Q (.
#
# 2 ' (. -
'/%" D
XF/%
7 . G * 3 3
#+*
7 N (. a'
#3 3
#+
X W"6!3
=
3 b
$ * 3 c+P / 3D
& % & $ h
!: SX7NYTwgSXYWSPWNgXvZa/NgVW;c%W;U[Zvtya/TNgc%U`/^YTU[Z*tqSXY`0aYTScPWcU[ZqO
NgTId>SXYS_wqWX'w7SZN-OQP(R=STU i WX'PU[XYZW fgU
9-
$%(
/
VWXYU.N-O]\Y^/ZW;X/U[Z_Zz "Ie/U0S^'PNgd>SPWNgX7Z^/aYaYNYTPIO~NgT[PeYWZVUfYUV'WZc%SVV;U[`7SX .
!: Sa/TN'bvU[cPGPU[Sd vZ@aYNgVWcWU[Z*tKaYTNgcU[`/^YTUZvtKSXY`aYTScPWcU[ZKO~NYT.SceYWUfgWX9w3SXST+PW O
ScP§N-OPeYU
(/
ZN-OQP(R=STU0a/TNYcU[Z_Zz "Ie/U0S^'PNgd>SPWNgX7Z^/aYaYNYTPIO~NgT[wqU[XYU[TSPWX'w:SXLSTPW O~ScP<WZqwqU[XYU[TSVV m@cSVVU[`7S .
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com
9 6 * 3 *
"! M-N-OP(R1STU.cNgZvP?UZvPWd>SPWNgXHPNgNgVZSXY`qM]P%NYNgVZSTU.^YZUO~^YV~O~NYTwqU[X/UTSPWX'wPe/U0a/V;SXYXYWX9w:ST+P%W O
ScPZz
#! -NgTJd>SX/SwqWX'w@SwqSWX/Z*P?aYVSX9tR=NgTxO
VN-R d>SXYS_wqU[d>U[X'PyPNgNgVZ]SXY`0SZN-OQP(R=STU#aYTN-bvU[cPcNYX'PTNYV'a/SXYU[V
PeYSPcSX
i
d>SWX9P%SW;XLSX7NgX V WXYUFfgU[TZ_WNgXLN-OgPeYU.ZvP%S_P%^/ZSZ_ZU[ZZd>U[X'P?STU.S`9fgSX9PSwqU[Ng^/Z_z
www.jntuworld.com
www.jntuworld.com
=)nqSPe/UTPeYSX¡O
Ngc^YZ
NYX cNYXYZWZ*PU[XYcm-tcNgd>a/VUPU[XYU[ZZvt3SXY`£PTSc%US\YWVW P(m N-O Wd>d>S_P%^/TU TU[|Y^/WTU[d>U[X'PZ
ZaYU[cW O~WcS_P%WNgX/ZvtyaYTN-bQUcP<X/UU[`HPNKO
Ngc^YZNgX7SceYWUfgWX9wPeYU.aYTNgaYU[T Za/Uc%W O
WcSPWNgX7N-OgPe/U0a/TN-bQU[cPIfgWZWNgXYz
0 4 6
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
#! r P?W;ZSVZN@XYU[U[`YU[`HPN@Z^Ya/aYNgT+PJPe/U0`/Ua/VN-mgd1UX9PJR=NgTx~O~VN-RP%e/TNY^'wqe/Ng^'PIPeYU.VW O
U0cmgcVU[z
>- ,-. - 8 :-
www.jntuworld.com
www.jntuworld.com
4 - / -- / Z_U[UFO~W wqh[¨¥ i ¥
"! -W wgh¨/¥ i ¥ ZeYN-R=Z ZNgd>U N-OPe/U Wd>a/NgT+P%SX'PCPTSX/ZScPWNgXYZ \YUP(R=U[UX WX'O~NYTd>S_P%WNgX TU[a/NgZW PNgTWU[Z_z "IeYU
S^9P%NYd>SPU[`.PTSXYZVSPW;NYX1N-O<`YU[ZW wgX1d>NY`YU[VZ}PN>ZNg^/Tc%U§c%Ng`YU:SX/`1`YU[ZW wqX§d>Ng`/UVZ PN1a/TNYcU[Z_ZFd1Ng`YU[VZFSTUKO~SWTV m
R=U[V;V'U[ZvP%S\YVWZ_e/U[`Yz
www.jntuworld.com
www.jntuworld.com
.> 0 / - : 0 0 / -: -
! r XcNgX'fYU[X'PWNgXYSVIZN-OP(R1STUd>SX/SwqU[d>U[X9PLa/TNYcU[Z_Zvt<\YSZU[VW;X/UcNgX'O
W wq^YTSPWNgXd1SXYSwgU[d>U[X'PsPUc%eYXYW|/^YU[Z?O~NgT
PU[ceYX/W;c%SV-STPW O~ScP%ZqR=U[TU.aYTU[`YNgd>WX/SX'PV m@SGVSPU.V;W O
U i cmYcVU0ScP%W fYW PmYz
www.jntuworld.com
www.jntuworld.com
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
.' . *
]
rP W;Z S X/Sd>U[` cNgVVUcP%WNgX N-O ZN-OPR=STU cNYd>aYNgX/U[X'PZ SX/` Z^YaYa/NgT+P%WX9w
`YNYc^Yd>U[X9P%S_P%WNgXPeYS_PCWZ3Z^Y\'bQU[cPPNlceYSX9wqU£d1SXYSwgU[d>U[X'PCSX/`jWZ^Ya9wqTS`YU[`9t,d>SWX'PSWXYU[`9t@P%U[ZvPU[`'t,SX/`
Ng\/Z_NYV;U[ZcU[`7SZSG^YX/W P%z
www.jntuworld.com
www.jntuworld.com
- "IeYU[TU.STUswgU[XYU[TSV;V mHPR=N@cVSZZU[ZN'O]\YSZU[VWXYU[ZhUPU[TX/SV'aYTNg`Y^/cP<TU[VUSZ_U[ZSXY`LW;X9PUTXYSVPU[ZvP%WX9w:TU[VU[SZU[Z_z
?U[XYU[TSVV m-tqPeYTU[U1VUfgU[VZKN'O\YSZU[VW;X/U1TU[V;U[SZU[ZKSTU=TU[|Y^/WTU[`LO~NYT<d>NgZvPGZvmYZvP%U[d>ZhId>SbQNgT ; td>WX/NgT ;tSX/`
WX'PU[TWd Qz
¤d>SbQNgTTU[VUSZ_U0TU[a/TU[ZU[X'PZ?S#XYUR wqU[XYU[TSPW;NYX@N-OqPeYULa/TNY`Y^YcPFNgTa/TN'bvU[cP(tR=eYWVU.d>WXYNgTJTU[VU[SZU0TU[aYTUZU[X'PZ
PeYU3ZSd1U3\YSZWc,aYTNg`Y^/cP\Y^9P7R=W P%eCU[XYe/SXYc%U`O
US_P%^/TU[Zvt0aYU[T+O~NgTd>SX/cUtLNYT@|Y^YSV;W P(mYz eYU[TU3SZ>SXkW;X9PUTWd
TUVU[SZU.cNgTTU[ZaYNgX/`YZqPN@SG`YUfgU[VNga/d>U[X'PSV'cNgX'O
W wq^YTSPWNgXHPeYS_P<WZW;X9PUX/`YU[`HPN@\YUFPU[d>aYNgTST+mgz
")
6 ? ) geYSX'wqU[Z PeYS_PSTU@X/N-PSLa/ST+PN-OJPe/U@N-PeYU[T]cSPUwqNgTWUZz#%Sd>a/V;U[ZFWXYc%V;^/`YU@`/Ngc^Yd1UX9PSPW;NYX
NgX/V m7NgT S?fYU[TZWNgX7^/a'wgTS`/UsPN@cNYd>d>U[Tc%W;SV-cNYd>aYNgX/U[X'PZz
.' .
. q*
*%
¤
=WZ?S<PU[Sd¡N-OaYU[Nga/VUPeYSPJO~^/XYcPWNgX@SZyP%e/UL`/Uc%W;ZWNgX@S^9PeYNgTW Pm
NgXHPe/U0cNYX'PU[X'P?N-O]cNgX9O~W wq^/TS_P%WNgXL\YSZU[VW;X/U[Z_z
www.jntuworld.com
www.jntuworld.com
#P%Sx-U7ScPW;NYXGPe/TNg^9wqe:\YNYST`:d>U[UPWX'wqZvtJNgX i VWXYU7`/W;ZvPTW;\/^'PWNgX:SXY`:SwgTU[U[d>U[X'Pz r PF`YUPU[Td1W;X/U[ZIPeYUsO~SPULN'O
Mgpsz
!A B+ "IeYU>TU[Z_a/NgXYZW\YVU>a/U[TZNgXSX/SV mgU[Zvt?Wd>a/VUd1UX9PZ*tSX/`7P%U[ZvPZS§Z_NYV;^9PW;NYX@PN,ZSPW;ZvOm@P%e/U>Mgpsz
"IeYWZqPSZx-ZWXYcV^Y`/U[Z^/aY`YS_P%WX9w:`YNgc%^Yd>U[X'PSPWNgX9tyTU[VU[SZU0X/N-PU[Z*tqSXY`7Z^/\Yd>W P(PW;X9w:XYUR M Yp vZvtyW O]XYU[cU[ZZSTmYz
<a/NgX Sce/W;UfYWX'w,cNgd1aYVUP%WNgX9teYU=cNgd>a/V;UPU[ZKTU[Z_NYV;^9PW;NYX Z_U[cPWNgX N-O}Pe/U=MgpSXY`>Z^/\Yd>W PZHW P
PNKPeYU.W;X/`YU[aYU[X/`YU[X'PIPUZvPIPUSdO~NgTJSZZ_U[ZZd>U[X'Pz
! A. c%NgXYc^/T PeYSP
B+ )e/U[X:PeYU `/UfgU[VNgaYd1UX9P.NgT+wqSX/W;SPWNgX9t<WXY`/U[aYU[XY`/UX9P<PU[Z*PGNgTwgSXYWSPWNgX'tSX/`
PeYU.M Yp)WZTU[ZNgV fgU[`9tyW P<WZqP%TSX/Z_W PWNgXYU[`HPN@SGcVNgZU[`7ZvPSP^YZz
.[]sHIq?]g
"Ie/U>O~^YX/`YSd1UX9PSV]aYTNgcU[ZZGO
NgT.cNgX'PTNgVVW;X9wPeYU ZN-OPR=STU `YUfYUVNga/d>U[X'P=SX/`)d>SW;X9PUX/SXYc%UScPW fgW PWUZ@STU
aYU[T+O~NgTd>U[`7\9m@Mgpsz I" eYU.M Yp)WZSZZ_W wgXYU[`7NgX/U0N-OYP%e/UsO
NgVVN-R=W;X9w:ZvPSPUZ\'mHPeYU qz
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
!A z
B+¤ aYTNgaYNYZ_U[`7c%eYSX9wqU.W;ZNg^9P%VWXYU[`7SXY`7Z^Y\/d>W P(P%U[`HPNKPeYU q
ceYU[cx'aYNgWX9P%Zvtyd1UPTWcZvtySXY`LZ*PSX/`YST`YZN-O]a/U[TO
NgTd1SXYcU
www.jntuworld.com
www.jntuworld.com
"=
! - & gSa9P%^/TU[Z.SXWX'fYU[X'PNgT+mN-O?P%NYNgVZ_z"IeYU[ZU:PNgNgVZ.STU:PeYU,S^9P%NYd>SPU[`
\Y^/WV;`/WX'w:\/V;NYcx-ZqO~TNgdR=eYWceLaYTN-bvU[cP?U[X'fYWTNgX/d>U[X'P?cSX7\/U0c%NgX'O
W wg^YTU[`LUOQO
W;c%W;U[X9P%V mLSXY`0U[cNgXYNYd>WcSVV mgz-M-Ngd1U.N'O
PeYUFP(mga/W;c%SV-c%Ngd>aYNYXYU[X'PZN-O]SX7NYTwgSXYWSPWNgXvZS^9PNgd>SPWNgX7\/^YWV`YWX'w:\/VNgcx'ZSTU[h
! MPSX/`YST`YWU[`HPNgNgVZZU[VU[cPW;NYXYZvtR=eYWce7a/TNYd>N-PU0c%Ngd>d>NgXR1NYTx~O~VN-R=ZSXY`7SGe/W wqeYU[TJnqprNgXHPTSW;X/WX'wqz
"! M~PSXY`/ST`@XYN-PSPWNgXYZyO~NgTJST+P%W O
ScPZvtyZ^Yce7SZ O~NgTJSVV-`/UZW wqXLd>Ng`YU[VZNgT¤<`YSO
NgT SVV'c^YZvPNgd i `YUfYUVNga/U[`
ST+PW O
ScPZz
#!"INgNgV'SP(P%SceYd>U[X9P%ZZ^YceLSZUWZvPW;X9w:ST+PW O
ScPIPUd1aYVSPU[ZNgTJc^YZvPNgd>WSPWNgXYZz
2 0 ;-> '4 - - 8 :- 2
U[X'wgW;X/U[UTWX'w)ST+PW O
ScPZz
"IeYUmSVZN)Z^Ya/aYNgT+P:\/UP(PU[TGcNgd>d1^YXYWcS_P%WNgX 7O
U[U`/\YSc%x-z
"IeYUmWXYc%V;^/`YUaYU[NgaYVU:O~TNgd
UPUTXYSV-SwgU[XYcWU[ZyR=W PeHPeYU.eYU[Va7N-OgPe/UsO
NgVV;N'R1WX9wR=SmgZh
\$"IeYWT` i a/STP(m7d>SWX'PU[XYSX/cU.cNgX'PTScPNgTZ
r XY`/Ua/U[XY`YU[X9PJfYU[TW O~WcS_P%WNgXLSXY`HfYSVW`YSPWNgX7c%NgX'PTScPNgTZ
c g
`YnqUa/TU[ZU[X'PSPW fgU[ZN-O]TUwq^YVSPNgT+m@S_wqU[XYcWU[Z
2 "
www.jntuworld.com
www.jntuworld.com
"Ie/UZU.SVVN-R£SccU[ZZyPN@`YUfYU[V;NYaYd>U[X'P?U[X'fYWTNgX/d>U[X'P?TU[ZNg^/TcU[Zz
i MPSx'U[eYNgV`/UTZ£U[X'fYWTNYXYd>U[X'PZ£^/ZU ZSd>U NgX i VWXYUoPNgNYV;Zvt `YS_P%S_tSXY` TU[a/NgTPZ£^/ZU` \9m `YUfYUVNga/d>U[X'P
NgT+wqSX/W_S_P%WNgXP%N@d1SXYSwgU0SXY`7d>NYXYW PNgT a/TN-bQU[cP?SXY`7`/WZ_a/NgZWX'wR=W Pe -TU[`Y^/cWX'w:a/SaYU[TJSTPW O~ScPZ_z
0 &
UR
¨ <W Z_NYd>U0STPW O~ScP%Zd>NgTU.USZ_WV mYz
fgWZ^YSV-d>NY`YU[VZ*tqZ_NY^YTcU0c%Ng`YU[z
¥ -
gr X/`YU[aYU[XY`/U[X'P?SZZ_U[ZZWX'w:N-O}UfYNgV fYW;X9w:ST+PW O
ScPZz
U[VW fgU[T+m@N-O}aYSa/UTJ`YNgc%^Yd>U[X'PZU[V;U[cPTNgXYWcSV;V mHP%N@ZSfYUFP%Wd>U-cNgZvPZz
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com
"!$#% '&()
*!) +, -!./(0#% !12!.+,!.3('
.45
!67789:+,
) (';
79<!$#=>?
@ ,!$!.4!.A7 45/3 45*!B*CDE+,874FG!.A+1 !.H+3!18 IE3J!1K
L .45*4F7M6!. 8*45/ !. !1 & ,&()
=H*!.K
N 8 +,4!.A+,
=)(,;H !$CG#= !./+,
) !B7G!.+, PO 87K
L M4F79<!$#=>A)394537Q /O8 ( !3CG!.4PB (2!.38*45/J!.38
!.
+,*45A
.45
!.K
! R
8*!.
.!.4!. 9& / /+,+,8!.4S+!. & !.H5!.384G!.A87A9
N 8 T!13)/4P H34F>/!.,453.!./&
!.K
R /+,+183.!.
78
!9-) 453H76.!.K
&
Z\ 4!P*!.D!1 O 8( !$CS9!1 ,&( &*4F79"!$#%3) 8+!.K
R B75E[HJ!.
.!.4!. +,k! /7+,8 (20:+,
)(,!.P*4!.A)38 +!
l !./+174F>+,+,83+C/9&H!.P
=HK
' () * (
L M4F>/+,+,8 !1AJ!1
!19!.A)394537 K
m J!. 4!. O 8( !$CS9-79<!$#=>A)38 +!.K
n (+,8 (.!.P*4!.A+,J!/7+, 8(A9-W79<!3#%3A)38 +!.K
+ , ',-, ,. , '
www.jntuworld.com
www.jntuworld.com
Z !.=
=3
79"!$#%3% '&()
*!) +1H7!.]3%7,&H=+,3%
,!.3P+1 K] ]
,!.+,^3%+1(P> 7 E
*!1D!$#%S+,.!.,457?
>.4H
=H*!Z P+1.!.
L
8( !$CSZ +, !1
R P+1.!.]d
,!13+VA%4538) 9S
='!.3+,J_W)39&F8 J!. 4gD!.i79"!$#%3i)39aJ+!.K 7
='!.3+,Q>A3 &GE3
!.A79"!$#%3*45K
. /
l MG)39453
9#%3MD) H E
/&H!.
8*45,!./+,J!/,;H) H !.83 +1J!+183/9&H!.
!1 "E*4F^!1
*C
+,
)37 H(+, 4H69&H!.
0 1
3 4 $ / $ /5 $ 6% '7 5 ( $ 5 & $ 5
5 / 5 5'
www.jntuworld.com
www.jntuworld.com
. ; ; < ,. , ; '
3 4 /
G&38>+!. & !.P !. !1 &/,&(P)
!I)39aJ+!I+,FB/
=H> 8 FBC] ,E4%
) ( H]J!1
!1S[!.D#%3M%]B*aJ+!. &S
=H> 8 ,_H!.!.3+,M4%)394537.45>P J!
!. .!) (K
!#"%$'&)(+*-,./01.23(1*4(657.98+$;:-,$;<0-,$,=
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
>?@AB#
C
AEDFGIH:+*1J1$'/CK10E,$'L323*1$;<810+*1M+$;&)0+*101M+$'&)$'*1.=
AB
N
#AEDH+GC,O(-PQ$*+$'J6RS.9$,.T8+(1:+/U,V$W1$'<:1.9$'J6RS$'XE0+L3:10+.923(1*
</
23.9$'/2304&!$.=
ABY#AB
C
A+H+(+&PQL3$'.923(+*Z([5\&!23L3$,.(1*1$,=
20 45? + ] T
8 / 9$ L 78
!W9-!1 =+,k!,;H) !.8 DGO8 !.3848*!!.%)39a"H+3!
( EA+C+,(20:) &*4F
.45
!+,*!.(K
T
b)8 ) 7 E>+,(
= !.3P*4 +,bB >+,,&bBC 8 7P*4i!1 3f&>(P8 JCk!.
#%+,
) &S!.X+,(D8 3J!1>*4i9+,k! U7+,8 (Y9WV)39aJ+!.K R %!.cB 7P+)3
,!.9H> HF&>(P8
JCJ!1
3?
www.jntuworld.com
www.jntuworld.com
,9$
Z !W ) +, EQ!.
) (P>V7) 4X) 90(PE]) aJ+!9& !.D) ( HV7+, 8(K
Q) 90(PI45 H3(( CD!.3+,MQJ!.."04F) 90(PK
& ; /
?!.%!.+, +,( >+,,&
*!D#%K\3K !.
!.f) ( Hd) 453H77KZ !GE((9#%^!. f)(
) 453H76/W78+,+,7JE8 (9) 9a"+!.K
;
c+3!18 ( +,J!,;H) f9&2Y>+!.8(57+, H 8(VY )39a"+!AW+,((5+!.8>(5+,J!.K[Z !
+,(7( CGE((9#%5!1 ) ( H)39E(/W78 +,+,7k08()39a"H+3!1K
, -
2&(85!..!) 7!. !. ) (P>/+1J!9!1 >+!.8()394537 K
-
A "-B ,!3#%G!.A+!.8>(9+,k! G!.AH> H^&(8 HK>PK
nIRIn
U
T H#(-,.PC$'/C&)(+*1.98
T +1H*!..45A9-7)( /B8 45,!
T 8 (P(T!1
AJ!.."-) :
*!.
' (( / 1
www.jntuworld.com
www.jntuworld.com
T: f
>Pd) 83)7Y9I!.
=.4
!
,!13+S3 83+,Y) ( P*4
&H378A+!.8>([3 83+,k_I.!.X9 P34
!.
) 7 (9>/ H+1(P 3.!.K
U
T :+&)K+$/C(65PQ$/,(1*E,V0+J1J1$'J\PC$'/C&)(+*1.98
:+&)K+$/C(65PQ$/,(1*E,VL3$'0+XE23*1M\PC$'/C&)(+*1.98
0 ;7 = ; '
8
B H%9
n 2
Y) &78
n 2
Y+,(7_/BC !$C) _ _ _ ] _ S
_ B*Ce+,
) !Y(7b
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
U
78 BJCJ!.
K
! 8 4 / . 1 /
$0
0+M1$
2,E H%:!.S.& 45S,;'!.H*!^9+,*45,_H#= +,%:!.S>
8*!^9
79<!$#=>/B 7(P G!..!2 H 3'#%3MK R
(1J+:1L30+/23. [!./.& 45B M.4
!.3/9&H!.
K
Q +,.!.[)39& H67 45*!!.D!.AMP /[J!$CS+, 3+!.:9-79<!$#=>A+,>45 %
U
n
3'#%3MH):+, 4,_ BC/(7'_5+,
) ![ 8 BJCk!.
/BCG!3C)
_ _ _ ] _ K
2 ) 4 ; $ & 1 $(+/
www.jntuworld.com
www.jntuworld.com
. & ) # >. 8# . 1
P !1 /.&.4/87.4G!.
G!..!I+,+,8 QB,!$#=
79<!$#=>D08( !.7K Z !2+,
) 8!.FBC] &4!.G!.J!283BCW!.8
=B9 !$C)
7 #, = 7, ,? , ; '
AQ S
.!.
.!.+,(E3
(3 &.!.G0:8 *4F7'&/+,3A
,!13+,6)3)3( CK69#%,& _>!.3I#%3
7) H+1 0+I7 0:7(H+3!1*4!.
?
AO8>(P !$CS +,.!.3Q>A3 &GE3
!.A,&( &4F) 8+3!3.!.H!. GE3
!.A !. 0+!.7K
TW,C )39& 7 45*! P*!. !. #%J!. 453.!. B*Cg!1 e)3+,77K
+,3) 3,#%Mg
='!.3+,U3e k!. 3
=H> 8
*!) H37)+!. &A9-
=J!
>80+!.834F) +, 77K
T: ,Ci+,45 7S!1 Y *!1( CUC
+S .!.83Y9WU !.H3.!. &X,&(P)
!)3+,77K N .!.-!1 %0+,8A%!.
&(8,_!. 'C/,;H)(+, !1( C/+,+1H*!..!.AG!.I!. 6:+, 4 #% !./7)+!!.D!.P
=HK
T e+,
B .!. 9Y7 45!=E3
!. +,8 3!=&(8 !. +,8 3!=!.3 )39&]!.*45B( +,.!.3]0
=.4
!+!.K
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
n A
,!.+,633O83/B+,8 72!.7AA3 &^0
,&( &4S) 8+3!3_9! .! !. E+!.7K ,C/) 9&7 45*!
*!1=!. F#%J!.F4 !1UB*C=!.X)3+,77K 7X
,!13+,A+,94 7Y*C
+S !1 8 X9>f !.H3.!. &c '&()
*!
) +, 7K
/ () & 5 ( " & " ( /
( )
.T2 ,O<(+*-,23J+$'/$'JZ&!$'01*+23*1M[5E:+L K .981$;<:-,.9(1&!$'/ RS&)0+*1M+$/ RS01*1J\PC$'/ 5E(+/&!$/
=
www.jntuworld.com
www.jntuworld.com
. J1$'&!(1*-,.9/0+.9$, 1:10+*1.92 5E230+K1L3$ <(1//
$'L301.92 (1* K1$'. $$'* PQ/(1<$,, PC$'/.:1/K+01.92 (1*-,
J+2 ,.9:+/K4(1/C<(+*65 :-,$01*+JZK+:-,23*+$,,%PQ$/ 5E(+/&!01*+<$'=
.N2 ,V(+K$<.923X $;01*1J4:1*+01&!K123M+:1(+:-,L J1$95 23*1$'J1=
.NJ12 , PCL30 E,V.9/
$'*1J-,=
.T2 ,O0Z*+01.9:+/01LK PC/
(1J+:1<.T(657.98+$?PC/
(1<$ , ,=
.T2 ,S,:-P+PC(1/
.9$'JZK 40+:1.9(+&)0+.923(1*+=
., '; .;
TA3
=C/)) `!.8 !.P5!.S8!.
!1I!.A)39a"H+3!+,!.(9+3!1 & !169-W79"!$#%3) aJ+!.K
T
9<!$#=> 39a"H+3! n !.( (
n
*!1>P 2= T"(&H37=9[!.FJ!1 !18 29I,&( &4
!1 0+!.2)39& H2
M,CS*&>!..45K
TQ+1+,)*![#%5E3k!3H+1
/BC R (
9<!$#=> n 8 +,(
39#%_
U
A#B A
##! @OB@
IB#
Y
# !@
@#
#
B
O %#A
UO V
.
[';H>
)(,_
-
79<!$#=>A)39a"H+3!
>.4H#%8(G#%*![!.S7WW7)(.CD#% !./9&(()39a"H+3![&(87K
T R !.HJ!
.45:
=.CD#%*![!.S7W P7) (P CDE+,86/
,!.3P+1Q7)+, 0P+:!.S8)+1
4FB ,!1
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
+1
)!.5E#= +,G!.,CS>A7)7B(K
T^ ) H(^+, 8 )) `!fJ!. E.!.83Y78+1eS#=> P*4 ( 45!.J_D!. 7( k_G&>B (Pb7+,(J_S 4 !1>(
03
.!.J_ (94DE3
.!.5!1S) 7!/9&`&,# 9!1 +183!7 !18 .!.K
T P8!.
!1i78) ) !F+,>
) &U
=.4
!F7 45*!F!. )39453 iO8 ( !3CV!.3d
) 9&]!.
>+,+,)!. +,-
,!.+,6BCG!1 *45*4!.H>
K
$ $ ' 5 1 ( 6 $ " ( ) /
.
? P+1.!.J_!.3J_ +1
)>7J_ >/) 9477
6
< @m Z78 ))`!E[79"!$#%3) 9a"+!
45:3(20(';HB P( !$CD!.S78) ) !!1 :3(H
www.jntuworld.com
www.jntuworld.com
. /
!1d,;'!.3+!.YE3
!. &
!!.(!..!
*!1>Pc!.i45 H34
9!..!.5E!.I&38Y !1 0+! ,!.7K
. / 6
!1]
.45
*!78)) !EI) )8 (.!.P*4F!1
,!.+,D7)(.CX9!. @m Z5>
J!14D!1 .!.W,;'!13+!./B*CD!. .45!.7K
. (
+!.8(
,!.+,6)37H*!..!.P5E[O_5J_
)_ > 77J_
!1 :)3947Q
77K
;
!3C)+,>(P( C_!.A
!.[^!1 >
J!. !1K
T L !1 <+,((H /(+L3$, P +,(8 S "!$#%S) aJ+!^
>.4H _: "!$#%S ,&()
=H*!!.H>
_ 79<!$#=>S3+, !.+!.J_ >
+18J!.
7K
. J1$95 23*1$,\PQ01*+$L1L30 +(+:1. ,5E/
(1& $ W12 ,.923*+M &!$<810+*12 ,&, R\M1/
0-PQ8123<01L (+K$<. , R\01*+J L32 *
0+M1$,Z.9(PC/
( $'<.J10+.90 + :1$'/2 $ ,
J101.0Z.9(4K1$;J+2 ,PQL30 +$'J401.NJ12 5 5E$'/
$*+.TL3$'XE$'L ,O(65 0+K-,.9/
01<.923(+*1=
; 23*E,.90+L3LS.81$A, ,.9$'&J1$95 23*1$, *1$ &!$'<8+01*12 ,&, R M+/0EPC812 <0+L%(1K '$ <. , R)01*+J L32 *
0+M1$,Z8+01*+J1L3$, 0+/<8123X 23*1M
5E:+*1<.923(1*E,NJ+$ 5 23*+$ ,O<(+&PQ(-,2 .923(1*401*+JZJ+$'<(+&PQ(-,23.23(1*\,.9/
:1<.9:1/
$ , 5E(+/NJ+2 ,PQL30 +2 *1M4&):+L3.92 PQL3$;L3$'XE$'L ,V([5701K-,.9/0+<.92 (1*1=
D#% (S7)(.C%I+,((H]) (K l !.])>( 3G453) +,(B*aJ+!.J_#%+,F3G!$C) H9Q(P C8*!.78+,F (
>/B :+, !17K
R ) (7!$C)+,(( CS+,!./W8
B[9453) +,(Ba"+!.Q) 7 !1 //W) !.+,8(45
,!.+,>(9(.C8!.K
R
,!13+7#=XF4>)+,>(5Ba"+!AW(P>B(HS#% !1/!.=
,!13+2!$C),_ !.
78
=
CX(P,&( _Q /!1
J!.+1
=
<78+,/>Q(69-+, ,_ 78BJCJ!1
_5 & K
www.jntuworld.com
www.jntuworld.com
; / $"
) 7!.[&(89&!.P
=/F) H3
!.8) ) ](9#%!.3 ([!.]B/ ,EK n 3774
!. 7(/+18(/B (MG!.S/77+,.!./ P+1.!.H!./ H) +!Q9!.+,B (PJ!..!.+,*45E
4^!./3 &P+1
&7K
; $ / $"
) 7!.S
8( !.)(=&(8D!.945,!. _9&!1
K n *& 45+,fW &H 45 +,U
4
&(86
.C/BA(P M9G!.S/ +,.!.3K
; $ / / $"
)37H*!.S)+1H*!]+,
) ('!.,_6#= d(
!.S9)39453 S>d7#=i^!13 !.
B ,!3#%/J!..!.H6 //3G&(8AQ77+,.!.G#% !./+,/J!..!.K
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com
)
8 7HI) !.Q!.X4) +,(Ba"+!7)(.C4Y])!WP/!.
c3P(( 9#%S!.S&,# !.
!.3G0H!.A
,!.+,K
) $
87I)P*!.Q!.YW453) +,(B*aJ+!7)(.C4X!.V>V3((PG9#%!./&,# !.
&(85E!.A
,!13+,K
) ) 6 ( (
A87:) !.5!1S4>)+,>(9B*aJ+!7)(.C4/)*!2!1
((
9#%G!.D&,# !1 ,;'!(,&(9-03
.!.K
) ) 6 (
f87W)!.2!1i/453) +,([Ba"+!S P7) (P C4 >dP +,.!.Dd ((
9#%G!.D&,# !1 B M#=9!.A,;'!(P,&(99P +,.!.37K
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
;7 < +, ,''
!#"$"%&'"#( )* ,+
-.
/ 01#23455678+9." 9"% )
+
"$
:.;<
=)>;!?9"@
" $ 9 1 . / $ 9 1
www.jntuworld.com
www.jntuworld.com
!
: # !
" +" "$9
;"
"- . " - "$2- #39
)19- "
29<2 - 3 )1#6
+ (# 2- 429: # 67-+ " #+ +#+3%# <
#3 +
"$< #+3 )1 ,
-3%
2#"$" ) #679 " 01#2 "#( ) 7 !#" "4.: ;<
46/ <4=67
+ #)*
#+ + .
#"
)19
"
2!#"$"
www.jntuworld.com
www.jntuworld.com
" $ $ / A $ $
+,(
!.M9 ( ^ *!1*!1
n n
] +1H7 (,;HB( !3C 2 45 +1H7 .!.83 !$C
N L
+, !1+!.8 ( 7M 6
;H) +,
R N
g>f!.g7
=g9!. g+, !.+,(I P
=H 7P!..!X 79"!$#%3g)39aJ+!V
45S
8J!c+17D#%
!.(34FW) +1H75E3
,#%3M6!.S+,3H !1AW)3+!.+,()3+,76P
=)(
!..!. .
' ; 7,
A
J!
) !1>!E+!.[G!.(P4SW "!$#%A)3+,75E3
,#%M!.G!.7)+, E+ H -9) aJ+!Q!1 !1!1>(
7+,>(PA9!. 79<!3#%3A)) (P+, !1 K
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
www.jntuworld.com
8 P*4V8*!.3 !12%87 #%*!6!.%
7S+,J!$_
;HP
= 7D!.D0.!.83S ,!_:]+,+1H(3.!.
!.P
=2!.S
3M'!$_#% P(A,&H()
!+,*!13+!.35#=>!!1S
=.;H
A)390 !.B (P !$CK
www.jntuworld.com
www.jntuworld.com
T 45/!.
3c(
J!P
=)77B(/!1Y+,((+,.!.,_XJC +,3 74fJ!1>M9(P ^,;H) H+3!1 1! W
+1((45*45K
T R ((7!. H7IE+3!15!.H G!.S,453 2!.
+, /
=8J!B
=.4/+,*!1 88 ( CK
,'' #7,? 8 7 = <
7+, 8(K
# 9 $ 5
!./Q&( 45+,8 J!1
,&H()
!Q,"0`!$_ !Q
4!QB7>B(!1P +,3)3.!.,# +,
+1P>(
) 8+3!!.F!.
9&H3(( 4V9^F,;'!.TP45 H3.!.V[!.3."0P++,!.(JCJ!.
K>G `!9^+,>45#%8(V3HO 83
+13.!.
=4 !. ,&H()
! +,!.3+!. _dE8 *4 .45 +C9_g87J_b+, !. 0+,.!. .4H +,k_g7 +,.!.
+1!.3+!.3 0:!. E+,*4!.AkCJ!.H
A_ 9!.7K
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
,'' . ; =
L 454FW
=.!.83) +1H76 0:7
)(H!. /
.45*4F
.!.83A)3+,7 K
T ^ 45> 7.!.P#= !.
S
!18 ])3+,7!3C)+,>(P( C
.&F/ 45%('&(9I) +,*!D,;H) H3+,F= '&()4
79"!$#%3
>/W 4/(,&(9-,;Hk!.4S)3+,7Q+,(P(.!.3(7!. .! B(A)3H +!.B(A)( 4F /,;H+,8!./9!1 ) +, 7K
T6%7 !=9F+,((.!.>(Q+1(P8 W#=((6,E
='!. J_) +1H7]8!.
=.!.PY!.(J_!.>P )37 H( _)( 4
='!.3+,J_ !1 0+!!1
) (.!.HJ_ >G#%3M70(9# !.
) (P !17K
T(P4SW
.!.83`4 7.!. Q) +1H75E[W7)+, E+I)39a"+!5453(( CSWJ!. 4!$E #%3G!.7M9K
; + , ; 7 'B
www.jntuworld.com
www.jntuworld.com
) `0
=+,,_ 3B 8J!.7 !.S+, 4'_5/JCJ!1
3(PB (P !$CK
T /,453G!.#% P+1W!. H7/37M9+1FB/(
.!.SB,E+,J!.38+!.SB,4P +,>S.&
=.!.P+23
E+, !1
!. ) +1H75!.(P4K
.; ,? , , ,
T5V ,&()
=H*!A 45 7.!. W
Y,;H)S459& W !1W>B( !$CF!.f+,&H 45VYX+,+1H)*!.B(V3+, !.+!.83VY
=P
8
8
B H[9- !..!. K
T [,;H
)(,_ `4 7.!.G!. ! QB 8( ![0 &45 H3.!.-9 >+,*!13(*J#% !.+, 6
=.C/B B(!./+,*& 45
>/O 8.!.AB7(P >+, !1+!.8 IE[W,# :>))(+,.!./G!$#%S!1 A)39!.9!$C) 3(H> A !.H3.!.7K
T R 7M9(( 79<!$#=>U`4 7.!.iB8(*4 !.G0P3J!F3W>))(+,.!.i
.CdO8 FE8 Q0 &f) !1!3C)Y(7
B ,E3+1&`4P*4F/>/O 8.!.AB7(P K
www.jntuworld.com
-- Converted from Word to PDF for free by Fast PDF -- www.fastpdf.com --
www.jntuworld.com
www.jntuworld.com