CHAPTER 1

The software is a key element in the evolution of systems and computer-based,

and one of the most important technologies worldwide products. In the last 50
years, the software has gone from being the solution of a problem and
specialized analysis tool information to an industry in itself. However, there are
still problems to develop high quality software on time and within budget. The
software-programs, data and descriptively information addresses a wide range
of technology and fields of application. Legacy software continues to pose
special challenges to those who must maintain it. The web-based systems and
applications have evolved from simple information content sets to
sophisticated systems with complex functionality and multimedia content.
Although these web apps have unique characteristics and requirements, they
are software. It includes software engineering processes, methods and tools to
develop timely and quality complex computer-based systems. The software
process incorporates five structural activities: communication, planning,
modeling, construction and deployment that are applicable to all software
projects. The practice of software engineering is an activity to solve problems,
which follows a set of fundamental principles. Many myths still make software
managers and workers mistake, even if has increased our collective knowledge
of software and technologies required to produce it. As the reader to learn more
about software engineering, you will begin to understand why they should be
rebutted these myths whenever they arise.

CHAPTER 2
A general model of process engineering software includes a set of structural
activities and umbrella, actions and work tasks. Each of the models can be
described by a process different from the process flow: description of how they
are organized chronologically sequential and structural activities, actions and
tasks. Process patterns can be used to solve the common problems that arise
as part of the software process. Prescriptive process models have been applied
for many years in an effort to bring order and structure to software
development. Each of these models suggests a somewhat different process
flow, but they all perform the same set of general structural activities:
communication, planning, modeling, construction and development. Sequential
process models, such as the waterfall and V, are the oldest of software
paradigms. Suggest a linear process flow is often not consistent with modern
realities (changing, evolving systems, tight deadlines, etc.) the software world.
However, they have application in situations where the requirements are well
defined and stable. Incremental process models are iterative in nature and
occur very quickly functional software versions. Evolutionary process models
recognize the iterative and incremental nature of most software engineering
projects and are designed to accept the changes. Evolutionary, such as the

prototyping and spiral models generate fast incremental work products (or
functional versions of the software). These models are adopted to be applied
throughout all activities of software engineering, from concept development to
system maintenance long term. The concurrent process model allows a
software team representing the iterative and concurrent elements of any
process model. Specialized models include based on components, which
emphasizes reuse and assembly of components; model is a formal methods
based on mathematics to develop and verify software approach; and aspectoriented model implies global concerns that affect the entire system
architecture. The unified process is a process designed as a framework for
software methods and tools UML, and is "driven use case focused on
architecture, and is iterative and incremental". They have been proposed
personnel and equipment to the software process models. Both emphasize
measurement, planning and self-direction as the key ingredients for a
successful software process.

CHAPTER 3
In a modern economy, market conditions change rapidly, customers and end
users need to evolve and new competitive threats arise without warning.
Professionals should focus on software engineering in order to enable them to
define maneuverable stay agile, adaptive and lean processes that meet the
needs of modern business. An agile philosophy for software engineering
emphasizes four key aspects: the importance of teams with own organization
have control over their work, communication and collaboration among team
members and between professionals and their clients the recognition that
change is an opportunity and insistence on rapid delivery of software that
meets the consumer. Agile process models have been designed to address
each of these aspects. Extreme programming (XP) is the process more agile
use. Organized with four structural activities: planning, design, coding and
testing, XP suggests a number of innovative and powerful techniques that allow
an agile team generate frequent deliveries of software that has features and
functionality that have been described and classified according to their priority
participants. Other agile process models also insist on human collaboration and
the organization of the team, but define their structural activities and select
different points of importance. For example, the DAS uses an iterative process
that includes an adaptive cycle planning, relatively rigorous methods for
gathering requirements and an iterative development cycle that incorporates
consumer groups and formal technical reviews as feedback mechanisms in real
time. Scrum emphasizes the use of a set of software patterns that have proven
effective for projects with tight deadlines, changing requirements or used in
critical business. Every pattern defines a set of process development tasks and
allows the Scrum team build a process that meets the needs of the project. The
Dynamic Systems Development Method (MDSD) highlights the use of

programming time box and suggests that each increase in software only
enough work to facilitate the transition to increase following is required. Crystal
is a family of agile process models that are tailored to the specific
characteristics of the project. Driven development features (DIC) is more
"formal" than agile other methods, but retains its agility by focusing the project
team on the development of features, valuable functions for the client that can
be implemented in two weeks or less. The lean software development (DES)
has adapted the principles of lean manufacturing to the world of software
engineering. Agile Modeling (MA) suggests that modeling is essential for all
systems, but that complexity, type and size of the model should fit the software
to be processed. Agile Unified Process (AUP) adopts a "serial in big" philosophy
and "iterative in the small" for the development of software

CHAPTER 4
The practice of software engineering includes principles, concepts, methods
and tools that software engineers apply throughout the development process.
All software engineering project is different. However, there is a set of general
principles that apply to the process as a whole and to each structural activity,
no matter what the project or product. There is a set of fundamental principles
that help in the implementation of a process of significant software and
implementation of effective methods of software engineering. At the process
level, the fundamental principles set out a philosophical foundation that guides
the team progresses through software when the software process. At the level
of practice, the fundamental principles set out a set of values and rules that
guide the analysis of the design problem and its solution, implementing it and
when tested to finally deploy the software community user. Communication
principles focus on the need to reduce noise and improve the bandwidth during
the conversation between the developer and the customer. Both sides should
work together to achieve better communication. Planning principles set
guidelines for developing the best map towards a system process or finished
product. The plan can be designed only for increased software, or for the entire
project. Without this amount, you must define what will be done, who will do it
and when the work will be completed. The modeling includes both analysis and
design, and describes increasingly detailed representations software. The goal
of the models is to affirm the understanding of the work to be done and give
technical guidance to implement the software. Modeling principles give
substance to the methods and notation are used to create software
representations. The construction includes a coding and testing cycle in which
certain component source code is generated and is tested. The coding
principles define the general actions that must take place before the code is
written, while typing and once finished. Although there are many principles for

testing, only one prevails: the proof is the process that leads to a program in
order to find an error. The deployment occurs when the client software has
increased, and includes delivery, support and feedback. The key principles for
delivery consider the management of customer expectations and provide
appropriate support information about the software. Support demand advance
preparation. The feedback allows the customer to suggest changes that have
business value and to provide developer information for the next iterative cycle
of software engineering.

CHAPTER 5
The tasks of requirements engineering are made to establish a solid foundation
for the design and construction. Requirements engineering occurs during
communication activities and modeling have been defined for the overall
process of software. The software team members perform seven functions
requirements engineering: design, investigation, preparation, negotiation,
specification, validation and management. In the conception of the project, the
participants set out the basic requirements of the problem, define the general
constraints of the project, as well as the main features and functions that must
submit the system to meet its objectives. This information enhances and
expands during the inquiry, activity in which the requirements are collected
and uses that facilitate meetings, DFC and development of usage scenarios.
The development further extends the requirements in a model based on a
collection of scenarios, classes and behavior and flow-oriented elements. The
model refers to patterns analysis: solutions to problems analysis has been
observed that are recurrent in various applications. As the requirements are
identified and their model is created, the computer software and other
participants negotiate the priority, availability and relative cost of each
requirement. In addition, each requirement and its model as a whole compared
with customer needs to ensure that it will build the right system is validated.

CHAPTER 6
The aim of modeling requirements is to create several representations to
describe what the customer needs, establish a basis for generating a software
design and define a set of requirements that can be validated once built the
software. The requirements model crosses the gap between the system
representation describing the system as a whole and business functionality and
design software that describes the architecture of the software application, the
user interface and the component structure. Models based on the scenario
illustrated software requirements from the point of view of the user. For
-description use, made with a narrative or a format of an interaction between
an actor and software- is the main element modeling. The use case is obtained
during the investigation of the requirements and defines the key stages of a

specific function or interaction. The degree of formality of the use case and its
level of detail varies, but the end result gives the necessary all other activities
of modeling inputs. Scenarios can also be described using an activity diagram
-Representation like a flowchart illustrating the flow of processing in a scenario
specific- graph. Channel diagrams illustrate how the flow of processing different
actors or classes is assigned. Data modeling is used to describe the information
space will be built or manipulated by the software. Data modeling begins with
the representation of data objects composite -information must be understood
by the software-. the attributes of each data object are identified and
relationships between these objects are described. Class-based modeling uses
information from modeling elements based on the scenario and data, to
identify analysis classes. a grammatical analysis is used to obtain candidates
for class attributes and operations, from text-based narratives. They defined
criteria to define a class. To determine the relationship between classes, classresponsibility-collaborator index cards are used. In addition, several elements
of the UML notation applied to define hierarchies, relationships, associations,
aggregations and dependencies between classes. analysis packages are used
to classify and group classes, so that they are more manageable in large
systems